2026-09-09 23:11:56
I've been waiting for more powerful const generics in #RustLang for since 2020 (blog post at <https://christian.amsuess.com/blog/website/2020-09-24_rust_2021/>). Se…
I've been waiting for more powerful const generics in #RustLang for since 2020 (blog post at <https://christian.amsuess.com/blog/website/2020-09-24_rust_2021/>). Se…
#Python Hypothesis package now requires #RustLang. This is a scale of reverse dependencies I can't handle. I guess this means it's the end of WD40 profiles on #Gentoo, and therefore the end of support for Alpha, ARM<v6, HPPA, M68k, i486 and some other random subsets of architectures and profiles. Thanks for all the fish, etc.
https://github.com/HypothesisWorks/hypothesis/issues/4740
I'm giving an actual Rust university lecture next semester and I can't shake the idea of bringing the obligatory Rust cat ears for the first day.
#RustLang
So if you're wondering how great #RustLang is, let's talk about #mypy. Mypy introduced its own Rust - #Python package, ast-serialize. This package had a deep crate dependency that was broken on PowerPC. The issue was fixed a month ago but everything is still blocked on a deep chain of dependencies being updated and released.
https://github.com/mypyc/ast_serialize/issues/68
EDIT: yes, I know, it's not Rust, it's Cargo. Because obviously Rust without Cargo makes so much sense for that one project using it.
Also, zero days (well, minus a lot of days because I've been slacking) since a random #Python package got a new #NIH dependency on another Python package which is actually a "fastest" #RustLang package which cannot be built because the author thinks it a great idea to require a nightly Rust compiler.
…and of course it's full of "unsafe" calls. Because Rust is obviously such a great language for making secure code.
https://github.com/awolverp/cachebox/issues/62
Official announcement will follow next week: we're meeting on Tuesday, October 7, for our next @… meetup in #Mannheim. We still have time for a second talk, so if you have a topic or project related to
I feel a bit dumb for having discovered that so late, but #VSCode / #VSCodium do not use the .gitignore file to decide what inodes to watch for changes...
Working on a big #Rustlang project can be a nightmare (burning CPU, eating up all the RAM...), given that the target/ directory can end up using more than 100gb of disk space.
Remember to set your "files.watcherExclude" setting to avoid that problem:
```
{
"search.useIgnoreFiles": true,
"search.useGlobalIgnoreFiles": true,
"files.watcherExclude": {
"target/**": true,
"**/target/**": true
}
}
```
Zero days since #RustLang wanted to kill a platform.
https://github.com/rust-lang/rust/issues/162011
I was running a test suite for pysequoia, and one test seemed to have been taking forever. I started suspecting it hit some infinite loop, then I recalled I have RUSTFLAGS=-Copt-level=0 in my development environment, to avoid wasting time on rebuilding the same thing over again. Yep, that was it.
Unoptimized #RustLang is like C code with -O(-1000). It's slow as hell that has frozen over twice, and I'm talking about the frozen part and not the part where sinners are skating on the ice.
Do people actually understand #RustLang types and borrowing and whatever, or do you just write the first approximation and then follow compiler errors like I do?
Finally reported the abusive behavior of #Cargo #jobserver: #RustLang
If you are developing in #Rustlang then you should check this post: #cybersecurity #infosec #supplychain #supplychainattack
A short video showcasing the current state of the #SoulCrafted Slicer I'm working on.
#3dPrinting #Resin3dPrinting #SoulCraftedSlicer #FLOSS #OpenSource #Rust #Rustlang
Oh, right, in case I thought I'm going to have time to do useful things, I just realized I still need to deal with the humongous #Gentoo fallout from #Hypothesis #Python package requiring #RustLang now.