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
Remove leaf operations which have no side-effects #3252
Comments
@jakemac53 please evaluate and determine if this gives any benefit after |
Definitely the change_* booleans get filtered out by dart2js if the value is never used. |
@yjbanov is this still relevant based on the changes coming? |
Sorry, I fixed it in #3361 by accident. I am reassigning this to myself. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
There are a lot of statements in code which only make sense if there is a next item following. If it is a leaf they should be removed.
Example:
Notice the else and assignment at the end. This is only needed if there would be a next item dereferencing it..
should be:
This requires some form of detecting leaves and stripping out the vars which are used of chaining.
The text was updated successfully, but these errors were encountered: