I feel like this breaking change should be justified here. Especially since you can easily fix it by improving the symbol explicitly instead of using glob imports
If you use a glob import and have a symbol From in the imported module it will stop compiling because of the prelude attention of From. Because if this breaking change the implementation got changed to not include the From macro in the prelude. In my comment I'm arguing that they should include it in the prelude anyway since this is a very uncommon situation and it is easily fixed.
Next time, just actually read the blog post instead of getting your Sunday from an LLM
Honestly, I admit I skimmed over that part, but the author explicitly acknowledges that it may not be possible to use this derive macro out of the box until an edition bump. I don't see any issues with that.
I always use stable unless I really need some specific feature I can't imitate on stable (custom_test_runners comes to mind). I'd just manually write out the From implementation in this case, even if already on nightly.
mr_birkenblatt@reddit
I feel like this breaking change should be justified here. Especially since you can easily fix it by improving the symbol explicitly instead of using glob imports
Theemuts@reddit
What breaking change?
mr_birkenblatt@reddit
The one mentioned in the blog post?
Theemuts@reddit
I don't see any breaking changes in this blog, what old code will fail to compile according to you?
mr_birkenblatt@reddit
If you use a glob import and have a symbol From in the imported module it will stop compiling because of the prelude attention of From. Because if this breaking change the implementation got changed to not include the From macro in the prelude. In my comment I'm arguing that they should include it in the prelude anyway since this is a very uncommon situation and it is easily fixed.
Next time, just actually read the blog post instead of getting your Sunday from an LLM
Theemuts@reddit
Who's jumping to conclusions now, lol...
Honestly, I admit I skimmed over that part, but the author explicitly acknowledges that it may not be possible to use this derive macro out of the box until an edition bump. I don't see any issues with that.
Key-Celebration-1481@reddit
Awesome! I look forward to being able to use this in stable in ten years /s
(For real though are most Rust devs actually using nightly? The grass seems so much greener over there.)
the-code-father@reddit
Rust nightly was (is?) the default for writing Rust internally at Google
________-__-_______@reddit
I always use stable unless I really need some specific feature I can't imitate on stable (
custom_test_runnerscomes to mind). I'd just manually write out theFromimplementation in this case, even if already on nightly.Key-Half1655@reddit
I could never get a nightly build past release team, stable or gtfo!
zzzthelastuser@reddit
I only use stable.
ferreira-tb@reddit
I always use nightly when not writing libraries. But I'm pretty sure I'm in the minority.
angelicosphosphoros@reddit
I do too.
It is just some features are really convenients, e.g. array_chunks or array_windows.
TeamDman@reddit
Great writeup, thanks for sharing!
ferreira-tb@reddit
I always use nightly when not writing libraries. But I'm pretty sure I'm in the minority.