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
Motivation Today, if you have a value of type 'any', dotting off of the value and requesting members for completion will return nothing back. The original motivation for this was that we should never risk giving users incorrect completions. This is great for a fully typed TypeScript project. However, for those migrating to TypeScript, as well as those who need to drop down to any fairly frequently
Instructions Self-assign an issue from this list: https://github.com/Microsoft/TypeScript/labels/Migrate-a-thon. Each includes a short description of what might be involved and the approximate size. If you don't like any of these and want to pick your own, just log a new bug and tag it Migrate-a-thon. Fork the repo (into your own account) Start porting! If you're looking for some other project, I
this type guards (#5906) Some unaddressed concerns in PR. Differences between parameter/this type guards Parameter type guards check against type of parameters this type-guards tied to a signature `this type-guards allowed on properties Rationale for allowing on properties is we needed to allow them for get-accessors. Type-compatibility Narrowing logic identifies when a method gets called or a pro
Since we updated from TS server 1.6 to 1.7 we notice sporadic crashes in the TS server for our VS Code code base that has around 1100 typescript files in one project. When I compare 1.6 with 1.7 I notice that you changed the strategy for watching for file changes from fs.watchFile to fs.watch. The latter is recommended because it leverages native file watching while the former is polling for chang
Linting Linting is now turned on in the CI build 🎉 Can we make TSLint part of the build? Yes. Make it part of ‘runtests’ Simple reachability checks Done as part of the binder Cheap in terms of perf ~Couple hundred LOC Found two bugs in the compiler Has some checks for e.g. while(true), but nothing extra-fancy Does not include definite assignment Need a faster implementation of Set to do this quic
Planned for discussion today Suggestion: Add the nameof compile-time operator to convert property and function names into strings #1579 nameof operator Contextual typing of object literal getters not working for return expressions #1611 contextually type getter return statements in object literal methods Support proposed ES Rest/Spread properties #2103 rest/spread object properties (Stage 2 ES7 pr
Intersection of abstract types have non-abstract constructors (#4559) What if one is abstract and one isn't? Runtime semantics could go either way really Just make it concrete Inference from 'this' property assignments in constructors (#4955) First up: Should we do this for TypeScript? Pro: Consistent with what we've done before Con: Bifurcates the universe in a weird way This is exactly analogous
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く