"#Rust development is going too fast (because they are stabilizing features I don't care about) and going too slow (because they are not stabilizing features I care about!"
There are only so many #RustLang contributors, hours in a day, days in a year to get to everything now, and some features are reliant on other, less flashy work that needs to happen before they can be even attempted.
But people are putting in a lot of work, the codebase changes so quickly that it is hard to keep up.
@ekuber I maintain a tool that uses rustc to do some useful things and I have to apply some workarounds to deal with rustc not providing some of the information. Workarounds lead to behavior confusing to users so I decided to make a fix upstream. I ended up submitting about 5 pull requests - some fixing related bugs and closing existing tickets and one with change I actually care about that depends on the rest. Bugfixes got merged, change I care about was approved more than a month ago but still sits in FCP stage.
@manpacket has there been any feedback on the fcp yet? Wrangling checkbox ticking can be difficult (particularly from users with lots of notifications). Do not forget that the backcompat requirements of the project are so high that it's hard to gain confidence or agreement on any user visible change. It's not ideal.
@ironchamber it is very common in open source. I just saw someone complaining that there won't be a Rust 2.0 and using that as proof that the project had ground to a halt 🤷🏻♂️
Everyone has an opinion, which I've learned to pick apart for actual useful feedback, but every now and then I see something soon off the mark that it is not even wrong.
Add comment