The closest thing I can think of is @author unascribed sometimes seen in Javadoc comments, but I don’t think that’s used in quite the same way as what you’re asking.

This culture war shit is pathetic. “DEI” has become a dogwhistle (if one can even call it that at this point) for “I don’t like black people/brown people/women”, and they all shamelessly parrot it with their whole chest. Good on the PSF for doing the right thing and calling this garbage out for what it is.

Have you actually worked in a programming role before? Googling things is absolutely the norm. Most people don’t know every single in and out of every library/framework they’re using, especially when learning new ones. This goes double for more complex or sprawling frameworks where it may be less than obvious how to perform a particular task from the documentation alone or when running into undocumented limitations or bugs (although admittedly an in-IDE assistant won’t be too useful for that anyway).

In what ways do you feel Rust is too clunky and how do you think it could be improved? Not looking to argue or even disagree necessarily; I’m just curious where that perspective comes from.

I mean, technically there’s nothing preventing that, but in practice it’s a fairly uncommon mistake to make and it’s immediately obvious that there’s an issue the first time that path is taken. If something like that makes it to production, it clearly points to an issue with test coverage rather than code paradigm.

continue is useful as a loop analog to early return in a function context, which helps keep indentation/nested conditionals under control and in turn improves code readability.

I don’t think I’ve ever felt the urge to apply an alignment chart to monospace fonts of all things, but Xenon and Radon are basically lawful and chaotic evil respectively.