The literal does not have an explicit type at all. The f64 suffix is simply interpreted as three hex digits, making the literal 0xDEA_DBEE_FF64.

Neither #rustc nor #clippy warn about this explicitly; clippy only warn about mixed case and inconsistent grouping, making 0xfff_f64 warning-free. https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=a207e7c4f445e6be53011468d5b7cdaf

Updated #mrustc in my #gentoo overlay (https://git.stikonas.eu/andrius/gentoo-bootstrap). Now #rustc can be bootstrapped from C starting with version 1.54 rather than 1.39.

Thanks to #Rust and its environment: #rustc, #rust-analizer #cargo, #clippy, #fmt for making me feel like I'm doing pair programming alone.

I wrote a thing.

https://mperez.io/noob-hacking-on-rustc-part-1

Might be interesting for anyone that wants to start contributing to #rust or hacking on #rustc but are a bit nervous on starting.

#rustc on alpine
SIGSEGV on stable-x86_64-unknown-linux-musl in a few cargo tools · Issue #93084 · rust-lang/rust
https://github.com/rust-lang/rust/issues/93084

Year 2054.
spoj.com is still running #rustc v1.33.

Meanwhile, #rustc at spoj.com is still v1.33.
*sigh*

I am not put off by #rustc rapid changes as I hear Stallman seems to be, since I think this is already addressed by specifying rust "editions", which only changes every few years, as specified in cargo toml, unless there is something I am missing.

A little #terminalporn with #rustc compiling #TubeFeeder on @mntmn #reform ... x)

@sir certainly the fast movement of #rustc has been the main thing slowing down my experimentation with it. Everytime I try an build #remacs run into some random compiler problem. However at the same time spending a lot of time as I do doing multi-threaded C I long to work with a language that properly supports you in getting it right. AIUI moving from C to #golang is easier as it's a minimal bit of extra syntax to learn but I'm not as sure of their concurrency story.