SSA for the win!

> I wish it was the default, and mutable was a keyword Rust ftw

Would be nice if we could make a variable const as part of an assignment. It's often the case that I need to modify it in a few branches, after which it should be frozen.

It surprising that C++ (or any language) doesn’t have explicit directives for scoping this kind of style request. Closest examples I can think of are async and yield, which usually code-gen a function into a different form. Why not allow fine grained policy?

Pretty sure that’s what rust does, you have to specify mut to make a variable mutable, otherwise it defaults to an unmutable variable

Similar situation with noalias. Back in the 1980s when the ANSI C standard was being created, they were going to have a keyword "noalias". Dennis wrote a letter to the committee saying he wouldn't endorse the standard if they included it. Very short sighted.

Immutable value holders are a goodness that usually only functional programmers appreciate.

This is Rust ser. I think you'll like it.

Use Rust.

FWIW, Rust defaults make this incredibly easy

yea can use frozenset and frozendict and such but have to be so careful, more cachable, yep the mutability is a real problem like you forget df.copy() and you accidentally update some kind of dict or something and its like a global so its like cache poisoning really, can mean some server just permanently stops working and when you deploy it seems to fix for a while lol untill it get cache poisoned again... arg... the mutable default way is pretty nice youll much more likely find that you need to set something as mutable via say the compiler or debugging process in these explicit mutable requirement languages pytorch is kind of nice because in place operations you need a _ so its uncommon eg add_, mul_, copy_ etc but yea idk if thats like super explicit but yea atleast its opt in ish

run a type checker and use the Final annotation :)

Variables being mutable by default in nearly all mainstream languages should be considered one of the greatest sins of PL design of all time. If I could keep one thing from Rust, it might just be variable immutability by default (w/ mut keyword for mutability).

Default const and nice syntax for initializing with result of a block are things that made me think Rust designers have good taste

Rusts “default immutable” has definitely grown on me since being introduced to it

Oh wait 'til you learn about Rust... you would really like Rust.

For TypeScript, `no-shadow` and `prefer-const` are some of the best ESLint rules out there. `prefer-const` forces you to use constants and `no-shadow` prevents you from reusing a variable name that's already been declared in the outer scope.

Erlang (all data is read only) and rust ( default to immutable) ♥️

This is also my pet peeve with people who().chain().functions().like().this() and then good luck debugging this!

I wish C++ had a kind of deferred const system where a variable did not have to be initialized at declaration as long as it was inited once and only once before use. For instance: const int x; if (cond) x = 1; else x = 2; You can do some of this with the ternary operator, but not with anything too complex.

I don’t understand the utility of a variable being const by default. If I want a variable to be a constant I’ll const it, but probably 70% of my variable declarations are done because I want the contents to change. Mind you I also dislike declare-and-assign statements.

In JS, we now have `const` and `let`, which at least during initialization helps to understand their usage. Everything used to be `var`, luckily these days are in the past.

funny enough, mypy can kind of catch this, if the variables are of incompatible type.

I've tried to learn Python a couple of times and it was when you were on Lex Fridman that I finally said, "Dammit if Carmack thinks it's the one language someone should pick up then I'm going to do it". I'm now giving it a second go!

I don't get this one, mister Carmack. Do you mean to only have constants, i.e not "variables" but data that never changes? What about stuff that actually changes e.g HP in a game?

Sir, I don't think you are ready for vibe coding 🙂

Mr Carmack I hope your coding skills didn't become rusty

"I wish it was the default, and mutable was a keyword." the reason i love working in rust

"I wish it was the default, and mutable was a keyword", why does that sound familiar?

preached these points for so long. No changing semantic meaning is part of why I push it but yea resequencing of code with less surprises is part of that. And const as default with mutable as optout, definitely wish it went this way.

Am I the only person that reads this and thinks, "your methods are probably way too big"?

U could always kotlin or 😅 go full haskell

What I typically do in C++ is to create the mut<T> type, where T is const. For instance, using u8 = const uint8_t; template<typename T> using mut = typename std::remove_const<T>::type;

Many things great about Kotlin and Haskell: FP and built-in, immutability with explicit mutability. Can’t really ever go back to C or C++. That ship has sailed and capsized years ago.

It's not lazy, it's seeing the SSA IR at a higher level :)

Functional Programming, baaaaaby!