Add a type-checking fast path for primitive types #755
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
Draft<T>
is applied to a large enum type, TypeScript has to do a lot of unnecessary structural comparisons to confirm that no element of the enum matchesFunction
,Date
,RegExp
, etc. Determining that they do matchstring
ornumber
, on the other hand, is trivial. This change splitsPrimitiveType
out ofAtomicObject
so that the fast path can be checked first.In microsoft/TypeScript#42824, this cut the check time from ~2.5 seconds to ~0.3 seconds.