<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Perceptes</author><text>The history of TryFrom&amp;#x2F;TryInto has spanned 3 years, from when it was originally proposed as an RFC in 2016. For a seemingly simple API, it&amp;#x27;s gone through a lot. Especially unusual was that it was stabilized a few releases ago and then had to be destabilized when a last-minute issue was discovered with the never type (`!`). The never type had been the primary blocker for stabilizing these APIs for the last year or so, but it was finally decided to simply use this temporary `Infallible` type, which would be mostly forwards compatible with the never type itself.&lt;p&gt;I&amp;#x27;ve followed the issue closely because it&amp;#x27;s one of the features used in Ruma, my Matrix homeserver and libraries. In fact, for the library components of the project, it was the last unstable feature. With the stabilization of these APIs, I&amp;#x27;ll finally be able to release versions of the libraries that work on stable Rust. This will happen later today!</text><parent_chain></parent_chain></comment><story><title>Rust 1.34.0</title><url>https://blog.rust-lang.org/2019/04/11/Rust-1.34.0.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>korethr</author><text>Hmm, fn before_exec strikes me as a thing that should be gotten rid of entirely in favor of unsafe fn before_exec if the former indeed turned out to actually have the potential to cause undefined behavior. But that&amp;#x27;d probably be a breaking change which would require a major version number bump, so deprecation is absolutely the right thing IMO. And it also sets the stage to get rid of it outright come the next major version bump.&lt;p&gt;This is the first such instance of &amp;quot;oops, turns out that wasn&amp;#x27;t safe after all, that should have been unsafe&amp;quot; that I&amp;#x27;ve heard of in Rust. Is that because this is the first such mistake since the 1.0 milestone (the rest of `unsafe` having been nailed down before 1.0), or have there been other such mistakes that I didn&amp;#x27;t hear about because I haven&amp;#x27;t read the notes for all of the prior releases of Rust?</text><parent_chain></parent_chain></comment><story><title>Rust 1.34.0</title><url>https://blog.rust-lang.org/2019/04/11/Rust-1.34.0.html</url></story>