Jamey Sharp

Hmm. I'm not quite sure how that should work. For my use cases so far, I've only wanted output from Corrode if there's a reasonable chance that `rustc` will give...

I've been doing my tests with `make -k`, to make it compile as many different source files as possible despite the previous commands "failing" to produce the expected `.o` files....

I've committed a script that does this almost correctly ([`scripts/corrode-cc`](https://github.com/jameysharp/corrode/blob/master/scripts/corrode-cc)). You can use it in place of `gcc`. It will try to run Corrode plus rustc and massage the result...

Yeah, since Rust doesn't support C-style unions quite yet, Corrode doesn't either. Thanks @dikaiosune for the pointer to the work in progress there! I'm going to repurpose this issue as...

I don't actually want to close this issue until Corrode has support for unions. :smile:

As a first step, Corrode now translates union types to non-constructable and non-copyable enums. This supports any code that only passes around pointers to union types, but doesn't try to...

I'm at RustConf today and @joshtriplett tells me that support for C-style unions has landed on Rust nightly. Hooray! Anyone want to try making Corrode use the new union syntax?

I think the key trick is to ensure that the Rust representation of complex numbers is ABI-compatible with the native C toolchain's representation when used through FFI. (Which strikes me...

This wouldn't be the first portability problem in Corrode-generated code (see the translation for `main` for instance, which relies on POSIX), so getting an implementation that generates code which is...

That's a sound plan! I initially wondered why `IsComplex` would wrap an arbitrary `CType` instead of just an `Int` indicating the floating point bit width. Reading your link on the...