Conversation
evaleev
added
enhancement
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
evaleev
force-pushed
the
498-contextstrict_braket_symmetry-can-be-misleading
branch
from
16fb194 to
98d6902
Compare
Krzmbrzl
approved these changes
Feb 18, 2026
evaleev
deleted the
498-contextstrict_braket_symmetry-can-be-misleading
branch
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
rename
Context::strict_braket_symmetryintroduced in #495 to emphasize that the bra-ket TN strictness checks are assertions, and will be disabled completely if SeQuant is configured withSEQUANT_ASSERT_BEHAVIOR=IGNORE