If you are wondering why #rustlang rust-analyzer suddenly stopped showing size info on hover on some, but not all types - the answer is here:
Remote
Manpacket
@manpacket@functional.cafe
mastodon 4.8.0-alpha.3+glitchA #rustlang programmer with interests in functional programming, category theory and advanced type sorcery
82 Followers
126 Following
23 Posts
Joined June 19, 2023
Pronouns:
He/Him
GITHUB:
https://blog.rust-lang.org/2026/04/16/Rust-1.95.0/
#rustlang 1.95.0 is out
I can finally see bits needed to make ranges more usable! Eventually, in the next language revision.
#rustlang 1.96 is out.
https://blog.rust-lang.org/2026/05/28/Rust-1.96.0/
Nothing from clippy for me, but finally proper Range types are getting there!
https://blog.rust-lang.org/2026/07/09/Rust-1.97.0/
#rustlang 1.97.0 is out
Be careful with `clippy --fix`, `manual_filter` auto fix can eat your comments.
An email from CI:
> CI: Some jobs were not successful
> There's 10 jobs that succeeded, if you want to see those that failed - follow this link.
Come on GitHub. Try harder. You can do better than that.
Spent a lot of time (a lot of time) trying to figure out why my shell completion experiments are failing. Turns out I was missing a " -- " in one place and "%" needed to be replaced with "%%"., but all the abstraction layers and shell's desire not to print an error on invalid input made it tricky to debug.
Printing errors is important.
@FromTheFourthPlanet@mas.to Trap Door?
Replying to
@Ambraven@social.mochi.academy godbolt is great if you want to share the results or run it across a bunch of different compiler versions. If you simply what to see the generated asm for your rust project - there's cargo-show-asm.
Replying to
@justindz@mastodon.social a year ago I switched to Fedora having more or less the same starting point as you in right now. I'm happy so far.
Replying to
@justindz@mastodon.social it doesn't force me to use snaps and there's no AI, at least for now. Installation was very uneventful. Doesn't require attention, just works.
Replying to
- Thus, there is currently pretty much no ethical way of using LLMs.
Replying to
@klausi@mastodon.social Yeah, leaking memory is totally safe thing to do in Rust.
For limiting memory usage you can look for a custom allocator (cap crate seem to be able to help, haven't used it myself) or an external solution like cgroups (works great, assuming Linux)
Replying to
@ruben NixOS might do the trick. Not beginner friendly, but all the configuration will be living in a few text files that you can copy or test locally.
Replying to
@david_chisnall he is in a business of selling shovels during a gold rush. Of cause he wants people to spend much more time digging.
Just realized that I have 20+ different version of stable #rustlang toolchain installed. Not as good as `cargo clean`, but freed some space.
Check yours with `rustup toolchain list`
Replying to
@subjectsphinx@mathstodon.xyz @abuseofnotation@mathstodon.xyz I would disagree on the font, at least what my browser substitutes. Ended up using the reader mode.
Replying to