rust-lang
blog post re ctfe ub change observed in 1.64.
This is offshoot of https://github.com/rust-lang/rust/issues/99923 and https://github.com/rust-lang/compiler-team/issues/549
I am thinking this ought to go on the main blog, rather than Inside Rust; it feels aimed at average users more so than rust project developers.
I'll echo commentary from Zulip around "why is that flag not the default"; I think we might want to give an answer there.
I am thinking this ought to go on the main blog, rather than Inside Rust; it feels aimed at average users more so than rust project developers.
I had internally debated about where it should go. In some ways, I chose "Inside Rust" because I didn't want to cause undue alarm amongst our users.
But this feedback has pushed me back over the other direction; I think I can trust our users to take the time to understand what this post is saying.
I'll echo commentary from Zulip around "why is that flag not the default"; I think we might want to give an answer there.
Yep, I'll add that in as well. (As well as noting that maybe it will be turned on by default in the future, if we determine that the performance cost is sufficently low.)
Okay hopefully I can now say I'm done wordsmithing here. :)
(Oh, and I changed the file name to 2022-09-15, since I figure this is unlikely to get pushed to the Rust blog as soon as tomorrow. The filename I chose may be wishful thinking, but we do want the post published well before the 1.64.0 release on 2022-09-22)
This looks good to me but I'd love if @oli-obk had a chance to review as well!
oh, just so its clear, Oli did look at an earlier draft of this; their feedback was delivered on zulip (and was what @Mark-Simulacrum was referencing in their comment above).