Daniel Rosenwasser
Daniel Rosenwasser
I'm super happy to see the enthusiasm here! I'd be a bit cautious though because depending on how your types differ, users may see some differences (at least initially) or...
(also we're looking for feedback!)
Minimal repro 👍 But also reporting with `--extendedDiagnostics` would go farther.
Just keep deleting surrounding code until you get a reasonable build time and build back up - maybe try to see what array extensions trigger it. @sanders_n might know more.
This is interesting, but I guess the question is how do you encode this in a generalized and pluggable manner? Additionally, do you end up having to import types to...
Hey all, @sandersn will be able to help out if you have any questions about supported tags and behaviors.
I notice the tree doesn't have `cooked` and `raw` - it has `cooked` and `value`. My instinct would be the processed string be stored as `cooked`, and the original string...
Really, you need something special to resolve these types correctly within 1. the language service 2. the Webpack loaders themselves There's always been a problem with importing from `.vue` files...
Would [RemoveUnused](http://mlton.org/RemoveUnused) be that optimization pass? Looks like the issue may partially be [documented in the comments](https://github.com/MLton/mlton/blob/01ad8549ebb63908a4fdd99689389cbff0a1d660/mlton/ssa/useless.fun#L36), but I don't know enough about the exact details.
@afc163 @zombieJ @John60676 any chance I can get a review on this PR? I expect it'll have a great downstream effect for you and your users!