gura VS rust-playground

If one is looking for an alternative config format, the best designed I've seen is https://github.com/gura-conf/gura

I really like the Gura format (https://github.com/gura-conf/gura). Seems to combine the best of yaml, json, and toml for the use case of human created configuration files.

If we're on the topic of config languages, I'd like to plug Gura (https://github.com/gura-conf/gura). It's not too well-known, but it probably has the best design I've seen, and seems to have a good coverage of languages with an available library.

The first version of Serde Gura is now available! Gura is a simple and readable configuration language that will be familiar to any YAML and TOML user. Its essence lies in simplicity and was introduced in detail in this post on this subreddit.

Hi! I've just published a Gura parser written in pure Rust. (Repository link below!) Gura aims to offer a much simpler and more readable alternative to TOML and YAML. If you are familiar with the latter language, learning Gura is easy and intuitive.

Cool! There was a mistake and a very important section in README was deleted. We have added a Rationale section where we compare Gura with other languages, as explained there, Gura is not aimed to replace JSON as it's the faster configuration file in the world! But maybe can be able to take advantage of Gura's other benefits :D

Gura is a new configuration language readable as YAML, simple as TOML that supports variables, importing, and has standardized errors (official site | official repo).

If you have an object that's !Unpin, then Miri will not apply uniqueness rules to anything containing it [0], including boxes and &mut references. (In the example code, replacing the PhantomPinned with a () will make Miri complain again.) This is considered a temporary (if long-lived) measure to allow async executors to manipulate pinned futures without invalidating all their references and whatnot. Thus, it might be seen as undetected UB, in lieu of a permanent solution.

[0] https://play.rust-lang.org/?version=stable&mode=debug&editio...

That would be true if you used `Vec::clear` too, it doesn't allocate a new vector. My point was that you still end up running Drop implementations with RepeatedField, just not all at once. See https://play.rust-lang.org/?version=stable&mode=debug&editio...

That's a valid Unix path, but rust's quoting does nothing to stop it: https://play.rust-lang.org/?version=stable&mode=debug&editio...

Self-referential structs work fine in Rust and always have.

https://play.rust-lang.org/?version=stable&mode=debug&editio...

The compiler will correctly prevent you from moving the value.

The other way to have a struct that starts out as non-self-referential and then becomes self-referential can be achieved with `unsafe` and `Pin::new_unchecked`, which is how `async {}` is handled.

In rust as currently stands: https://play.rust-lang.org/?version=stable&mode=debug&editio...

On the other hand, both this wrapper and yours are counterproductive if the element size is dynamic (e.g. perhaps you're dealing with some nonsense like:)

    struct ITableColumn {

Overflow checks turn into two's compliments' wrapping, but that's only considered acceptable because bounds checks are not turned off.

https://play.rust-lang.org/?version=stable&mode=release&edit...

I have no idea what you're talking about, but it sounds unnecessarily complicated and why I don't use Rust for any serious work.

This demonstrates the ABA problem in safe Rust: https://play.rust-lang.org/?version=stable&mode=debug&editio...

Substitute the sleep with a combination of doing computation/work and the OS thread scheduler, and you can see how the bug surfaces.

You can also try Rust online using the Rust playground: https://play.rust-lang.org/

(Click ... beside build to get assembly) https://play.rust-lang.org/?version=stable&mode=release&edit...

Unfortunately the go playground doesn't seem to support emitting assembly?