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
First off, those people are targeting ES3 environments, they need some sort of break.
Well even the compiler was restricted to ES3, and we could've made our lives easier by setting that as the lib instead of yelling at them not to use .map and .filter and .reduce
Add AST/checking support before we add .d.ts emit support
Add .js emit support later on.
Maybe flip the name to modernClassFieldEmit?
Can you make it depend on the target?
Feels weird?
Need a good way to evangelize the change if we do this, but the truth is that this is just slower and doesn't actually match our mental model of how the feature should work.
The text was updated successfully, but these errors were encountered:
Refactor to Named Parameters
#23552
async
refactoring does have some sort of bailout case.strictBindCallApply
is the only place whereWell it's the same problem as looking for all references of subtypes
Yeah, but you can always rename parameters
this
parameterses3.d.ts
#28372
lib
instead of yelling at them not to use.map
and.filter
and.reduce
Omit
inlib.d.ts
#29254
Omit
s that had different behavior - and it would conflict with a global.Omit
that are duplicated over DefinitelyTypedExclude
on a generic, so maybe you want to wait for negated types?Loosening restriction on
Array
methods taking predicates#27509
{} | null | undefined
is wrong, move tounknown
filter
now allowsany
which means you can not returnfilter
toboolean
orunknown
, notany
.any
tounknown
is reasonable.find
andfilter
being different stinks.Handling class fields breaking changes
#27644
Interesting ideas
.d.ts
emit support.js
emit support later on.modernClassFieldEmit
?The text was updated successfully, but these errors were encountered: