-
Notifications
You must be signed in to change notification settings - Fork 6
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
Integrate resolve_extension_ops into validate / infer_and_validate #508
Comments
This was referenced Sep 8, 2023
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 12, 2023
This turns out to be pretty trivial, as ExtensionRegistry looks exactly the same as HashMap as far as this code is concerned. Most of the effort here is in fixing up imports and doclinks. This addresses the first (easy) part of #508 but the second remains as an issue/question for discussion, not attempting to resolve that here.
acl-cqc
changed the title
Update
Integrate resolve_exetsion_ops into validate / infer_and_validate
Sep 13, 2023
resolve_extension_ops
w/ ExtensionRegistry; integrate into validation??
acl-cqc
changed the title
Integrate resolve_exetsion_ops into validate / infer_and_validate
Integrate resolve_extension_ops into validate / infer_and_validate
Sep 13, 2023
acl-cqc
added a commit
that referenced
this issue
Sep 28, 2023
This was done in #603, renaming |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Moreover,
resolve_extension_ops
was intended to use after loading the Hugr, but the checks in here that saved Signatures match the Signatures that would be computed, would make sense to do in validation.validate
andinfer_and_validate
are also the main entry points for when you do have an ExtensionRegistry. Invalidate
the Hugr is immutable but we could do this ininfer_and_validate
just prior to validation....The text was updated successfully, but these errors were encountered: