Michael Schmidt

#4202 implemented this. You can see similar behavior in the tests of that PR in the `Foo#weird` property. Previously, WBG always emitted fields to type properties, but that was plain...

> I'm concerned that this is exactly whats happening. Yeah, the fact that we had a test for this is a bad omen. So a third opinion would be nice....

> But my concern is in practice, I don't want to break maybe a whole ecosystem out there without even a warning. In general, we should probably add docs clarifying...

> These kind of docs are in great need for improvement indeed, any help here would be appreciated! Then I'll try to write down TypeScript guarantees somewhere the next few...

> The concern is more general, I'm more concerned with finding the time to review PRs and fixing issues then making beta releases and collecting feedback. Wouldn't a beta release...

> I sent you a private Email about further discussing stuff like that, did you get it? Straight to spam. Thanks gmail 😆

Merge conflicts resolved. Thanks for merging this!

Okay, after some more local testing, I could not find a way to remove the `multivalue` and `reference-types` features. Even setting `RUSTFLAGS` to `-C target-feature=-multivalue` does nothing. And I know...

Okay, https://github.com/rust-lang/rust/issues/109807 and https://github.com/rust-lang/rust/pull/128511 have a similar issue, and the solution is that std needs to re-built to disable default features. However, this is (AFAIK) only possible with a nightly...

> `camelify_by_default` sounds a bit too funny to me. How about `default_rename_camel_case`? Kinda terrible as well, let me know if you have any better ideas. [This comment](https://github.com/rustwasm/wasm-bindgen/issues/1818#issuecomment-543216831) suggests `auto_camel_case`, which...