-
Notifications
You must be signed in to change notification settings - Fork 369
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
[Merged by Bors] - feat: renaming symmetric MvPolynomials #11251
Conversation
Co-authored-by: Junyan Xu <[email protected]>
/-- `MvPolynomial.rename` induces an isomorphism between the symmetric subalgebras. -/ | ||
def rename_symmetricSubalgebra [CommSemiring R] (e : σ ≃ τ) : | ||
symmetricSubalgebra σ R ≃ₐ[R] symmetricSubalgebra τ R := | ||
AlgEquiv.ofAlgHom | ||
(((rename e).comp (symmetricSubalgebra σ R).val).codRestrict _ <| fun x => x.2.rename e) | ||
(((rename e.symm).comp <| Subalgebra.val _).codRestrict _ <| fun x => x.2.rename e.symm) | ||
(AlgHom.ext <| fun p => Subtype.ext <| by simp) | ||
(AlgHom.ext <| fun p => Subtype.ext <| by simp) |
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.
Do we have any kind of two-sided restriction for AlgEquiv
s? If not, do we have an API we could copy from LinearEquiv
or RingEquiv
or MulEquiv
?
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.
Not that I could find quickly
bors merge |
bors r- |
Canceled. |
bors merge |
bors delegate+ |
✌️ Ruben-VandeVelde can now approve this pull request. To approve and merge a pull request, simply reply with |
Co-authored-by: Junyan Xu <[email protected]>
Pull request successfully merged into master. Build succeeded: |
Co-authored-by: Junyan Xu <[email protected]>
Co-authored-by: Junyan Xu <[email protected]>
Co-authored-by: Junyan Xu <[email protected]>
Co-authored-by: Junyan Xu <[email protected]>
Co-authored-by: Junyan Xu <[email protected]>
Co-authored-by: Junyan Xu <[email protected]>
Co-authored-by: Junyan Xu [email protected]