Juniper Tyree

Thank you for the report @nmsv! `serde` unfortunately changed how adjacently tagged enums work in a non-breaking version update, which `ron` can do very little about. Whereas before the correct...

@nmsv On the main branch, and in the soon-coming v0.9 version, there is a `ron::value::RawValue` type, which captures some valid ron literally. Does this fit your needs? If not, what...

@nmsv I’m happy to hear that this is what you needed! We should probably leave this issue open for now to track its fix in some distant future

If you only want to support the `(2023, 9, 17)` syntax, you could define the `DateTuple` type as a private helper and forward the `Serialize` and `Deserialize` impls to it....

I think adding support for doc comments is definitely a neat idea and could help with the question of how to preserve comments across serde - here doc comments would...

I may need some clarification before I'm able to give you a good answer. During serialisation, we always serialise numeric values as-is, and the `ron::ser::PrettyConfig::number_suffixes` flag can be used to...

The ron `Value` currently does not yet support storing struct names, but we are exploring the option. Since ron does not distinguish between structs and enums in its data format,...

I just came across this bug as well and can confirm that @matteopolak's fix works - thank you so much for finding it and saving me lots of debugging time!...

Thank you for investigating as well! If you look at your wasm32 output module with wasm2wat, do you still see the imports? I also agree solving that problem would be...

This issue is getting weirder. I have two different WASM modules that both depend on zstd-sys: - the first one depends on `zstd-rs` and does not experience any issues, as...