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] - chore: small splits of RingTheory.Ideal.Operations
; clean imports
#12090
Conversation
Maybe use |
af68c57
to
2cd4fc4
Compare
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.
maintainer merge
🚀 Pull request has been placed on the maintainer queue by Ruben-VandeVelde. |
bors merge |
…12090) This is based on seeing the import `RingTheory.Ideal.Operations` → `LinearAlgebra.Basis` on the [longest pole](https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/The.20long.20pole.20in.20mathlib/near/432898637). It feels like `Ideal.Operations` is a bit of a chokepoint for compiling Mathlib since it imports many files and is imported by many files. So splitting out a few obvious parts should help with compile times. Moreover, there are a bunch of imports that I could remove and have the file still compile: presumably these are (were) transitive dependencies that shake does not remove. The following results and their corollaries were split off: * `Ideal.basisSpanSingleton` * `Basis.mem_ideal_iff` * `Ideal.colon` In particular, now `Ideal.Operations` should no longer need to know about `Basis` or submodule quotients.
Pull request successfully merged into master. Build succeeded: |
RingTheory.Ideal.Operations
; clean importsRingTheory.Ideal.Operations
; clean imports
This PR was supposed to be simultaneous with #12090 but I got ill last week. This is based on seeing the import `Algebra.Algebra.Subalgebra.Basic → RingTheory.Ideal.Operations` on the [longest pole](https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/The.20long.20pole.20in.20mathlib/near/432898637). It feels like `Ideal.Operations` should not be needed to define the notion of subalgebra, only to construct some interesting examples. So I removed the import and split off anything that wouldn't fit. The following results and their corollaries were split off: * `Subalgebra.prod` * `Subalgebra.iSupLift` * `AlgHom.ker_rangeRestrict` * `Subalgebra.mem_of_finset_sum_eq_one_of_pow_smul_mem` Co-authored-by: Anne Baanen <Vierkantor@users.noreply.github.com>
This PR was supposed to be simultaneous with #12090 but I got ill last week. This is based on seeing the import `Algebra.Algebra.Subalgebra.Basic → RingTheory.Ideal.Operations` on the [longest pole](https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/The.20long.20pole.20in.20mathlib/near/432898637). It feels like `Ideal.Operations` should not be needed to define the notion of subalgebra, only to construct some interesting examples. So I removed the import and split off anything that wouldn't fit. The following results and their corollaries were split off: * `Subalgebra.prod` * `Subalgebra.iSupLift` * `AlgHom.ker_rangeRestrict` * `Subalgebra.mem_of_finset_sum_eq_one_of_pow_smul_mem` Co-authored-by: Anne Baanen <Vierkantor@users.noreply.github.com>
…12090) This is based on seeing the import `RingTheory.Ideal.Operations` → `LinearAlgebra.Basis` on the [longest pole](https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/The.20long.20pole.20in.20mathlib/near/432898637). It feels like `Ideal.Operations` is a bit of a chokepoint for compiling Mathlib since it imports many files and is imported by many files. So splitting out a few obvious parts should help with compile times. Moreover, there are a bunch of imports that I could remove and have the file still compile: presumably these are (were) transitive dependencies that shake does not remove. The following results and their corollaries were split off: * `Ideal.basisSpanSingleton` * `Basis.mem_ideal_iff` * `Ideal.colon` In particular, now `Ideal.Operations` should no longer need to know about `Basis` or submodule quotients.
This PR was supposed to be simultaneous with #12090 but I got ill last week. This is based on seeing the import `Algebra.Algebra.Subalgebra.Basic → RingTheory.Ideal.Operations` on the [longest pole](https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/The.20long.20pole.20in.20mathlib/near/432898637). It feels like `Ideal.Operations` should not be needed to define the notion of subalgebra, only to construct some interesting examples. So I removed the import and split off anything that wouldn't fit. The following results and their corollaries were split off: * `Subalgebra.prod` * `Subalgebra.iSupLift` * `AlgHom.ker_rangeRestrict` * `Subalgebra.mem_of_finset_sum_eq_one_of_pow_smul_mem` Co-authored-by: Anne Baanen <Vierkantor@users.noreply.github.com>
…12090) This is based on seeing the import `RingTheory.Ideal.Operations` → `LinearAlgebra.Basis` on the [longest pole](https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/The.20long.20pole.20in.20mathlib/near/432898637). It feels like `Ideal.Operations` is a bit of a chokepoint for compiling Mathlib since it imports many files and is imported by many files. So splitting out a few obvious parts should help with compile times. Moreover, there are a bunch of imports that I could remove and have the file still compile: presumably these are (were) transitive dependencies that shake does not remove. The following results and their corollaries were split off: * `Ideal.basisSpanSingleton` * `Basis.mem_ideal_iff` * `Ideal.colon` In particular, now `Ideal.Operations` should no longer need to know about `Basis` or submodule quotients.
This PR was supposed to be simultaneous with #12090 but I got ill last week. This is based on seeing the import `Algebra.Algebra.Subalgebra.Basic → RingTheory.Ideal.Operations` on the [longest pole](https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/The.20long.20pole.20in.20mathlib/near/432898637). It feels like `Ideal.Operations` should not be needed to define the notion of subalgebra, only to construct some interesting examples. So I removed the import and split off anything that wouldn't fit. The following results and their corollaries were split off: * `Subalgebra.prod` * `Subalgebra.iSupLift` * `AlgHom.ker_rangeRestrict` * `Subalgebra.mem_of_finset_sum_eq_one_of_pow_smul_mem` Co-authored-by: Anne Baanen <Vierkantor@users.noreply.github.com>
This is based on seeing the import
RingTheory.Ideal.Operations
→LinearAlgebra.Basis
on the longest pole. It feels likeIdeal.Operations
is a bit of a chokepoint for compiling Mathlib since it imports many files and is imported by many files. So splitting out a few obvious parts should help with compile times. Moreover, there are a bunch of imports that I could remove and have the file still compile: presumably these are (were) transitive dependencies that shake does not remove.The following results and their corollaries were split off:
Ideal.basisSpanSingleton
Basis.mem_ideal_iff
Ideal.colon
In particular, now
Ideal.Operations
should no longer need to know aboutBasis
or submodule quotients.