Yeah it's mad. Tbh I don't think GitHub PRs are the best workflow, but I absolutely know that git send-email is the worst. I tried to use it once to contribute to OpenSBI, which inexplicably also insists on it. Suffice it to say my patch was never merged...

Yeah. I think the smallest number of number types you can reasonably have is two - f64 and arbitrary precision integers types. One of the few good decisions Python made.

I support the idea but is it really that important? It's just a name. Call it ECMAScript if you're worried. JavaScript if you aren't.

Impressive. I would imagine it is very difficult to get native performance without ISA extensions like Apple had to do for TSO and other awkward x86isms.

I would guess someone will make a RISC-V extension for that stuff eventually, though I haven't seen anyone propose one yet.

Only if you are desperate or masochistic.

It's just this: https://westling.dev/b/extremely-linear-git

Basically, if your tree is static or you only add nodes, the easiest option is to store all nodes in a Vec and have the child/parent links be indices. I recommend the typed-index-collection crate if you go that route.

If you need to move/delete nodes a lot then either Rc<Refcell< or you can wrap the Vec in something that takes care of the admin of fixing up pointers.

E.g. see this crate https://crates.io/crates/orx-tree

If you want to get really fancy you can even do things like compacting GC. You're basically implementing a memory allocator at that point.

Note that you might say "what's the point of Rust if I just have to implement a memory allocator to bypass the borrow checker?" but that's silly. You still get the benefits of Rust for the rest of your code, and Rust still prevents things like type confusion and UB.

Dunno why you're being downvoted. It's very obviously deliberately chosen to make 12 year olds giggle.

Yeah that sounds very unlikely to me. I guess the definition of "open source maintainer" and "unpaid" are wide open. Does it count if a company pays your salary and you are allowed to do the open source stuff as part of your job? How popular does your project have to be before you are an "open source maintainer"?

Yes. For the project I work on pip install takes about 60 seconds and replacing it with uv reduces that to about 7 seconds. That's a very significant improvement. Much less annoying interactively and in CI we do this multiple times so it saves a significant chunk of time.

only access secrets from environment variables

I kind of think this is a bad idea because environment variables can be read from anywhere and aren't designed to be secret.

But I'm not sure what a better solution is tbh.

If everyone had a magic lamp that told them whether performance was going to be an issue when they started a project then maybe it wouldn't matter. But in my experience people start Python projects with "performance doesn't matter", write 100k lines of code and then ask "ok it's too slow now, what do we do". To which the answer is "you fucked up, you shouldn't have used Python".