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.
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
Make internal Layout and CouplingMap attrs slotted and adjust passes for fast access #7036
Make internal Layout and CouplingMap attrs slotted and adjust passes for fast access #7036
Changes from all commits
09f2486
8e15742
15e90e2
9268df5
550e8c6
e36efe3
adfe5ca
2f6d836
b7d7171
73d541a
0154230
bc92386
6809acf
b6bed17
0fc21a2
4e4da2b
bdba278
adccd4f
013c804
2e1db9c
95caec8
2ada462
009b005
8046f43
657d605
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
These things are (presumably) part of the old
FencedObject
stuff that appeared at the start of the transpiler. I'm guessing it's being removed because theLayout
became slotted and you didn't want to add the extra slot? Do we need theFencedPropertySet
stuff at all really - is it useful for error checking?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.
Yeah, I removed this because slots meant I couldn't add an arbitrary attribute to the
Layout
object and it didn't seem worth the slot especially since it wasn't universally used.I think we can look into deprecating the
FencedPropertySet
. At one time it was used to ensure that aTransformationPass
could not modify the property set but that restriction was removed in #4387 so I'm not sure anything needs it anymore.(edit: looking at the running passmanager object the flow controller gets a fenced property set to prevent a condition callable from modifying it. I'm not sure how important that is in practice, I've never seen an error like that come up before)
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.
Sounds sensible to me!