Rust-lang

This is actually not a problem, lifetimes are erased at runtime so a function cannot change its behaviour depending on them. So even if at the type level the function might indirectly name a lifetime, without values (i.e. inputs or outputs) directly tied

Morgane55440: so it is unclear why a new optics_type! compiler macro should be necessary. Here optics_type! is just a randomly picked name for combined view types and pattern types.

r-a can expand #doc(hidden) macros just fine, but if they arms are private they won't be resolved. It could be taught to expand them (since the macro itself is resolved) but in this propsal this changes behavior by ignoring later non-private arms. It coul

Facing same issue. This prerelease and stable version conflict is in weird state. Cargo treats prerelease as incompatible (like multiple major versions), but does not allow you to have both pre-release and stable version (from transitive deps) even though

Empowering everyone to build reliable and efficient software.

daniel-pfeiffer: Before 1.97.1 was announced I got nervous sniffing for it on bug reports. So I did rustup update and cancelled it when it was still downloading 1.97.0. Surprise: the safety conscious language Rust had very unatomically shot itself in the

Empowering everyone to build reliable and efficient software.

TL;DR We are enabling the next iteration of the borrow checker (coined Polonius Alpha) on nightly in preparation for stabilization in the next few months. Whaaaaaat? Yes! You heard it right! The next iteration of the Rust borrow checker is coming! Rust's

Empowering everyone to build reliable and efficient software.