Sometimes I wish that rustc had a database of small breaking changes that affect only a handful of crates, so that we could on the fly patch them going forward. Things like "we now correctly check for lifetimes in assoc types" can technically be a breaking change that affects a handful of crates, but I want to ensure that building a project from today in 15 years doesn't require a compiler tool chain from today.
I guess this is the windows backwards compatibility approach. #rust#rustlang
It's hard to find #cargo add-ons. crates.io has very poor search options.
For example, I recall one which I think began with 'b' which sits in the terminal running the build and shows errors in order, unlike cargo build where they scoll off screen and out of view. [EDIT: from replies it is called 'bacon']
But I can't list search results by name, only things like newest etc. #RustLang
"#Rust development is going too fast (because they are stabilizing features I don't care about) and going too slow (because they are not stabilizing features I care about!"
There are only so many #RustLang contributors, hours in a day, days in a year to get to everything now, and some features are reliant on other, less flashy work that needs to happen before they can be even attempted.
But people are putting in a lot of work, the codebase changes so quickly that it is hard to keep up.
Hit an edge case in the #Rust compiler that appears to be quadratic at best and potentially exponential. Trivial to make happen with real-world code. Investigating...
"cargo-buttplug: ensuring positive reinforcement during long, tiring code sessions". Yup, you guessed it right: 10 seconds of vibration if Rust compilation is successful 😅 Be careful: as you become fluent with the language compilation succeeds more often 🤣 #RustLanghttps://github.com/vmfunc/cargo-buttplug
🦉 added an action bar, placed items can be used via number keys
🦊 added item type 'spell' (no individual cooldowns yet)
🦐 made spell items out of the dash and past projectile attacks
"Unfortunately, most people seem to have taken the wrong lesson from Rust. They see all of this business with lifetimes and ownership as a dirty mess that Rust has had to adopt because it wanted to avoid garbage collection. But this is completely backwards! Rust adopted rules around shared mutable state and this enabled it to avoid garbage collection. These rules are a good idea regardless."
If you're doing a lot of work in C/C++/Rust consider using sccache to cache compilations. It's easy to set up and will save you a lot of time and a huge amount of power.
https://nexte.st/ is awesome. The expression language to filter for tests or simply display a list of available test made is "must-have" for me. #rustlang#rust