> > Does it pass the SWIG testsuite? > No. I have only done some initial works. The other parts, for example the director feature are not modified yet.
I think one of the biggest advantages is that it can shorten the wrapper code. When C++ inheritance hierarchy is large and deep, the wrapper code could be easily bloated, and as a result compiling them needs more memory and time, and the final executable size will be larger than using embedded types, as it contains more code. I have little knowledge about the go compiler, so please correct me if I'm wrong. 在 2016年10月4日星期二 UTC+8下午10:22:34，Ian Lance Taylor写道： > > On Tue, Oct 4, 2016 at 7:07 AM, Shengqiu Li <[email protected] > <javascript:>> wrote: > > I have made a preliminary demo using the anonymous field feature > > github.com/dontpanic92/swig > > This is written in a way that I find hard to understand--I can't > easily see the differences between the old code and the new. > > Does it pass the SWIG testsuite? > > Perhaps you are right that SWIG could have implemented using Go > embedded types. Ultimately SWIG deals with interface types, as I > think it must, and perhaps that lets it hide the differences between > the languages. > > Is there any advantage to having SWIG generate embedded types? > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
