@bradleymeck @adamrackis @zenparsing the dual-parse option was by far the better one, perf hit was well worth it
-
-
Replying to @getify
@getify My understanding was that corner cases made that _impossible_ to do correctly. Or was it just perf?@bradleymeck@zenparsing1 reply 0 retweets 0 likes -
Replying to @AdamRackis
@AdamRackis@getify@zenparsing ambiguities, difficulty w/ other tools outside node supporting interop, perf is a problem but not the only 13 replies 0 retweets 0 likes -
Replying to @bradleymeck
@AdamRackis@getify@zenparsing in particular: https://tc39.github.io/ecma262/#sec-strict-mode-of-ecmascript … effects arent analyzable due to behavior being determined at runtime1 reply 0 retweets 0 likes -
Replying to @bradleymeck
@AdamRackis@getify@zenparsing note: behaviors sometimes cause errors, sometimes silently have different semantics, args binding, this, ...1 reply 0 retweets 0 likes -
Replying to @bradleymeck
@bradleymeck@AdamRackis@getify@zenparsing My suggestion, use: import ‘’; as internal designator for rare script-like modules.2 replies 1 retweet 6 likes -
Replying to @awbjs
@bradleymeck@AdamRackis@getify@zenparsing Loader would have to be trained to ignore empty string uses as ModuleSpecifier2 replies 0 retweets 0 likes -
Replying to @awbjs
@awbjs@bradleymeck@AdamRackis@getify@zenparsing you'd need a real JS parser because: /* import ''; */ (which could totally happen!)1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@bradleymeck@AdamRackis@getify@zenparsing yup, I was assuming that.1 reply 0 retweets 0 likes -
Replying to @awbjs
@awbjs@zenparsing fwiw TypeScript has this heuristic and I once spent hours trying to figure out where a global was coming from.1 reply 0 retweets 2 likes
@awbjs @zenparsing turned out I never learned that a file without an import was a script. It was baffling.
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.