-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design Meeting Notes, 8/12/2016 #10307
Comments
Performance Optimization using "Slow Objects"We've achieved meaningful performance gains in #10270 & #10298 (~15% faster) through
This means that TypeScript as a compiler could not run on ES3 due to use of
ConclusionDrop ES3 host support. **NOTE that this DOES NOT mean we are dropping support for ES3 targets. Allowing UMD globals in modules (#10178)Issue: people were taking advantage of globals being introduced even though they were using modules.
ConclusionNiche case, let's not do anything. Downlevel Generators
ConclusionCan't ship something that will only sometimes work. Narrowing from
|
@DanielRosenwasser can you clarify what you mean by "Symbol.iterator may not be around" and how that differs from a Promise polyfill may not be around. |
I was really... surprised... by this. This is really confusing! |
There is #12346. Does it mean generators will be transpiled to ES3/ES5? |
yes. in TS 2.2 |
Object.create(null)
to produce maps increases overall perf ~15-20% and decreases memory ~20%hasOwnProperty
delete
operator) to get better perffor/of
) doesn't work: { }
/: any
type annotations on catch variables #10000 / Can't narrow error type in catch clause #8677/cc @DanielRosenwasser who I think has some better notes on the last two
The text was updated successfully, but these errors were encountered: