News for hackers. Stuff that matters.
Re:Formatting Is Unreasonably Expensive for Embedded Rust by wizzwizz4 on Monday December 09, 2019 @12:45PM (#21744639)
I'm not sure how to contact the author, but just a nitpick:

    fn inner_main() -> Result<(), ()>
should be:

    fn inner_main() -> Result<!, ()>
since it shouldn't return except in the case of an error. It's important to make the compiler aware of such semantics, so that it can better optimise the program.
Re:Formatting Is Unreasonably Expensive for Embedded Rust by pvik on Monday December 09, 2019 @12:52PM (#21744715)
The author has his email (and twitter handle) in his about page (https://jamesmunns.com/about/)
Re:Formatting Is Unreasonably Expensive for Embedded Rust by fra on Monday December 09, 2019 @01:44PM (#21745143)
He's super responsive on twitter: https://twitter.com/bitshiftmask
Re:Formatting Is Unreasonably Expensive for Embedded Rust by nemothekid on Monday December 09, 2019 @04:20PM (#21746719)
I think this is right, but I don't think the never type is stable.
Re:Formatting Is Unreasonably Expensive for Embedded Rust by kibwen on Monday December 09, 2019 @04:55PM (#21747044)
The Never type should be stable in 1.41, I believe.
Re:Formatting Is Unreasonably Expensive for Embedded Rust by NieDzejkob on Monday December 09, 2019 @05:03PM (#21747122)
I checked, and you seem to be right. It feels weird, considering all the jokes that "never is named after its stabilization date"
Re:Formatting Is Unreasonably Expensive for Embedded Rust by monocasa on Monday December 09, 2019 @06:34PM (#21747886)
The seamntics of ! is stable as far as I know. It being retconned into the Never type is the unstable bit.