@encthenet Current version is 1.66, not sure why you think 1.61 is current. There are some crates that rely on the most recent features, it's just how it is. It doesn't make the language a joke, it's just being actively developed, and some crates want those features that are being added. If you don't want to upgrade periodically it's not going to be your cup of tea, at least for another 5-10 years at least, unless you have few dependencies.
@encthenet Apologies, I misinterpreted. I don't have many problems of this sort tbh, but I do update every 6mos or so to get the lastest tooling features and compiler speed bump. Perhaps that has kept it from being an issue. Or it's isolated to dependencies that I don't use. On the other hand, the upgrade process has never failed for me, so I trust it to some degree, mitigating the apprehension, learned from experience, that I always feel when updating language tools.
@ambihelical Where id I say 1.61 was current? I clearly said it was 7 months old.
Yes, the language is actively being developed, which means (in my book) that it isn't stable enough to be used. Having to recompile your compiler every month isn't really sane choice in my book.
I've started eschewing dependencies because of breakage like these.
Also, the dependent rust version wasn't declared, and having a dependency failure is a bad experience.