←back to thread

Unexpected productivity boost of Rust

(lubeno.dev)
517 points bkolobara | 1 comments | 27 Aug 25 15:48 UTC | HN request time: 0.211s | source
Show context
merdaverse ◴[27 Aug 25 18:15 UTC] No.45043051[source]▶
Code written below your line gets executed if you don't return early. More breaking news at 8.

Seriously, why would you think that assigning a value would stop your script from executing? Maybe the Typescript example is missing some context, but it seems like such a weird case to present as a "data race".

replies(8): >>45043245 #>>45043339 #>>45043398 #>>45043537 #>>45043876 #>>45046033 #>>45046975 #>>45049155 #
lights0123 ◴[27 Aug 25 18:38 UTC] No.45043339[source]▶
exit(), execve(), and friends do immediately stop execution—I could understand why you'd think a redirect would as well.
replies(4): >>45043409 #>>45043410 #>>45049020 #>>45049406 #
dvt ◴[27 Aug 25 18:44 UTC] No.45043410[source]▶
The redirect is an assignment. In no language has a variable assignment ever stopped execution.
replies(6): >>45043422 #>>45043544 #>>45043663 #>>45043805 #>>45047504 #>>45047601 #
1. AdieuToLogic ◴[28 Aug 25 02:01 UTC] No.45047504[source]▶
> The redirect is an assignment. In no language has a variable assignment ever stopped execution.

Many languages support property assignment semantics which are defined in terms of a method invocation. In these languages, the method invoked can stop program execution if the runtime environment allows it to do so.

For example, source which is defined thusly:

  foo.bar = someValue
Is evaluated as the equivalent of:

  foo.setBar (someValue)