He’s (rather Bessent) literally crashing the economy in order to force the Fed to lower the rates. To be fair, a soft landing was a pipe dream. Bessent has a long history of talking about this type of reckoning.
"Setting the building on fire was and in turn the entire blockthe only way to address the creaky floors". There's no Trump masterplan here (or anywhere else) than the sanewashing of his bs by his fanbois.
function add2(x: Int, y: Int): Int {
return x + y;
}
add2(2, 3) //5
add2(x=2, y=3) //5
add2(y=2, 5) //7
The language already supports '=' operator for assignment of variables in the current scope, so should you use the same operator for denoting value assignment formal parameters in a function call? This can lead to a lot of confusion between variables in the scope and formal parameter names in a function that is called from the current scope.
This seems like a non issue to me and as tomp said, is already done in popular languages without problems. The third example (keyword arguments before positional) does seem a bit odd though, as interleaving positional and keyword arguments seems like a recipe for confusion, but using = for keyword arguments doesn’t seem like a problem to me.
I love this feature - calling named parameters is (for me) a glaring omission from Javascript (and surprisingly Typescript), I know you can define an object argument, but not many do and that’s not very elegant.
