-
-
I personally like using const and don’t see any issues mentioned in the thread to affect me. I used to love the idea of immutability too
-
The main issue with overusing const is that you lose the user intent of "this ought not be mutated" as in const fs = require('fs')
-
I’ve spent the last few months working on partial evaluating React code via Prepack. So I probably see JS in a different way to most haha
-
It's very easy for prepack to apply the "un-mutated let binding" optimization and I really hope you do.
-
It’s not that easy. Nothing is safe from side effects it seems. The only somewhat safe thing is strict type annotations
-
What exactly is not easy. Are you referring to use of direct eval? Or something else?
-
Global side effects, eval, getters/setters, proxies etc.
-
How can global side effects, getters/setters or proxies affect the analysis of whether a let-bound variable in a module is ever mutated?
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.