Conversation
Member
|
Did you check whether this impacts performance, particularly in the binder? The existing casts have zero run-time cost (because they're compiled away), but the changes you are introducing do, and this is a very time critical function. Also, eventually we're going to switch the I'd prefer just leaving things the way there are here. |
Contributor
|
I am not sure i see much value in this reorganization. the type assertions do not get removed, they just reorganized, but now we have some additional code to execute at runtime. closing for now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Use one cast for each node kind, not one cast per property.