David Tolnay

Can you provide some runnable code that reproduces this?

Thanks! Indeed this was a bug. I've published a fix in serde_yaml 0.9.6.

This looks like a bug. I don't necessarily know how to fix it but I would accept a PR!

That code doesn't seem like it would be the problem, or else lines would always be wrong when deserializing a map, not just when using flatten.

I am interested for a static assertion that some trait bound currently in scope is statically impossible. Example: ```rust #![feature(trivial_bounds)] macro_rules! void { ($($tt:tt)*) => { unreachable!() // FIXME };...

That looks fine to me. Is it something that would be a good fit for this crate?

We would love to pick this up in https://github.com/hibari/hibari-brick-rs/issues/8. @DaGenix could you take a look?

https://github.com/rust-lang/rust-analyzer/issues/12973#issuecomment-1208162732 sounds the most promising to me. Here are Cargo's build script environment variables: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-build-scripts. The criteria for selecting one for this purpose are: 1. It has to be set...

This has been fixed by https://github.com/rust-lang/rust-analyzer/pull/13010.

I would love for this to happen. :) I would accept a PR to add both both sync and unsync OnceCell and Lazy as unstable. We tend to get more...