Jamey Sharp

Thanks for trying Corrode! This is because Rust doesn't support defining varargs functions. I haven't been able to think of any workable translation for this yet. :slightly_frowning_face:

Yes, I implemented a cheesy hack instead of properly handling array types. The current hack gets arrays translated correctly in function arguments, but gets them wrong everywhere else. Thank you...

I'd like to get patches adding support for arrays that is correct _except_ for not having VLA support at first. Variable length arrays have enough challenging quirks that I think...

I've merged #38, and I fixed #18 earlier, so I think the path is clear to push forward on this now!

I love this discussion, please keep it up! :smile: I'd just like to point out one thing: I don't want to fix the `unused_mut` warnings, because it should always be...

I dropped this, and I apologize! I did add some randomized property testing for the `goto` work I merged recently, so there are some tests on `master` now, but still,...

True! I wasn't very happy with the amount of OS-specific stuff I did in translating `main`, but it was a start. (Handling the POSIX-permitted third argument, for the environment variables,...

Hmm, yes, whoops. So when Emscripten translates irreducible control flow like this, since it's targeting JavaScript, nobody cares whether there could be a code path where a variable is used...

Absolutely true! As it happens, I've already been trying to work out how to fix this, though I got distracted trying to make the generated code more readable (see #6)....

You're right, detecting undefined behavior related to sequence points is hard and Corrode shouldn't do it. But we indeed can generate more readable code by relying on the definition of...