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
We currently have var and let variables and fields, the only difference being that once setup a let cannot be reassigned to. This gives a small amount of extra type checking, if the programmer chooses to use it.
Is this worth having or should we remove it?
Personally I'm currently thinking no.
The text was updated successfully, but these errors were encountered:
I am sure that there could be some optimizations being made if there would be let-fields. From a programmers perspective, I would say its unnecessary and therefore I am personally currently your opinion!!
These turn out to be very useful to the programmer, allow certain optimisations, and are particularly useful for certain forms of publicly accessible fields. We'll keep let.
We currently have var and let variables and fields, the only difference being that once setup a let cannot be reassigned to. This gives a small amount of extra type checking, if the programmer chooses to use it.
Is this worth having or should we remove it?
Personally I'm currently thinking no.
The text was updated successfully, but these errors were encountered: