map witch ebel ⛧ 🧙‍♀️🗺️🌍 @ebel@moytura.org

I'm going to have to learn how #rust's futures & async works at some point.

"I know I'll just write a quick #Rust programme to proxy my http connections and add the header that I want".

Oh cripes, I forgot hyper's now gone weird with Futures and the like.

I have also learned about `impl Into<Cow<_>>` to accept a `&T` and `T`. Which, in retrospect, should have been obvious to me, but I just didn't put 2 and 2 together.
It should make my #rust code more cleaner/ergonomic!

"Elegant Library APIs in #Rust"
Now this is an interesting guide!
(I learned about the `impl Into<Option<T>>` which looks very useful!)
https://deterministic.space/elegant-apis-in-rust.html

Ung. I love #Rust in many ways, but the String/&str thing often wrecks my head. Why is there &str *and* &String? Making functions they can take either type is annoying. (currently trying to wrap my head around Borrow vs AsRef).

OMG, I just discovered if you put this in your Cargo.toml (in a #Rust proj) then dev mode will run as fast a release mode!

[profile.dev]
opt-level = 3

I was using the #rr debugger with #Rust yesterday and it was pretty cool. 🙂

Must resist siren song of writing my own library for #JSONSchema validation. Though there is only one #rust library for #JSON schema validation..... Why not 2?

I'm using nightly #Rust for the sweet sweet TryInto

I quite like programming in #Rust. I think I'm getting the hang of it, and the more I write it, the more confident I get.

I'm gonna have to figure out how to compile this #Rust programme into a binary for #Windows on my #Linux machine... 🤔🤔🤔

Yay, get to make a #Rust project!