Bart Janssens

I just tried replacing that error with a warning, but unfortunately none of the methods defined in the C++ module work after that, so I'll investigate some more on how...

It seems to work now on master, using the `types.jl` test at least. A problem with smart pointer types required a specific fix, so there may be other edge cases...

No, and unlike the arrays types like `Set` are implemented completely in Julia, so the easiest way is to manipulate the set on the Julia side, maybe converting it to...

I just hit the same thing with `pthread` on freeBSD, which is also an opaque pointer. I found no way around it, the type mapping needs to have some kind...

OK, this was a bug, that should be fixed in the latest libcxxwrap-julia master. You should also be able to work around it by adding the following line, until we...

That is indeed an issue. My proposed solution for that would be to build binaries on AppVeyor using MSVC. This is already done for libcxxwrap, but when combining several CxxWrap-based...

Yes, basically it would be nice for users to have an option to say "I want MSVC for binaries" (on a specific environment), and then it would load the MSVC...

Weird, I can't reproduce this on my mac (clean package dir, 0.6 RC3 binaries from the site). I am using cmake 3.8, but I doubt that's the problem. @SylvainCorlay any...

@togo59 Thanks, this should be fixed in master now by not loading the startup file.

Where exactly in your code does this happen? It definitely looks like a CxxWrap bug, the JuliaComplex type should never "escape" into your code but be converted to std::complex automatically,...