[Merged by Bors] - refactor: make several NonUnitalAlgHom definitions take a particular algebra homomorphism - #43579
Conversation
…er} take in a concrete morphism instead and fix associated theorems
PR summary c31a893819Import changes for modified filesNo significant changes to the import graph Import changes for all files
|
Co-authored-by: Monica Omar <23701951+themathqueen@users.noreply.github.com>
Co-authored-by: Monica Omar <23701951+themathqueen@users.noreply.github.com>
themathqueen
left a comment
There was a problem hiding this comment.
Looks good! Thanks!
maintainer delegate
|
🚀 Pull request has been placed on the maintainer queue by themathqueen. |
Co-authored-by: Monica Omar <23701951+themathqueen@users.noreply.github.com>
…algebra homomorphism (#43579) as opposed to a `NonUnitalAlgHomClass`. Specifically, this PR changes `NonUnitalSubalgebra.{map, comap}` as well as `NonUnitalAlgHom.{range,rangeRestrict,codRestrict,equalizer}`. Since this removes all uses of a bundled morphism class, we also remove the assocated variable lines and align them with standard mathlib style. Adapt (almost) all theorems about them to take in a concrete morphism also. This follows the general patterns established in #31365: > we should restrict definitions to explicit morphisms, instead of morphism classes in order to avoid proliferating definitions. > Given a definition Bar that takes FooHom as an argument, a theorem whose statement involves Bar should only ever be written for FooHoms and never FooHomClasses. Indeed in the latter case, the statement would require the coercion from the morphism class to the morphism, thereby making it less general.
|
Build failed: Fix if necessary, and then someone with permission can run |
|
CI error looks intermittent and unrelated: |
…algebra homomorphism (#43579) as opposed to a `NonUnitalAlgHomClass`. Specifically, this PR changes `NonUnitalSubalgebra.{map, comap}` as well as `NonUnitalAlgHom.{range,rangeRestrict,codRestrict,equalizer}`. Since this removes all uses of a bundled morphism class, we also remove the assocated variable lines and align them with standard mathlib style. Adapt (almost) all theorems about them to take in a concrete morphism also. This follows the general patterns established in #31365: > we should restrict definitions to explicit morphisms, instead of morphism classes in order to avoid proliferating definitions. > Given a definition Bar that takes FooHom as an argument, a theorem whose statement involves Bar should only ever be written for FooHoms and never FooHomClasses. Indeed in the latter case, the statement would require the coercion from the morphism class to the morphism, thereby making it less general.
|
Build failed: Fix if necessary, and then someone with permission can run |
|
bors r+ |
…algebra homomorphism (#43579) as opposed to a `NonUnitalAlgHomClass`. Specifically, this PR changes `NonUnitalSubalgebra.{map, comap}` as well as `NonUnitalAlgHom.{range,rangeRestrict,codRestrict,equalizer}`. Since this removes all uses of a bundled morphism class, we also remove the assocated variable lines and align them with standard mathlib style. Adapt (almost) all theorems about them to take in a concrete morphism also. This follows the general patterns established in #31365: > we should restrict definitions to explicit morphisms, instead of morphism classes in order to avoid proliferating definitions. > Given a definition Bar that takes FooHom as an argument, a theorem whose statement involves Bar should only ever be written for FooHoms and never FooHomClasses. Indeed in the latter case, the statement would require the coercion from the morphism class to the morphism, thereby making it less general.
|
Pull request successfully merged into master. Build succeeded: |
as opposed to a
NonUnitalAlgHomClass.Specifically, this PR changes
NonUnitalSubalgebra.{map, comap}as well asNonUnitalAlgHom.{range,rangeRestrict,codRestrict,equalizer}.Since this removes all uses of a bundled morphism class, we also remove the assocated variable lines
and align them with standard mathlib style.
Adapt (almost) all theorems about them to take in a concrete morphism also.
This follows the general patterns established in #31365:
Continuation of #43377.