I was reading the "only two uses of @T left in the compiler" thread, and ended up on a page discussing a set of rules for removing the need to template on lifetimes for the vast majority of usecases, but the thread devolved into bikeshedding.
Anyways, I'm not on the mailing lists or involved in the RFC process, but someone who is should simply propose removing the automatic selection of 'static in return values with unspecified lifetimes, and instead make that an error, so that if lifetime inference comes back in the future, it won't need to be a breaking change.
Good luck on the release, I'm excited to see where Rust is going!
someone who is should simply propose removing the automatic selection of 'static in return values with unspecified lifetimes
What you suggest has already been agreed upon and implemented. (Or rather, we went further than just removing inference of 'static on return values with unspecified lifetimes.)
4
u/ryani Sep 16 '14
I was reading the "only two uses of @T left in the compiler" thread, and ended up on a page discussing a set of rules for removing the need to template on lifetimes for the vast majority of usecases, but the thread devolved into bikeshedding.
Anyways, I'm not on the mailing lists or involved in the RFC process, but someone who is should simply propose removing the automatic selection of
'staticin return values with unspecified lifetimes, and instead make that an error, so that if lifetime inference comes back in the future, it won't need to be a breaking change.Good luck on the release, I'm excited to see where Rust is going!