Notices by Jonathan ‘theJPster’ Pallant (thejpster@hachyderm.io)

Hey @bagder, I was wondering about the default Rust install command:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Is the restriction on --proto to =https strictly required? Will curl switch to http even given an https URL?

Is the restriction to TLSv1.2 strictly required? Will curl downgrade to TLSv1.1 or SSLv3 if the server suggests it?

The -s and -S are fine, but I'd probably live with the stderr output for the sake of command brevity. The -f seems reasonable though.

@unlambda @bagder a MITM with a valid certificate?

Idle thought: what if in Rust you were able to write:

pub nopanic fn foo() { … }

Functions marked nopanic can only perform operations that are themselves nopanic. A bit like const fns. If you really wanted you could make main a nopanic function. Unchecked arithmetic and slicing, and functions like unwrap, would all be forbidden inside a nopanic function.

You could also use the keyword “safe” instead of “nopanic”, leaving the default to be ?safe, or semi-safe (no UB, but could panic).

https://github.com/rust-lang/rust/pull/117472

Soon you will be able to write c"Hello" in rust and get a valid UTF-8 encoded *NUL-terminated* string. This is amazing for people who work with C APIs.

@thomasfuchs I know! I was so upset about this I made my own computer and wrote a manual to go with it.

@thomasfuchs what?! that's incredible.

@nova I haven’t logged in over there in weeks now. The biggest issue is Fomo, especially when work tracks @s on a zulip thread and I know I mustn’t click on any of those posts for fear of being sucked back in.