ron
ron copied to clipboard
ron-rs
Rusty Object Notation
Consider the following types: ```rust #[derive(Debug, PartialEq, Eq, Serialize, Deserialize)] #[serde(untagged)] enum MyValue { Int(i64), String(String), Enum(Enum), List(Vec), } #[derive(Debug, PartialEq, Eq, Serialize, Deserialize)] enum Enum { First(String), Second(i64), }...
Followup to #393 Adds explicit variants in `ron::Error` for `serde` errors from [`serde::de::Error`](https://docs.rs/serde/latest/serde/de/trait.Error.html) (`serde::ser::Error` only has the `Error::custom` method). * [ ] I've included my change in `CHANGELOG.md`
> Oh, I see! The MSRV on 0.7 is still 1.36 anyways. > > How will we handle such breakage in the future? _Originally posted by @MomoLangenstein in https://github.com/ron-rs/ron/issues/383#issuecomment-1159623984_
not 100% sure but i think named_field should allow whitespace after the colon and before the value in the EBNF
See https://github.com/epgts/rontest/commit/b1fde4463ba9e1c64efd106fa5786c4d316d1882#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542 for simple reproduction recipe. Works reliably on amd64, crashes reliably on aarcy64. Configuration: - Ubuntu 22.04 - cargo --version --verbose - cargo 1.57.0 - release: 1.57.0 - host:...
Take a look at `serde_json::from_value` and `serde_json::to_value` - these functions would exactly mirror that. RON has the unique opportunity to be an "impartial" serialization format for storing structured data internally...
Is there a formatter or linter for ron available for vscode? The vscode-ron extension seems to do syntax highlighting but not formatting.
[Tree-sitter](https://github.com/tree-sitter/tree-sitter) is a parsing library that can be used with editors such as neovim or [helix(by default)](https://github.com/helix-editor/helix). Would it be possible to add support for it?
Are there Ron parsers for making automated edits to Ron files? As far as I understand, whitespace-preserving parsing should be based on something other that Serde. Does Ron have some...
RON solves a number of pain points with JSON (e.g. it actually supports enums, actually supports types), and unlike most better-than-JSON attempts it's also managed to get some traction -...
