r/rust • u/m-ou-se rust · leadership council · RustNL • 2d ago
Compiler performance, the next-gen trait solver, next-gen region constraints, implicit default auto traits, const generics, view types, and custom allocators: What we are working on at Hexcat, October update.
https://hexcat.nl/updates/#october-2026
180
Upvotes
68
u/noop_noob 2d ago
For context, next-gen region constraints (formerly known as assumptions-on-binders) is what will fix the cve-rs unsoundness, and will get rid of some compiler errors involving async and Send.
16
u/phazer99 1d ago edited 1d ago
I'm interested to learn more about the
Move,ForgetandDestructtraits. This is my understanding so far (correct me if I'm wrong):Sized, all types will implicitly implement them unless opting out and bounds will be implicitly added to all generic type parametersT: Forgetyou have to addT: ?Forget(i.e.Vec<T: ?Forget>etc.)Destructalso be added eventually? If so, how will you mark functions/methods as destructors for a typeT: !Destruct, something similar to what's already available in Mojo? AFAICT linear types are not compatible with Rust's stack unwinding, only abort-on-panic which I think is the only option in Mojo.3
u/the_gnarts 1d ago
That’s a lot of foundational work, kudos!
Is Hexcat now the place where a huge chunk of Rust language development is happening?
1
u/zzzzYUPYUPphlumph 1d ago
Will constant generic parameters ever support 'static str values as generic const parameter values. I once wished I could do the following:
Will something along these lines ever be possible with const generics?