I try to use toml as much as possible, because it feels like something the Rust ecosystem has mostly settled on as a default format, and I think most sysadmins have encountered .ini files at some point in their career. However, I'm working on something that uses a highly hierarchical configuration format -- and noticed that this is a weak spot for toml.
I checked through what formats serde supports and found something called "ron", which felt a little verbose, but it's explicit in a way that I like -- or so I thought. Apparently to set something that's an Option in Rust it must be specified as a Some in the ron buffer. That's a little too explicit for me. Or rather, I personally could live with it but I'm certain my non-Rust-programming users would be confused by the syntax.
I loathe yaml with a flaming passion, however it is very hierarchical by it's nature so I might use that. However, before I do: Are there any other formats that are suitable for configuration files that you think are uncontroversial to use both with regards to the Rust community and for non-programmers? .. with serde support, of course.
The user needs to define a "service", which contains one or more "interfaces", which contains one or more "binds" -- all of which can contain some other key/value pairs, and some of the values are required and some are optional.
Is this a proper use of Serde? My knowledge may be outdated, but, last I heard, Serde was meant to serialize a program's state and then deserialize that same state: it was meant to parse input that was generated by itself or another piece of software, not to parse something a user wrote, a consequence of which is that its handling of errors in the input is somewhat an afterthought and not user-friendly. Maybe this has changed in the last few years; I don't know.
(Edit: My opinion on the actual question might be unhelpful, as I like YAML and wouldn't think to use anything else. )
(Edit 2: I guess I might think to use JSON instead if YAML support were too heavyweight for where the program needs to fit.)
This is definitely not correct. Why couldn't you parse something a user wrote? I think you should be using Serde for reading and writing configs, because it's well-supported across the ecosystem, and many popular formats have serde parsers/writers.
At work, we use a YAML file for something that is almost always written by a human and the actual experience is terrible. Serde doesn't provide any way to get the location of something in its source text, and previousproposals have been rejected as out-of-scope, which means if there are any semantic issues with the document you have no way to say "there's an error on this line over here" like rustc does.
For a file that is meant to be written by humans and will be later checked for higher-level consistency (e.g. to make sure there is a particular relationship between different items in the document), not having any way to track where each element of your document comes from is a deal breaker.
Additionally, the error messages you get from #[derive(Deserialize)] when something fails to deserialize are fine for a programmer, but not something you would ever want to show a user. If you want to get nice errors from deserializing it often means writing the Deserialize implementations yourself, which is impractical and goes against a lot of the reasons for using serde in the first place.
But it doesn't need to, does it? It's the parser's job to track source location – it's the only one that knows the low-level format, after all.
Just because serde-yaml doesn't currently do it, it's not impossible. It could implement such functionality if it chose to do so. In fact I have written a Serde format that does just that – it gives out byte-exact, Unicode-aware locations for every parser error.
I think you might have misunderstood me - what I am referring to are semantic errors, not syntactic errors like invalid YAML or missing fields which would cause deserialize() to fail immediately.
For example, imagine you are using a YAML file to describe some sort of DAG (e.g. a data processing pipeline or orchestration tool where services might depend on another having already started) where an input node creates data and a processing node reads data from some input node and does stuff with it. The DAG's edges are denoted using an inputs array on processing nodes.
The second node receives inputs from the non-existent-node node, but no such node was defined
The third node receives input from itself, which creates a loop in the DAG and doesn't make sense
You can write a document type which uses #[derive(serde::Deserialize)] to deserialize from YAML/JSON/whatever, however this will only detect syntactic errors. You would need to do a separate post-processing stage to make sure the overall document is semantically valid (possibly accessing external resources like checking if a file exists) - similar to why rustc has distinct parsing and type checking phases.
You then end up in a sticky situation where, because serde has no mechanism for retrieving the location of an arbitrary element (not just a parsing error), and because proposals have been rejected in both serde_yaml specifically and a more general mechanism in serde proper, it's not possible to get nice rustc-style error messages which provide line numbers and let you attach hints that refer to other sections of the config file.
I'll add that even the handling of these errors by failing immediately provides a suboptimal user experience compared to collecting all the syntactic errors in the file to display at once (like a typical compiler), rather than making the user restart a server or otherwise reload the configuration after fixing each error to see the next error.
I don't mean that Serde should collect errors like that (which I imagine would pessimize it for reading actual serialized program state) but that Serde makes trade-offs that favor reading actual serialized program state over user-written configuration.
(Edit: maybe moderators should split this discussion about Serde out of this topic about configuration file formats.)
However, wouldn't one need to perform such post-processing anyway? No configuration file parsing library can hope to detect arbitrary domain-specific semantic errors, so some manual work is surely required in such cases.
Furthermore, while it is theoretically nice to be able to report such errors with source location, if the configuration has deep semantics, then it likely also provides a means of identifying entities by something more meaningful than line/column. So instead of saying "circle detected at line X character Y", the type-checker could say "entities Foo, Bar and Baz form a cycle which isn't allowed". This would arguably be even better and more human-friendly than spitting out a pair of numbers.
While this is orthogonal to the point being discussed, as a frequent user of command-line tools, I very much disagree with this. For instance, I wish rustc stopped after the first error instead of its current strategy of "you forgot to import this item but it's used in a macro so here's 1 MB of error messages". It's very distracting and overwhelming, and it doesn't add any value, since I can't focus on fixing more than one error at a time anyway.