Repository navigation
compiler: Linearize Indexeds nested in other Indexeds' indices #3065
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
ggorman
wants to merge
1
commit into
main
Choose a base branch
from
fix-linearize-nested-guard
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's the wrong fix, Uxreplace should be fixed instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed the root cause is in
uxreplace:_uxreplace(symbolics/manipulation.py:80-83) returns a matched key's replacement verbatim, likexreplace, so withT[0, I[0,0,0], 0] -> TL0(0, I[0,0,0], 0)the innerI[0,0,0](also a key) is never visited.The catch is that any fix there turns the mapper from a simultaneous substitution into a transitive one somewhere, and
uxreplacehas ~86 call sites here and ~60 in PRO, so I'd like your view before picking one. I prototyped two (with the call-site resolution in this PR reverted, both fix the reported case and 3-level nesting, and the same set of suites passes, ~1230 tests):{x: x+1}still terminates). Changes simultaneous semantics, e.g.{x: y+1, y: x+1}ona[x,y,z]givesa[x+2, y+2, z]instead ofa[y+1, x+1, z]; ~7% slower on a uxreplace micro-benchmark._uxreplaceforIndexed, and only when key and replacement are bothIndexedsubstitute inside the replacement's indices. Everything else unchanged; the one behaviour change is{a[x,y,z]: b[x,y,z], x: y}ona[x,y,z]now givingb[y,y,z](wasb[x,y,z]). No measurable cost.Uxreplace(subs, nested=True)(Transformer already has anestedkwarg), used only by linearization. No change for anyone else, a bit more plumbing.I'd lean to B, but you know the callers better. Which would you prefer?