Simplify and apply field sensitivity before value-set-deref #4949
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.
This means that any member-of-symbol constructs introduced by a nested dereference,
such as
x->y ==> (x == &o1 ? o1 : o2).y, can be simplified to produce e.g.(x == &o1 ? o1.y : o2.y) ==> (x == &o1 ? o1..y : o2..y). value_set_dereferencet willthen special-case the if-expression, dereferencing the inner
o1..yando2..yindividually.In the best case where each has a single possible alias,
&o3and&o4respectively, weend up with
(x == &o1 ? &o3 : &o4), rather than the current result:let p = (x == &o1 ? o1 : o2).y in (p == &o3 ? o3 : o4).The net benefit: smaller expressions, and thanks to simpler expressions a higher chance that future simplification will succeed.