You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As long as every type contains nil, I don't think "being explicit" is a good idea there, because it gives the wrong impression to readers that T and T | nil are different things.
trace.ent?.name
Nil-coalescing operators would be nice, I'd like to have them, but implementing them properly would change the code generation a lot. So not a simple task!
pbdot
changed the title
Optional property accesses and nullish coalescing operator
Nil-coalescing operators
Dec 18, 2024
Since every value can also be nil and we can also be explicit:
It would very nice to be able to:
... and if we know valid:
Coming from TypeScript the "or" operator didn't occur to me, and not sure if any value in nullish coalescing
The text was updated successfully, but these errors were encountered: