Javascript disdain shared! 😜
We are a lot of #rustacean to praise #zola!
Everything is markdown once your templates and styles are set up.
I had to add a bit of js on top of it for some complex components but it wasn't enough to make me feel nauseous.
https://www.getzola.org/documentation/getting-started/overview/
Uhhhhhh...
😼 **cargo-cat** — A Cargo subcommand that prints random ASCII cats.
🦀 Also ships a library if you want cats in your Rust code.
⭐ GitHub: https://github.com/blyxyas/cat-ascii-faces
#rustlang #cargo #cli #devtools #rustacean #ascii #cats #meme
(You can get this triptych on an insulated tumbler of your very own here! https://fogwave.printify.me/product/25251869/ferris-the-rustacean-copper-vacuum-insulated-tumbler-22oz)
#rustlang #rust #ferris #rustacean #shopindie #blackfriday #fedigiftshop
Just in time for Black Friday: Ferris the Rustacean hats (in two colors!) https://fogwave.printify.me/product/25246678/ferris-the-rustacean-denim-hat-embroidery
Ferris is embroidered on the front; Corro the unsafe rusturchin is embroidered on the back :D
#rustlang #rust #ferris #rustacean #fedigiftshop #blackfriday #shopindie
Holy shit. This formerly frustrated new #Rustacean was about to unleash a rant about how surprisingly difficult it is to protect your build env in this super safe language.
After all, cargo tries to force you to expose yourself to supply chain BS, like it's some kind of curl|sh on drugs.
I appear to be the only person in existence to ever have attempted this, but to force #cargo to use distro installed crates, apparently it suffices to create a `workspacedir/.cargo/config.toml` with the contents:
```
[source.crates-io]
directory = "/usr/share/cargo/registry"
```
Would be great if cargo had some kind of "--online" flag to override offline mode. This way you could run it offline by default and go online only if you so wish.
Next up is trying to find out how to harden rust-analyzer so I can look at files without it executing crate supplied code.
Does any #rustacean know an example of getting observable undefined behavior out of an uninitialized integer?
I tried pretty hard starting with this and tried getting a branch to go in the wrong way with no success.
let numbers = unsafe { MaybeUninit::<[u32; 16]>::uninit().assume_init() };
// ^ this code causes undefined behavior when executedAdditionally, if you have any insight into the history of how strings in Rust were designed I’d love the links and stories. Thank you.