WTF I didn’t understand, thanks for the explanation. The fact that it’s used all around the world in big companies doesn’t matter I guess.

Why the fuck would they prevent private browsing? I use that a lot to be sure the session is closed correctly.

• I put the types first in the file, sorted by importance
• then the public free functions
• then the impl blocks, sorted by importance, also. Usually, display impls and similar end up being at the end
• then the private free functions (helpers)

The idea is that I can see all the types in one glance, then I look at the rest.

It’s a toy example. In that case, the solution is to assign the expression to a variable to compute its result upfront.

There are still obvious things the BC cannot get. For example:

struct Foo;

impl Foo {
    fn num(&mut self) -> usize { 0 }
    fn index(&mut self, _i: usize) { }
}

let foo = Foo;
foo.index(foo.num()); //error

My coworkers do document the code:

/// Returns a list of foos, given a bar. 
fn get_foos_from_bar(bar: Bar)

I really like this instance, so of course I’m 100% for the move

While you’re at it, with sum types, you can replace this stupid nil with an optional type. Also, you can replace the stupid error handling with an either/result type. Then you can add a keyword to return early if it’s left/err. Then you have Swift or Rust.

I’d argue the macros are quite bad:

• Declarative macros are hard to read, same level as regex
• Procedural macros require to write a new crate with a ton of boilerplate, sometimes for stuff conceptually really simple (like hash is: apply the same function to every field, then compose the results)

I agree, though, that it’s better there’re here than nothing. It’s just that there is to be a better solution.

I think they just don’t like cringe

Sorry for the late answer. Those days, I’m interested in Ante. The language creator has some novel ideas for a non-GC memory safe language. And the compiler is written in Rust. It’s not finished at all tho.

I didn’t even know there were a survey (and I’ve used Rust professionnaly for years)

And a light theme. I’m tired of websites having dark theme only.

I honestly try and read Go news from time to time, with an open mind, but the amount of terrible footguns is astounding, especially when the language is marketed as “simple” and easy for beginner to grasp. I would pick C# or Java over it anytime.

I know this is a piece of humor, but half of these are not surprising coming from a FP background (expression oriented, sum types, strong generic typing… )

Also, daring to compare Go and Rust error handling, and saying that Go’s one is better is… bold. It’s arguably one of the worst in any language.

When senior devs get older, they’re tired to look cool and take care of their eyes with light themes.