| 11 Dec 2025 |
 Charles | i would explain it as XID_Start followed by zero or more XID_Continue because that's what it is, and you don't need to explain what those are because explaining that is unicode's job | 21:27:15 |
| Charles | for example https://doc.rust-lang.org/reference/identifiers.html#grammar-IDENTIFIER | 21:27:38 |
| Charles | * for example https://doc.rust-lang.org/reference/identifiers.html | 21:27:50 |
 Rutile (rootile) | In reply to @charles:computer.surgery
i would explain it as XID_Start followed by zero or more XID_Continue because that's what it is, and you don't need to explain what those are because explaining that is unicode's job Something something consecutive hyphens | 21:28:03 |
 helle (just a stray cat girl) | I mean...... for a first year compsci student with the two classes I just mentioned, :P that is the level a lot of people starting out with any new language actually would have roughly, even if they are super skilled in say PHP | 21:28:07 |
| Charles | the motivation is to ban those from what i'm calling literal identifiers | 21:28:35 |
| Charles | that's the entire point | 21:28:51 |
 rosssmyth | Nix is an immutable lang so there are no "variables", as nothing can ever change. For functional languages you usually call things "[let] bindings," as it is bound to a specific value, and will never change (unless you shadow the binding). | 21:28:52 |
| rosssmyth | * Nix is an immutable lang so there are no "variables", as nothing can ever change. For functional languages you usually call things "[let] bindings," as it is bound to a specific value, and will never change (unless you shadow the binding). Even then you aren't changing the binding itself as once you go back to the original scope, it will still be bound to the original value. | 21:29:33 |
