The mathlib review queue

Welcome to the mathlib review page. Everybody's help with reviewing is appreciated. Reviewing contributions is important, and everybody is welcome to review pull requests! If you're not sure how, the pull request review guide is there to help you.
This page is the main reviewer-facing queue: if a PR is ready for review, it belongs here. The triage page contains additional triage-oriented views, but it is not the primary review queue.
This page contains tables of

This dashboard was last updated on: November 22, 2026 at 14:59 UTC

Review queue

Number Author Title Description Labels +/- Modified files (first 100) 📝 💬 All users who commented or reviewed Assignee(s) Updated Last status change total time in review blocks
33928 jsm28
author:jsm28
feat(Combinatorics/Tiling/TileSet): indexed families of tiles Define the type `TileSet` for indexed families of tiles (in a discrete context), and some associated definitions (including `symmetryGroup`) and API lemmas. `TileSet` can be used for tilings of the whole space; for tilings of part of the space; for patches of tiles (extracted from a tiling by considering tiles meeting some set of points, or considered on their own without extracting from a tiling); for multiple tilings (covering the space more than once). In particular, the fact that people study multiple tilings provides a clear justification for using indexed families rather than sets of tiles, and basic definitions and API lemmas generally work for all these different uses of `TileSet` (sometimes with weak constraints such as tiles being finite, nonempty and only having finitely many tiles meeting any point of the space). Definitions for saying e.g. "this `TileSet` is a tiling of the whole space" are to be included in subsequent files in subsequent PRs. From AperiodicMonotilesLean. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 460/0 Mathlib.lean,Mathlib/Combinatorics/Tiling/TileSet.lean 2 23 ['Parcly-Taxel', 'b-mehta', 'eric-wieser', 'github-actions', 'jsm28', 'vihdzp'] nobody
187-50353
6 months ago
312-67461
312 days ago
312-67406
312 days
0
36719 NoneMore
author:NoneMore
feat(ModelTheory): add `PartialType` for first-order theories This PR adds the definitions of partial types over theories and over parameter sets, and proves several equivalent characterizations. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #36667 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-logic new-contributor 432/17 Mathlib.lean,Mathlib/ModelTheory/PartialTypes.lean,Mathlib/ModelTheory/Semantics.lean 3 7 ['NoneMore', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'vihdzp'] nobody
129-48075
4 months ago
129-48596
129 days ago
137-31502
137 days
0
42513 plp127
author:plp127
feat(ModelTheory): typeclass for theory to have nonempty models We add a typeclass for a theory to have nonempty models. We provide instances for `nonemptyTheory`, `infiniteTheory`, and `completeTheory`. --- - [x] depends on: #42508 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-logic 51/0 Mathlib/ModelTheory/Algebra/Ring/Basic.lean,Mathlib/ModelTheory/Semantics.lean 2 2 ['github-actions', 'mathlib-dependent-issues'] nobody
107-9393
3 months ago
107-16872
107 days ago
107-19367
107 days
1
43123 harahu
author:harahu
chore(Testing): tidy markdown headers This PR ensures files in `Mathlib/Testing` have one and only one H1 header. In the cases where the file did not already have an obvious H1 header candidate, a new header was authored by Claude Opus 5. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) 5/1 Mathlib/Testing/Plausible/Functions.lean,Mathlib/Testing/Plausible/Sampleable.lean,Mathlib/Testing/Plausible/Testable.lean 3 1 ['github-actions'] nobody
88-21807
2 months ago
88-22541
88 days ago
88-22486
88 days
0
42590 AntoineduFresne
author:AntoineduFresne
feat(Order/UpperLower/Closure): the upper and lower closures of a maximal antichain cover the order I add `IsMaxAntichain.upperClosure_union_lowerClosure`. It says that the upper and lower closures of a maximal antichain cover the whole order. I put it right after `ordConnected_iff_upperClosure_inter_lowerClosure`, next to `upperClosure_inter_lowerClosure`, which seems the right spot. The lemma is about antichains, so `Mathlib/Order/Antichain.lean` would have looked like the natural file to modify, but `upperClosure` is defined in `Mathlib/Order/UpperLower/Closure.lean`, which imports `Mathlib.Order.Interval.Set.OrdConnected`, which imports `Mathlib.Order.Antichain`. So to avoid an import loop I put it in `Closure.lean`. I split this out of #40741, where a reviewer suggested it. Nothing in that PR uses the lemma. t-order new-contributor 13/0 Mathlib/Order/Antichain.lean,Mathlib/Order/UpperLower/Closure.lean 2 12 ['AntoineduFresne', 'Ruben-VandeVelde', 'SnirBroshi', 'github-actions', 'tdwag123'] nobody
82-23722
2 months ago
82-62182
82 days ago
98-19162
98 days
0
43407 thomaskwaring
author:thomaskwaring
feat(Order/Hom/CompleteLattice): order adjoints for `{sSup/sInf}Hom` This PR defines the order adjoint of a `sSup` or `sInf` preserving function, which defines an equivalence `sSupHom α β ≃ sInfHom β α`, and an order isomorphism `sSupHom α β ≃o (sInfHom β α)ᵒᵈ` (plus duals). --- I'm not 100% certain on the naming here, and would very much appreciate any advice & help with `to_dual` — an alternative option is `upperAdj` and `lowerAdj`, which `to_dual`-ises automatically. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 69/0 Mathlib/Order/Hom/CompleteLattice.lean 1 4 ['SnirBroshi', 'github-actions', 'thomaskwaring'] nobody
79-13818
2 months ago
79-83592
79 days ago
79-83537
79 days
0
43507 SnirBroshi
author:SnirBroshi
fix(Combinatorics/SimpleGraph): namespace `completeBipartiteGraph` under `SimpleGraph` and fix the names of `CompleteBipartiteGraph.bicoloring` and `CompleteBipartiteGraph.chromaticNumber`. --- Moved the `namespace SimpleGraph` in `Basic.lean` to right after the definition of `SimpleGraph`, to avoid putting things outside of the namespace. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 29/20 Mathlib/Combinatorics/SimpleGraph/Basic.lean,Mathlib/Combinatorics/SimpleGraph/Coloring/Vertex.lean 2 1 ['github-actions'] nobody
76-32403
2 months ago
76-47303
76 days ago
76-47248
76 days
0
43360 metakunt
author:metakunt
feat(RingTheory/AdjoinRoot/MapCyclotomic): define algebra isomorphism isAdjoinRoot for roots of unity From #43343 Section is deliberately not exposed. I think the API developed should be enough. But if needed it can always be exposed later. t-ring-theory LLM-generated 111/7 Mathlib.lean,Mathlib/RingTheory/AdjoinRoot/MapCyclotomic.lean,Mathlib/RingTheory/IsAdjoinRoot.lean 3 19 ['github-actions', 'mathlib-bors', 'metakunt', 'tb65536'] nobody
75-79013
2 months ago
75-81000
75 days ago
77-73521
77 days
0
43401 thomaskwaring
author:thomaskwaring
feat(Order): counterparts of `iSupIndep.disjoint_biSup_biSup{'}` for `sSup` Transfer `iSupIndep.disjoint_biSup_biSup'` and `iSupIndep.disjoint_biSup_biSup` to `sSupIndep.disjoint_sSup_sSup'` and `sSupIndep.disjoint_sSup_sSup`. Also add the supporting rewrite lemma `biSup_preimage`, roughly dual to `sSup_image`. --- Used downstream for working with `Partition`, whose fields are stated in terms of `sSupIndep`. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 22/0 Mathlib/Order/CompactlyGenerated/Basic.lean,Mathlib/Order/CompleteLattice/Basic.lean,Mathlib/Order/SupIndep.lean 3 5 ['SnirBroshi', 'github-actions', 'mathlib-merge-conflicts'] nobody
74-27026
2 months ago
74-30137
74 days ago
79-35402
79 days
0
43672 javgomzar
author:javgomzar
chore(LinearAlgebra/Matrix): add push tags to transpose lemmas --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra new-contributor
label:t-algebra$
6/5 Mathlib/LinearAlgebra/Matrix/Defs.lean 1 3 ['github-actions'] nobody
73-1877
2 months ago
73-4411
73 days ago
73-4356
73 days
0
42424 lydia-schiff
author:lydia-schiff
feat(Order/Partition/Finpartition): transport a set partition along a type equivalence - Adds `Finpartition.congr` to transport a `Finpartition` along a type equivalence. - We can use `Finpartition.map` if we have an order-iso, and the equivalence induces one via the new `Finset.congrOrderIso` which is based on `Equiv.finsetCongr`. - Includes parts, card, refl, and round-trip lemmas. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - `Equiv.finsetCongr` already gives us an equivalence of Finsets, so the new `Finset.congrOrderIso` just adds that the power-set lattice structure is also preserved. - Includes lemmas showing that the parts are e-images of the old ones, card is preserved, and refl + round-trip for the equivalence. - The cardinality lemma was the original motivation from some work on Stirling numbers, but I thought that `Finpartition.congr` and `Finset.congrOrderIso` seemed reusable and hopefully useful in their own right, and thought it would make a good first contribution. - Zulip thread about naming and placement [here](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/.60Finpartition.2Econgr.60.20.E2.80.94.20naming.20.26.20placement) - I used Claude Opus 4.8 to help draft the proofs and explore the API. I have spent several weeks making sure I understand and can justify every line and I've learned a lot which is great. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order LLM-generated new-contributor 61/0 Mathlib/Data/Finset/Image.lean,Mathlib/Order/Partition/Finpartition.lean 2 6 ['github-actions', 'lydia-schiff', 'mathlib-merge-conflicts'] nobody
72-71434
2 months ago
72-75891
72 days ago
99-60398
99 days
0
43766 hawkrobe
author:hawkrobe
feat(LinearAlgebra/SymmetricAlgebra): functoriality --- Add `SymmetricAlgebra` functoriality (parallel to `TensorAlgebra` and `ExteriorAlgebra`) [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
31/0 Mathlib/LinearAlgebra/SymmetricAlgebra/Basic.lean 1 1 ['github-actions'] nobody
70-23291
2 months ago
70-24808
70 days ago
70-24753
70 days
0
43767 hawkrobe
author:hawkrobe
feat(LinearAlgebra/SymmetricAlgebra): symmetric algebra is graded --- I also followed `TensorAlgebra` and `ExteriorAlgebra` here. I used Claude to initialize the proof. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
55/0 Mathlib.lean,Mathlib/LinearAlgebra/SymmetricAlgebra/Grading.lean 2 1 ['github-actions'] nobody
70-21911
2 months ago
70-22690
70 days ago
70-22635
70 days
0
40782 tb65536
author:tb65536
feat(Combinatorics/SimpleGraph/Coloring/EdgeLabeling): add predicates for monochromatic subsets This PR adds predicates for monochromatic subsets, in preparation for Ramsey theory. Co-authored-by: Bhavik Mehta <bhavikmehta8@gmail.com> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 143/0 Mathlib/Combinatorics/SimpleGraph/Coloring/EdgeLabeling.lean 1 28 ['SnirBroshi', 'YaelDillies', 'b-mehta', 'github-actions', 'tb65536'] nobody
68-70406
2 months ago
68-71207
68 days ago
145-26366
145 days
0
43820 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Maps): dualize `Embedding.completeGraph` and `Copy.topEmbedding` Also `Copy.topEmbedding` doesn't need a `Copy`, it can use a `Hom`, unlike its dual `Copy.botEmbedding`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 115/15 Mathlib/Combinatorics/SimpleGraph/Clique.lean,Mathlib/Combinatorics/SimpleGraph/Copy.lean,Mathlib/Combinatorics/SimpleGraph/Maps.lean 3 1 ['github-actions'] nobody
68-48348
2 months ago
68-50546
68 days ago
68-50491
68 days
0
38499 SnirBroshi
author:SnirBroshi
feat(Order/Hom/Basic): `Relation.Map`/`Function.bicompl` form an order isomorphism between relations For injective functions `f` and `g`, `Relation.Map · f g` is an order embedding between relations. For surjective functions `f` and `g`, `Function.bicompl · f g` is an order embedding between relations. For bijective functions `f` and `g`, `Relation.Map · f g` and `Function.bicompl · f g` form an order isomorphism between relations. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #38432 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 46/0 Mathlib/Order/Hom/Basic.lean 1 7 ['SnirBroshi', 'github-actions', 'mathlib-dependent-issues', 'plp127', 'wwylele'] nobody
68-36027
2 months ago
72-73504
72 days ago
76-84453
76 days
0
43793 justus-springer
author:justus-springer
doc(Algebra/Group/SelfInv): extend module docstring Follow-up to #42611. Explains the original motivation for this. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
7/0 Mathlib/Algebra/Group/SelfInv.lean 1 8 ['SnirBroshi', 'YaelDillies', 'eric-wieser', 'github-actions', 'justus-springer'] nobody
68-30791
2 months ago
68-79888
68 days ago
69-2692
69 days
0
41304 plp127
author:plp127
chore(Data/Set/Lattice): `Sort*` polymorphism Generalize some theorems from `Type*` to `Sort*`. --- - [x] depends on: #39857 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 30/25 Mathlib/Data/Set/Lattice/Bounded.lean,Mathlib/Data/Set/Lattice/Indexed.lean 2 6 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
67-66714
2 months ago
67-68827
67 days ago
67-82710
67 days
0
43819 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/DeleteEdges): morphisms between `deleteEdges` graphs Accepting two sets and a proof of `Sym2.map f ⁻¹' t ⊆ s` lets us use the morphisms with `Set.preimage` or `Set.image` or anything else that's convenient. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 74/1 Mathlib/Combinatorics/SimpleGraph/Copy.lean,Mathlib/Combinatorics/SimpleGraph/DeleteEdges.lean 2 5 ['SnirBroshi', 'b-mehta', 'github-actions'] nobody
67-26895
2 months ago
67-27089
67 days ago
67-71606
67 days
2
43861 SnirBroshi
author:SnirBroshi
chore(Algebra/Order/Achimedean/Class): use `inferInstanceAs%` for `LinearOrder MulArchimedeanClass` --- The motivation is the `TODO`; I don't know if core's `inferInstanceAs` elaborator would be better here. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
1/2 Mathlib/Algebra/Order/Archimedean/Class.lean 1 1 ['github-actions'] nobody
67-25458
2 months ago
67-26268
67 days ago
67-26213
67 days
0
43957 thomaskwaring
author:thomaskwaring
feat(Order/Hom): congruence of order homs by order isos Order isomorphisms between domains and codomains induce equivalences between types of order homomorphisms: `{Sup/Inf/Lattice/SupBot/InfTop/BoundedLattice/sSup/sInf/Frame/CompleteLattice}Hom`. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 78/0 Mathlib/Order/Hom/BoundedLattice.lean,Mathlib/Order/Hom/CompleteLattice.lean,Mathlib/Order/Hom/Lattice.lean 3 1 ['github-actions'] nobody
64-18214
2 months ago
64-22898
64 days ago
64-22870
64 days
1
43901 vlad902
author:vlad902
feat(AffineSpace): characterize affine subspaces of dimension 0 and 1 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-convex-geometry 94/10 Mathlib/Algebra/Order/Monoid/Unbundled/WithTop.lean,Mathlib/LinearAlgebra/AffineSpace/Dimension.lean,Mathlib/Order/WithBot.lean 3 2 ['github-actions', 'vlad902'] nobody
63-80189
2 months ago
65-37200
65 days ago
65-42456
65 days
0
34078 joneugster
author:joneugster
feat(scripts/autolabel): add more label dependencies Add more label dependencies. --- - [x] depends on: #34948 - [x] depends on: #34949 - [x] depends on: #34066 - [x] depends on: #34079 - [x] depends on: #34677 - [x] depends on: #34678 - [x] depends on: #34952 - [x] depends on: #36242 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) CI 31/11 scripts/autolabel.lean 1 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
62-84238
2 months ago
95-59052
95 days ago
95-59282
95 days
0
43780 SashaIr
author:SashaIr
feat: q-analogs An implementation of q-analogs, q-binomials, and counting results. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics 965/0 Mathlib.lean,Mathlib/Combinatorics/QAnalog/Basic.lean,Mathlib/Combinatorics/QAnalog/Binomial.lean,Mathlib/Combinatorics/QAnalog/Counting.lean,Mathlib/Combinatorics/QAnalog/Subspace.lean 5 7 ['SashaIr', 'SnirBroshi', 'b-mehta', 'github-actions'] nobody
62-68314
2 months ago
69-66284
69 days ago
69-66585
69 days
0
38334 8e7
author:8e7
feat(Combinatorics/SimpleGraph/TreeDecomp): define tree decompositions Add definition for tree decompositions on simple graphs. Define the tree width of a simple graph and prove basic statements and conversions. ```lean structure TreeDecomp (G : SimpleGraph V) (W : Type) where /-- The set of vertices in each bag. -/ bag : W → Finset V /-- The graph adjacency relation of bags. -/ tree : SimpleGraph W /-- T must be a tree. -/ isTree : IsTree tree /-- All vertices in G must appear in some bag. -/ vertexCover : ∀ v : V, ∃ w : W, v ∈ bag w /-- For any edge (u, v) in G, there is a bag containing both u and v. -/ edgeCover ⦃u v : V⦄ : G.Adj u v → ∃ w : W, u ∈ bag w ∧ v ∈ bag w /-- For any vertex v in G, the set of bags that contain v is preconnected. -/ connectedBags : ∀ v : V, (tree.induce ({w | v ∈ bag w})).Preconnected ``` AI Usage: Some proofs are written with the help of Claude Code, and everything has been manually reviewed. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #38027 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics LLM-generated 395/0 Mathlib.lean,Mathlib/Combinatorics/SimpleGraph/TreeDecomp.lean 2 42 ['8e7', 'SnirBroshi', 'YaelDillies', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
62-50355
2 months ago
119-38393
119 days ago
143-21673
143 days
1
44027 kim-em
author:kim-em
chore(RingTheory/Unramified/LocalRing): explain the backward.inferInstanceAs.wrap.data option This PR adds a comment explaining why `FormallyUnramified.isField_quotient_map_maximalIdeal` needs `set_option backward.inferInstanceAs.wrap.data false`, and that the option can be removed once https://github.com/leanprover/lean4/issues/13408 (Kernel error for `inferInstanceAs` with let declarations) is fixed. A fix is proposed in https://github.com/leanprover/lean4/pull/15245. 🤖 Prepared with Claude Code t-ring-theory 3/0 Mathlib/RingTheory/Unramified/LocalRing.lean 1 1 ['github-actions'] nobody
62-31802
2 months ago
62-33169
62 days ago
62-33114
62 days
0
43953 hasjack
author:hasjack
feat(Combinatorics/SimpleGraph/LapMatrix): bound Laplacian eigenvalues by `|V|` Prove that every Laplacian eigenvalue of a finite simple graph is at most the number of vertices, via comparison of the Rayleigh quotient with the complete graph. Also record the underlying quadratic-form bound `xᵀ L x ≤ |V| · ‖x‖²`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---` , otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) Adds `dotProduct_mulVec_lapMatrix_le_card` and `eigenvalues_lapMatrix_le_card` in `LapMatrix.lean` only. The claim is the uniform bound `λ ≤ |V|` for every indexed eigenvalue; it does not assert `|V| ∈ spectrum` for every graph. Searched existing LapMatrix API (PSD, `zero_mem_spectrum_lapMatrix`, `lapMatrix_top`) and did not find a card upper bound under another name. Happy to rename if a preferred lemma already exists. new-contributor t-combinatorics LLM-generated 37/1 Mathlib/Combinatorics/SimpleGraph/LapMatrix.lean,Mathlib/Data/Matrix/Mul.lean 2 61 ['Parcly-Taxel', 'SnirBroshi', 'github-actions', 'hasjack'] nobody
62-8267
2 months ago
62-55286
62 days ago
64-49367
64 days
0
43187 gaetanserre
author:gaetanserre
chore: tag some measurability lemmas with `fun_prop` Tag some measurability lemma with `fun_prop`. These lemmas were not tagged most likely because one of the subgoals was of the form `MeasurableSet ...`. However, tagging them and using `fun_prop (disch := measurability)` can close goals that require these lemmas. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) 3/0 Mathlib/MeasureTheory/MeasurableSpace/Basic.lean,Mathlib/MeasureTheory/MeasurableSpace/Constructions.lean,Mathlib/Probability/Kernel/Defs.lean 3 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
61-79932
2 months ago
61-81982
61 days ago
85-72752
85 days
0
43785 kim-em
author:kim-em
chore: point Order/Atoms deprecations at the right replacements This PR corrects the replacement named by three deprecations in `Mathlib/Order/Atoms.lean`. `IsStronglyCoatomic.of_wellFounded_gt`, `isAtomic_of_orderBot_wellFounded_lt` and `isCoatomic_of_orderTop_gt_wellFounded` all named `instIsStronglyAtomicOfWellFoundedLT`, which is neither coatomic nor the `IsAtomic`/`IsCoatomic` instance a user of those lemmas wants; they now name `instIsStronglyCoatomicOfWellFoundedGT`, `IsStronglyAtomic.isAtomic` and `IsStronglyCoatomic.toIsCoatomic`. A Lean nightly has grown a check comparing the type of a deprecated declaration against its replacement, which is how these surfaced. 🤖 Prepared with Claude Code https://claude.ai/code/session_01FEhDfMiCzEAX4QJdrALfQC t-order 3/3 Mathlib/Order/Atoms.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
61-46777
2 months ago
61-51133
61 days ago
63-69316
63 days
0
41541 felixpernegger
author:felixpernegger
chore: prefer `classical` over `open scoped Classical` in proofs In #41423 it came up that it is preferable to use `classical` in proofs instead of `open (scoped) Classical`, as its slightly easier to maintain. This PR replaces all such occurences where it can be reasonably done. This is likely my last PR about this topic. (I used Claude to fix some git issue, which is why it shows up in the commit) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) 111/58 Mathlib/Basic/Logic/Basic.lean,Mathlib/Logic/Function/Basic.lean,Mathlib/Order/Basic.lean,Mathlib/Order/Defs/PartialOrder.lean 4 5 ['felixpernegger', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] nobody
61-25603
2 months ago
61-31182
61 days ago
106-82384
106 days
0
44103 xiahongchi
author:xiahongchi
feat: equate derivatives of ordered functions at contact points This adds Fréchet-derivative and scalar-derivative lemmas saying that two everywhere-ordered real-valued functions have equal derivatives wherever they agree. The proof applies Fermat’s theorem to their nonnegative difference. This packages and generalizes the scalar envelope argument from Bryan Sanchez’s `NSBlwChain/Caveats/C2_Envelope.lean` at `Brsanch/ns-lean-proofs@b73f537d1646165fbdc0993c5b2e223355dc3469` (MIT). The new declarations elaborate under the released toolchain; compiling the current master file there reports only one pre-existing current-Lean field-notation incompatibility before the new code. Current-toolchain CI is authoritative. t-analysis new-contributor 20/0 Mathlib/Analysis/Calculus/LocalExtr/Basic.lean 1 2 ['github-actions'] nobody
60-49436
1 month ago
60-50695
60 days ago
60-50937
60 days
0
44064 mcdoll
author:mcdoll
chore: tag definitions with `fun_prop` No new lemmas are being tagged yet, just the definitions. To fix the build, some `measurability` attributes had to be changed to `fun_prop` and a test had to be adjusted. Only slightly controversial change could be the import of `FunProp` in `Mathlib/Logic/Function/Defs.lean`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> large-import 30/9 Mathlib/Analysis/BoxIntegral/Basic.lean,Mathlib/Analysis/Calculus/ContDiffHolder/Pointwise.lean,Mathlib/Logic/Function/Defs.lean,Mathlib/MeasureTheory/Function/LpSeminorm/Defs.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/AEStronglyMeasurable.lean,Mathlib/MeasureTheory/Integral/IntegrableOn.lean,Mathlib/MeasureTheory/Integral/IntervalIntegral/Basic.lean,Mathlib/Tactic/FunProp.lean,Mathlib/Topology/EMetricSpace/Lipschitz.lean,Mathlib/Topology/MetricSpace/Holder.lean,MathlibTest/FunPropMinimal.lean 11 1 ['github-actions'] nobody
60-36425
1 month ago
60-40797
60 days ago
60-50663
60 days
0
41565 grunweg
author:grunweg
chore: specify doc-strings of auto-generated additive declarations di… …rectly There's no need for add_decl_doc any more. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) 64/107 Mathlib/Algebra/Category/Grp/Basic.lean,Mathlib/Algebra/Group/Action/Basic.lean,Mathlib/Algebra/Group/Action/Defs.lean,Mathlib/Algebra/Group/Action/Hom.lean,Mathlib/Algebra/Group/Hom/Basic.lean,Mathlib/Algebra/Group/Subsemigroup/Basic.lean,Mathlib/Algebra/Notation/Defs.lean,Mathlib/Algebra/Order/BigOperators/Group/Finset.lean,Mathlib/GroupTheory/Finiteness.lean,Mathlib/MeasureTheory/Group/Action.lean,Mathlib/MeasureTheory/Measure/MeasureSpaceDef.lean,Mathlib/Topology/Algebra/ConstMulAction.lean 12 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
59-55804
1 month ago
59-58820
59 days ago
80-12362
80 days
0
44136 SnirBroshi
author:SnirBroshi
chore: clean up a few `have : Std.Symm`s and some other relation properties --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 10/26 Mathlib/Algebra/Group/Basic.lean,Mathlib/Analysis/Normed/Module/FiniteDimension.lean,Mathlib/Data/Finset/NoncommProd.lean,Mathlib/Data/List/MinMax.lean,Mathlib/Data/Multiset/Bind.lean,Mathlib/LinearAlgebra/LinearIndependent/Lemmas.lean,Mathlib/NumberTheory/Divisors.lean,Mathlib/Order/Preorder/Chain.lean,Mathlib/Topology/NatEmbedding.lean 9 1 ['Parcly-Taxel', 'github-actions'] nobody
58-76182
1 month ago
59-83609
59 days ago
59-84176
59 days
0
43197 SnirBroshi
author:SnirBroshi
feat(Order/Basic): relation properties of complement relations The complement turns `Refl` into `Irrefl`, `Total` into `Asymm`, and `Trichotomous` into `Antisymm`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 60/14 Mathlib/Basic/Rel/Separated.lean,Mathlib/Order/Antichain.lean,Mathlib/Order/Basic.lean,Mathlib/Topology/MetricSpace/MetricSeparated.lean 4 5 ['SnirBroshi', 'chenson2018', 'github-actions'] nobody
58-72259
1 month ago
58-76800
58 days ago
84-37904
84 days
0
42955 mpacholski
author:mpacholski
feat(diffgeo): add Hom-bundle support and fix pullback base points in T% elaborator # Changes ## `Mathlib/Geometry/Manifold/Notation.lean` * **Add support for pullback bundles:** Replaced the hardcoded bound variable `x` with the dynamically extracted argument `arg`, which allows for using elaborator `T%` with pullback bundles, where the base point lies in a different manifold, e.g. `v : Π (m : M), E₁ (b m)`, where `b : M → B`. * **Add support for Hom-bundles:** The elaborator now supports sections of Hom-bundles (`ContinuousLinearMap` between two fiber bundles, e.g. `ϕ : ∀ x, (E₁ x →L[𝕜] E₂ x`). It also supports the case where the base point lies in a different manifold (e.g. `ϕ : ∀ x, (E₁ (b x) →L[𝕜] E₂ (b x))`) * **Support nested `TangentSpace`:** Modified `findModelFiber?` to natively intercept `TangentSpace` applications and extract the model fiber at index 2. This prevents typeclass synthesis failures when `TangentSpace` is used inside a Hom-bundle. ## `MathlibTest/DifferentialGeometry/Notation/Basic.lean` * **Added tests for all the new usecases** this includes pullback bundles, Hom-bundles, pullback Hom-bundles, and Hom-bundles where one of the fibers is a `TangentSpace`. ## `Mathlib/Geometry/Manifold/VectorBundle/Hom.lean` * **Refactor `Hom.lean`:** Replaced verbose `TotalSpace.mk'` boilerplate in with the newly supported `T%` syntax (e.g. `MDiffAt[s] T% ϕ x` instead of `MDiffAt[s] (fun m ↦ TotalSpace.mk' (F₁ →L[𝕜] F₂) (E := fun (x : B) ↦ (E₁ x →L[𝕜] E₂ x)) (b m) (ϕ m)) x)` # Use of AI The help of AI was used in writing the code in `Mathlib/Geometry/Manifold/Notation.lean`. It was hence manually edited to simplify the code as much as possible. While the author is not yet an expert in metaprogramming in Lean, he is willing to learn and receive feedback, and put all the effort to understand the presented code. The code was carefully tested with different parts of it changed and removed to make sure that every line serves a purpose to provide the expected functionality. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-differential-geometry new-contributor LLM-generated 127/36 Mathlib/Geometry/Manifold/Notation.lean,Mathlib/Geometry/Manifold/VectorBundle/Hom.lean,MathlibTest/DifferentialGeometry/Notation/Basic.lean 3 5 ['github-actions', 'grunweg', 'mpacholski'] nobody
58-50352
1 month ago
93-85964
93 days ago
93-85909
93 days
3
44222 SamuelSchlesinger
author:SamuelSchlesinger
feat(Analysis/SpecialFunctions/Stirling): asymptotics of the central binomial coefficient Upstreaming `n.centralBinom ~ 4 ^ n / √(π * n)` and its `4 ^ n`-normalised corollaries, needed for a Razborov–Smolensky `AC⁰[p]` lower bound in a circuit-complexity formalization, together with the Catalan asymptotic `catalan n ~ 4 ^ n / (√π * n ^ (3 / 2))` as a first application in Mathlib. Drafted with Claude Code from my existing proof of the same statement, then revised by me against Mathlib conventions. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis LLM-generated new-contributor 85/1 Mathlib.lean,Mathlib/Analysis/SpecialFunctions/Stirling.lean,Mathlib/Combinatorics/Enumerative/Catalan/Asymptotics.lean 3 4 ['SamuelSchlesinger', 'github-actions'] nobody
57-31026
1 month ago
57-31947
57 days ago
57-31892
57 days
0
44184 kim-em
author:kim-em
feat(AlgebraicTopology): semilocally simply connected spaces This PR defines semilocally simply connected spaces: `SemilocallySimplyConnectedAt x` says `x` has a neighbourhood `U` in which every loop at `x` is nullhomotopic in the ambient space, with `SemilocallySimplyConnectedOn` and the class `SemilocallySimplyConnectedSpace`. It proves the equivalent formulations via the fundamental group (`semilocallySimplyConnectedAt_iff_range_eq_bot`: `π₁(U, x) → π₁(X, x)` is trivial) and via paths (`semilocallySimplyConnectedAt_iff_paths`), and that simply connected spaces are semilocally simply connected. Supporting additions: `Path.codRestrict`, groupoid lemmas relating homotopic paths to nullhomotopic loops (`Path.Homotopic.paths_homotopic_iff_loops_nullhomotopic` and friends), and `FundamentalGroup.map_fromPath` and `FundamentalGroup.map_range_eq_bot_iff`. This is the second of four PRs constructing the universal cover (split from https://github.com/leanprover-community/mathlib4/pull/38292). It is independent of the first. 🤖 Prepared with Claude Code t-topology LLM-generated 270/0 Mathlib.lean,Mathlib/AlgebraicTopology/FundamentalGroupoid/Basic.lean,Mathlib/AlgebraicTopology/FundamentalGroupoid/FundamentalGroup.lean,Mathlib/AlgebraicTopology/FundamentalGroupoid/SemilocallySimplyConnected.lean,Mathlib/Topology/Path.lean 5 1 ['github-actions'] nobody
57-5056
1 month ago
58-11717
58 days ago
58-11662
58 days
2
44241 thomaskwaring
author:thomaskwaring
feat(Basic/Rel): relation composition preserves unions Add the binary counterpart to `SetRel.comp_iUnion` and friends. t-data 6/0 Mathlib/Basic/Rel.lean 1 1 ['github-actions'] nobody
56-15963
1 month ago
56-18207
56 days ago
56-18152
56 days
0
43153 NoahW314
author:NoahW314
feat(Data/Finsupp/Basic): range of `equivMapDomain` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data 9/0 Mathlib/Data/Finsupp/Basic.lean 1 3 ['BoltonBailey', 'NoahW314', 'github-actions'] nobody
55-78159
1 month ago
57-43190
57 days ago
77-31446
77 days
0
44297 langston-barrett
author:langston-barrett
feat(Data/FinEnum): `Std.PRange.LawfulUpwardEnumerable` instance --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> I'm not sure how Mathlib feels about interfacing with std constructs, but I was looking for something along the lines of `succMany?` and found `Std.PRange.LawfulUpwardEnumerable`, so I figured I'd implement it and see what the appetite is. Even if we don't decide to use this particular typeclass, the underlying functionality still seems useful. This is my first ever Lean development, so I would greatly appreciate any tips and feedback on the style! I wrote all of this by hand, though I asked some questions about Lean to GPT 5.6 Luna along the way. A `LinearlyUpwardEnumerable` instance would be a good follow-up. t-data new-contributor 112/0 Mathlib/Data/FinEnum.lean 1 3 ['github-actions', 'langston-barrett'] nobody
53-65581
1 month ago
53-74874
53 days ago
53-82577
53 days
0
44328 Multramate
author:Multramate
chore: fix misspelling `supsets` in `Set.sUnion_mono_supsets` Fixes the misspelling `supsets` in `Set.sUnion_mono_supsets`. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-data LLM-generated 3/1 Mathlib/Data/Set/Lattice/Bounded.lean 1 5 ['JX-Mo', 'Multramate', 'github-actions'] nobody
53-62628
1 month ago
53-72666
53 days ago
53-72611
53 days
0
44216 peabrainiac
author:peabrainiac
feat(Topology): add `IsCozeroSet` Define a predicate `IsCozeroSet` for sets in topological spaces that are the support of some continuous function to $\mathbb R$. We prove: * Every cozero set is open, and in perfectly normal spaces every open set is a cozero set. * Finite intersections and locally finite unions of cozero sets are cozero sets. * Preimages of cozero sets under continuous functions are cozero sets. * Images and coimages of cozero sets under open proper maps are cozero sets. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Taken from [classifying-bundles](https://peabrainiac.github.io/classifying-bundles/docs/ClassifyingBundles/IsCozeroSet), where this API was useful for working with numerable covers. t-topology 227/0 Mathlib.lean,Mathlib/Algebra/BigOperators/Finprod.lean,Mathlib/Algebra/Order/Group/Indicator.lean,Mathlib/Topology/IsCozeroSet.lean 4 1 ['github-actions'] nobody
53-48849
1 month ago
57-50601
57 days ago
57-51800
57 days
1
44354 Rob23oba
author:Rob23oba
fix: use a more robust definition for unquot `unsafeCast`, and by extension, `cast lcProof`, is quite unstable in the compiler. Instead using an unsound `Quot.lift` is much more stable, since it uses the intended features for `Quot` and translates into an explicit `Quot.lcInv` application in the compiler. You can however not just use `Quot.lcInv` as the definition because the computability check catches it as an application of an axiom. See also leanprover/lean4#14719 for an issue with the `unsafeCast` definition of `unquot`. t-data 1/1 Mathlib/Data/Quot.lean 1 1 ['github-actions'] nobody
53-6577
1 month ago
53-10643
53 days ago
53-10588
53 days
0
43362 TJHeeringa
author:TJHeeringa
feat(Analysis/InnerProductSpace/Reproducing): add RKHS.SMul.smulSpace This PR defines the scalar multiple `c • H` for a given RKHS `H` and shows that it is an RKHS. --- Can be constructed just as the sumSpace in #41127. However, the discussion below concluded that the current type copy approach was better in this case. The notation `scoped infix:50 " • " => smulSpace` was not introduced. That caused overload issues that I don't know how to fix. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 119/5 Mathlib/Analysis/InnerProductSpace/Reproducing.lean,Mathlib/Analysis/InnerProductSpace/Reproducing/Operations.lean 2 9 ['Maldooor', 'TJHeeringa', 'github-actions', 'mathlib-merge-conflicts'] nobody
52-83444
1 month ago
52-84519
52 days ago
52-85515
52 days
1
44351 homeowmorphism
author:homeowmorphism
chore(Topology/MetricSpace/Bounded): add grind annotations to lemmas about the diameter --- I was browsing this API in the light of #43723 and noticed these possible improvements. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology 6/3 Mathlib/Topology/MetricSpace/Bounded.lean 1 3 ['github-actions', 'homeowmorphism'] nobody
52-60217
1 month ago
52-83269
52 days ago
52-86340
52 days
0
43695 gasparattila
author:gasparattila
feat(Topology/Algebra): define a topology on `Homogenization` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #43339 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-topology 377/0 Mathlib.lean,Mathlib/Topology/Algebra/Homogenization.lean 2 2 ['github-actions', 'mathlib-dependent-issues'] nobody
52-615
1 month ago
52-67790
52 days ago
52-67820
52 days
0
36406 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Matching): `#verts = 2 * #edgeSet` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #36442 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 44/0 Mathlib/Combinatorics/SimpleGraph/DegreeSum.lean,Mathlib/Combinatorics/SimpleGraph/Matching.lean,Mathlib/SetTheory/Cardinal/Finite.lean 3 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
51-55651
1 month ago
51-60074
51 days ago
52-58006
52 days
1
44437 FawadHa1der
author:FawadHa1der
perf(Analysis/Normed/Lp/SmoothApprox): manifold-free proof of smooth approximation in Lp Authored with AI help. Created after @mcdoll feedback on [leanprover-community/mathlib4#42451](https://github.com/leanprover-community/mathlib4/pull/42451) This is an alternate solution. This removes the manifold chain from the longest pole and even if the poisson summation is approved using denseRange_toLpCLM. We would still be saving roughly 5% in build time. There is only one new lemma but no change to existing lemmas/statements. t-analysis new-contributor 82/36 Mathlib/Analysis/Normed/Lp/SmoothApprox.lean 1 3 ['FawadHa1der', 'github-actions'] nobody
50-77086
1 month ago
50-77837
50 days ago
50-77782
50 days
0
36595 mcdoll
author:mcdoll
feat(Analysis/TemperedDistribution): polynomially bounded locally integrable functions define tempered distributions Every polynomially bounded and locally integrable function defines a tempered distribution, this generalizes the previous version for temperate growth functions. Breaking change: we deprecate the temperate growth embedding - it is a special case and we prove that every temperate growth function satisfies the polynomial bound outside a compact set. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [ ] depends on: #36711 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 172/2 Mathlib/Analysis/Asymptotics/Lemmas.lean,Mathlib/Analysis/Distribution/SchwartzSpace/Basic.lean,Mathlib/Analysis/Distribution/TemperateGrowth.lean,Mathlib/Analysis/Distribution/TemperedDistribution.lean,Mathlib/MeasureTheory/Function/LocallyIntegrable.lean,Mathlib/MeasureTheory/Integral/IntegrableOn.lean 6 3 ['github-actions', 'mathlib-bors', 'mathlib-dependent-issues'] nobody
47-80846
1 month ago
47-83598
47 days ago
47-83544
47 days
0
44440 vincentqb
author:vincentqb
feat(Computability/TuringMachine): bound the output length of a TM2 run This PR bounds the output length of a TM2 run by the input length plus a machine constant times the step count. It deduces `TM2ComputableInPolyTime.length_le`, the polynomial output-length bound used in composition. It also adds step-count induction and defines `initList` and `haltList` using `Function.update`. --- Relates to #7172 #33132 #35366 The code, the testing, and this description were prepared with the help of an AI coding assistant (Codex). t-computability LLM-generated new-contributor 82/7 Mathlib/Computability/StateTransition.lean,Mathlib/Computability/TuringMachine/Computable.lean,Mathlib/Computability/TuringMachine/StackTuringMachine.lean 3 3 ['github-actions', 'vincentqb'] nobody
47-35853
1 month ago
50-59227
50 days ago
50-59172
50 days
1
44541 vincentqb
author:vincentqb
feat(Computability/Partrec): computability of list operations This PR adds `Computable.list_foldl`, `list_foldr`, `list_rec`, and `list_map`, with the same statements as their `Primrec` counterparts. --- The code, the testing, and this description were prepared with the help of an AI coding assistant. LLM-generated new-contributor t-computability 37/0 Mathlib/Computability/Partrec.lean 1 3 ['github-actions', 'vincentqb'] nobody
47-34539
1 month ago
47-34796
47 days ago
47-34741
47 days
0
44392 yhx-12243
author:yhx-12243
fix(Algebra/Polynomial/Roots): fix tendstoCofinite with normal generic universe Remove the extraneous accidentally {R : Type} [CommRing R] [IsDomain R] in the signature of `Polynomial.tendstoCofinite_of_natDegree_ne_zero`, make it generic. t-algebra new-contributor
label:t-algebra$
2/2 Mathlib/Algebra/Polynomial/Roots.lean 1 3 ['github-actions', 'plp127'] nobody
45-80059
1 month ago
51-86201
51 days ago
51-86146
51 days
0
44618 barni120400
author:barni120400
feat(RingTheory/MvPolynomial/Homogeneous): powers of linear forms span the homogeneous polynomials Prove that the `n`-th powers of linear forms span the homogeneous polynomials of degree `n` (`MvPolynomial.homogeneousSubmodule_eq_span_pow`). Along the way, add the identity `Finset.sum_powerset_neg_one_pow_card_mul_sum_sdiff_pow_card` used in the proof. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-data new-contributor LLM-generated 64/0 Mathlib/Data/Nat/Choose/Sum.lean,Mathlib/RingTheory/MvPolynomial/Homogeneous.lean 2 2 ['github-actions'] nobody
45-59282
1 month ago
45-62413
45 days ago
45-64573
45 days
0
44040 kim-em
author:kim-em
chore: adaptation notes for the backward.privateInPublic uses blocked on lean4#14708 This PR adds an `#adaptation_note` at each `variable` declaration with an autoParam binder whose users need `backward.privateInPublic`. These uses (about 80 of the remaining option lines, in 14 files) are not removable on the Mathlib side: the autoParam helper declaration generated for a `variable` is always private, and any declaration using that variable in a public section silently elaborates to `sorry` without the option. This is https://github.com/leanprover/lean4/issues/14708. The note says which `set_option`s can go once that is fixed, and stops anyone from spending time on them before then. Each affected file was checked by removing its `true`-only option lines and observing the `sorry` warnings and the follow-on `autoParam … is not a constant` errors. It also deletes the one option line in `CategoryTheory/SmallObject/Iteration/ExtendToSucc` that turned out to be unnecessary. 🤖 Prepared with Claude Code tech debt LLM-generated 116/0 Mathlib/Algebra/Module/ZLattice/Covolume.lean,Mathlib/AlgebraicTopology/SimplicialSet/CompStruct.lean,Mathlib/AlgebraicTopology/SimplicialSet/StrictSegal.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/NonUnital.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Unital.lean,Mathlib/Analysis/Distribution/TemperedDistribution.lean,Mathlib/CategoryTheory/ComposableArrows/Basic.lean,Mathlib/CategoryTheory/Join/Basic.lean,Mathlib/CategoryTheory/Limits/Shapes/Reflexive.lean,Mathlib/CategoryTheory/LocallyCartesianClosed/ChosenPullbacksAlong.lean,Mathlib/CategoryTheory/Monoidal/Braided/Basic.lean,Mathlib/CategoryTheory/Monoidal/CommGrp_.lean,Mathlib/CategoryTheory/Monoidal/Functor.lean,Mathlib/CategoryTheory/Sites/Point/Basic.lean,Mathlib/CategoryTheory/SmallObject/Iteration/ExtendToSucc.lean 15 1 ['github-actions'] nobody
45-59242
1 month ago
61-51062
61 days ago
61-52192
61 days
0
44619 artie2000
author:artie2000
refactor(Algebra/Ring): rename IsSemireal property * Rename field `IsSemireal.one_add_ne_zero` to the more descriptive `IsSemireal.one_add_ne_zero_of_isSumSq`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
10/5 Mathlib/Algebra/Ring/Semireal/Defs.lean 1 3 ['SnirBroshi', 'artie2000', 'github-actions', 'vihdzp'] nobody
45-4801
1 month ago
45-47110
45 days ago
45-59157
45 days
0
44019 bally65
author:bally65
feat(Computability/Primrec): primality is primitive recursive Primrec.nat_prime : PrimrecPred Nat.Prime, via Nat.prime_def_lt' and the bounded quantifier PrimrecRel.forall_lt. Mathlib had no computability statement about Nat.Prime. AI disclosure: I used Claude and ChatGPT to discuss ideas, to adjust and optimize the approach, and to explore whether there was something worth taking on. They also proposed many of the problems, lines of thought, and decisions about direction. Almost all of the Lean code was written by Claude Code. I applied the reviewer's suggested changes myself. AI 使用聲明:我使用 Claude 和 ChatGPT 討論構思、調整與優化,也討論有沒有值得挑戰的方向。它們也提出了許多題目、思路和決策方向。Lean 程式碼幾乎全部由 Claude Code 撰寫。審稿人提供的修改建議由我自己套用。 Note: the English disclosure is a translation of my Chinese text, assisted by Claude. t-computability new-contributor LLM-generated 44/0 Mathlib.lean,Mathlib/Computability/Primrec/Prime.lean 2 6 ['bally65', 'github-actions', 'pepamontero'] nobody
44-84967
1 month ago
61-5318
61 days ago
62-39916
62 days
0
42051 vihdzp
author:vihdzp
feat: lemmas relating `smallInductiveDimension` and `ZeroDimensionalSpace` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #40879 - [x] depends on: #40901 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-topology 15/0 Mathlib/Topology/InductiveDimension/Functions.lean 1 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
44-62861
1 month ago
44-63522
44 days ago
44-65795
44 days
0
44261 javgomzar
author:javgomzar
feat(Algebra/Category/Grp): free functor preserves monomorphisms Refactored the proof for AddCommGrpCat, so that it also works in GrpCat. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra new-contributor
label:t-algebra$
18/5 Mathlib/Algebra/Category/Grp/Adjunctions.lean 1 15 ['JX-Mo', 'github-actions', 'javgomzar', 'mathlib-merge-conflicts'] nobody
43-79843
1 month ago
43-80538
43 days ago
55-53070
55 days
0
44681 Altabeh
author:Altabeh
feat(Analysis/ODE/Linearization): the derivative of a flow at a fixed… Add a new file `Mathlib/Analysis/ODE/Linearization.lean`. Let `ϕ : Flow ℝ E` on a real Banach space be generated by a vector field `f`, meaning `∀ x t, HasDerivAt (fun s ↦ ϕ s x) (f (ϕ t x)) t`. If `e` is a fixed point of `ϕ` and `f` has derivative `A` at `e`, then every time-`t` map has derivative `exp (t • A)` at `e`: * `Flow.hasFDerivAt_of_isFixedPt`: `HasFDerivAt (ϕ t) (exp (t • A)) e` for every `t : ℝ`. * `Flow.fderiv_eq_exp_of_isFixedPt`: the `fderiv` form. * `Flow.eventually_norm_sub_exp_le`: a uniform estimate on compact time intervals. For `0 ≤ T` and `0 < ε`, eventually for `x` near `e`, `‖ϕ t x - e - exp (t • A) (x - e)‖ ≤ ε * ‖x - e‖` for all `t ∈ [0, T]`. Only differentiability of `f` at `e` is needed; nothing is assumed about `f` elsewhere. The estimate comes from comparing `ϕ t x - e` with `exp (t • A) (x - e)` using Grönwall's inequality. Negative times are handled by applying the result to `ϕ.reverse`. --- This PR is independent of the `LipschitzWith.flow` PR. It applies to any `Flow ℝ E` with a generating vector field, which includes those flows. **Proof of `eventually_norm_sub_exp_le` is done by a combination of `Claude Opus 5.5` and `GPT-5.6 Sol`. Linting and comments were done by AI.*** new-contributor t-analysis LLM-generated 166/0 Mathlib.lean,Mathlib/Analysis/ODE/Linearization.lean 2 3 ['github-actions', 'grunweg'] nobody
43-66745
1 month ago
43-67348
43 days ago
43-69916
43 days
0
44680 Altabeh
author:Altabeh
feat(Analysis/ODE/LipschitzFlow): the flow of a globally Lipschitz ve… Add a new file `Mathlib/Analysis/ODE/LipschitzFlow.lean`. A globally Lipschitz vector field `v : E → E` on a real Banach space has a unique solution of `γ' = v ∘ γ` through every point, defined for all time, and these solutions form a continuous flow: * `LipschitzWith.exists_forall_hasDerivAt`: global existence of solutions. * `LipschitzWith.dist_le_of_forall_hasDerivAt`: two solutions satisfy `dist (γ t) (δ t) ≤ dist (γ 0) (δ 0) * exp (K * |t|)`. * `LipschitzWith.flow : Flow ℝ E`: the flow of `v`. * `LipschitzWith.hasDerivAt_flow`: the orbits of the flow solve `γ' = v ∘ γ`. * `LipschitzWith.flow_eq_of_hasDerivAt`: every global solution is an orbit of the flow. * `LipschitzWith.dist_flow_le`: `dist (flow t x) (flow t y) ≤ dist x y * exp (K * |t|)`. The field does not need to be bounded. For a bounded field, Picard–Lindelöf (`IsPicardLindelof`) gives solutions on each interval `(-(n + 1), n + 1)`, and uniqueness glues them into a global solution. A general field is reduced to this case by multiplying `v` by a Lipschitz cutoff that is `1` on `closedBall 0 R`. Grönwall's inequality, using `‖v y‖ ≤ ‖v 0‖ + K * ‖y‖`, shows that for large `R` the solution stays in that ball on the time interval, so the cutoff does not change it. --- Continuity of the flow jointly in `(t, x)` comes from `continuousOn_prod_of_continuousOn_lipschitzOnWith'`, using the exponential separation bound on bounded time intervals. **The proofs of`exists_forall_hasDerivAt_of_forall_Ioo`, `lipschitzWith_cutoff_smul`, `norm_le_gronwallBound` and part of `dist_le_of_forall_hasDerivAt` used a combo of `GPT-5.6 Sol` and `Claude Opus 5.5`. Linting and comments were done by AI as well.** t-analysis new-contributor LLM-generated 276/0 Mathlib.lean,Mathlib/Analysis/ODE/LipschitzFlow.lean 2 3 ['github-actions', 'grunweg'] nobody
43-66624
1 month ago
43-67253
43 days ago
43-70069
43 days
0
44199 emlis42
author:emlis42
feat(Order): add `EReal.coe_cs{Sup, Inf}` This PR adds `WithTop.leftOrdContinuous_coe`, and adds `WithBotTop` and `EReal` version and `EReal.coe_c{s, i}{Sup, Inf}` as consequences. Discussed here: [Is there code for X? > Lemmas relating `Real.toEReal` and `sSup`/`sInf` of images](https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/Lemmas.20relating.20.60Real.2EtoEReal.60.20and.20.60sSup.60.2F.60sInf.60.20of.20images/with/626667637) t-order large-import 98/0 Mathlib/Data/EReal/Operations.lean,Mathlib/Order/CompleteLatticeIntervals.lean,Mathlib/Order/OrdContinuous.lean,Mathlib/Order/WithBotTop.lean 4 10 ['SnirBroshi', 'emlis42', 'eric-wieser', 'github-actions', 'mathlib-merge-conflicts'] nobody
43-5643
1 month ago
43-5643
43 days ago
57-34404
57 days
0
44740 user202729
author:user202729
chore(Algebra/Ring/CompTypeclasses): fix a typo and reformat slightly Change `σ₂₃` to `σ` in the header, this one is clearly a typo. Do some minor reformatting for the rest of the file, which I think make it nicer. --- t-algebra new-contributor
label:t-algebra$
7/11 Mathlib/Algebra/Ring/CompTypeclasses.lean 1 3 ['github-actions', 'user202729', 'vihdzp'] nobody
42-35533
1 month ago
42-39202
42 days ago
42-39147
42 days
0
43885 plp127
author:plp127
refactor: reduce defeq abuse in `Representation.asModule` Reduce defeq abuse around `Representation.asModule` by adding explicitly uses of `Representation.asModuleEquiv` to convert between `V` and `ρ.asModule`. Also reorganize some `@[simp]` lemmas and fix some naming issues. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra tech debt
label:t-algebra$
70/89 Mathlib/RepresentationTheory/Basic.lean,Mathlib/RepresentationTheory/Intertwining.lean,Mathlib/RepresentationTheory/Rep/Iso.lean,Mathlib/RepresentationTheory/Submodule.lean,Mathlib/RepresentationTheory/Subrepresentation.lean 5 21 ['JX-Mo', 'github-actions', 'plp127'] nobody
41-51794
1 month ago
62-72865
62 days ago
66-68665
66 days
0
44712 plp127
author:plp127
chore: rename arguments to `Shrink.rec` Name the motive `motive` and name the minor premises according to their contents. While we're here, also unexpose `Shrink.rec`, which is the last exposed declaration in this file, so also remove the `@[expose]` from the `@[expose] public section` at the top of the file because none of the declarations are actually exposed. Also add a docstring. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-logic 10/10 Mathlib/Logic/Small/Defs.lean,scripts/nolints.json 2 2 ['github-actions', 'vihdzp'] nobody
41-33344
1 month ago
42-60301
42 days ago
42-60246
42 days
0
44784 shunfeng8421
author:shunfeng8421
feat(Combinatorics): prove finitary Van der Waerden by compactness Proves the finitary version of Van der Waerden's theorem: ```lean theorem van_der_waerden (k : ℕ) {κ : Type*} [Finite κ] [Nonempty κ] : ∃ N : ℕ, ∀ C : Fin (N + 1) → κ, HasMonoAPWithin k N C ``` i.e. every finite coloring of a sufficiently large initial segment `[0, N]` contains a monochromatic arithmetic progression of length `k`. This resolves the TODO in `Mathlib/Combinatorics/HalesJewett.lean` asking for a finitary version of Van der Waerden's theorem. ## Proof sketch The proof goes by compactness (Rado's selection lemma), the route explicitly suggested in the TODO ("either by compactness or by modifying the current proof"): 1. Assume the theorem fails: every segment `[0, N]` admits a "bad" coloring with no monochromatic AP of length `k`. 2. For each finite set `s ⊆ ℕ`, pick the bad coloring of the covering interval `[0, s.sup id]` and extend it (arbitrarily) to all of `ℕ`. 3. **Rado's selection lemma** (`Finset.rado_selection`, from `Mathlib/Combinatorics/Compactness.lean`, itself proved via Tychonoff's theorem) stitches these local bad colorings into a global coloring `χ : ℕ → κ` that agrees with some local bad coloring on every finite set. 4. The **infinite** Van der Waerden theorem — `Combinatorics.exists_mono_homothetic_copy`, a corollary of Hales–Jewett — produces a monochromatic AP `(a * t + b)_{t < k}` in `χ`. 5. Viewed as a finite set, this AP lies inside the covering interval of some finite set `t` on which the bad coloring agrees with `χ`, so it is also monochromatic there — contradicting badness of that local coloring. No explicit bounds are produced; this is purely an existence proof, which is exactly what the compactness route buys. ## New definitions - `Combinatorics.HasMonoAPWithin k N C`: the coloring `C : Fin (N+1) → κ` of the initial segment `[0, N]` contains a monochromatic AP of length `k`. ## Changes - `Mathlib/Combinatorics/HalesJewett.lean`: removed the completed TODO item ("Prove a finitary version of Van der Waerden's theorem ... by compactness"), added a pointer to the new theorem in the "Main results" list. - `Mathlib/Combinatorics/VanDerWaerden.lean`: new file. ## Notes for the reviewer - The file header still contains the `[Author]` placeholder: fill in your name before committing. ------- **AI disclosure**: AI-assisted tools were used to draft the proof outline and Lean code, and to debug type/simplifier issues; all contributions were reviewed and verified by the author, who takes full responsibility for the correctness of the mathematics and code. t-combinatorics new-contributor LLM-generated 100/3 Mathlib.lean,Mathlib/Combinatorics/HalesJewett.lean,Mathlib/Combinatorics/VanDerWaerden.lean 3 5 ['github-actions', 'grunweg', 'shunfeng8421'] nobody
40-60742
1 month ago
40-60742
40 days ago
40-69043
40 days
0
44147 eric-wieser
author:eric-wieser
feat(Data/List/Sort): lemmas about sublists and orderedInsert Add `List.orderedInsert_eq_cons_of_forall_rel`, and characterize when one `orderedInsert` is a sublist of another (`List.orderedInsert_sublist_orderedInsert_iff`, `List.orderedInsert_sublist_orderedInsert_iff_of_notMem`, `List.erase_sublist_iff_sublist_orderedInsert_of_notMem`), a permutation of another (`List.orderedInsert_perm_orderedInsert_iff`, `List.orderedInsert_perm_orderedInsert_iff_right`), or a sub-permutation of another (`List.orderedInsert_subperm_orderedInsert_iff`). Also add `List.perm_cons_right_iff : a :: l ~ b :: l ↔ a = b`, the `cons` version of `List.perm_append_right_iff`. These are split out from work on a basis for `CliffordAlgebra`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data LLM-generated 48/9 Mathlib/Data/List/Perm/Basic.lean,Mathlib/Data/List/Sort.lean 2 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
40-33596
1 month ago
43-39388
43 days ago
47-79177
47 days
0
42878 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Star): the nth star graph is contained in a graph iff max degree is at least `n` - `starGraph (r : W) ⊑ G ↔ Nat.card W ≤ G.maxDegree + 1` - `starGraph v ⊑ starGraph w ↔ Nonempty (V ↪ W)` - `starGraph v ⊴ starGraph w ↔ Nonempty (V ↪ W)` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 86/1 Mathlib/Combinatorics/SimpleGraph/Star.lean 1 7 ['SnirBroshi', 'b-mehta', 'github-actions', 'mathlib-merge-conflicts'] nobody
40-32729
1 month ago
40-33278
40 days ago
85-20492
85 days
0
44845 DanielJHorton
author:DanielJHorton
feat(LinearAlgebra/PiTensorProduct/Projective): implement properties of tensor products of families of projective modules This PR adds a new file `LinearAlgebra/PiTensorProduct/Projective` which develops the properties of tensor products of families of projective modules. Results for binary tensor products from `LinearAlgebra/Contraction` are extended to `PiTensorProduct`, and the main result `dualDistribEquiv` of `LinearAlgebra/PiTensorProduct/Dual` is generalized from free modules over a ring to projective modules over a semiring. The major results are: - `PiTensorProduct.Projective` - An instance proving that the tensor product of a finite collection of projective modules is projective. - `PiTensorProduct.piTensorHomEquiv` - A linear equivalence whose underlying linear map is `piTensorHomMap` from `LinearAlgebra/PiTensorProduct/Basic`. - `PiTensorProduct.dualDistribEquivOfProjective` - A linear equivalence whose underlying map is `dualDistrib` from `LinearAlgebra/PiTensorProduct/Dual`. This generalizes `dualDistribEquiv`, replacing hypotheses `[CommRing R]` and `[Module.Free R (P i)]` with `[CommSemiring R]` and `[Module.Projective R (P i)]`. This PR also adds a small definition `dualBaseRingEquiv (R : Type*) [CommSemiring R] : Dual R R ≃ₗ[R] R` to `LinearAlgebra/Dual/Defs` (as well as associated `@[simp]` lemmas) which were used in some of the proofs. Disclamer: I am still a relatively new contributor here and this is my largest PR so far. I am grateful for the time of any reviewers who look at this PR and I am happy to answer any questions about implementation/design choices. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
216/1 Mathlib.lean,Mathlib/LinearAlgebra/Dual/Defs.lean,Mathlib/LinearAlgebra/PiTensorProduct/Projective.lean 3 1 ['github-actions'] nobody
39-58380
1 month ago
39-59855
39 days ago
39-61713
39 days
0
43324 plp127
author:plp127
feat: fine uniformity This PR continues the work from #24016. Original PR: https://github.com/leanprover-community/mathlib4/pull/24016 --- - [x] depends on: #43312 t-topology 130/0 Mathlib.lean,Mathlib/Topology/UniformSpace/FineUniformity.lean 2 2 ['github-actions', 'mathlib-dependent-issues'] nobody
39-47199
1 month ago
39-48495
39 days ago
39-49384
39 days
0
44858 vihdzp
author:vihdzp
feat: connect regular cardinal orders to regular cardinals --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory 10/0 Mathlib/SetTheory/Cardinal/Regular.lean 1 1 ['github-actions'] nobody
39-18274
1 month ago
39-19551
39 days ago
39-19496
39 days
0
44855 vihdzp
author:vihdzp
feat: link `Order.enum` to `Subtype.orderIsoOfNat` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory large-import 15/3 Mathlib/SetTheory/Cardinal/Aleph.lean,Mathlib/SetTheory/Cardinal/Cofinality/Enum.lean 2 2 ['github-actions', 'vihdzp'] nobody
39-16789
1 month ago
39-19455
39 days ago
39-20049
39 days
0
44831 scottdhughes
author:scottdhughes
feat(Analysis/MeanInequalitiesPow): add a real power difference bound Add `Real.abs_rpow_sub_rpow_le` in `Mathlib/Analysis/MeanInequalitiesPow.lean`: for nonnegative real bases and `0 ≤ p ≤ 1`, ```lean |a ^ p - b ^ p| ≤ |a - b| ^ p ``` Provide a direct scalar API for downstream fractional-power regularity estimates. Derive the bound from the neighboring `Real.rpow_add_le_add_rpow`, then handle the two input orders. Include both exponent endpoints. Add one lemma and its docstring, with no new imports. --- Local validation on Lean/Mathlib 4.35.0: - `lake build Mathlib.Analysis.MeanInequalitiesPow` - `lake exe lint-style Mathlib.Analysis.MeanInequalitiesPow` - Fresh source elaboration, exported-type and axiom checks, plus all 15 default declaration linters for the new lemma. The axiom check reports only `propext`, `Classical.choice` and `Quot.sound`. AI assistance: Codex adapted an existing downstream proof, searched Mathlib and relevant open PRs, drafted this description, and ran the local checks. t-analysis new-contributor LLM-generated 19/0 Mathlib/Analysis/MeanInequalitiesPow.lean 1 3 ['copilot-pull-request-reviewer', 'github-actions', 'scottdhughes'] nobody
38-75870
1 month ago
39-79034
39 days ago
39-78979
39 days
0
44537 vincentqb
author:vincentqb
feat(Analysis/Convex/Cone): prove that open sets have open hulls This PR proves `ConvexCone.isOpen_hull`: if addition and multiplication by each fixed scalar are continuous, the convex cone hull of an open set is open. It defines `ConvexCone.interior`, with coercion, membership, and equality lemmas parallel to the closure API. The hull theorem then follows from cone minimality. The original hypotheses do not suffice, see #44689 for a counterexample. --- AI-assisted contribution. t-analysis LLM-generated new-contributor file-removed 57/24 Mathlib.lean,Mathlib/Analysis/Convex/Cone/Basic.lean,Mathlib/Analysis/Convex/Cone/Interior.lean,Wanted.lean,Wanted/Analysis/Convex/Cone/Basic.lean 5 15 ['github-actions', 'pepamontero', 'vincentqb'] nobody
38-56905
1 month ago
43-44105
43 days ago
46-57325
46 days
0
44846 artie2000
author:artie2000
feat(Algebra/Polynomial): variants of Polynomial.reverse functional equation Split from https://github.com/leanprover-community/mathlib4/pull/44338 - these were helper lemmas for a discarded approach. AI usage disclosure: ChatGPT 5.5 was used to split this PR from https://github.com/leanprover-community/mathlib4/pull/44338. All of the changes in this PR were made by a human. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
25/9 Mathlib/Algebra/Polynomial/Reverse.lean 1 9 ['SnirBroshi', 'artie2000', 'github-actions'] nobody
38-48654
1 month ago
38-50387
38 days ago
39-5370
39 days
0
44900 justus-springer
author:justus-springer
feat(Geometry/Convex/Cone/Caratheodory): conic Carathéodory theorem Carathéodory's theorem (see `Analysis/Convex/Caratheodory.lean`) says that any point in the convex hull of a set can be represented as a convex combination of some affinely independent subset. This PR adds the conic version of this theorem: Every point in the conic hull (`PointedCone.hull`) of a set can be represented as a positive span of some linearly independent subset. We basically follow the same proof strategy as in `Analysis/Convex/Caratheodory.lean`. The conic version is slightly simpler, as the weights don't have to sum to one. Also, we use strong induction on finsets directly instead of defining a minimal set (see also the refactor PR #44863). A small helper lemma `mem_hull_finset` is also added, the finset version of `mem_hull_set`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-convex-geometry 108/0 Mathlib.lean,Mathlib/Geometry/Convex/Cone/Caratheodory.lean,Mathlib/Geometry/Convex/Cone/Pointed.lean 3 1 ['github-actions'] nobody
38-4543
1 month ago
38-5505
38 days ago
38-5450
38 days
0
44941 CollinYuanjieRen
author:CollinYuanjieRen
feat(Data/Finset/Sort): add filtering and greatest insertion lemmas Prove that filtering commutes with `Finset.sort`, and that inserting a new greatest element appends it to the sorted list. Both lemmas work for general total, transitive, antisymmetric relations. Continues the sorting portion of #9605 by @davikrehalt. Codex (GPT-6 Astra) assisted with the Lean proofs. t-data LLM-generated new-contributor 13/0 Mathlib/Data/Finset/Sort.lean 1 3 ['CollinYuanjieRen', 'github-actions'] nobody
37-6689
1 month ago
37-8291
37 days ago
37-8236
37 days
0
44893 unknown8575
author:unknown8575
chore(Topology/MetricSpace/Polish): generalize `IsClopenable.iUnion` to countable index types The proof only used ℕ to get `t' ≤ t` through index 0, but `exists_polishSpace_forall_le` already gives this directly. So the lemma now works for any countable index type, and the TODO is removed. I used an LLM to find this TODO and draft the change. I've checked it, built it locally, and understand every line. t-topology new-contributor 18/15 Mathlib/Topology/MetricSpace/Polish.lean 1 5 ['github-actions', 'plp127', 'unknown8575', 'vihdzp'] nobody
36-81927
1 month ago
38-14608
38 days ago
38-14553
38 days
0
44945 CollinYuanjieRen
author:CollinYuanjieRen
chore(Algebra/Lie): generalize subalgebra map membership Generalize `LieSubalgebra.mem_map_submodule` to arbitrary Lie algebra morphisms. Add `mem_map_equiv` and update the three skew-adjoint equivalence proofs. Continues Eric Rodriguez Boidi's #7994, marked `please-adopt`. --- Checked the five affected modules with Lean 4.36.0-rc1 and a zero-morphism client regression. AI-assisted: Codex prepared the Lean changes; GPT-6 Astra assisted with proof checks. t-algebra LLM-generated new-contributor
label:t-algebra$
9/6 Mathlib/Algebra/Lie/SkewAdjoint.lean,Mathlib/Algebra/Lie/Subalgebra.lean 2 3 ['CollinYuanjieRen', 'github-actions'] nobody
36-63857
1 month ago
36-64624
36 days ago
36-64569
36 days
0
43899 plp127
author:plp127
refactor(RepresentationTheory/Character): assume `FiniteDimensional k ρ.asModule` instead Change the assumptions of some theorems to `FiniteDimensional k ρ.asModule` instead of `FiniteDimensional k V`, so that typeclass inference may use `ρ` as an argument to typeclass search. Prove that irreducible representations of finite groups are finite dimensional, and use it to remove some `FiniteDimensional` assumptions. --- - [x] depends on: #44763 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
27/12 Mathlib/RepresentationTheory/Basic.lean,Mathlib/RepresentationTheory/Character.lean,Mathlib/RepresentationTheory/Coinvariants.lean,Mathlib/RepresentationTheory/Irreducible.lean 4 8 ['JX-Mo', 'github-actions', 'mathlib-dependent-issues', 'plp127'] nobody
36-2015
1 month ago
36-15881
36 days ago
55-83418
55 days
0
44899 RemyDegenne
author:RemyDegenne
feat: add a class for reflexive topological vector spaces Define reflexive spaces and show that - Hilbert spaces are reflexive - finite-dimensional normed spaces are reflexive --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> The first commit of this PR was LLM-generated (it results from an interaction between me and an LLM over several steps, but the code is entirely from the LLM). Subsequent commits are my changes. The main reason I want this class is to then introduce spaces with the Radon-Nilodym property (for properties of martingales) and show that reflexive spaces have it. brownian t-analysis LLM-generated t-measure-probability 250/33 Mathlib.lean,Mathlib/Analysis/InnerProductSpace/Reflexive.lean,Mathlib/Analysis/Normed/Module/DoubleDual.lean,Mathlib/Analysis/Normed/Module/HahnBanach.lean,Mathlib/MeasureTheory/Function/AEEqOfIntegral.lean 5 2 ['github-actions', 'peakpoint'] nobody
35-84279
1 month ago
38-6176
38 days ago
38-6121
38 days
0
29713 jessealama
author:jessealama
feat(Algebra/Homology): add Euler–Poincaré formula This PR builds on the generalized Euler characteristic framework from #31121 to prove the Euler-Poincaré formula for chain complexes. PR #31121 defines the Euler characteristic for general homological complexes. This PR specializes those definitions to ℤ-indexed chain complexes and proves the main Euler-Poincaré theorem. ### Main result (in `EulerPoincare.lean`) * `ChainComplex.eulerChar_eq_homologyEulerChar`: For ℤ-indexed bounded chain complexes of finite-dimensional modules over a division ring, the alternating sum of chain dimensions equals the alternating sum of homology dimensions. ### Supporting lemmas The file also provides dimension lemmas generalized to arbitrary `HomologicalComplex (ModuleCat k) c` (not just ℤ-indexed chain complexes): * `HomologicalComplex.dFrom_zero_range` / `dTo_zero_range`: zero range when the target/source object is zero * `HomologicalComplex.dFrom_range_finrank_eq_d` / `dTo_range_finrank_eq_d`: range of `dFrom`/`dTo` has the same dimension as the underlying differential * `HomologicalComplex.range_dTo_le_ker_dFrom`: range of `dTo` is contained in the kernel of `dFrom` t-algebra new-contributor
label:t-algebra$
264/0 Mathlib.lean,Mathlib/Algebra/Homology/EulerPoincare.lean 2 26 ['github-actions', 'jessealama', 'joelriou', 'kim-em', 'mathlib-merge-conflicts', 'mathlib4-merge-conflict-bot'] nobody
35-63152
1 month ago
35-63361
35 days ago
71-22706
71 days
0
44991 vihdzp
author:vihdzp
refactor(SetTheory/Ordinal/Notation): deprecate module This module has not seen any major changes since at least the port and is unlikely to be used downstream. So we deprecate it altogether. --- I'm opening this PR as a way to spark some discussion. There's a lot of things that can be improved about this module. `NFBelow` is unnecessary and `NF` can be characterized directly. The order structure on `ONote` is not computable but could made to be. Exponentiation can be given a more direct characterization. The construction of fundamental sequences is ad-hoc, and we could instead create a larger API around them. And so on. On a more practical level, the convoluted proofs of this module are quite prone to breaking, and have done so seemingly every time I touch any part of the ordinal API. If you look at the history of this file, you'll largely see refactors which have required convoluted adaptations on this particular module. Two years ago, I [rewrote this entire file](https://github.com/vihdzp/ordinal-notation/blob/master/OrdinalNotation/Notations/Cantor.lean) in an experimental, since archived repository of mine. I considered upstreaming these changes to Mathlib. However, there were three things that gave me pause. 1. This would be a thousand line PR. There's no way to split this up without losing functionality, since it's a complete rewrite which changes most of the definitions. Perhaps I could upstream it to a new file, and deprecate the old one when done, but this doesn't address the other two points. 2. I doubt the Mathlib maintainers would be interested. There's not that many reviewers for ordinal PRs as is, and I fear this upstreaming process would be glacial. Which brings me to my third point. 3. The Cantor Normal Form is far from the only ordinal notation, and the existence of this file seems to open the doors to further developments, such as Veblen's Normal Form, or Veblen's Klammersymbolen, or the (Extended) Buchholz Ordinal Notation... which I highly doubt anyone will be willing to review. Now, perhaps I'm wrong here. Perhaps there are a handful of Mathlib maintainers who are enthusiastic about this material. And in that case, I'll be glad to close this PR, make a new `SetTheory/Ordinal/Notation` folder, and make PRs working towards the most popular ordinal notations. But realistically, I suspect it's easier for everyone if we just deprecate this module. If anyone is ever interested on working on ordinal notations outside of Mathlib, my Zulip DMs are open. t-set-theory 2/0 Mathlib/SetTheory/Ordinal/Notation.lean 1 1 ['github-actions'] nobody
35-23896
1 month ago
35-24564
35 days ago
35-24509
35 days
0
44982 sw1sh
author:sw1sh
feat(Data/List): define Lyndon words This PR adds `Mathlib/Data/List/Lyndon.lean` with the definition of Lyndon words and their two basic properties. * `List.IsLyndon w`: the list `w` is nonempty and strictly smaller, in the lexicographic order, than each of its proper nonempty suffixes. * `List.IsLyndon.not_hasPeriod`: a Lyndon word has no period `p` with `0 < p < w.length`; that is, it is unbordered. It is stated with `List.HasPeriod` from `Mathlib/Data/List/PeriodicityLemma.lean`. * `List.IsLyndon.append`: if `u` and `v` are Lyndon words and `u < v`, then `u ++ v` is a Lyndon word. Two general lemmas on the lexicographic order of lists are added along the way: * `List.Lex.append_of_not_isPrefix`: if `Lex r u s` holds and `u` is not a prefix of `s`, then `Lex r (u ++ v) (s ++ w)` holds. * `List.lt_append_of_ne_nil`: a list is smaller than each of its proper extensions. A planned follow-up uses these to prove the Ehrenfeucht–Silberger theorem for infinite words: over a finite ordered alphabet, an infinite word whose sufficiently long factors are all bordered is eventually periodic. The proof cuts off longest Lyndon prefixes, which gives a non-increasing sequence of short Lyndon words. --- AI disclosure: this code was written with Claude Code (Anthropic, model Opus 5.5) as part of a project that formalizes equivalent forms of Wolfram's Rule 30 Problem 1 (https://github.com/WolframInstitute/Rule30PrizeKit). 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-data new-contributor LLM-generated 120/0 Mathlib.lean,Mathlib/Data/List/Lyndon.lean 2 3 ['github-actions'] nobody
35-18221
1 month ago
35-68653
35 days ago
35-68598
35 days
0
44660 jessealama
author:jessealama
feat(Combinatorics/SimpleGraph/Hamiltonian): close a Hamiltonian path into a Hamiltonian cycle Add `SimpleGraph.Walk.isHamiltonianCycle_cons`: closing a path `p` from `b` to `a` with an edge `a ~ b` gives a Hamiltonian cycle if and only if `p` is a Hamiltonian path that does not already use that edge. This is the Hamiltonian analogue of `Walk.cons_isCycle_iff`. It was originally extracted at @YaelDillies's suggestion during review of #36376, which no longer needs it. t-combinatorics 6/0 Mathlib/Combinatorics/SimpleGraph/Hamiltonian.lean 1 9 ['SnirBroshi', 'YaelDillies', 'github-actions', 'jessealama'] nobody
34-12420
1 month ago
44-13353
44 days ago
44-14366
44 days
0
43723 homeowmorphism
author:homeowmorphism
feat(Topology/MetricSpace): define hyperbolic pseudometric spaces We define hyperbolic pseudometric spaces using the Gromov product. This will be used to define hyperbolic groups. Co-authored-by: Katerina Hristova <katherina.hristova@gmail.com> --- - [x] depends on: #43641 Use of AI: Claude Fable was used to look up things quickly and sketch the API, but this was mostly written (or rewritten) by hand. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-topology 115/0 Mathlib.lean,Mathlib/Topology/Bornology/Basic.lean,Mathlib/Topology/MetricSpace/Hyperbolic.lean 3 15 ['SnirBroshi', 'github-actions', 'homeowmorphism', 'mathlib-dependent-issues', 'tb65536', 'vlad902'] nobody
34-5127
1 month ago
52-84479
52 days ago
71-37848
71 days
1
38055 felixpernegger
author:felixpernegger
feat(Topology/EMetricSpace): add r-variation Redoing #37007 (I had accidently deleted my fork which nuked the PR). See https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/p-variation for discussion. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-topology t-analysis 395/0 Mathlib.lean,Mathlib/Topology/EMetricSpace/RVariation.lean 2 29 ['felixpernegger', 'github-actions', 'jvanwinden', 'luigi-massacci', 'luigimassacci-ax', 'mathlib-merge-conflicts'] nobody
33-82177
1 month ago
109-12817
109 days ago
214-6004
214 days
0
45055 grunweg
author:grunweg
feat: bundled symmetric linear maps We construct bundled symmetric linear maps with their basic operations. The design follows the corresponding file on alternating linear maps closely. This is the first step towards the vector bundle of symmetric maps, which features in one possible definition of jet spaces and jet bundles. This work was partially conducted at the workshop "Techniques and Tools for the Formalization of Analysis" at ICERM in May 2026. While at it, we remove two outdated items from the module doc-string of the alternating maps' file. --- Best reviewed by diffing with the alternating file, and then thinking about any reasons for divergences. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
836/10 Mathlib.lean,Mathlib/LinearAlgebra/Alternating/Basic.lean,Mathlib/LinearAlgebra/Symmetric/Basic.lean 3 1 ['github-actions'] nobody
33-60249
1 month ago
33-61870
33 days ago
33-61815
33 days
4
44531 emlis42
author:emlis42
feat(Analysis/SpecialFunctions): add the polylogarithm function This PR adds the polylogarithm function $$\mathrm{Li}_ s(z)$$, together with its integral representation, power series, the recurrence `z * deriv (Li_ (s + 1)) z = Li_ s z`, and analyticity off the branch cut. ## Main definitions * `Complex.polylogKernel`: the integrand `polylogKernel z t = z / (cexp t - z)`. * `Complex.polylogIntegral`: the integral representation $$ \mathrm{Li}_ s(z) = \dfrac{1}{\Gamma(s)}\int_0^{\infty}t ^ {s - 1} \dfrac{z}{e^z -z} \mathrm{d}t $$ * `Complex.polylogSeries`: the power series $$ \mathrm{Li}_ s(z) = \sum_{n = 1}^{\infty} \dfrac{z^n}{n^s} $$ * `Complex.polylog`: the polylogarithm `Li_ s z`. ## Main statements * `Complex.polylog_eq_polylogSeries`: `Li_ s z = polylogSeries s z` for `‖z‖ < 1`. * `Complex.summable_polylogSeries_of_norm_lt` and `_of_norm_le`: the defining series is summable for `‖z‖ < 1`, resp. for `‖z‖ ≤ 1` when `1 < s.re`. * `Complex.polylog_eq_polylogIntegral`: `Li_ s z = polylogIntegral s z` for `0 < s.re` and `z` off the branch cut. * `Complex.mul_deriv_polylog_add_one`: the recurrence `z * deriv (Li_ (s + 1)) z = Li_ s z` for `z` off the branch cut. * `Complex.analyticOnNhd_polylog_right`: `Li_ s` is analytic off the branch cut. ## Implementation notes The definition follows DLMF 25.12: `Li_ s z` is defined on the complement of the branch cut `Ici 1 ×ℂ {0}` via the integral representation for `0 < s.re`, and extended to general `s` by repeatedly applying the recurrence `Li_ s = z * deriv (Li_ (s + 1))` until the real part becomes positive. On the branch cut itself we take the limit from the lower half-plane. --- I used an LLM agent only to verify the definitions in this work. I did not use any LLM-generated code. t-analysis 624/0 Mathlib.lean,Mathlib/Analysis/SpecialFunctions/Polylog/Basic.lean,Mathlib/Topology/Separation/Hausdorff.lean 3 2 ['emlis42', 'github-actions'] nobody
33-55351
1 month ago
33-57062
33 days ago
47-27281
47 days
0
42067 themathqueen
author:themathqueen
feat(RingTheory): define Frobenius algebras A `FrobeniusAlgebra` is an algebra that is equipped with a `dual : Module.Dual R A` such that the bilinear form `(LinearMap.mul R A).compr₂ dual` is bijective. A straightforward example: a matrix over a field with the trace as its dual is a Frobenius algebra. (Not an instance because there can be other choices of the dual.) A `FrobeniusAlgebra` induces a coalgebra such that it satisfies the Frobenius equations (`Coalgebra.IsFrobenius`). Note that this is not an instance since you can have a different coalgebra that is not equal to this one (for example, if you have a `Bialgebra R A` where `A` is not isomorphic to `R` then the coalgebra cannot satisfy the Frobenius equations, so this is not equal to the coalgebra coming from a `FrobeniusAlgebra R A`). A coalgebra that satisfies the Frobenius equations (`Coalgebra.IsFrobenius`) naturally induces a Frobenius algebra (`FrobeniusAlgebra`). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [x] depends on: #xyz [optional extra text] --> - [x] depends on: #27493 - [x] depends on: #42077 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 331/21 Mathlib.lean,Mathlib/RingTheory/Coalgebra/IsFrobenius.lean,Mathlib/RingTheory/FrobeniusAlgebra/Basic.lean,Mathlib/RingTheory/FrobeniusAlgebra/IsFrobenius.lean 4 21 ['JX-Mo', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'themathqueen'] nobody
33-37359
1 month ago
62-5282
62 days ago
62-5388
62 days
0
44958 dkaysin
author:dkaysin
feat(Combinatorics/SimpleGraph/Cayley): reachability and connectedness of Cayley graphs This PR adds reachability and connectedness results for Cayley Simple graphs. --- Implements connectedness results requested [here](https://github.com/leanprover-community/mathlib4/pull/44853#discussion_r4296323074). Implementation details: * One-directional reachability results can also be proven for semigroups and monoids. I chose to implement one such result for monoids: `reachable_mulCayley_mul_of_mem_submonoidClosure`. * Machinery with values of darts can be useful for further proofs when working with Cayley graphs in geometric group theory. Edit: made private for now as per reviewer's comment. Use of AI: I used Claude Opus 5.5 for the following tasks: * To brainstorm and compare API design ideas and naming conventions * To propose simplifications to proofs * To check docstrings for consistency All AI-generated content was reviewed and edited by me. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor t-combinatorics large-import 106/1 Mathlib/Combinatorics/SimpleGraph/Cayley.lean 1 11 ['SnirBroshi', 'dkaysin', 'github-actions'] nobody
32-81403
1 month ago
32-81633
32 days ago
32-84050
32 days
0
43157 NoahW314
author:NoahW314
feat(Algebra/Category): divisible R-modules over a PID are injective This generalizes the existing result that divisible groups that injective to hold over any principal ideal ring. The same proof works with only minor modifications. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) large-import t-algebra
label:t-algebra$
27/16 Mathlib/Algebra/Category/Grp/Injective.lean,Mathlib/Algebra/Category/ModuleCat/Injective.lean,Mathlib/Algebra/Module/CharacterModule.lean 3 3 ['NoahW314', 'github-actions', 'mathlib-merge-conflicts'] nobody
32-78377
1 month ago
32-79021
32 days ago
76-19690
76 days
0
44864 user202729
author:user202729
feat(Order/Bounds): notation for sSup and sInf Also fix a typo (add a full stop) and change some call sites to use the new notation. --- As discussed on Zulip: https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Adding.20notation.20for.20sSup.2FsInf.3F t-topology new-contributor 14/3 Mathlib/Order/Bounds/Defs.lean,Mathlib/Order/SetNotation.lean,Mathlib/Topology/Sets/Closeds.lean,Mathlib/Topology/Sets/Opens.lean 4 5 ['Multramate', 'github-actions', 'user202729'] nobody
32-19472
1 month ago
37-79151
37 days ago
37-82857
37 days
0
44741 mortarsanjaya
author:mortarsanjaya
feat: weaken even more assumptions on theorems about `FloorRing` This PR is mostly about weakening the assumptions of type `IsOrderedRing` or `IsStrictOrderedRing` to `IsOrderedAddMonoid` on theorems about `FloorSemiring` and `FloorRing`. However, none of these assumptions are completely removed. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> ~~Unfortunately, the new proof of `floor_div_natCast`, done for the sake of reducing `IsStrictOrderedRing K` to `IsOrderedAddMonoid K`, is quite complicated and can definitely be refactored. If we use the old proof, `IsStrictOrderedRing K` can be reduced to `IsOrderedAddMonoid K` + `AddLeftStrictMono K`, but `AddLeftStrictMono K` cannot be removed. I will need help with this proof. If nothing else works, the lemma can also be reverted into the previous form with `IsOrderedAddMonoid K` + `AddLeftStrictMono K`.~~ ~~The lemma `floor_div_natCast` affects `floor_div_eq_div`, `IsNNRat.natFloor`, and the `norm_num` extension `evalNatFloor`.~~ (The above has been resolved at the cost of one extra import.) Other than this problem, should I give a documentation of when to use `IsOrderedAddMonoid`, `IsOrderedRing`, etc. or avoid them altogether in lemmas about `FloorRing`s? t-algebra
label:t-algebra$
87/100 Mathlib/Algebra/Order/Floor/BigOperators.lean,Mathlib/Algebra/Order/Floor/Defs.lean,Mathlib/Algebra/Order/Floor/Ring.lean,Mathlib/Algebra/Order/Floor/Semifield.lean,Mathlib/Algebra/Order/Round.lean,Mathlib/MeasureTheory/Integral/IntervalIntegral/Periodic.lean 6 6 ['chenson2018', 'github-actions', 'mortarsanjaya'] nobody
32-16935
1 month ago
41-31912
41 days ago
41-32005
41 days
0
45111 will1491
author:will1491
feat(Topology/ContinuousMap): define normal families Define `IsNormalFamily` for families of continuous maps into `OnePoint Y` as compactness of their closure in the compact-open topology. The one-point compactification is chosen for applications in complex dynamics. See the [Zulip discussion](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Geometry.20and.20complex.20dynamics.20formalization/with/615696635) for the definition and design discussion. Co-authored-by: Lasse Rempe <lasse.rempe@manchester.ac.uk> Co-authored-by: Filip Moruś <filip.morus@postgrad.manchester.ac.uk> --- t-topology new-contributor 30/0 Mathlib.lean,Mathlib/Topology/ContinuousMap/NormalFamily.lean 2 3 ['JX-Mo', 'github-actions'] nobody
32-10902
1 month ago
32-45601
32 days ago
32-45546
32 days
0
45130 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Basic): `commonNeighbors` is a strict subset of `neighborSet` for adjacent vertices Add `G.Adj u v → G.commonNeighbors u v ⊂ G.neighborSet u` and use it to golf `Adj.card_commonNeighbors_lt_degree`. --- Also reworded the docstring because `card_commonNeighbors_le_degree` does not exist (never did) and it confused me. This is from leanprover-community/mathlib3#5789. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-combinatorics 14/7 Mathlib/Combinatorics/SimpleGraph/Basic.lean,Mathlib/Combinatorics/SimpleGraph/Finite.lean 2 1 ['github-actions'] nobody
32-4813
1 month ago
32-5516
32 days ago
32-5461
32 days
1
43578 WilliamCoram
author:WilliamCoram
feat: identifying WithZero (Multiplicative M) and WithTop M We identify `Mᵐ⁰ = WithZero (Multiplicative M)` with `WithTop M` in the form of an order-and-additive isomorphism. In future work this will allow us to define additive valuations from valuations with a usable target (specifically attaching to a rank one discrete valuation an additive valuation into WithTop Z). AI usage: The need of attaching additive valuations to valuations came up in my Newton polygon work - after some discussion with people and Claude this was the approach I felt worked best for me. The file was drafted and written by Claude with my input and cleaning. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) LLM-generated t-algebra
label:t-algebra$
142/0 Mathlib.lean,Mathlib/Algebra/Order/GroupWithZero/NegLog.lean 2 7 ['Multramate', 'WilliamCoram', 'faenuccio', 'github-actions', 'jjdishere'] nobody
31-84983
1 month ago
75-2679
75 days ago
75-2863
75 days
1
45135 rmcrkd
author:rmcrkd
feat(Analysis/Calculus/Deriv/Inverse): add HasDerivWithinAt.of_local_left_inverse Add lemma `HasDerivWithinAt.of_local_left_inverse`, following the existing pattern via `HasDerivWithinAt.hasFDerivWithinAt_equiv`. Assisted by Claude (found the gap, helped with learning and examples, linting and building). --- [#mathlib4 > HasDerivWithinAt.of_local_left_inverse](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/HasDerivWithinAt.2Eof_local_left_inverse/with/633245785) t-analysis new-contributor 18/0 Mathlib/Analysis/Calculus/Deriv/Inverse.lean 1 9 ['github-actions', 'grunweg', 'rmcrkd'] nobody
31-65233
1 month ago
31-65233
31 days ago
31-66213
31 days
0
45156 mcdoll
author:mcdoll
feat: the Fourier transform from L1 to C0 and simplification of Riemann-Lebesgue --- The deprecated theorems amount to roughly 120 lines of code less. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology large-import 89/31 Mathlib/Analysis/Distribution/SchwartzSpace/Basic.lean,Mathlib/Analysis/Distribution/SchwartzSpace/Fourier.lean,Mathlib/Analysis/Fourier/LpSpace.lean,Mathlib/Analysis/Fourier/RiemannLebesgueLemma.lean,Mathlib/Topology/ContinuousMap/ZeroAtInfty.lean 5 1 ['github-actions'] nobody
31-32269
1 month ago
31-33033
31 days ago
31-32978
31 days
0
45176 marcelolynch
author:marcelolynch
ci: shake Archive and Counterexamples in the weekly shake job This PR adds `Archive` and `Counterexamples` to the weekly `lake shake` job. The job fetches their oleans with `lake exe cache get Archive.lean Counterexamples.lean` and builds them before it runs `lake shake`. Five files get `shake: keep` annotations. `lake shake` does not see the uses inside `example` declarations or the `deriving Fintype` handler. Without the annotations, its edits break these files. With the annotations, the 76 shake edits to `Archive` and `Counterexamples` build. A fork PR runs the workflow file from `master`, so this PR cannot test the workflow change in CI. 🤖 new-contributor 10/10 .github/workflows/shake.yaml,Archive/Examples/Eisenstein.lean,Archive/Imo/Imo1988Q6.lean,Archive/Wiedijk100Theorems/Konigsberg.lean,Counterexamples/OrderedCancelAddCommMonoidWithBounds.lean,Counterexamples/ZeroDivisorsInAddMonoidAlgebras.lean 6 2 ['github-actions'] nobody
30-83269
30 days ago
30-83269
30 days ago
30-83214
30 days
0
44028 alreadydone
author:alreadydone
feat(Topology): add `Homeomorph.Isotopy` and `MappingClassGroup` Also defines action of `MappingClassGroup` on singular homology, which can be used to define Torelli groups. Note: for an orientable surface (or manifold) it's common in the literature to refer to the subgroup consisting of orientation-preserving (equivalently, acting trivially on top homology) homeomorphisms as the mapping class group. In our setup, this can be obtained by `(MappingClassGroup.toAutSingularHomology n).ker`, where `n` is the dimension. TODO: define relative `Isotopy` (similar to `HomotopyRel`) and relative MCG. Homotopy invariance of relative singular homology is at https://github.com/TauCetiProject/TauCeti/pull/7266. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebraic-topology t-topology 236/2 Mathlib.lean,Mathlib/AlgebraicTopology/SingularHomology/Basic.lean,Mathlib/AlgebraicTopology/SingularHomology/HomotopyInvariance.lean,Mathlib/Topology/Category/TopCat/Basic.lean,Mathlib/Topology/ContinuousMap/Basic.lean,Mathlib/Topology/Homotopy/Basic.lean,Mathlib/Topology/Homotopy/Equiv.lean,Mathlib/Topology/Homotopy/Isotopy.lean 8 4 ['github-actions', 'joelriou', 'mathlib-merge-conflicts'] nobody
30-20667
30 days ago
30-69524
30 days ago
38-71077
38 days
1
43332 SnirBroshi
author:SnirBroshi
feat(SimpleGraph/Walk/Basic): walks with equal support have equal darts and similar statements: - `p.darts = q.darts ↔ p.support = q.support` (equal) - `p.darts <:+: q.darts ↔ p.support <:+: q.support` (infix) - `p.darts <+: q.darts ↔ p.support <+: q.support` (prefix) - `p.darts <:+ q.darts ↔ p.support <:+ q.support` (suffix) --- I hope the review process can help golf these or find better proofs. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 71/23 Mathlib/Combinatorics/SimpleGraph/Walk/Basic.lean,Mathlib/Combinatorics/SimpleGraph/Walk/Operations.lean,Mathlib/Combinatorics/SimpleGraph/Walk/Subwalks.lean 3 17 ['SnirBroshi', 'github-actions', 'mathlib-merge-conflicts', 'vlad902'] nobody
30-17560
30 days ago
30-18231
30 days ago
78-13594
78 days
0
45202 Hagb
author:Hagb
feat(RingTheory/MvPolynomial/MonomialOrder): some lemmas about `withBotDegree` It is lemmas used in #45208. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory 50/0 Mathlib/RingTheory/MvPolynomial/MonomialOrder.lean 1 4 ['github-actions', 'vlad902'] nobody
29-85049
29 days ago
30-28385
30 days ago
30-28515
30 days
1
44968 SnirBroshi
author:SnirBroshi
feat(LinearAlgebra/Finsupp/LinearCombination): bundle `linearCombination` as an `AddMonoidHom` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
47/48 Mathlib/LinearAlgebra/Dimension/Basic.lean,Mathlib/LinearAlgebra/Dimension/StrongRankCondition.lean,Mathlib/LinearAlgebra/Finsupp/LinearCombination.lean,Mathlib/RingTheory/Ideal/Basic.lean,Mathlib/RingTheory/MvPolynomial/Groebner.lean,Mathlib/RingTheory/MvPolynomial/Homogeneous.lean,Mathlib/RingTheory/MvPolynomial/WeightedHomogeneous.lean,Mathlib/RingTheory/Unramified/Finite.lean 8 9 ['Hagb', 'SnirBroshi', 'github-actions', 'leanprover-radar', 'themathqueen'] nobody
29-77477
29 days ago
33-66215
33 days ago
35-63555
35 days
1
42072 joneugster
author:joneugster
feat(scripts/autolabel): use PR-title to find labels If present, use the paths specified in the PR title to determine labels. If this fails, fall back to the existing `git diff` logic. - further: cleanup to use `githubAnnotation` consistently throughout the script. (the helper itself could be refactored to make some arguments optional, I'd prefer doing that in a follow-up) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) CI 48/12 .github/workflows/add_label_from_diff.yaml,scripts/autolabel.lean 2 5 ['SnirBroshi', 'github-actions', 'joneugster', 'mathlib-merge-conflicts'] nobody
29-53520
29 days ago
56-2565
56 days ago
70-66779
70 days
0
42186 marcelolynch
author:marcelolynch
refactor(Tactic/Linter/MinImports): make the minImports linter stateful This PR rewrites the `minImports` linter as a stateful linter (leanprover/lean4#14357). The linter behavior does not change. The existing tests in `MathlibTest/MinImports.lean` pass without changes. The PR adds one test section that sets `Elab.async true` explicitly: it checks that the linter accumulates imports correctly under parallel elaboration, and that `#import_bumps` keeps parallel elaboration on. The old implementation kept the cumulative imports in a global `IO.Ref`. The ref is not safe under parallel elaboration. For this reason, `#import_bumps` set `Elab.async false` for the rest of the file. The new implementation keeps the same data in the linter state. The elaborator threads the state through the commands of the file, and the data stays correct under parallel elaboration. `#import_bumps` does not disable `Elab.async` anymore. Implementation notes: - The `#reset_min_imports` elaborator does nothing. The linter detects the command syntax and clears its own state. The reset works also when the linter option is off, as before. - The post phase removes `set_option ... in` prefixes with `withSetOptionIn` from core. leanprover/lean4#14581 generalizes the result type of that function, so it accepts the phase of a stateful linter and not only a `CommandElab`. The generalization ships in v4.34.0-rc1. - The state type `ImportState` and the linter handle are public. A follow-up can pass the computed import set to the `upstreamableDecl` linter, which computes the same data a second time today. Measurements on synthetic files (Apple Silicon, 18 cores, medians of 3 runs): - Proof-heavy file (150 commands, about 120 ms each), linter on: 20.0 s before, 8.8 s after. The old version serialized elaboration of the whole file. The new version keeps elaboration parallel and runs the lint chain next to it. - The old version with `Elab.async true` emits 123 warning lines instead of the correct 11, because parallel lint tasks race on the ref. The new version emits the correct 11 lines. - Linter off (2000 trivial commands): the added cost is about 45 microseconds per command. `registerStatefulLinter` shipped in v4.34.0-rc1 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-linter LLM-generated 149/78 Mathlib/Tactic/Linter/MinImports.lean,MathlibTest/MinImports.lean 2 3 ['JovanGerb', 'github-actions', 'thorimur'] nobody
29-50354
29 days ago
102-62285
102 days ago
102-62230
102 days
0
40204 Jun2M
author:Jun2M
feat(Combinatorics/HypergraphLike): add HypergraphLike class Introduces `HypergraphLike V I E G`, an object-indexed incidence interface for developing common graph theory across different representations. Defines links and adjacency, incidence maps and fibers, and sets of incident vertices and edges. The basic API provides membership characterizations, fiber disjointness and union identities, and relationships between incidence data, links, and adjacency. Codex assisted with the initial implementation and review; the code was subsequently revised by me. The following is a longer write-up about what this PR is for, what this PR has, and why it is in this shape. ## Considerations 1. The main consideration for this PR is to create a common language different graph types can use to communicate their structure. The data in the type class is deliberately chosen to be as general as possible, accommodating hypergraphs, digraphs, simple graphs, and more. 2. (Hyper)Graphs are used both as a setting in which vertices, edges, walks, and colorings live, and as an algebraic object that can be modified. These two viewpoints can sometimes be at odds with each other. This typeclass is an acknowledgement that these two viewpoints are different, and both need to be fully supported separately with explicit connection. `HypergraphLike` is the way to view a graph as a setting. Various different graph structures are ways to view a graph as an algebraic object. 3. Graph theory has a lot of uses outside of graph theory. For example, group theory, topology, and more. The type class is designed to be easily applied to an arbitrary object that can be associated with a graph structure. ## Contents The definition consists of: | Data | Meaning | | --- | --- | | `V`, `I`, `E` | Ambient types of vertex, incidence, and edge labels | | `V(G)`, `I(G)`, `E(G)` | The set of objects of the (hyper)graph structure | | `attach'`, `edgeMap'` | The vertex and edge assigned to each incidence | | `IsSource`, `IsTarget` | The directions in which an incidence can be traversed | Every incidence is a source, a target, or both. This allows directed and undirected incidences in the same object. Distinct incidences may belong to the same vertex and edge. `HypergraphLike` does not require the object to be a graph or hypergraph, or to be related to one. Any object can be associated with a (hyper)graph structure and use the graph theory API as such via a `HypergraphLike` instance. As a result, it is possible for an arbitrary object to be associated with a graph structure that it has nothing to do with. - **`Link G e u v`:** a traversal of `e` from `u` to `v`, retaining a source incidence and a distinct target incidence. Distinctness prevents entering and leaving an undirected edge through the same incidence. - **`IsLink` and `Adj`:** the existence of a link through a specified edge, and the existence of an edge linking two vertices. - **`attach` and `edgeMap`:** total extensions of the incidence maps when the corresponding types are nonempty. - **`edgeFiber` and `vertexFiber`:** the incidences belonging to an edge or vertex. - **`incVerts` and `incEdges`:** the vertices incident to an edge and the edges incident to a vertex. Apart from operations, graph API should be built on this type class. More specialized theories can add assumptions such as undirectedness, looplessness, or restrictions on the incidences of each edge. See PRs #43768, #43748 and more to come. ## Design decisions ### Why not require one concrete representation? Alternative approach to unify various graph structures is to have one very general hypergraph definition and put all possible API there. By extending the definition with other conditions, you can inherit all the API while describing the graph class you want. This is not used here because 1. It either loses the expected extensionality or restricts which representations can use the API. 2. The API can be inherited using the current instance method more generally (you don't need to `extend` the particular def to inherit them) 3. These two approaches have virtually no difference in formalization cost. Asterisk for number 3 is that I have not tried to formalize every part of graph theory so it should be taken with a grain of salt. Nevertheless, I have not found cases where `extend` method reduces the formalization cost significantly. The generality of application is the strong suit of the current approach. The discussion that led to this PR started with efforts to unify different graph structures in Mathlib and future structures to be implemented. The instance method allows even more flexibility. We could talk about a group (with a chosen generating set) being `HypergraphLike` by associating it with a Cayley graph, a CW complex with its 1-skeleton graph, or a lattice with its Hasse graph, in the same manner `SimpleGraph` is `HypergraphLike`. With `extend`, these will require a separate, bespoke association with the appropriate graph structure. So, it suffices to argue that number 1 is true. The difficulty comes from the fact that the child structures have to contain additional data and therefore additional freedom that it really doesn't need. Consider two simple graphs `G` and `H`, each with vertex set `{u, v}` and single edge between them. In the naive approach where you define `SimpleGraph` like this: ```lean structure SimpleGraph (ν ι ε : Type*) extends undirected ν ι ε, noMultiEdges ν ι ε ... where ``` Then, `G = H` may not hold. They could have different edge type, incidence type, edge set, incidence set, etc. That is, we have extensionality issue. The fix is to constrain further until simple graph structure uniquely determines the rest. Here is one possible definition: ```lean structure SimpleGraph (ν : Type*) extends undirected ν (ν × ν) (Sym2 ν), noMultiEdges ν (ν × ν) (Sym2 ν) ... where edgeMap'_eq (i) : edgeMap' i = Sym2.mk i.val.fst i.val.snd attach'_eq (i) : attach' i = i.val.fst ``` Now, any `multigraph` that happens to be a simple graph cannot use `SimpleGraph` results without going through the normalization function, showing that normalization only changed the labels and showing that the normalization function preserves whatever properties, etc. Results that depend on simplicity should be available for arbitrary incidence representations satisfying simplicity, rather than only for a canonical `SimpleGraph` representation. This happens every time a canonical form is chosen to resolve extensionality issues. ### Why per-object indexing? Indexing by graph type was something I have adopted from `HasAdj` PR (#35776) without critical thinking. In the discussion for `Quiver` (#45034), as soon as I wrote "HypergraphLike expects you to know the edge type before you know what graph you are working with.", I started to think why this is necessary. It is not. All the code I have about HypergraphLike can be migrated to per-object indexing very easily. The statements did get longer due to adding `HypergraphLike` instance to each graph object but virtually all proofs worked without any changes. Philosophically, it makes the role of `HypergraphLike` clearer. `HypergraphLike` is defined to have one common language between different graph structures and that common language is the label types and incidence data. Merely belonging to the same Lean type should not impose additional uniformity. Where a result needs shared labels or compatible incidence maps, it can state those requirements explicitly. In the cases of `Quiver`, it can be supported by `HypergraphLike` as now we supply the edge type along with the specific `Quiver` instance, not before. Another benefit is that you can use `HypergraphLike` even when not all elements of a type can be interpreted as a graph. This aligns with the rest of the type class hierarchy being built on `HypergraphLike`. (#43768, #43748) `G : Graph V E` could happen to be a simple graph. A subset of a plane could be graph-like. ### Why ambient labels and support sets? The `id` function holds a special place in our heads. Consider `G`, K4 graph with vertex set `{1, 2, 3, 4}`, and `H`, K5 graph with vertex set `{1, 2, 3, 4, 5}`. Remove edge `s(1, 2)` from `H`. Up to isomorphism, `G` is still a subgraph of `H`. But, with respect to the `id` function, `G` is no longer a subgraph of `H`. Without support sets, the vertex set is the whole type, so graphs on different vertex sets live on different types. Then only embeddings can be stated, and you lose the labelled subgraph relation. That is, without some special treatment for subtypes, `HypergraphLike` will say `G` is a subgraph of `H` as there exists embedding of `G` into `H`. Support sets in the type class are exactly the mechanism that allows "special treatment" for subtypes. ## Related work (Not dependency) - #36743 - [HasAdj discussion](https://leanprover.zulipchat.com/#narrow/channel/252551-graph-theory/topic/HasAdj/with/575843445) Co-authored-by: OpenAI Codex <codex@openai.com> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics LLM-generated maintainer-merge 458/0 Mathlib.lean,Mathlib/Combinatorics/HypergraphLike/Basic.lean 2 59 ['Jun2M', 'SnirBroshi', 'YaelDillies', 'copilot-pull-request-reviewer', 'github-actions', 'tb65536'] nobody
29-3017
29 days ago
29-44776
29 days ago
141-9123
141 days
10
44913 Hagb
author:Hagb
chore(Algebra/MonoidAlgebra/Ideal): prove `AddMonoidAlgebra.mem_ideal_span_of'_image` with its `MonoidAlgebra` version Resolve the TODO in `AddMonoidAlgebra.mem_ideal_span_of'_image`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra large-import
label:t-algebra$
6/29 Mathlib/Algebra/MonoidAlgebra/Ideal.lean 1 1 ['github-actions'] nobody
28-78783
28 days ago
28-78785
28 days ago
28-79041
28 days
0
44061 teorth
author:teorth
feat(NumberTheory/Mertens): abstract theory of Mertens weights This is the first of a three-PR stack splitting the Mertens theorems development (#41394) into pieces under 500 LoC each. It introduces `Mathlib/NumberTheory/Mertens/Weight.lean`: the abstract theory of *Mertens weights* — the `Mertens.Weight` structure and the basic estimates attached to it (the `E₁`/`E₂` error bounds, `sum_sub_log_*`, `M_bounds`, `sum_div_log_*`, …). No concrete weight is constructed here; this will be done in #44062. --- The code was human-generated, but reviewed by AI. - [x] depends on: #41120 - [x] depends on: #43471 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-number-theory 502/0 Mathlib.lean,Mathlib/NumberTheory/Mertens/Weight.lean 2 11 ['MichaelStollBayreuth', 'amellendijk', 'github-actions', 'loefflerd', 'mathlib-dependent-issues', 'xroblot'] amellendijk
assignee:amellendijk
28-65562
28 days ago
52-3500
52 days ago
60-43939
60 days
2
45266 RemyDegenne
author:RemyDegenne
feat(MeasureTheory): analytic sets wrt a paving Define analytic sets with respect to a paving (`IsPavingAnalytic`), which will be used to prove Choquet's capacitability theorem (the full proof is ready in the Brownian motion project). These sets are not the same as `MeasureTheory.AnalyticSet`, although in Polish spaces they are closely related as described in the file docstring (this will be shown in a future PR). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Most of the PR was written by hand first (notable exception: the lemma `IsPavingAnalyticFor.isPavingAnalyticFor_nat_nat`), but an LLM reviewed and golfed several proofs. brownian LLM-generated t-measure-probability 395/1 Mathlib.lean,Mathlib/MeasureTheory/PavingAnalytic.lean,Mathlib/Topology/Compactness/CompactSystem.lean,docs/references.bib 4 1 ['github-actions'] nobody
28-28280
28 days ago
28-28915
28 days ago
28-28860
28 days
0
45268 RemyDegenne
author:RemyDegenne
feat: bounds on covering numbers in finite dimensional spaces The main result is bounds of order `(r / ε) ^ d` on the covering numbers of a ball of radius `r` at scale `ε`. Co-authored-by: Etienne Marion <66847262+EtienneC30@users.noreply.github.com> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> First written by hand for the `volume` measure in inner product spaces, then generalized with an LLM. LLM-generated t-analysis brownian t-measure-probability 277/0 Mathlib.lean,Mathlib/Analysis/Normed/Module/Ball/Pointwise.lean,Mathlib/Basic/ENNReal/Inv.lean,Mathlib/MeasureTheory/Measure/Lebesgue/CoveringNumbers.lean,Mathlib/MeasureTheory/Measure/Lebesgue/EqHaar.lean,Mathlib/Topology/EMetricSpace/Defs.lean,Mathlib/Topology/MetricSpace/MetricSeparated.lean 7 1 ['github-actions'] nobody
28-20442
28 days ago
28-21803
28 days ago
28-21748
28 days
0
45272 RemyDegenne
author:RemyDegenne
feat(Topology/EMetricSpace): chaining sequences Define a chaining sequence, which is a tool used to bound the supremum of stochastic processes. Part of the proof of the Kolmogorov-Chentsov theorem. Co-authored-by: Markus Himmel <markus@lean-fro.org> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology brownian 284/0 Mathlib.lean,Mathlib/Analysis/SpecificLimits/Basic.lean,Mathlib/Topology/EMetricSpace/Chaining.lean 3 1 ['github-actions'] nobody
28-15937
28 days ago
28-17243
28 days ago
28-17188
28 days
0
44810 zixiaowang17
author:zixiaowang17
feat(Combinatorics): add abstract graphical Markov properties Introduce the global, local, and pairwise Markov properties for undirected graphs, and prove the forward implications global → local → pairwise under the semigraphoid axioms. The implementation is a single module importing `Mathlib.Combinatorics.SimpleGraph.Walk.Basic`. The current framework allows arbitrary vertex types, including infinite and uncountable types. Reference: David Montague and Bala Rajaratnam, *Graphical Markov models for infinitely many variables*, *Transactions of the American Mathematical Society* **370** (2018), no. 11, 7557–7603. [doi:10.1090/tran/7048](https://doi.org/10.1090/tran/7048). --- I want to introduce “a graphical framework in which we can analyze the Markov properties from a purely set theoretic perspective which is independent of probability theory,” as described in [Section 4](https://arxiv.org/pdf/1501.07878#page=8). Motivation: I was trying to provide a common foundation connecting graphical models in statistics, random fields, and percolation on lattices. Along the way, I found that most of the materials I read assumed finite vertex sets. However, I want to understand better what drives the equivalence of the Markov properties, so that we can talk about theorems with more flexibility. I then found this paper, which, in Section 4, takes a purely set-theoretic approach to independence and graphical Markov properties, separately from its treatment of measure-theoretic conditional independence in probabilistic models. If this PR meets the requirements and is in the right direction, I plan to finish proving the equivalence of the pairwise, local, and global Markov properties for ternary relations under suitable intersection assumptions. In the long term, I plan to connect conditional independence in probability with graphical models, including DAGs. AI assistance: OpenAI Codex assisted with the Lean definitions and proofs. I checked every line of the code. t-combinatorics LLM-generated new-contributor 231/0 Mathlib.lean,Mathlib/Combinatorics/SimpleGraph/Markov.lean,docs/references.bib 3 4 ['github-actions', 'zixiaowang17'] nobody
27-79624
27 days ago
40-55074
40 days ago
40-55019
40 days
0
44978 ArtificialZeng
author:ArtificialZeng
feat(Analysis/Normed/Module): uniform bounds for compact injective families A continuous family of injective continuous linear maps, with finite-dimensional source over a complete nontrivially normed field, has a uniform positive lower bound on a compact parameter set. A second lemma gives a uniform operator-norm perturbation radius preserving injectivity; the perturbing family need not be continuous. These estimates support compact-family derivative perturbation arguments. The proof uses `LinearMap.exists_antilipschitzWith` and `IsCompact.induction_on`, adds no imports, and does not require the target to be finite-dimensional or complete. --- Local validation on base `4c71e7e7e5f99e938e520c4242aaf2522a594953`, Lean 4.36.0-rc1: - `lake build Mathlib.Analysis.Normed.Module.FiniteDimension` passed after refreshing the base's dependency cache. - Standard Mathlib source linters and examples covering a nonconstant compact family, empty sets, and a zero-dimensional source passed. - A separate fresh compilation and axiom queries passed; both lemmas use only `propext`, `Classical.choice`, and `Quot.sound`. - The same new proofs and a downstream derivative-estimate consumer also compiled against the pinned Lean 4.35.0 baseline. AI disclosure: OpenAI Codex generated and adapted the proofs and performed automated source review and local checks. This draft is pending human review of the mathematics and API choices. Automated checks and AI review do not replace that review. Full upstream CI is still required. t-analysis LLM-generated new-contributor 57/0 Mathlib/Analysis/Normed/Module/FiniteDimension.lean 1 3 ['ArtificialZeng', 'github-actions'] nobody
27-79408
27 days ago
35-78299
35 days ago
35-78244
35 days
0
45204 Hagb
author:Hagb
feat(Combinatorics/Colex): `Colex (Finset _)` is well-founded It is used in #45208 to prove the termination of multivariate polynomial reduction with decreasing `Colex` order on support of reduced polynomial w.r.t. the monomial order. (Lemmas about this fact are proved in #45206.) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> large-import t-combinatorics 74/0 Mathlib/Combinatorics/Colex.lean,Mathlib/Data/DFinsupp/WellFounded.lean,Mathlib/Order/PiLex.lean 3 14 ['Hagb', 'github-actions', 'vihdzp'] nobody
27-78602
27 days ago
30-37445
30 days ago
30-37390
30 days
1
42874 teorth
author:teorth
feat(RingTheory/MvPolynomial/Symmetric): basic API lemmas for Multiset.esymm Add basic lemmas for the elementary symmetric functions `Multiset.esymm`: `esymm_cons`, `esymm_zero`, `esymm_one`, `esymm_card`, `esymm_eq_zero_of_card_lt`, `two_mul_esymm_two`, and `esymm_map_inv` (with a private auxiliary). Also drop the redundant `@[simp]` on `esymm_pair_one`, which is now provable by `simp` from `esymm_one`. --- The code here was prepared with AI assistance, but then golfed and reviewed by myself. It will be used in a forthcoming PR on the Newton and Maclaurin inequalities. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 32/0 Mathlib/RingTheory/MvPolynomial/Symmetric/Defs.lean 1 8 ['felixpernegger', 'github-actions', 'teorth', 'vlad902'] nobody
27-76799
27 days ago
54-55506
54 days ago
55-59173
55 days
1
43211 YaelDillies
author:YaelDillies
feat(Geometry/Convex): ordered convex spaces Define ordered convex spaces as those convex spaces for which taking convex combinations is monotone in its inputs. Since `sConvexComb : StdSimplex R X → X`, the best way to do so is to equip `StdSimplex R X` with the stochastic dominance order and requiring `sConvexComb` to be monotone under that order. Also define two constructors to pull back a ConvexSpace instance under an injective map with convex range: a computable one further taking a section of the map as input, and a non-computable one. Redefine the `Subtype` instance and define the `OrderDual` instance using the computable one. Generated by Claude Opus following my existing draft, then reviewed and partly rewritten by myself. From the convexity refactor. Ordered convex spaces will be used to define convex/concave functions. Assisted-by: Claude Opus 5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-convex-geometry LLM-generated 458/10 Mathlib.lean,Mathlib/Algebra/Order/Monoid/Unbundled/Basic.lean,Mathlib/Data/Finsupp/Basic.lean,Mathlib/Geometry/Convex/ConvexSpace/Defs.lean,Mathlib/Geometry/Convex/ConvexSpace/Order.lean,Mathlib/Geometry/Convex/Set.lean,Mathlib/Order/UpperLower/Basic.lean 7 21 ['YaelDillies', 'eric-wieser', 'github-actions', 'mathlib-merge-conflicts'] nobody
27-72001
27 days ago
40-27913
40 days ago
79-23155
79 days
0
41053 hawkrobe
author:hawkrobe
refactor(RingTheory): bialgebra and Hopf algebra structures on RingCon quotients --- Since #40451, SymmetricAlgebra R M is (symRingCon R M).Quotient, which the ideal quotients of #39790 don't cover. This PR adds the congruence-level constructions, so SymmetricAlgebra's bialgebra and Hopf algebra structures can descend from TensorAlgebra as suggested in #39579, once #31898 lands. - [x] depends on: #41052 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory new-contributor 154/41 Mathlib/RingTheory/Bialgebra/Quotient.lean,Mathlib/RingTheory/HopfAlgebra/Quotient.lean 2 6 ['github-actions', 'hawkrobe', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
27-61574
27 days ago
34-61252
34 days ago
34-66621
34 days
0
45136 raja-19
author:raja-19
chore(RingTheory/MvPolynomial/Homogeneous): add lemmas These lemmas are used in the proof that the Motzkin polynomial is not expressible as a polynomial sum of squares: #45138. t-ring-theory new-contributor 52/0 Mathlib/RingTheory/MvPolynomial/Homogeneous.lean 1 9 ['github-actions', 'raja-19', 'vihdzp', 'wwylele'] nobody
27-16123
27 days ago
31-82690
31 days ago
31-82635
31 days
1
45137 raja-19
author:raja-19
chore(Algebra/Polynomial/BigOperators): add `natDegree_sum_pow_eq_of_even` This lemma is used in the proof that the Motzkin polynomial is not expressible as a polynomial sum of squares: #45138 . t-algebra new-contributor
label:t-algebra$
125/0 Mathlib/Algebra/Polynomial/BigOperators.lean,Mathlib/Algebra/Polynomial/Degree/Operations.lean,Mathlib/Order/WithBot.lean 3 20 ['SnirBroshi', 'github-actions', 'raja-19', 'wwylele'] nobody
27-14108
27 days ago
30-69426
30 days ago
31-62027
31 days
1
42561 SnirBroshi
author:SnirBroshi
feat(Order/RelSeries): order series by refinement Define a partial order on `RelSeries`, add basic lemmas for the operations (e.g. `p < p.append q`), and relate to `IsChain` on sets. This lets us spell "maximal chain" using series. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) tech debt t-order 151/5 Mathlib/Order/RelSeries.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
26-68334
26 days ago
26-70529
26 days ago
106-30607
106 days
0
45326 hawkrobe
author:hawkrobe
feat(Algebra/DirectSum): internal direct sums under equivalences and fibrewise regrouping this PR gives two ways of producing internal direct sums. * a direct sum is the internal direct sum of the images of its summands. * regrouping an internal direct sum along the fibres of `f : ι → κ` gives an internal direct sum. these are used in the proof that a tensor product of graded modules is graded (#42365). Claude Code was used to prepare this PR. t-algebra
label:t-algebra$
89/1 Mathlib/Algebra/DirectSum/Basic.lean,Mathlib/Algebra/DirectSum/Module.lean 2 1 ['github-actions'] nobody
26-68229
26 days ago
26-70498
26 days ago
26-72932
26 days
2
45157 tb65536
author:tb65536
feat(Analysis/Matrix/Normed): non-archimedean operator norm inequality For matrices over a non-archimedean `SeminormedAddCommGroup`, the operator norm is not quite non-archimedean, but is at least non-archimedean up to multiplication by the number of columns (independent of the number of terms of the sum). This is used in #42985 to prove that the Gelfand radius norm is nonarchimedean. (I didn't bother adding the two-term version `‖M + N‖ ≤ Fintype.card β * max ‖M‖ ‖N‖` since it only beats the trivial bound `‖M + N‖ ≤ 2 * max ‖M‖ ‖N‖` when `β` is subsingleton). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 15/0 Mathlib/Analysis/Matrix/Normed.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
26-60888
26 days ago
26-61569
26 days ago
31-14174
31 days
1
44021 mcdoll
author:mcdoll
feat(Analysis/Normed): boundedness of seminorms Define abstract boundedness and equivalence and use it to define both for seminorms. This has several aims: (a) do the same thing for families of seminorms and simplify some of the boundedness of linear maps construction (b) allow for equivalent norms of a normable space without any type synonyms (c) a streamlined version of `LinearMap.extendOfNorm` which hides most of the boilerplate. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 277/0 Mathlib.lean,Mathlib/Algebra/Order/Module/Defs.lean,Mathlib/Analysis/Normed/Module/Seminorm/Bounded.lean 3 1 ['github-actions'] nobody
26-51623
26 days ago
26-53727
26 days ago
26-55783
26 days
0
43427 smmercuri
author:smmercuri
feat: `LiesOver` valuations on `adicCompletion` --- - [x] depends on: #36769 - [x] depends on: #43428 - [x] depends on: #41702 - [x] depends on: #44279 - [x] depends on: #44666 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 191/13 Mathlib/NumberTheory/NumberField/Completion/FinitePlace.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Completion.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Ramification.lean,Mathlib/RingTheory/Valuation/Extension.lean 4 5 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'tb65536'] nobody
26-16720
26 days ago
26-17544
26 days ago
26-28251
26 days
2
45331 plp127
author:plp127
feat(RingTheory/Valuation): cardinality of a valued field is bounded by the cardinality of the residue field and value group We show the cardinality of a valued field is at most the cardinality of the residue field raised to the power of the cardinality of the value group. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory 89/0 Mathlib.lean,Mathlib/RingTheory/Valuation/Basic.lean,Mathlib/RingTheory/Valuation/Cardinality.lean 3 4 ['github-actions', 'vihdzp'] nobody
25-68873
25 days ago
26-70108
26 days ago
26-70053
26 days
0
42189 cameronfreer
author:cameronfreer
feat(ModelTheory/Basic): add characterization of languages with countably many symbols Add the instance `Countable.countable_relations`, the counterpart of `Countable.countable_functions`, and relate `Countable L.Symbols` and `L.card ≤ ℵ₀` to the separate countability of function and relation symbols, which is how model-theoretic statements usually assume a countable language: * `countable_symbols_iff : Countable L.Symbols ↔ Countable (Σ l, L.Functions l) ∧ Countable (Σ l, L.Relations l)` * `card_le_aleph0_iff_countable : L.card ≤ ℵ₀ ↔ Countable (Σ l, L.Functions l) ∧ Countable (Σ l, L.Relations l)` Also add a general instance `Countable.countable_sum` for `L.sum L'`, move the `constantsOn` instance from `Encoding.lean` to `LanguageMap.lean` as `Countable.countable_constantsOn`, and replace the `withConstants` instance in `Encoding.lean` with `Countable.countable_withConstants` in `LanguageMap.lean`, derived from the sum instance. --- For example, [`Descriptive/Polish.lean#L46`](https://github.com/cameronfreer/infinitary-logic/blob/1a478e80794080a536931c029281bb65266b3171/InfinitaryLogic/Descriptive/Polish.lean#L46) in cameronfreer/infinitary-logic assumes only that the relation symbols are countable. Thanks to @NoneMore for suggesting the `Encoding.lean` cleanup. 🤖 These proofs were written with the assistance of Claude Opus 5 high and reviewed by GPT Sol 5.6 xhigh. t-logic new-contributor LLM-generated 33/12 Mathlib/ModelTheory/Basic.lean,Mathlib/ModelTheory/Encoding.lean,Mathlib/ModelTheory/LanguageMap.lean 3 5 ['NoneMore', 'cameronfreer', 'github-actions'] nobody
25-68356
25 days ago
116-26935
116 days ago
116-30088
116 days
0
42758 cameronfreer
author:cameronfreer
feat(ModelTheory): add syntax and semantics for infinitary logic Add syntax and semantics for the infinitary logics L∞ω and Lω₁ω. In `BoundedFormulaInf L ι α n`, the `iSup`/`iInf` constructors are indexed by a single type `ι`, which is used for every infinitary conjunction and disjunction in a formula. The specialization ```lean abbrev BoundedFormulaω (α : Type u') (n : ℕ) := L.BoundedFormulaInf ℕ α n ``` lives in the same universe as the finitary `BoundedFormula`, as suggested by @plp127 in [#mathlib4 > ModelTheory: API for infinitary formulas of L_{∞,ω} @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/ModelTheory.3A.20API.20for.20infinitary.20formulas.20of.20L_.7B.E2.88.9E.2C.CF.89.7D/near/613390601). Also add derived connectives with `alls`/`exs`, `Realize` with `simp` lemmas for each constructor and derived connective, and the embedding `BoundedFormula.toInf` with `realize_toInf`. --- I developed this with extensive assistance from several Claude and GPT models along with [lean4-skills](https://github.com/cameronfreer/lean4-skills) and [lean-lsp-mcp](https://github.com/oOo0oOo/lean-lsp-mcp) as part of the ongoing project [cameronfreer/infinitary-logic](https://github.com/cameronfreer/infinitary-logic/). t-logic LLM-generated new-contributor 446/0 Mathlib.lean,Mathlib/ModelTheory/Infinitary/Semantics.lean,Mathlib/ModelTheory/Infinitary/Syntax.lean,MathlibTest/InfinitarySyntax.lean 4 4 ['cameronfreer', 'github-actions'] nobody
25-68346
25 days ago
100-49426
100 days ago
100-49371
100 days
0
45385 vihdzp
author:vihdzp
feat: cofinality lemmas for ordinal arithmetic --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory 37/0 Mathlib/SetTheory/Cardinal/Cofinality/Ordinal.lean 1 1 ['github-actions'] nobody
25-63222
25 days ago
25-64648
25 days ago
25-64593
25 days
0
29624 mcdoll
author:mcdoll
feat(LinearAlgebra/LinearPMap): add definition of resolvent and resolvent identities This PR defines the resolvent of an unbounded operator as a linear map. There are slight differences to the way the resolvent is defined in the literature: we use a purely algebraic description, in particular we do not assume that the operator is closed. We prove the well-known first and second resolvent identities. --- <!-- The text above the `---` will become the commit message when your PR is merged. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. To indicate co-authors, include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" When merging, all the commits will be squashed into a single commit listing all co-authors. If you are moving or deleting declarations, please include these lines at the bottom of the commit message (that is, before the `---`) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #42423 - [x] depends on: #42425 - [x] depends on: #43923 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra t-analysis
label:t-algebra$
292/5 Mathlib.lean,Mathlib/Algebra/Algebra/Spectrum/Basic.lean,Mathlib/LinearAlgebra/LinearPMap.lean,Mathlib/LinearAlgebra/Resolvent.lean 4 66 ['YaelDillies', 'github-actions', 'j-loreaux', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mathlib4-merge-conflict-bot', 'mcdoll', 'riccardobrasca'] nobody
25-59740
25 days ago
25-59740
25 days ago
133-29116
133 days
0
32157 peabrainiac
author:peabrainiac
feat(Analysis/Calculus): Hadamard's lemma Add [Hadamard's lemma](https://en.wikipedia.org/wiki/Hadamard%27s_lemma) for functions from finite-dimensional normed spaces to Banach spaces. --- <!-- The text above the `---` will become the commit message when your PR is merged. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #31141 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 121/0 Mathlib.lean,Mathlib/Analysis/Calculus/Hadamard.lean 2 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
25-48784
25 days ago
25-49259
25 days ago
25-50589
25 days
0
45404 davidiach
author:davidiach
feat(InformationTheory/KullbackLeibler): add restriction lemmas Restricting two finite measures to the same set decreases their KL divergence. This PR adds the integral identity that explains why, and the inequality that follows from it. Neither lemma requires the set to be measurable. Both concern restrictions without normalization and build on the existing `klFun` API. Verified against current mathlib on Lean 4.36.0-rc2, including builds, linters, and axiom checks. AI assistance: Astra Pro identified the contribution; Codex extracted and refined the proofs, checked for duplicates, and ran verification. t-measure-probability LLM-generated new-contributor 32/0 Mathlib/InformationTheory/KullbackLeibler/Basic.lean 1 3 ['davidiach', 'github-actions'] nobody
25-22520
25 days ago
25-23015
25 days ago
25-22960
25 days
0
44841 grunweg
author:grunweg
feat: `ContDiffAt.hasStrictFDerivAt_fderiv_of_minSmoothness_le` Give a sufficient criterion for a derivative being a strict derivative: a map being `C^1` at a point suffices over the real or complex numbers, otherwise we need analyticity. This will be used to generalise the inverse function theorem to analytic manifolds. --- - [x] depends on: #44840 I added the new lemmas to a new file, as there was no existing module with the right set of imports. I'm happy to move it elsewhere (or give the file a better name) if preferred. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 112/4 Mathlib.lean,Mathlib/Analysis/Calculus/ContDiff/RCLike.lean,Mathlib/Analysis/Calculus/ContDiff/StrictFDerivAt.lean,Mathlib/Analysis/Calculus/FDeriv/Symmetric.lean 4 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
25-19135
25 days ago
25-19771
25 days ago
25-20234
25 days
2
45409 JackFeliks
author:JackFeliks
feat(Analysis/SpecificLimits): bound alternating series error from convergence Our change allows the same error bound to be used in more cases, for example when calculating π/4 using the Leibniz series. Existing uses continue to work. --- I came up with this contribution while testing my own experimental stack of algorithms. Codex prepared the code and tests, and Argon reviewed the proposal. t-analysis LLM-generated new-contributor 81/27 Mathlib/Analysis/Real/Pi/Leibniz.lean,Mathlib/Analysis/SpecificLimits/Normed.lean,MathlibTest/AlternatingSeries.lean 3 3 ['JackFeliks', 'github-actions'] nobody
25-9964
25 days ago
25-13517
25 days ago
25-13462
25 days
0
45207 Hagb
author:Hagb
feat({Algebra/MonoidAlgebra,RingTheory/MvPolynomial}/Ideal): characterize membership of ideal generated by polynomial terms $p \in \langle {i | c_ix^{\alpha_i}} \rangle$ if and only if $\mathrm{coeff}_d(p) \in \langle c_i | \alpha_i \le d \rangle$. It is used in #45208. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory large-import 76/27 Mathlib/Algebra/MonoidAlgebra/Ideal.lean,Mathlib/RingTheory/MvPolynomial/Ideal.lean 2 1 ['github-actions'] nobody
25-8581
25 days ago
28-77837
28 days ago
28-78425
28 days
1
45376 plp127
author:plp127
feat(Order): `IsModularLattice` instances for `WithTop` and `WithBot` Provide `IsModularLattice` instances for `WithTop` and `WithBot` when the base type is a modular lattice. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 11/0 Mathlib/Order/ModularLattice.lean 1 4 ['github-actions', 'plp127', 'vihdzp'] nobody
24-58557
24 days ago
25-77939
25 days ago
25-77884
25 days
0
45441 janbernloehr
author:janbernloehr
feat(Analysis/Normed/Operator/Compact): preserve compact remainders under one-sided inverses Add `IsCompactOperator.sub_id_of_rightInverse` and `IsCompactOperator.sub_id_of_leftInverse`: if `f - id` is compact and `g` is a continuous linear right or left inverse of `f`, then `g - id` is compact. Work over an arbitrary ring and a module whose underlying additive group is a topological group. The proofs use compactness under composition and negation, through the identities `(f - id) ∘L g = id - g` and `g ∘L (f - id) = id - g`. These lemmas are used in my thesis formalization to show that compact derivative remainders are preserved under inverse coordinate changes. They package an elementary consequence of compactness being preserved under composition with continuous linear maps and negation. --- Local validation passed with Lean `v4.36.0-rc2`: the affected-module build, style lint, axiom checks, standalone usage examples, and `git diff --check`. There are no PR dependencies. AI assistance: OpenAI Codex was used when writing the Lean proofs. Related background: #35048 (the existing Fredholm alternative), #39274 (broader Fredholm infrastructure), and #43906 (a closed, unmerged compact-perturbation development). t-analysis new-contributor LLM-generated 37/0 Mathlib/Analysis/Normed/Operator/Compact/Basic.lean 1 2 ['github-actions'] nobody
24-58306
24 days ago
24-61681
24 days ago
24-61626
24 days
0
45444 janbernloehr
author:janbernloehr
feat(Analysis): characterize weighted summability by geometric tails Add `ENNReal.tsum_rpow_mul_lt_top_iff_geometric_tails`: for $f:I\to[0,\infty]$, a size map $\nu:I\to\mathbb N$, a real base $b>1$, a positive integer cutoff $M$, and real $t>0$, set $$ \begin{aligned} S&:=\sum_i f_i, & W_t&:=\sum_i(1+\nu(i))^t f_i,\\ T_k&:=\sum_{\nu(i)\ge b^kM}f_i, & G_t&:=\sum_{k=0}^{\infty}b^{kt}T_k. \end{aligned} $$ Prove the quantitative ENNReal estimates $$ W_t\le(1+bM)^t(S+G_t), \qquad G_t\le\frac{b^t}{b^t-1}\,W_t, $$ and hence the equivalence $$ W_t<\infty \quad\Longleftrightarrow\quad S<\infty\;\land\;G_t<\infty. $$ The estimates allow infinite coefficients and divergent sums; the first also holds at order zero. Use nonnegative double-sum interchange and finite geometric-series estimates, then derive the real-valued summability criteria as corollaries. No monotonicity of the coefficients or finiteness of the size-map fibers is required. This criterion is used in the formalisation of my dissertation, in a weighted-regularity argument. --- Local validation passed with Lean `v4.36.0-rc2`: the affected-module build, style lint, 15 linters, axiom checks, standalone usage examples (including the nonintegral base $b=3/2$ and natural-base specialisations), and `git diff --check`. There are no PR dependencies. AI assistance: OpenAI Codex was used to adapt and generalize the proofs for the ENNReal formulation. t-analysis new-contributor LLM-generated 274/0 Mathlib.lean,Mathlib/Analysis/SummableGeometricTails.lean 2 2 ['github-actions'] nobody
24-58301
24 days ago
24-59349
24 days ago
24-59294
24 days
0
45445 janbernloehr
author:janbernloehr
feat(Analysis/Normed/Lp): detect PiLp norms by conjugate pairings Add norm-attaining conjugate test vectors for finite real or complex `PiLp` spaces, and deduce a criterion for bounding the norm from all conjugate-unit-ball pairings. Include the corresponding Hölder bound, both endpoint pairs `(1, ∞)` and `(∞, 1)`, and empty index types. Use the bilinear pairing `∑ i, a i * b i`, with conjugation incorporated into the test vector, so the results support holomorphic interpolation. Reuse `NNReal.isGreatest_Lp` for finite exponents and handle the endpoints explicitly. These lemmas are used in the formalization of my dissertation to recover ℓp norm bounds from finite test-pairing estimates in the discrete Hilbert-transform argument. --- ## Dependencies and merge order No prerequisite PRs. Merge this before #45447, which is stacked on this change. The coordinate-restriction contribution is independent. ## Validation Checked using Lean `v4.36.0-rc2`: - Module build, style linter and declaration linters. - Real/complex examples, p=2, both conjugate endpoint pairs and an empty index type. - Generated import and diff/whitespace checks. - Axiom inspection: only `propext`, `Classical.choice`, `Quot.sound`. ## AI assistance OpenAI Codex has been used in the writing of the Lean implementation. t-analysis LLM-generated new-contributor 167/0 Mathlib.lean,Mathlib/Analysis/Normed/Lp/PiLpDual.lean 2 2 ['github-actions'] nobody
24-58296
24 days ago
24-59010
24 days ago
24-58955
24 days
1
36878 plp127
author:plp127
chore: override `npow` in compositional monoids If `FooHom` is the type of foo homomorphisms, then `FooHom A A` naturally gets the structure of a monoid by setting one to be the identity homomorphism and setting multiplication to be composition. This PR overrides the `npow` field of this `Monoid` to have `f ^ n` be definitionally equal to `f^[n]`. `FooEquiv A A` also naturally gets a group structure in the same way, this PR overrides the `npow` field to have `f ^ n` be definitionally equal to `f^[n]` and to have `f ^ (n + 1)` be definitionally equal to `f ^ n * f`. This does break one pre-existing definitional equality: when `e : Equiv.Perm α`, `e⁻¹ ^ n = (e ^ n)⁻¹` will no longer be definitional. This PR also sets the `zpow` field of `Group (FooEquiv A A)` instances so that `(f ^ n).toEquiv` is definitionally equal to `f.toEquiv ^ n`. The monoid and group instances to modify are found by searching loogle for `"one_apply"`. The motivation is to make natural number powers commute definitionally with the coercion from `AlgEquiv` to `LinearMap`. --- - [x] depends on: #45218 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) large-import 206/66 Mathlib/Algebra/AddConstMap/Equiv.lean,Mathlib/Algebra/Algebra/Equiv.lean,Mathlib/Algebra/Algebra/Hom.lean,Mathlib/Algebra/Group/End.lean,Mathlib/Algebra/Group/Hom/Defs.lean,Mathlib/Algebra/Module/LinearMap/End.lean,Mathlib/Algebra/Order/Group/End.lean,Mathlib/Algebra/Ring/Aut.lean,Mathlib/Algebra/Ring/Hom/Defs.lean,Mathlib/Algebra/Star/MonoidHom.lean,Mathlib/Algebra/Star/StarAlgHom.lean,Mathlib/Algebra/Star/StarRingHom.lean,Mathlib/FieldTheory/Perfect.lean,Mathlib/GroupTheory/Perm/Cycle/Basic.lean,Mathlib/RingTheory/Bialgebra/Hom.lean,Mathlib/RingTheory/Coalgebra/Hom.lean,Mathlib/Topology/Algebra/Algebra.lean,Mathlib/Topology/Algebra/Module/ContinuousLinearMap/Basic.lean 18 11 ['eric-wieser', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'plp127'] nobody
24-52383
24 days ago
24-54969
24 days ago
29-78124
29 days
1
45450 mcdoll
author:mcdoll
chore(NumberTheory): replace anonymous constructor by .mk in `ArithmeticFunction` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-number-theory tech debt 24/27 Mathlib/NumberTheory/ArithmeticFunction/Defs.lean,Mathlib/NumberTheory/ArithmeticFunction/LFunction.lean,Mathlib/NumberTheory/ArithmeticFunction/Misc.lean,Mathlib/NumberTheory/ArithmeticFunction/Moebius.lean,Mathlib/NumberTheory/ArithmeticFunction/VonMangoldt.lean,Mathlib/NumberTheory/ArithmeticFunction/Zeta.lean,Mathlib/NumberTheory/LSeries/Convolution.lean 7 1 ['github-actions'] nobody
24-51242
24 days ago
24-51921
24 days ago
24-51866
24 days
0
44470 SnirBroshi
author:SnirBroshi
feat(SetTheory/Ordinal/Exponential): `opow_le_of_isSuccLimit` works for `c ≠ 0` When `IsSuccLimit b`, `a ^ b ≤ c ↔ ∀ b' < b, a ^ b' ≤ c` holds unless `a = c = 0`. (otherwise the LHS is true but the RHS is false because `b' = 0` requires `0 ^ 0 ≤ 0`) We have this lemma for `a ≠ 0`, and this adds it for `c ≠ 0`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory 14/0 Mathlib/SetTheory/Ordinal/Exponential.lean 1 2 ['github-actions', 'vihdzp'] nobody
24-50356
24 days ago
49-32149
49 days ago
49-32094
49 days
0
44443 plp127
author:plp127
feat(Topology/Algebra/IsUniformGroup): group is left/right uniform group iff it's equal to left/right uniformity Prove that for a topological group `G` with a uniform space structure, `G` is a left/right uniform group iff the uniformity is equal to `IsTopologicalGroup.leftUniformSpace G`/`IsTopologicalGroup.rightUniformSpace G`. Also rename `uniformity_eq_comap_nhds_one'` to `uniformity_eq_comap_nhds_one_right` to match `uniformity_eq_comap_nhds_one_left`. --- - [x] depends on: #44423 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology t-group-theory 61/25 Mathlib/Analysis/CStarAlgebra/Matrix.lean,Mathlib/Topology/Algebra/IsUniformGroup/Basic.lean,Mathlib/Topology/Algebra/IsUniformGroup/Defs.lean,Mathlib/Topology/Algebra/Module/Multilinear/Topology.lean,Mathlib/Topology/Algebra/Module/Spaces/UniformConvergenceCLM.lean 5 2 ['github-actions', 'mathlib-dependent-issues'] nobody
24-46592
24 days ago
37-18482
37 days ago
37-18727
37 days
1
41466 EzequielS2
author:EzequielS2
feat(Algebra/Order): stronger sublist product inequality via diff ## Summary Add `Sublist.prod_le_prod'_of_mem_diff` and `Sublist.sum_le_sum_of_mem_diff`. ## Test plan - [x] `lake build` and `lake exe runLinter` on `Mathlib.Algebra.Order.BigOperators.Group.List` t-algebra new-contributor
label:t-algebra$
12/4 Mathlib/Algebra/Order/BigOperators/Group/List.lean 1 8 ['EzequielS2', 'github-actions', 'mathlib-merge-conflicts', 'themathqueen', 'wwylele'] nobody
24-41932
24 days ago
24-42836
24 days ago
65-59744
65 days
0
41449 EzequielS2
author:EzequielS2
feat(Topology/ContinuousMap): domMulAct action on C(X, Y) ## Summary - Define the action of `Mᵈᵐᵃ` on `C(α, β)` when `M` acts continuously on `α`. - Add `SMul`, `MulAction`, `SMulCommClass`, and `ContinuousSMul` instances. - Closes #5379. ## Test plan - [x] `lake build Mathlib.Topology.ContinuousMap.DomAct` - [x] `lake exe runLinter Mathlib.Topology.ContinuousMap.DomAct` t-topology new-contributor 105/0 Mathlib.lean,Mathlib/Topology/ContinuousMap/DomAct.lean 2 7 ['EzequielS2', 'github-actions', 'j-loreaux'] nobody
24-39726
24 days ago
24-40534
24 days ago
45-71663
45 days
1
45454 artie2000
author:artie2000
feat(Algebra/Group/Submonoid): bot is pointed, top is not Unnecessary lemmas split from #36863 using ChatGPT 5.5. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
12/2 Mathlib/Algebra/Group/Submonoid/Support.lean 1 1 ['github-actions'] nobody
24-39241
24 days ago
24-40919
24 days ago
24-40864
24 days
0
45442 plp127
author:plp127
feat(Order/ModularLattice): dualize `IsModularLattice` Dualize `IsModularLattice.mk` and `IsModularLattice.sup_inf_le_assoc_of_le`, so that `@[to_dual]` can translate them properly. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 8/9 Mathlib/Order/ModularLattice.lean 1 1 ['github-actions', 'vihdzp'] nobody
24-33967
24 days ago
24-60743
24 days ago
24-60688
24 days
0
45392 vihdzp
author:vihdzp
chore: state Borel isomorphism theorem using `Uncountable` We also deprecate the specialization of it to `ℕ → Bool`, after proving the instance that allows to infer the uncountability of this type automatically. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability tech debt 53/25 Mathlib/Basic/Countable/Defs.lean,Mathlib/LinearAlgebra/Dimension/ErdosKaplansky.lean,Mathlib/MeasureTheory/Constructions/Polish/Basic.lean,Mathlib/MeasureTheory/Constructions/Polish/EmbeddingReal.lean,Mathlib/SetTheory/Cardinal/Basic.lean,Mathlib/SetTheory/Cardinal/Finite.lean 6 1 ['github-actions'] nobody
24-28180
24 days ago
25-36420
25 days ago
25-43782
25 days
0
44363 Parcly-Taxel
author:Parcly-Taxel
chore: remove `set_option` in `Order.Nucleus` tech debt t-order 7/15 Mathlib/Order/Nucleus.lean 1 13 ['Parcly-Taxel', 'github-actions', 'grunweg', 'mathlib-merge-conflicts', 'mathlib-splicebot'] nobody
24-15296
24 days ago
25-15489
25 days ago
50-73487
50 days
0
43209 YaelDillies
author:YaelDillies
feat(Geometry/Convex): `WithTop X` is a convex space if `X` is ... by setting any convex combination that puts positive weight on `⊤`/`⊥` to `⊤`/`⊥`. This will be used to talk about convex/concave functions to the extended real numbers. Generated by Claude Opus, largely rewritten by hand afterwards. Assisted-by: Claude Opus 5 --- - [x] depends on: #43610 - [x] depends on: #43612 - [x] depends on: #43613 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-convex-geometry LLM-generated 176/1 Mathlib.lean,Mathlib/Data/Finsupp/Option.lean,Mathlib/Geometry/Convex/ConvexSpace/Defs.lean,Mathlib/Geometry/Convex/ConvexSpace/WithTop.lean 4 37 ['YaelDillies', 'b-mehta', 'eric-wieser', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
24-10257
24 days ago
24-12552
24 days ago
34-54952
34 days
0
37579 IvanRenison
author:IvanRenison
feat(Combinatorics/SimpleGraph/Girth): add lemmas about the length of a walk being equal to the girth --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #37561 - [x] depends on: #37577 - [x] depends on: #37574 - [x] depends on: #37562 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 30/0 Mathlib/Combinatorics/SimpleGraph/Girth.lean 1 19 ['IvanRenison', 'SnirBroshi', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
24-2412
24 days ago
24-2948
24 days ago
58-19767
58 days
0
45455 artie2000
author:artie2000
feat(Algebra/Ring/Subsemiring): more properties of pointed, spanning subsemiring * Pointed subsemiring (ring cone) does not contain $$-1$$ * Spanning subsemiring preserved by map and comap Unnecessary lemmas split from #36863 using ChatGPT 5.5. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #36863 t-algebra
label:t-algebra$
13/0 Mathlib/Algebra/Ring/Subsemiring/Support.lean 1 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
23-76098
23 days ago
23-76524
23 days ago
23-76960
23 days
0
45456 artie2000
author:artie2000
feat(Algebra/Order/Ring): more constructors for ring (pre)orderings Unnecessary lemmas split from #36863 using ChatGPT 5.5. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #36863 t-algebra
label:t-algebra$
18/0 Mathlib/Algebra/Order/Ring/Ordering/Basic.lean 1 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
23-76046
23 days ago
23-76542
23 days ago
23-76879
23 days
0
42923 plp127
author:plp127
feat(FieldTheory/KummerExtension): criterion for `X ^ n - C a` to be irreducible for even `n` Prove the criterion for `X ^ n - C a` to be irreducible when `n` is not necessarily odd. This resolves a TODO. --- - [x] depends on: #42344 - [x] depends on: #42886 - [x] depends on: #45461 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra t-ring-theory
label:t-algebra$
169/22 Mathlib/FieldTheory/KummerExtension.lean,Mathlib/FieldTheory/KummerPolynomial.lean 2 9 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'plp127', 'tb65536', 'vihdzp'] nobody
23-73021
23 days ago
23-77134
23 days ago
49-81155
49 days
0
45227 artie2000
author:artie2000
chore(Algebra/Group/Subgroup): deprecate HasMemOrNegMem All usages of this class have been removed in favour of the definition `AddSubmonoid.IsSpanning`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #36863 - [x] depends on: #37298 t-algebra increases-technical-debt
label:t-algebra$
10/6 Mathlib/Algebra/Group/Subgroup/Defs.lean 1 2 ['github-actions', 'mathlib-dependent-issues'] nobody
23-69836
23 days ago
23-72167
23 days ago
23-73972
23 days
0
45412 JadAbouHawili
author:JadAbouHawili
doc(Order/RelIso): fix docstrings in RelEmbedding and RelIso --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 4/3 Mathlib/Order/RelIso/Basic.lean 1 5 ['chenson2018', 'github-actions', 'themathqueen'] nobody
23-68821
23 days ago
23-73132
23 days ago
25-11483
25 days
0
45479 Jun2M
author:Jun2M
feat(Logic/Function): factor functions along surjections Define `Function.Surjective.factor`. If `g.FactorsThrough f`, this gives the unique function `d` satisfying `d ∘ f = g`. Adapted from the [Matroid repository](https://github.com/apnelson1/Matroid). Codex was used for review. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 94/0 Mathlib/Data/Set/Image.lean,Mathlib/Logic/Function/Basic.lean 2 1 ['github-actions'] nobody
23-63334
23 days ago
23-67446
23 days ago
23-67391
23 days
0
45482 chenle02
author:chenle02
feat(Analysis/Distribution/SchwartzSpace): the Schwartz space on a finite-dimensional space is separable ## What is proved In `Mathlib/Analysis/Distribution/SchwartzSpace/Separable.lean`: ```lean instance SchwartzMap.instSecondCountableTopology {E F : Type*} [NormedAddCommGroup E] [NormedSpace ℝ E] [NormedAddCommGroup F] [NormedSpace ℝ F] [FiniteDimensional ℝ E] [SecondCountableTopology F] : SecondCountableTopology 𝓢(E, F) ``` so `SeparableSpace 𝓢(E, F)` is found by instance search, for example for `𝓢(EuclideanSpace ℝ (Fin d), ℂ)`, and in particular for `𝓢(ℝ, ℝ)`. There are two supporting instances, both stated in general form: ```lean -- Mathlib/Topology/Compactification/OnePoint/Basic.lean instance OnePoint.instSecondCountableTopology [WeaklyLocallyCompactSpace X] [R1Space X] [SecondCountableTopology X] : SecondCountableTopology (OnePoint X) -- Mathlib/Analysis/Distribution/SchwartzSpace/Separable.lean instance ContinuousMultilinearMap.instSecondCountableTopologyFin [FiniteDimensional 𝕜 E] [SecondCountableTopology F] (n : ℕ) : SecondCountableTopology (E [×n]→L[𝕜] F) ``` ## Proof idea * For `f : 𝓢(E, F)`, the function `x ↦ ‖x‖ ^ k • iteratedFDeriv ℝ n f x` tends to `0` along `cocompact E`, because it is bounded by `‖x‖⁻¹ * seminorm (k + 1) n f`. It therefore extends by `0` to a continuous function on `OnePoint E`, and the sup norm of that extension is exactly `SchwartzMap.seminorm ℝ k n f`. * The resulting map `𝓢(E, F) →L[ℝ] Π (k, n), C(OnePoint E, E [×n]→L[ℝ] F)` is inducing, because each Schwartz seminorm is the norm of one coordinate. * Its target is second countable. `OnePoint E` is compact and second countable (new instance), `E [×n]→L[ℝ] F` is second countable (new instance, proved by induction via currying from the existing `E →L[𝕜] F` instance), and `ContinuousMap.instSecondCountableTopology` gives the rest. ## History of this PR The first version of this PR proved only the case `E = ℝ`, by bounding each Schwartz seminorm by the `L¹` norm of a derivative (`norm_le_integral_norm_deriv`, `derivCLM_pow_apply`). The general argument above covers `E = ℝ`, so that `L¹` proof and its two auxiliary lemmas have been removed. The file now depends only on `SchwartzSpace.Basic`, not on `SchwartzSpace.Deriv` and the integration library. ## Follow-ups * `ContinuousMultilinearMap.instSecondCountableTopologyFin` could be moved next to the `E →L[𝕜] F` instance in `Mathlib/Analysis/Normed/Module/FiniteDimension.lean`, possibly in a more general form (a `Fintype` index with finite-dimensional factors). It sits in this file for now so that the PR does not trigger a rebuild of most of the analysis library. * Consequences that need separability, for example for tempered distributions. AI tools (Claude and Codex) were used to port and adapt this proof to Mathlib; the author reviewed it. t-analysis new-contributor LLM-generated 177/0 Mathlib.lean,Mathlib/Analysis/Distribution/SchwartzSpace/Separable.lean,Mathlib/Topology/Compactification/OnePoint/Basic.lean 3 3 ['github-actions', 'lua-vr'] nobody
23-57201
23 days ago
23-64389
23 days ago
23-64334
23 days
0
44906 yudukikun5120
author:yudukikun5120
feat(Archive): formalize negation in vector logic This adds a formalization of negation in Mizraji's two-valued vector logic to `Archive/VectorLogic.lean`, using mathlib's matrix and real-number APIs. For two orthonormal real vectors `s` and `n` in an arbitrary finite-dimensional coordinate space, define `N = nsᵀ + snᵀ` and the logical identity `I₂ = ssᵀ + nnᵀ`. Prove that negation exchanges the truth vectors, exchanges the coefficients of their linear combinations, and satisfies `N * N = I₂`. Double negation fixes every linear combination of the truth vectors. The formalization also shows that negation annihilates vectors orthogonal to both, so it does not assert that `N²` is the ambient identity in higher dimension. The definitions follow Eduardo Mizraji's *Vector logics: The matrix-vector representation of logical calculus* (1992), as reproduced in §4.2, equations (15)–(16), of his 2016 paper: https://doi.org/10.1387/theoria.13959. --- This is a draft for feedback on whether this paper-specific formalization is suitable for `Archive`; its placement has not been agreed with maintainers. Validation on macOS arm64 with Lean 4.35.0: - `lake build Archive.VectorLogic` - `lake exe lint-style Archive.VectorLogic` - `lake exe mk_all --lib Archive --check` - Separate local checks with a three-dimensional truth pair, including a counterexample to the ambient identity assertion. AI disclosure: OpenAI Codex generated the implementation, proofs, and this PR description, and ran the local validation. The changes are marked as LLM-generated. This description does not claim completion of independent human review. LLM-generated new-contributor t-data 102/0 Archive.lean,Archive/VectorLogic.lean 2 3 ['github-actions', 'yudukikun5120'] nobody
23-51714
23 days ago
38-1103
38 days ago
38-1048
38 days
0
45470 benpigchu
author:benpigchu
feat(Data): theorem about `List.splitBy` of `List.append` when `getLast` of the first list and `head` of the second list are related This PR add a theorem describing the behaviour of `List.splitBy` of `List.append` when the `ha` assumption in `List.splitBy_append` does not hold. --- This theorem came from https://github.com/dwrensha/compfiles/blob/1745e6ced3e671bd74417548494b034eb2c87da8/Compfiles/Imo2022P1.lean#L148 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data new-contributor 59/0 Mathlib/Data/List/SplitBy.lean 1 2 ['github-actions'] nobody
23-44087
23 days ago
23-85267
23 days ago
23-85212
23 days
0
44939 JX-Mo
author:JX-Mo
feat(RepresentationTheory): add Schur's lemma for central elements We add a bridge lemma saying that central elements act as scalars on simple modules. t-algebra
label:t-algebra$
7/0 Mathlib/RepresentationTheory/AlgebraRepresentation/Basic.lean 1 12 ['JX-Mo', 'alreadydone', 'github-actions', 'themathqueen'] nobody
23-40305
23 days ago
23-40781
23 days ago
36-66762
36 days
1
45494 chenle02
author:chenle02
feat(MeasureTheory): the cylinder σ-algebra on the weak dual This PR adds `Mathlib/MeasureTheory/Constructions/WeakDual.lean`, which defines the cylinder σ-algebra on `WeakDual 𝕜 E` (the σ-algebra generated by the evaluations `T ↦ T x`) and proves that a finite measure for it is determined by its finite-dimensional marginals. ## Statements The setting is the general one of `WeakDual`: `𝕜` a commutative topological semiring with `[MeasurableSpace 𝕜]`, and `E` a topological `𝕜`-module. * `WeakDual.cylinderMeasurableSpace 𝕜 E : MeasurableSpace (WeakDual 𝕜 E)`, defined as `MeasurableSpace.comap (fun T x ↦ T x) MeasurableSpace.pi`. This mirrors the definition of the weak-* topology as an induced topology. * `cylinderMeasurableSpace_eq_iSup`: it equals `⨆ x, MeasurableSpace.comap (fun T ↦ T x) ‹_›`. * `measurable_cylinder_iff`: a map `f : α → WeakDual 𝕜 E` is measurable iff `fun a ↦ f a x` is measurable for every `x`. Also `measurable_eval_cylinder` and `measurable_coeFn_cylinder`. * `cylinderMeasurableSpace_le_borel` (needs `[BorelSpace 𝕜]`): it is contained in `borel (WeakDual 𝕜 E)`. `cylinderMeasurableSpace_le` gives the same for any `OpensMeasurableSpace` structure. * `ext_of_forall_finset_map_eq`: two measures `μ ν`, with `μ` finite, are equal if `μ.map (fun T (x : I) ↦ T x) = ν.map (fun T (x : I) ↦ T x)` for every `I : Finset E`. * `map_eq_iff_forall_finset_map_eq`: two a.e.-measurable random elements `X : Ω → WeakDual 𝕜 E` and `Y : Ω' → WeakDual 𝕜 E` (under a finite `P` and `P'`) have the same law iff they have the same finite-dimensional laws. This is the analogue of `ProbabilityTheory.map_eq_iff_forall_finset_map_restrict_eq` for processes. * `cylinderMeasurableSpace_eq_comap_of_denseRange` (needs `[FrechetUrysohnSpace E] [PseudoMetrizableSpace 𝕜] [BorelSpace 𝕜]`): for any `d : ι → E` with `DenseRange d`, the σ-algebra is `comap (fun T i ↦ T (d i)) pi`. * `ext_of_forall_finset_map_eq_of_denseRange`: under the same hypotheses, it is enough to compare finite-dimensional marginals along `d`. * `countablyGenerated_cylinderMeasurableSpace`: if in addition `E` is separable and `𝕜` is countably generated, then the cylinder σ-algebra is countably generated. ## Design: a `def`, not an instance The measurable structure of a topological type in Mathlib is normally its Borel σ-algebra, and lemmas such as `Continuous.measurable` rely on `OpensMeasurableSpace`. On `WeakDual 𝕜 E` the cylinder σ-algebra is contained in the Borel σ-algebra, but the two are different in general. Equality needs extra hypotheses, for instance E separable Fréchet/nuclear, and that is not proved here. A global instance would therefore close off the Borel choice for every user of `WeakDual`. So the σ-algebra is a `def` marked `@[instance_reducible]`, in the same way as `borel` and `cylinderEvents`, and users enable it with `attribute [local instance] WeakDual.cylinderMeasurableSpace`. This adds no global instance and creates no diamond. `WeakDual` is a non-reducible `def`, so the norm-Borel instance `ContinuousLinearMap.instMeasurableSpace` on `E →L[𝕜] F` (for normed `E`) does not apply to it. I checked that `MeasurableSpace (WeakDual ℝ ℝ)` still fails to synthesize after importing that file. A downstream project that wants an instance can set `instance : MeasurableSpace (WeakDual 𝕜 E) := WeakDual.cylinderMeasurableSpace 𝕜 E` on its own type synonym. Projects that do this all get the same σ-algebra. ## Proof idea The coercion `F : T ↦ (x ↦ T x)` generates the σ-algebra by definition. Hence `μ.map F` and `ν.map F` are both projective limits of the same family of finite-dimensional laws, and `IsProjectiveLimit.unique` makes them equal. Every measurable set has the form `F ⁻¹' t`, so `μ = ν` follows. For the dense-range version, `T x` is the limit of `T (d (j n))` along a sequence (Fréchet–Urysohn, and each `T` is continuous), so `measurable_of_tendsto_metrizable` shows that the evaluations along `d` already generate the σ-algebra. ## Prior art * Two projects outside Mathlib already define this σ-algebra, each as a global instance: * mrdouglasny/gaussian-field defines `instMeasurableSpaceConfiguration` on `Configuration E := WeakDual ℝ E` as `comap (fun ω f ↦ ω f) pi`. It proves `configuration_measurable_of_eval_measurable` and, for Gaussian measures, `pushforward_eq_of_eval_eq`. * mrdouglasny/bochner (`Minlos/NuclearSpace.lean`) defines an instance on `WeakDual ℝ E` as `⨆ f, (borel ℝ).comap (· f)`. These two definitions are not defeq, so importing both projects fails to synthesize instances; gaussian-field's notes record this. A shared definition in Mathlib avoids that diamond. No code was taken from either project. * Mathlib has `cylinderEvents` and `measurableCylinders` on product types, and `ProbabilityTheory.map_eq_iff_forall_finset_map_restrict_eq` for processes. Neither covers `WeakDual`, and Mathlib has no `MeasurableSpace` on `WeakDual`, `WeakBilin` or `WeakSpace`. * Open PRs: a search for WeakDual measurable, cylinder, Minlos, nuclear, "random distribution" and "measure on dual" found no overlapping PR. #42278 (nuclear spaces) touches no measurable structure on duals, but it would be a natural input to a later Minlos theorem. #44909 (Kolmogorov extension) covers existence on product spaces, so it complements the uniqueness result here. * Zulip could only be searched through the public web archive, which showed no prior thread. ## Follow-ups * The Bochner–Minlos theorem on duals of nuclear spaces, stated for this σ-algebra. * Borel = cylinder on `WeakDual 𝕜 E` under suitable separability hypotheses (e.g. separable Fréchet `E`). This would allow a `BorelSpace` statement for the cylinder σ-algebra. * Tempered distributions: once the `SeparableSpace 𝓢(ℝ, ℝ)` instance (#45482) lands, `countablyGenerated_cylinderMeasurableSpace` and `ext_of_forall_finset_map_eq_of_denseRange` apply directly to `WeakDual ℝ 𝓢(ℝ, ℝ)`. `SchwartzMap` is already first-countable on master. AI tools (Claude and Codex) were used to port and adapt this proof to Mathlib; the author reviewed it. t-measure-probability new-contributor LLM-generated 245/0 Mathlib.lean,Mathlib/MeasureTheory/Constructions/WeakDual.lean 2 2 ['github-actions'] nobody
23-9423
23 days ago
23-59420
23 days ago
23-59365
23 days
0
45487 chenle02
author:chenle02
feat(Probability/Distributions/Poisson): higher moments of the Poisson distribution This PR adds a new file `Mathlib/Probability/Distributions/Poisson/Moments.lean` with the moments of the Poisson distribution `poissonMeasure r`, `r : ℝ≥0`. Main statements (namespace `ProbabilityTheory`): * `hasSum_mul_descFactorial_poissonMeasure` and `integral_descFactorial_poissonMeasure`: the factorial moments, `∫ n, (n.descFactorial k : ℝ) ∂Po(r) = r ^ k`. * `integrable_exp_mul_map_cast_poissonMeasure`, `integrableExpSet_id_map_cast_poissonMeasure`: `x ↦ exp (t * x)` is integrable for every `t`, so `integrableExpSet id Po(ℝ, r) = univ`. * `memLp_id_map_cast_poissonMeasure (p : ℝ≥0) : MemLp id p Po(ℝ, r)` and `integrable_pow_map_cast_poissonMeasure : Integrable (fun x ↦ x ^ k) Po(ℝ, r)`. * `hasSum_mul_pow_poissonMeasure` and `integral_pow_map_cast_poissonMeasure`: the raw moments are the Touchard polynomials, `∫ x, x ^ k ∂Po(ℝ, r) = ∑ j ∈ range (k + 1), S(k, j) * r ^ j` with `S(k, j) = Nat.stirlingSecond k j`. * `integral_id_map_cast_poissonMeasure : ∫ x, x ∂Po(ℝ, r) = r` * `integral_pow_two_map_cast_poissonMeasure : ∫ x, x ^ 2 ∂Po(ℝ, r) = r ^ 2 + r` * `integral_pow_three_map_cast_poissonMeasure : ∫ x, x ^ 3 ∂Po(ℝ, r) = r ^ 3 + 3 * r ^ 2 + r` * `integral_pow_four_map_cast_poissonMeasure : ∫ x, x ^ 4 ∂Po(ℝ, r) = r ^ 4 + 6 * r ^ 3 + 7 * r ^ 2 + r` * `variance_id_map_cast_poissonMeasure : Var[id; Po(ℝ, r)] = r` * `centralMoment_three_map_cast_poissonMeasure : centralMoment id 3 Po(ℝ, r) = r` * `centralMoment_four_map_cast_poissonMeasure : centralMoment id 4 Po(ℝ, r) = 3 * r ^ 2 + r` Proof idea: the factorial moment sum is reindexed by `n ↦ n + k` (the first `k` terms vanish) and becomes `r ^ k` times the total mass of `Po(r)`. Writing `n ^ k` in terms of falling factorials with `Nat.pow_eq_sum_stirlingSecond_mul_descFactorial` gives the general raw moment; the moments of order 1 to 4 are its special cases. The central moments follow by expanding `(x - r) ^ j` into raw moments, adding the corresponding `HasSum` statements and `ring`. Integrability comes from finiteness of the moment generating function via `memLp_of_mem_interior_integrableExpSet`. --- Relation to #33688: that PR adds `HasSum`/`tsum` expectation lemmas for the old `poissonPMF` / `poissonPMFReal` API in `Mathlib/Probability/Distributions/Poisson.lean`. Those declarations and that file are no longer on master (the distribution is now `poissonMeasure` in `Poisson/Basic.lean`), and #33688 is labelled `merge-conflict` / `awaiting-author`. This PR states the mean at the level of `poissonMeasure` in the same style as `integral_id_binomial` and `integral_id_gaussianReal`; it does not depend on #33688 and touches different files. AI tools (Claude and Codex) were used to port and adapt this proof to Mathlib; the author reviewed it. t-measure-probability new-contributor LLM-generated 187/0 Mathlib.lean,Mathlib/Probability/Distributions/Poisson/Moments.lean 2 2 ['github-actions'] nobody
23-9415
23 days ago
23-60425
23 days ago
23-60370
23 days
0
45384 vihdzp
author:vihdzp
feat: type alias for overriding the order instance of a type See the module docstring for motivation. This is intended as a stepping stone towards switching the ordinal API to bundled relations (see #44009, #44010), while still allowing the usage of unbundled relations when they're needed (see e.g. #38357). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 97/0 Mathlib.lean,Mathlib/Order/ConditionallyCompleteLattice/Defs.lean,Mathlib/Order/SuccPred/Basic.lean,Mathlib/Order/WellFounded.lean,Mathlib/Order/WithLT.lean 5 5 ['SnirBroshi', 'github-actions', 'vihdzp'] nobody
23-3220
23 days ago
24-32752
24 days ago
24-43048
24 days
0
44599 CBirkbeck
author:CBirkbeck
chore(CategoryTheory/Limits/Shapes/Equalizers): deprecate duplicate `parallelPairIsoMk` Deprecate `parallelPairIsoMk`, a duplicate of `parallelPair.ext` (they are equal by `rfl`), and use `parallelPair.ext` instead. `IsKernel.ofIso` and `IsCokernel.ofIso` are now the (co)kernel cases of `Fork.isLimitOfIsos` and `Cofork.isColimitOfIsos`. --- <!--redteam:v1 {"owner":"AI-DOOM-97fce5ac-e255-4515-b311-12ecf245ce72","findings":["RT-20261007-e6d8f0"],"patterns":["second-construction-same-file"],"severity":"MAJOR"}--> 🤖 Generated with [Claude Code](https://claude.com/claude-code) LLM-generated 14/26 Mathlib/Algebra/Category/ModuleCat/Sheaf/Quasicoherent.lean,Mathlib/CategoryTheory/Limits/Shapes/Equalizers.lean,Mathlib/CategoryTheory/Limits/Shapes/Kernels.lean 3 4 ['github-actions', 'mathlib-merge-conflicts', 'tb65536'] nobody
22-82454
22 days ago
22-85644
22 days ago
22-85589
22 days
0
44613 keithadler
author:keithadler
feat(RepresentationTheory): irreducible representations are bounded by conjugacy classes For a finite group `G` and an algebraically closed field `k` in which `|G|` is invertible, `Representation.char_orthonormal` gives orthogonality of irreducible characters. This PR adds the consequence that is used in practice: * `Representation.classFunction ρ : ConjClasses G → k`, the character as a class function; * `Representation.linearIndependent_classFunction`: the class functions of a family of pairwise non-isomorphic irreducible representations are linearly independent; * `Representation.card_le_card_conjClasses`: such a family has at most `Nat.card (ConjClasses G)` members. This is the upper-bound half of "the number of irreducible representations equals the number of conjugacy classes" (the other half, that characters span the class functions, is not yet in Mathlib). The bound is exactly what is needed to show that an explicit list of `Nat.card (ConjClasses G)` pairwise non-isomorphic irreducibles is complete; e.g. with the companion PR on conjugacy classes of `Perm α`, that the Specht modules exhaust the irreducible representations of `S_n` (used downstream in https://github.com/keithadler/saxl-lean). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- t-algebra new-contributor LLM-generated
label:t-algebra$
118/0 Mathlib.lean,Mathlib/RepresentationTheory/CharacterCount.lean 2 3 ['artie2000', 'github-actions'] nobody
22-77993
22 days ago
45-69670
45 days ago
45-69615
45 days
0
45420 PSchwahn
author:PSchwahn
feat(Algebra): define sets of finite products in a magma This PR adds a file `Algebra/Products.lean` containing declarations about products of tuples of elements in a magma, together with some basic API. We plan to expand on this later. Ultimately we plan to use these to prove results about [Leibniz algebras](https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Leibniz.20algebras/with/598438796). We note that `Fin.prod` (from `Batteries.Data.Fin.Basic`) provides a similar functionality as our declaration `OrderedLeftProduct`. However `Fin.prod` requires a multiplicative unit on the magma and it associates the products to the right, whereas `OrderedLeftProduct` is associated to the left and works for any magma. This will become important because we work with non-associative operations and in the future would like to align with the literature (e.g. on Leibniz algebras). Co-authored by: Viviana del Barco, Gustavo Infanti, Artem Lopatin, Exequiel Rivas --- t-algebra new-contributor
label:t-algebra$
162/0 Mathlib.lean,Mathlib/Algebra/Products.lean 2 2 ['github-actions'] nobody
22-68493
22 days ago
24-71606
24 days ago
24-72147
24 days
0
44208 urkud
author:urkud
chore(Calculus/FDeriv/Prod): reorganize the file Prepare `Calculus/FDeriv/Prod` for generalizing to topological vector spaces. - replace the anonymous sections by `section Prod` (covering the lemmas about `E × F`) and rename the inner `section Prod` to `section ProdMk`; - move the variables about `f`, `f'`, `s`, `x`, `L` to the sections that use them, so that `section Pi` and `section PiFin` are independent of the rest of the file; - move `hasFDerivAt_prodMk_left`/`hasFDerivAt_prodMk_right` out of `section ProdMk`, `HasFDerivAtFilter.fst` before `HasStrictFDerivAt.fst`, and `fderiv.snd` after `fderivWithin_snd`. This order reduced `diff` to the TVS version to actual typeclass assumptions changes. No lemma is added, removed, or restated. Extracted by Claude from a larger refactor written by Yury. Co-authored-by: Claude Opus 5 <noreply@anthropic.com> --- t-analysis LLM-generated 37/41 Mathlib/Analysis/Calculus/FDeriv/Prod.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
22-67877
22 days ago
22-84071
22 days ago
35-32718
35 days
0
45514 PSchwahn
author:PSchwahn
feat(Logic/Equiv/Fin/Basic): extension/deletion operations on permutations on `Fin n` Add basic operations on permutations on `Fin n`: - `Fin.Perm.castSucc`: extend a permutation on `Fin n` to one on `Fin (n + 1)` in the obvious way. - `Fin.Perm.removeNth`: removes a given position in a permutation on `Fin (n + 1)`, and collapses the domain and range to `Fin n`. Useful in conjunction with `Fin.succAbove`. Along this, add some API theorems: - `removeNth_of_castSucc_lt₁`, `removeNth_of_castSucc_lt₂`, `removeNth_of_le_castSucc₁` and `removeNth_of_le_castSucc₂` are analogous to [Fin.succAbove_of_castSucc_lt](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/Fin/SuccPred.html#Fin.succAbove_of_castSucc_lt) resp. [Fin.succAbove_of_le_castSucc](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/Fin/SuccPred.html#Fin.succAbove_of_le_castSucc). - `succAbove_removeNth` shows how `Fin.Perm.removeNth` interacts with [Fin.succAbove](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/Fin/SuccPred.html#Fin.succAbove). - `castSucc_zero` and `castSucc_succ` are simp lemmas for `Fin.Perm.castSucc`. --- new-contributor t-logic 130/0 Mathlib/Logic/Equiv/Fin/Basic.lean 1 3 ['github-actions'] nobody
22-62482
22 days ago
22-65216
22 days ago
22-65161
22 days
0
42029 NoneMore
author:NoneMore
feat(ModelTheory): add elementary chains This PR adds the definition of elementary chains and construct their direct limits, shows that the canonical maps and compatible cocone lifts are elementary and derives theory preservation and cardinality bounds for the limit. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #42125 AI disclosure: Most declarations, comments, and documentation in this PR were generated with Codex. Some proofs were structurally simplified using the `/golf` command from Lean 4 Skills. I reviewed the resulting code and documentation and can vouch for all submitted content. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-logic 312/0 Mathlib.lean,Mathlib/ModelTheory/ElementaryChain.lean 2 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
22-29341
22 days ago
22-33429
22 days ago
22-38573
22 days
1
44955 user202729
author:user202729
chore: change all occurrences of equational lemma to equation lemma Change all occurrences of "equational lemma" to "equation lemma". Also add a missing apostrophe. --- As far as I can tell, both are grammatical: the "equation" in "equation lemma" is a noun adjunct, while "equational" is an adjective. It feels like noun adjunct is "more advanced English" though. Before this pull request: ("equation lemma" is more popular than "equational lemma") ``` [mathlib4]$ rg 'equational lemma'|wc -l 10 [mathlib4]$ rg 'equation lemma'|wc -l 31 [mathlib4]$ rg 'equational theorem'|wc -l 6 [mathlib4]$ rg 'equation theorem'|wc -l 2 ``` and in Lean: (same, but only slightly) ``` [lean4]$ rg 'equational lemma'|wc -l 16 [lean4]$ rg 'equation lemma'|wc -l 20 [lean4]$ rg 'equational theorem'|wc -l 85 [lean4]$ rg 'equation theorem'|wc -l 38 ``` Not sure if it's worth unifying the theorem case (probably yes. But in this case, apparently "equational theorem" is more popular than "equation theorem".), and/or unify lemma and theorem (probably not, mathlib distinguishes lemmas and theorems). new-contributor 10/10 Mathlib/Algebra/Homology/HomotopyCategory/HomComplex.lean,Mathlib/Algebra/Homology/HomotopyCategory/MappingCone.lean,Mathlib/CategoryTheory/Limits/Final.lean,Mathlib/CategoryTheory/Sites/CoversTop/Basic.lean,Mathlib/CategoryTheory/Sites/Hypercover/One.lean,Mathlib/Data/Nat/Fib/Zeckendorf.lean,Mathlib/Tactic/Eqns.lean,Mathlib/Tactic/Translate/ToAdditive.lean,docs/Conv/Guide.lean 9 4 ['SnirBroshi', 'github-actions', 'mathlib-merge-conflicts'] nobody
22-15715
22 days ago
22-19078
22 days ago
31-67217
31 days
0
43023 SnirBroshi
author:SnirBroshi
feat(Order/RelSeries): change `FiniteDimensional` to allow empty types This also means that the zero ring is now `FiniteRingKrullDim`, and that `Empty` is `FiniteDimensionalOrder`. [#mathlib4 > Should zero ring be finite-dimensional?](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Should.20zero.20ring.20be.20finite-dimensional.3F/with/495871110) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 67/55 Mathlib/Order/KrullDimension.lean,Mathlib/Order/RelSeries.lean,Mathlib/RingTheory/Ideal/Height.lean,Mathlib/RingTheory/Ideal/KrullsHeightTheorem.lean,Mathlib/RingTheory/KrullDimension/Basic.lean 5 5 ['SnirBroshi', 'github-actions', 'plp127', 'themathqueen'] nobody
21-33672
21 days ago
92-83011
92 days ago
92-82956
92 days
0
44404 peabrainiac
author:peabrainiac
feat(Topology): σ-locally finite families of sets Define σ-locally finite families of sets, i.e. families that consist of countably many locally finite families, and provide API for them analogous to some of the existing API for `LocallyFinite`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> For some mathematical context, σ-locally finite families generalise both countable and locally finite families but are incomparable to locally countable families - that is, not every locally countable family is σ-locally finite, and not every σ-locally finite family is locally countable. While local countability might seem like a more natural condition in a vacuum, the reason σ-locally finite families are of interest is that they show up in several point-set topological applications: - In order for a regular space to be paracompact, it suffices for open covers of it to admit σ-locally finite open refinements instead of locally finite ones; we prove this and conclude that regular Lindelöf spaces are paracompact in the follow-up PR #44411. This characterisation is also useful e.g. for proving that Fσ subsets of regular paracompact spaces are paracompact, which is one way to prove paracompactness of Milnor's $EG$ and $BG$ for compact Hausdorff groups. - In order for a cover to be numerable (i.e. admit a subordinate partition of unity) it suffices for it to be refined by a σ-locally finite cover by cozero sets. This is important for e.g. proving the stacking lemma for numerable covers, which was useful for proving homotopy invariance of numerable fibre bundles in [classifying-bundles](https://peabrainiac.github.io/classifying-bundles/docs/ClassifyingBundles/NumerableBundle.html). - Cozero sets and Fσ sets are both closed under σ-locally finite unions but not e.g. locally countable ones. Since Engelking's general topology book introduces σ-locally finite families and proves several theorems about them, among others the mentioned paracompactness criterion, we list it as a reference in the file. The term is not exclusive to the book though, see e.g. nlab [here](https://ncatlab.org/nlab/show/countably+locally+finite+set+of+subsets) and pi-base [here](https://topology.pi-base.org/properties/P000054). t-topology 150/0 Mathlib.lean,Mathlib/Data/Set/Restrict.lean,Mathlib/Topology/SigmaLocallyFinite.lean 3 17 ['github-actions', 'peabrainiac', 'peakpoint'] nobody
21-28670
21 days ago
21-28717
21 days ago
28-52945
28 days
3
45556 JX-Mo
author:JX-Mo
feat(RingTheory/TensorProduct): add base change for the center of algebras We compare the base change of the center and the center of the base change for a given algebra. Opus 5.5 comes up the idea of introducing the helper `δ` as a linear map to simplify the last proof. t-ring-theory LLM-generated 86/0 Mathlib.lean,Mathlib/RingTheory/TensorProduct/Center.lean 2 2 ['JX-Mo', 'github-actions'] nobody
21-18940
21 days ago
21-19379
21 days ago
21-19358
21 days
0
43280 idontgetoutmuch
author:idontgetoutmuch
feat(Topology/VectorBundle): coordinate lemmas for the bundle of bilinear forms Coordinate lemmas for bundles of continuous linear maps. Bundle.Trivialization.continuousLinearMap_symm_apply, hom_trivializationAt_symm_apply: the inverse of the trivialization of the bundle fun x ↦ E₁ x →SL[σ] E₂ x sends a model map L to v ↦ e₂⁻¹ (L (e₁ v)). inCoordinates_apply_eq₂_of_trivial: inCoordinates_apply_eq₂ when the target bundle is trivial. trivializationAt_symm_apply_bilin: the same for bilinear maps into a fixed space, deduced from hom_trivializationAt_symm_apply. Motivation: in #33714 (existence of a Riemannian metric), the local metric is defined as the inverse trivialization applied to the inner product on the model fibre, and trivializationAt_symm_apply_bilin rewrites it as ⟪e u, e v⟫, from which symmetry and positivity follow. This PR is the first piece split out of #33714, which will be rebased on it. t-topology new-contributor 68/20 Mathlib/Topology/VectorBundle/Hom.lean,Mathlib/Topology/VectorBundle/Riemannian.lean 2 29 ['github-actions', 'grunweg', 'idontgetoutmuch'] grunweg
assignee:grunweg
21-17622
21 days ago
21-17766
21 days ago
78-40735
78 days
0
42471 mo271
author:mo271
feat(RingTheory/LaurentSeries): add Leibniz rule This adds `hasseDeriv_mul` and `derivative_mul`. Written with the help of Gemini --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory LLM-generated 101/0 Mathlib/RingTheory/LaurentSeries.lean 1 10 ['felixpernegger', 'github-actions', 'mathlib-bors', 'mo271', 'wwylele'] mariainesdff
assignee:mariainesdff
20-51251
20 days ago
100-25283
100 days ago
106-23504
106 days
0
43220 wwylele
author:wwylele
refactor(Combinatorics/Partition): eliminate T2Space requirement from generating function Previously, the key lemma in this file had the shape `HasProd (fun i ↦ 1 + ∑' j, f (i + 1) (j + 1) • X ^ ((i + 1) * (j + 1))) (genFun f)`, which has a nested infinite sum inside the infinite prod. As a result, all related lemma needed T2Space when it doesn't have to. The new formulation extract the inner sum into a power series definition `genFunFactor` that works in general topological space, eliminating `T2Space` for the `HasProd`/`HasSum` lemma. The old formula is kept under the name `hasProd_genFun'`. This is still used in the downstream file `Glaisher.lean`. To reduce the code change size, the refactor in `Glaisher.lean` is deferred to a future PR --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 96/79 Mathlib/Combinatorics/Enumerative/Partition/Basic.lean,Mathlib/Combinatorics/Enumerative/Partition/GenFun.lean,Mathlib/Combinatorics/Enumerative/Partition/Glaisher.lean 3 3 ['copilot-pull-request-reviewer', 'github-actions', 'mathlib-merge-conflicts'] nobody
20-47169
20 days ago
44-7213
44 days ago
84-47346
84 days
1
44584 CBirkbeck
author:CBirkbeck
chore(AlgebraicTopology/FundamentalGroupoid): deprecate `transReflReparamAux` in favor of `qRight` Deprecate `Path.Homotopy.transReflReparamAux` and its lemmas: the function is `fun t ↦ unitInterval.qRight (t, 0)`, which `trans_refl_reparam` and `transRefl` now use. --- <!--redteam:v1 {"owner":"AI-DOOM-97fce5ac-e255-4515-b311-12ecf245ce72","findings":["RT-20261006-546cb9"],"patterns":["parallel-reparametrisation-helper"],"severity":"MAJOR"}--> 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-algebraic-topology tech debt LLM-generated 10/12 Mathlib/AlgebraicTopology/FundamentalGroupoid/Basic.lean 1 1 ['github-actions', 'tb65536'] nobody
20-6455
20 days ago
22-85617
22 days ago
22-85562
22 days
0
45583 ouboub
author:ouboub
feat(Analysis/ODE): Grönwall's inequality with a variable coefficient Title: feat(Analysis/ODE): Grönwall's inequality with a variable coefficient- #45583 Description: I believe I have successfully implemented and tested the differential form of Grönwall's inequality with variable coefficients. Details can be found in https://leanprover.zulipchat.com/#narrow/channel/144837-PR-reviews/topic/Gronwall.27s.20inequality.3A.20differential.20form.2C.20variable.20coeff/with/636639527 which includes two PDFs with a more detailed description. - Here is a short description: Add Grönwall's inequality in differential form with a variable coefficient `K` and a variable inhomogeneous term `ε`, both continuous and of arbitrary sign, for a function with right derivatives: if `f` is continuous on `[a, b]`, `f' t ≤ K t * f t + ε t` on `[a, b)` and `f a ≤ δ`, then on `[a, b]` `f t ≤ (δ + ∫ s in a..t, ε s / exp (∫ r in a..s, K r)) * exp (∫ s in a..t, K s)`. This addresses (for differentiable `f`) the TODO in `Mathlib/Analysis/ODE/Gronwall.lean` asking for a variable coefficient `K x` of any sign. The main results found in the new file `Mathlib/Analysis/ODE/GronwallVariableCoeff.lean` are * `gronwallBoundVar`: the bound above; * `le_gronwallBoundVar_of_deriv_right_le`: the inequality; * `gronwallBoundVar_const`: for constant `K` and `ε`, `gronwallBoundVar` agrees with the existing `gronwallBound`; * `le_mul_exp_integral_of_deriv_right_le_mul`: the homogeneous case `ε = 0`. The proof uses the integrating factor `exp (∫ s in a..t, K s)` and the comparison lemma `image_le_of_deriv_right_le_deriv_boundary`. - Some open problems: 1. The two auxiliary lemmas `continuousOn_primitive_of_continuousOn` and `hasDerivWithinAt_Ici_primitive` (one-sided FTC) are stated here; I did not find them in Mathlib. Should they move to `Mathlib/MeasureTheory/Integral/IntervalIntegral/`, or into the `intervalIntegral` namespace? 2. I did not dare to put my results into `Mathlib/Analysis/ODE/Gronwall.lean` itself, 3. There might be another TODO in the module docstring: the energy form of Bahouri–Chemin–Danchin, Lemma 3.3. At some point, I asked Claude for advice on the main lemma, but I didn't include syntax I don't understand or haven't tested. The code might be clumsy. regards Uwe Brauer t-analysis new-contributor 270/0 Mathlib.lean,Mathlib/Analysis/ODE/GronwallVariableCoeff.lean 2 4 ['github-actions', 'ouboub'] nobody
20-4014
20 days ago
20-15593
20 days ago
20-15606
20 days
0
45595 IvanRenison
author:IvanRenison
feat(Data/Holor): define the Hadamard product for holors --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 45/0 Mathlib/Data/Holor.lean 1 2 ['github-actions'] nobody
19-76901
19 days ago
19-77428
19 days ago
19-77373
19 days
0
45282 3y3y3y-huaiji
author:3y3y3y-huaiji
feat(Topology/Order): add zero-crossing for odd maps on antipodal paths Add `exists_zero_of_antipodal_path`: a continuous odd map (`f (τ x) = -f x`) along a path connecting antipodal points (`γ b = τ (γ a)`) must have a zero. This provides a direct path-lifting bridge over `intermediate_value_Icc` for spaces with domain involutions. * `exists_zero_of_antipodal_path`: main existence theorem. * `IsOddMap`: anti-invariance predicate `f (τ x) = -f x`. --- > [!NOTE] > **LLM Disclosure / AI Use**: This PR was prepared with the assistance of an LLM (`LLM-generated`). All proofs and statements have been formally verified by Lean 4 and checked with linters. t-topology LLM-generated new-contributor 71/0 Mathlib.lean,Mathlib/Topology/Order/Antipodal.lean 2 5 ['3y3y3y-huaiji', 'github-actions', 'leanprover-radar'] nobody
19-74074
19 days ago
19-74606
19 days ago
27-39904
27 days
0
45591 DanielJHorton
author:DanielJHorton
feat(LinearAlgebra/ExteriorPower/WedgePairing): add lemma wedgePairing_apply This PR adds two lemmas: - `wedgePairing_apply` in `LinearAlgebra/ExteriorPower/WedgePairing` - `eqRec_apply` in `Algebra/Module/LinearMap/Baisc` `eqRec_apply` is an analogue of `_root_.apply_eqRec` for linear maps and is used in the proof of `wedgePairing_apply`. `wedgePairing_apply` unfolds and simplifies applications of `exteriorPower.wedgePairing`. It has no simp tag because `wedgePairing` is an abbrev (not a def), so the LHS is not in simp NF. This PR was motivated by a project of mine where I had a proof that needed to expose the application of the underlying volume form in an expression containing `wedgePairing`. I should probably mention here that there already exists a lemma `exteriorPower.apply_eqRec` in `LinearAlgebra/ExteriorPower/WedgePairing` (not to be confused with `_root_.apply_eqRec`) which is marked as private, but serves a vaguely similar purpose to this proposed `wedgePairing_apply` lemma. That said, it is more tailored to its use case later in the file and I don't think making it public is the way to go (especially if it has potential namespace conflicts with `_root_`). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
23/0 Mathlib/Algebra/Module/LinearMap/Basic.lean,Mathlib/LinearAlgebra/ExteriorPower/WedgePairing.lean 2 1 ['github-actions'] nobody
19-58971
19 days ago
19-60646
19 days ago
19-64953
19 days
0
43036 SnirBroshi
author:SnirBroshi
feat(Order/RelSeries): a strict order on a finite domain is finite dimensional Bound the length of a `RelSeries r` by the cardinality of `α` when `r` is a strict order (irreflexive and transitive), and show: - `Finite α → r.IsIrrefl → r.IsTrans → Finite (RelSeries r)` - `Infinite α → Infinite (RelSeries r)` - `Finite α → Nonempty α → r.IsIrrefl → r.IsTrans → r.FiniteDimensional` - `r.IsIrrefl → r.IsTrans → r.InfiniteDimensional → Infinite α` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 65/14 Mathlib.lean,Mathlib/Order/RelSeries.lean,Mathlib/Order/RelSeries/Lemmas.lean 3 4 ['Ruben-VandeVelde', 'SnirBroshi', 'github-actions'] nobody
19-55177
19 days ago
19-56645
19 days ago
92-39162
92 days
0
42995 jacob-greenfield
author:jacob-greenfield
feat: add `List.Pairwise.orderedInsert'`, `List.sortedLE_orderedInsert_lt`, and `List.sortedGE_orderedInsert_gt` Introduce a generalized `Pairwise.orderedInsert'` lemma to prove that `Pairwise r l` is maintained after performing an `orderedInsert` using a relation stronger than `r` under certain conditions. Prove `sortedLE_orderedInsert_lt`, showing that `l.orderedInsert (· < ·) a` preserves `SortedLE` for decidable total preorders (analogously for `sortedGE_orderedInsert_gt`). This is useful for inserting an element into a sorted list *behind* any other elements which compare equal. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> I was hoping to avoid `omit`, but that would require moving all of `Pairwise.orderedInsert'`, `Pairwise.orderedInsert`, `pairwise_insertionSort`, `sublist_insertionSort'`, `pair_sublist_insertionSort'`, and `mergeSort_eq_insertionSort` after `end sort` on line 365 and reintroducing all the section variables. I also considered moving `Pairwise.orderedInsert'` somewhere _before_ `variable {α β : Type*} (r : α → α → Prop) (s : β → β → Prop)` on line 30, but that would place it before `orderedInsert` is defined. "Omit" seemed like the least invasive approach. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data new-contributor 27/11 Mathlib/Data/List/Sort.lean 1 8 ['github-actions', 'jacob-greenfield', 'theebayuser'] TwoFX
assignee:TwoFX
19-51247
19 days ago
93-41617
93 days ago
93-41562
93 days
0
44398 j-loreaux
author:j-loreaux
feat: transfer algebraic structure to the `WithTopology` synonym `WithTopology` is a type synonym that changes the topology, but in various circumstances, one may wish to have the same algebraic structures available on this synonym, as we do for example for `WithLp`. This PR transfers those over using `WithTopology.equiv`. --- Because this is very mechanical work, I generated this with Claude Code and checked the output. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology t-algebra LLM-generated
label:t-algebra$
500/0 Mathlib.lean,Mathlib/Topology/Algebra/WithTopology.lean 2 2 ['artie2000', 'github-actions'] nobody
19-41757
19 days ago
19-42260
19 days ago
19-43132
19 days
0
44491 staroperator
author:staroperator
feat(Order/Ideal): reprove Rasiowa–Sikorski lemma and deprecate `Order.Cofinal` Reprove Rasiowa–Sikorski lemma as `Order.exists_ideal_meets_cofinals`. This non-constructive version is closer to its usual statement (e.g. `Countable` instead of `Encodable`), hides internal constructions and is shorter. Its dual version, `Order.exists_pfilter_meets_coinitials` which is used in set theory more often, will be proved in #34855 when `Order.PFilter` gets `to_dual`-ized. We also deprecate `Order.Cofinal`, which is the bundled version of `IsCofinal` and can be replaced by its unbundled version. **The proofs of `embedding_from_cg` and `equiv_between_cg` in ModelTheory/PartialEquiv.lean are fixed by LLM (GPT-6 Astra).** Others are written by me. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order increases-technical-debt LLM-generated 149/94 Mathlib/ModelTheory/PartialEquiv.lean,Mathlib/Order/Cofinal.lean,Mathlib/Order/CountableDenseLinearOrder.lean,Mathlib/Order/Ideal.lean 4 10 ['github-actions', 'staroperator', 'vihdzp'] nobody
19-41360
19 days ago
19-42666
19 days ago
48-46776
48 days
1
43285 WenrongZou
author:WenrongZou
feat(ValuativeTopology): valuative topology of Z_p Let `K` be a field with assumption `[ValuativeRel K] [TopologicalSpace K] [IsValuativeTopology K]`. Let `R` be its ring of integers and the topology of `R` is induced by `K`, then there is a valuative topology over `R` . This can be used to deduce the valuative topology of `Z_p`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 59/0 Mathlib/NumberTheory/Padics/PadicNumbers.lean,Mathlib/NumberTheory/Padics/ValuativeRel.lean,Mathlib/Topology/Algebra/ValuativeRel/ValuativeTopology.lean 3 5 ['WenrongZou', 'github-actions', 'mathlib-merge-conflicts', 'tb65536'] nobody
19-10804
19 days ago
19-11510
19 days ago
62-19724
62 days
1
45540 arsmagic
author:arsmagic
feat(RingTheory/ZMod): odd-unit square criterion in ZMod (2^n) For an odd integer a, a is a square in ZMod (2^n) iff a ≡ 1 (mod 2^min(n,3)): case forms isSquare_two_pow_iff_of_odd_three_le (n≥3, mod 8) and isSquare_two_pow_iff_of_odd_le_three (n≤3, mod 2^n), plus the uniform form. Discussed on Zulip (#Is there code for X? > Squares in ZMod (2^n) for odd units). (https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/Squares.20in.20ZMod.20.282.5En.29.20for.20odd.20units) (Xavier Roblot confirmed #45509 will not cover squares; split into two case forms per Snir Broshi's suggestion.) Adds the characterization of squares among odd (unit) residues modulo a power of two. For an odd integer a: ZMod.isSquare_two_pow_iff_of_odd_three_le — for 3 ≤ n, IsSquare (a : ZMod (2^n)) ↔ a ≡ 1 [ZMOD 8]. ZMod.isSquare_two_pow_iff_of_odd_le_three — for n ≤ 3, ↔ a ≡ 1 [ZMOD 2^n]. ZMod.isSquare_two_pow_iff_of_odd — uniform form via min n 3. Sufficiency is derived from `ZMod.isComplement'_zpowers_unitFive_neg_one` (#45509), and the custom Hensel lifting has been removed. AI-tools used during preparation. LLM-generated t-data new-contributor 128/0 Mathlib.lean,Mathlib/RingTheory/ZMod/IsSquare.lean 2 21 ['SnirBroshi', 'arsmagic', 'felixpernegger', 'github-actions', 'wwylele'] nobody
19-1342
19 days ago
21-76271
21 days ago
21-76994
21 days
0
44358 TJHeeringa
author:TJHeeringa
chore(LinearAlgebra): generalize IsAdjointPair The implemented definition `IsAdjointPair` required sesquilinear maps. This is a stronger requirement than necessary. This PR relaxes the conditions on `IsAdjointPair` to the minimal ones. --- This is needed to generalize the RKHS from `InnerProductSpace/Reproducing.lean`. The location of the definition is still `LinearAlgebra/SesquilinearForm/Basic`. That is clearly not a good fit. However, I don't know a better location either. Places like `LinearAlgebra/BilinearForm/Basic` are also dealing with a less general construction. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
85/45 Mathlib/LinearAlgebra/SesquilinearForm/Basic.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
18-71158
18 days ago
18-73107
18 days ago
41-79082
41 days
0
43394 harahu
author:harahu
feat(Order/WithBot): add `WithBot.map_lt_map_iff` Add `WithBot.map_lt_map_iff`, the `<` analogue of `WithBot.map_le_iff`, for use in a follow-up. Also rename `map_le_iff` to `map_le_map_iff` (with a deprecated alias), since the operation appears on both sides of the relation. The bare `X_le_iff` form is used throughout Mathlib for the one-sided shape `f a ≤ b ↔ ...`. --- Developed with help from Claude Opus 5. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order LLM-generated 10/3 Mathlib/Order/Hom/WithTopBot.lean,Mathlib/Order/WithBot.lean 2 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
18-11506
18 days ago
18-13678
18 days ago
73-32246
73 days
0
42844 plp127
author:plp127
refactor(Logic/Hydra): cleanup file Change the definition of `CutExpand` to be more correct. Rename some theorems and add some theorems. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-logic 104/55 Mathlib/Logic/Hydra.lean 1 8 ['github-actions', 'mathlib-merge-conflicts', 'plp127', 'vihdzp'] nobody
17-61352
17 days ago
17-63682
17 days ago
93-58405
93 days
0
45537 wwylele
author:wwylele
feat(RingTheory/Valuation): more lemmas for ValuativeRel - lemma about additive negation - more lemma about vle and veq - `ValuativeRel.vle_one_or_inv_vlt_one` is the counterpart of `Valuation.val_le_one_or_val_inv_lt_one` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory 80/0 Mathlib/RingTheory/Valuation/ValuativeRel/Basic.lean 1 11 ['github-actions', 'plp127', 'vihdzp', 'wwylele'] nobody
17-55511
17 days ago
22-2932
22 days ago
22-2877
22 days
2
40050 ReemMelamed
author:ReemMelamed
feat(Algebra/Group/GreensRelations): add definitions for Green's relations This PR introduces the foundational definitions for Green's relations (L, R, H, D, and J) on semigroups. This is the first in a series of PRs aimed at formalizing Green's relations for semigroups. [Zulip](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Formalization.20of.20Green.27s.20Relations.20for.20semigroups/with/598557876) --- - [x] depends on: #40843 t-algebra new-contributor
label:t-algebra$
505/0 Mathlib.lean,Mathlib/Algebra/Group/GreensRelations/Basic.lean 2 33 ['ReemMelamed', 'YaelDillies', 'YanYablonovskiy', 'github-actions', 'mathlib-bors', 'mathlib-dependent-issues'] mattrobball
assignee:mattrobball
17-51257
17 days ago
72-15200
72 days ago
92-6295
92 days
1
42226 espottesmith
author:espottesmith
feat(Combinatorics/Hypergraph): add restriction `x ≠ y` to hypergraph vertex and edge adjacency --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> This introduces a small change to the definitions of adjacency and edge-adjacency for undirected hypergraphs, based on a conversation with @Jun2M and @b-mehta in [#28613](https://github.com/leanprover-community/mathlib4/pull/28613). Previously, any two vertices (edges) `x` and `y` could be adjacent, provided that there was an edge in the edge set containing both of them (there was a vertex contained in both of them). Now, we add the restriction that `x` is not equal to `y`. This should allow `SimpleGraph` to be a clean specialization of `Hypergraph` and to ease the eventual implementation of walks. This PR has no dependencies, but see also [42164](https://github.com/leanprover-community/mathlib4/pull/42162), @Jun2M's implementation of `HyperGraphLike` and formalization that `Hypergraph`s are `HyperGraphLike`, which includes this restriction on `Adj`. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics new-contributor 4/4 Mathlib/Combinatorics/Hypergraph/Basic.lean 1 3 ['github-actions'] b-mehta
assignee:b-mehta
17-51255
17 days ago
116-24066
116 days ago
116-24011
116 days
0
42820 tolgadgrmnc27
author:tolgadgrmnc27
feat(Data/Nat/Choose): elementary Chernoff bound for tail sums of binomial coefficients Adds an elementary, purely combinatorial Chernoff-type bound on tail sums of binomial coefficients: ```lean theorem Nat.sum_Ico_choose_le_div (n m : ℕ) {x : α} (hx : 1 ≤ x) : ∑ j ∈ Ico m (n + 1), (n.choose j : α) ≤ (1 + x) ^ n / x ^ m ``` together with the specialization at `x = 2`: ```lean theorem Nat.sum_Ico_choose_le_three_pow_div (n m : ℕ) : ∑ j ∈ Ico m (n + 1), (n.choose j : α) ≤ 3 ^ n / 2 ^ m ``` The proof is the classical exponential moment trick done combinatorially: for `m ≤ j` and `1 ≤ x` we have `x ^ m ≤ x ^ j`, so the tail sum is bounded by `x ^ (-m) * ∑ j, n.choose j * x ^ j = x ^ (-m) * (1 + x) ^ n` by the binomial theorem. A helper `Nat.sum_range_choose_mul_pow` states the binomial theorem in the convenient form `∑ j ≤ n, n.choose j * x ^ j = (1 + x) ^ n`. ### Why this is not already in Mathlib * `Nat.sum_range_choose` gives the *total* sum `∑ j ≤ n, n.choose j = 2 ^ n`. * `Mathlib/Data/Nat/Choose/Bounds.lean` bounds a *single* coefficient (`choose_le_pow`, `choose_le_two_pow`, `choose_le_pow_div`, …). * `Mathlib/Probability/Moments/SubGaussian.lean` has Chernoff/Hoeffding, but measure-theoretically: using it for a counting argument requires setting up a probability space with independent Bernoulli variables and translating back to cardinalities. I could not find a statement bounding a *partial* sum of binomial coefficients. The version here needs no probability space and applies directly to counting arguments (its original use was bounding the number of `n < 2 ^ k` whose first `k` binary digits contain at least `m` ones). ### Notes * Stated over a general `[Semifield α] [LinearOrder α] [IsStrictOrderedRing α]`, matching the typeclass style of `Mathlib/Data/Nat/Choose/Bounds.lean`. * `Ico m (n + 1)` rather than a `filter (m ≤ ·)` form, as is idiomatic in Mathlib; the two are equal by `Finset.filter_le_eq_Ico`-style reasoning. * Names are of course open to bikeshedding. --- - [x] depends on: nothing t-data new-contributor 84/0 Mathlib.lean,Mathlib/Data/Nat/Choose/Tail.lean 2 3 ['github-actions'] eric-wieser
assignee:eric-wieser
17-51254
17 days ago
98-12230
98 days ago
98-12175
98 days
0
45697 felixpernegger
author:felixpernegger
chore(SetTheory): remove unused hypothesis Removes unused hypothesis from #45673 in SetTheory. t-set-theory LLM-generated 38/20 Mathlib/SetTheory/Cardinal/Basic.lean,Mathlib/SetTheory/Cardinal/Embedding.lean,Mathlib/SetTheory/Ordinal/Arithmetic.lean,Mathlib/SetTheory/Ordinal/CantorNormalForm.lean,Mathlib/SetTheory/Ordinal/Exponential.lean,Mathlib/SetTheory/Ordinal/FixedPoint.lean,Mathlib/SetTheory/Ordinal/Notation.lean,Mathlib/SetTheory/Ordinal/Principal.lean 8 3 ['felixpernegger', 'github-actions', 'vihdzp'] nobody
17-46846
17 days ago
17-49217
17 days ago
17-49626
17 days
1
45672 plp127
author:plp127
chore(Data/Multiset/ZeroCons): rename arguments to `Multiset.rec` Name the motive `motive` and name the minor premises according to their contents. `cons_swap` was chosen in analogy to `Multiset.cons_swap`. Also rename arguments to `Multiset.induction`, `Multiset.induction_on`, `Multiset.induction_on'`, and `Multiset.recOn`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 169/178 Mathlib/Algebra/BigOperators/Associated.lean,Mathlib/Algebra/BigOperators/Group/Finset/Basic.lean,Mathlib/Algebra/BigOperators/Group/Multiset/Basic.lean,Mathlib/Algebra/BigOperators/Group/Multiset/Defs.lean,Mathlib/Algebra/GCDMonoid/Multiset.lean,Mathlib/Algebra/Module/BigOperators.lean,Mathlib/Algebra/Order/BigOperators/Ring/Multiset.lean,Mathlib/Algebra/Order/Group/Multiset.lean,Mathlib/Algebra/Order/Ring/IsNonarchimedean.lean,Mathlib/Algebra/Polynomial/BigOperators.lean,Mathlib/Algebra/Polynomial/Derivative.lean,Mathlib/Algebra/Polynomial/Monic.lean,Mathlib/Algebra/Tropical/BigOperators.lean,Mathlib/Analysis/Normed/Group/Ultra.lean,Mathlib/Analysis/Polynomial/MahlerMeasure.lean,Mathlib/Data/DFinsupp/Defs.lean,Mathlib/Data/Finset/Insert.lean,Mathlib/Data/Multiset/AddSub.lean,Mathlib/Data/Multiset/Antidiagonal.lean,Mathlib/Data/Multiset/Bind.lean,Mathlib/Data/Multiset/Count.lean,Mathlib/Data/Multiset/DershowitzManna.lean,Mathlib/Data/Multiset/Filter.lean,Mathlib/Data/Multiset/Find.lean,Mathlib/Data/Multiset/Lattice.lean,Mathlib/Data/Multiset/MapFold.lean,Mathlib/Data/Multiset/Pi.lean,Mathlib/Data/Multiset/Powerset.lean,Mathlib/Data/Multiset/Sections.lean,Mathlib/Data/Multiset/UnionInter.lean,Mathlib/Data/Multiset/ZeroCons.lean,Mathlib/Data/Nat/Choose/Multinomial.lean,Mathlib/FieldTheory/AbelRuffini.lean,Mathlib/FieldTheory/Differential/Basic.lean,Mathlib/GroupTheory/Perm/Cycle/Type.lean,Mathlib/Logic/Hydra.lean,Mathlib/NumberTheory/ArithmeticFunction/Misc.lean,Mathlib/RingTheory/DiscreteValuationRing/TFAE.lean,Mathlib/RingTheory/Ideal/Basic.lean,Mathlib/RingTheory/Polynomial/ScaleRoots.lean,Mathlib/RingTheory/UniqueFactorizationDomain/Basic.lean,Mathlib/RingTheory/UniqueFactorizationDomain/NormalizedFactors.lean 42 1 ['github-actions'] nobody
17-43175
17 days ago
17-66003
17 days ago
17-65948
17 days
0
45598 JunkaiWang-TheoPhy
author:JunkaiWang-TheoPhy
feat(Analysis/Fourier): translate frequency under character modulation ## Summary This PR adds the frequency-shift identity dual to the existing translation-to-phase identity for Fourier integrals. Modulating a function by an additive character translates its Fourier transform in frequency. ## Changes - Add the general `VectorFourier.fourierIntegral_smul_addChar` identity. - Add the scalar `Fourier.fourierIntegral_smul_addChar` specialization. - Add the real inner-product-space theorem `Real.fourier_smul_fourierChar`. - Add the corresponding inverse-transform identity `Real.fourierInv_smul_fourierChar`. The general theorem is proved by pointwise equality of the integration kernels. It does not require integrability, continuity, Haar invariance, finite dimensionality, or a nondegenerate pairing beyond the assumptions already present in the Fourier integral definition. With the convention `𝓕 f w = ∫ e (-L v w) • f v`, the forward shift is `w - w₀`; the inverse-transform identity consequently uses `w + w₀`. The change is confined to `Mathlib/Analysis/Fourier/FourierTransform.lean`. It adds no definitions, imports, instances, simp attributes, or dependencies. ## Validation - `lake build Mathlib.Analysis.Fourier.FourierTransform Mathlib.Analysis.SpecialFunctions.Gaussian.FourierTransform Mathlib.Analysis.Fourier.FourierTransformDeriv` — passed (`Build completed successfully (6312 jobs)`). - `lake exe batteries/runLinter --no-build Mathlib.Analysis.Fourier.FourierTransform` — passed. - Standalone local examples covering zero modulation, degenerate pairings, non-Haar measures, non-integrable total-function cases, the inverse sign, and a modulated Gaussian derivation — passed with the repository Lean options. - `#print axioms` for the four new declarations reports only `propext`, `Classical.choice`, and `Quot.sound`. - Full `MathlibTest` and hosted CI have not been run locally; hosted CI should provide the final repository-level check. ## AI disclosure Codex (gpt-6.1-sol) assisted with candidate discovery, Lean implementation, and local verification. I have reviewed the declarations and proofs, and I am responsible for understanding and explaining the mathematical design and sign conventions. t-analysis new-contributor LLM-generated 35/2 Mathlib/Analysis/Fourier/FourierTransform.lean 1 3 ['JunkaiWang-TheoPhy', 'github-actions'] nobody
17-9821
17 days ago
19-69509
19 days ago
19-69454
19 days
0
45684 felixpernegger
author:felixpernegger
chore(Combinatorics): remove unused hypothesis Removes unused hypothesis from #45673 in Combinatorics. t-combinatorics LLM-generated 20/18 Mathlib/Combinatorics/Additive/AP/Three/Behrend.lean,Mathlib/Combinatorics/Matroid/Circuit.lean,Mathlib/Combinatorics/SimpleGraph/Tutte.lean 3 5 ['felixpernegger', 'github-actions', 'vlad902'] nobody
17-9185
17 days ago
17-51110
17 days ago
17-51552
17 days
1
45205 Hagb
author:Hagb
feat(Combinatorics/Colex): lemmas about `Colex (Finset _)` These lemmas are used in #45206 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-combinatorics 21/0 Mathlib/Combinatorics/Colex.lean 1 2 ['Hagb', 'github-actions', 'vihdzp'] nobody
17-6668
17 days ago
30-37426
30 days ago
30-37371
30 days
2
45678 felixpernegger
author:felixpernegger
chore(Algebra): remove unused hypothesis Removes unused hypothesis from #45673 in Algebra. t-algebra LLM-generated
label:t-algebra$
107/92 Mathlib/Algebra/Algebra/Spectrum/Basic.lean,Mathlib/Algebra/EuclideanDomain/Basic.lean,Mathlib/Algebra/Homology/SpectralObject/Differentials.lean,Mathlib/Algebra/MonoidAlgebra/Degree.lean,Mathlib/Algebra/MvPolynomial/Basic.lean,Mathlib/Algebra/MvPolynomial/CommRing.lean,Mathlib/Algebra/MvPolynomial/Eval.lean,Mathlib/Algebra/MvPolynomial/NoZeroDivisors.lean,Mathlib/Algebra/MvPolynomial/SchwartzZippel.lean,Mathlib/Algebra/Order/Floor/Semiring.lean,Mathlib/Algebra/Order/GroupWithZero/Canonical.lean,Mathlib/Algebra/Order/GroupWithZero/Finset.lean,Mathlib/Algebra/Order/Monoid/Unbundled/WithTop.lean,Mathlib/Algebra/Order/Ring/Unbundled/Basic.lean,Mathlib/Algebra/Polynomial/Degree/Lemmas.lean,Mathlib/Algebra/Polynomial/Derivation.lean,Mathlib/Algebra/Polynomial/Reverse.lean,Mathlib/Data/ZMod/ValMinAbs.lean,Mathlib/MeasureTheory/Covering/DensityTheorem.lean,Mathlib/RingTheory/EuclideanDomain.lean,Mathlib/RingTheory/PowerSeries/Derivative.lean 21 4 ['Deicyde', 'github-actions', 'themathqueen'] nobody
16-83520
16 days ago
17-49157
17 days ago
17-49616
17 days
1
45566 PeaBrane
author:PeaBrane
feat(Analysis/Convex): limits and sums of convex functions Add pointwise-limit and summation lemmas for convex and concave functions. * `convexOn_of_frequently_convexOn_of_tendsto`, `concaveOn_of_frequently_concaveOn_of_tendsto`: if `F i` is frequently convex (concave) on `s` along a filter and `F i x → f x` for every `x ∈ s`, then `f` is convex (concave) on `s`. * `convexOn_finsetSum`, `concaveOn_finsetSum`: a finite sum of convex (concave) functions is convex (concave). * `convexOn_tsum`, `concaveOn_tsum`: a pointwise summable series of convex (concave) functions is convex (concave). These complement `isClosed_setOfPred_convexOn` from #37352. Closedness of the set of convex functions covers limits in the product topology, which needs convergence at every point of the domain. The new limit lemmas need convergence only on `s`, and only frequently along the filter, following `monotoneOn_of_frequently_monotoneOn_of_tendsto`. Finite sums and series of convex functions were not stated before; only `ConvexOn.add` existed. I needed the series version to show that a periodic kernel defined by an image sum is convex. `FunctionTopology.lean` now imports `Mathlib.Topology.Algebra.InfiniteSum.Defs` for `tsum`. AI disclosure: the statements, the proofs, and a draft of this description were written with Claude Code. I checked them against existing Mathlib conventions and built the changed files locally. --- t-analysis LLM-generated new-contributor 69/1 Mathlib/Analysis/Convex/Function.lean,Mathlib/Analysis/Convex/FunctionTopology.lean 2 6 ['PeaBrane', 'github-actions', 'wwylele'] nobody
16-82206
16 days ago
17-72351
17 days ago
20-67721
20 days
0
42095 DrDMT-VR
author:DrDMT-VR
feat(Analysis/CStarAlgebra): the non-unital CFC maps into closed two-sided ideals ## What For a non-unital C*-algebra `A`, a closed two-sided ideal `I`, an element `a ∈ I`, and any `f : ℝ → ℝ`, this proves `cfcₙ f a ∈ I`. No hypotheses on `f` are needed: whenever `cfcₙ` would take its junk value (`f` not continuous on the quasispectrum, `f 0 ≠ 0`, or `a` not selfadjoint) that value is `0 ∈ I`. New declarations (namespace `TwoSidedIdeal`): - `smul_mem_of_isClosed` — a closed two-sided ideal in a non-unital C*-algebra is closed under the scalar action (proved via the canonical approximate unit `CStarAlgebra.approximateUnit`). - `cfcₙHom_mem_of_isClosed` — for selfadjoint `a ∈ I`, every value of the underlying homomorphism `cfcₙHom` lies in `I` (Weierstrass induction on `C(σₙ ℝ a, ℝ)₀`). - `cfcₙ_mem_of_isClosed` — the main result. ## Why Closed two-sided ideals of a C*-algebra are hereditary under the continuous functional calculus; this is a basic tool for spectral-projection and ideal-membership arguments, and complements the existing "cfc commutes with *-homomorphisms" results. `smul_mem_of_isClosed` is of independent interest (a closed two-sided ideal is a submodule). ## Notes This is my second contribution (see #42093). I checked the referenced cfc / approximate-unit API against current master at the source level; CI is the first full build and I will fix anything it flags. Suggested location `Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Ideal.lean`; happy to relocate if preferred. Parts of this contribution were developed with AI assistance (Claude). All statements are machine-checked by the Lean kernel; `#print axioms` on the new declarations reports only `[propext, Classical.choice, Quot.sound]`. t-analysis new-contributor LLM-generated 92/0 Mathlib.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Ideal.lean 2 5 ['DrDMT-VR', 'github-actions', 'grunweg'] nobody
16-59813
16 days ago
25-65013
25 days ago
27-26350
27 days
1
44288 artie2000
author:artie2000
feat(Algebra/Ring): sums of squares in a formally real ring form a positive cone * Prove that sums of squares in a formally real ring form a positive cone * Add helper lemma relating the additive submonoid and subsemiring of sums of squares --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra large-import
label:t-algebra$
14/0 Mathlib/Algebra/Ring/IsFormallyReal.lean,Mathlib/Algebra/Ring/SumsOfSquares.lean 2 2 ['github-actions', 'mathlib-merge-conflicts', 'vihdzp'] nobody
16-54049
16 days ago
16-54504
16 days ago
54-76797
54 days
0
45547 artie2000
author:artie2000
feat(Algebra/Order/Ring): ring preordering extends to ordering * Prove every preordering on a ring extends to an ordering. * Characterise maximal ring orderings. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
158/9 Mathlib.lean,Mathlib/Algebra/Order/Ring/Ordering/Basic.lean,Mathlib/Algebra/Order/Ring/Ordering/Extend.lean,Mathlib/Basic/SetLike/Basic.lean 4 3 ['artie2000', 'github-actions', 'vihdzp'] nobody
16-52673
16 days ago
21-49350
21 days ago
21-49357
21 days
0
42363 ghseeli
author:ghseeli
feat(Combinatorics): card_le_card_biUnion_of_card_le_card This PR contributes a lemma to combinatorics, `card_le_card_biUnion_of_card_le_card`. this is a set theoretic corollary of a double counting result proved for bipartite graphs (`Finset.sum_card_bipartiteAbove_eq_sum_card_bipartiteBelow`). This result was needed for our Latin Square PR https://github.com/leanprover-community/mathlib4/pull/36698. This result was proved in less general terms in that PR, but is independent of Latin Square considerations and so we have generalized and moved it into this file. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics new-contributor 38/0 Mathlib/Combinatorics/Enumerative/DoubleCounting.lean 1 16 ['cjrl', 'github-actions', 'vlad902', 'wwylele'] b-mehta
assignee:b-mehta
16-51253
16 days ago
99-50953
99 days ago
112-42416
112 days
1
43048 alreadydone
author:alreadydone
feat(Counterexamples): an invertible semimodule of different cardinality than the semiring example due to Sixuan Gu (CUHKSZ) and Wei Qi (Ohio State U) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra increases-technical-debt
label:t-algebra$
181/0 Counterexamples.lean,Counterexamples/CommSemiring7InvertibleModule6.lean,Mathlib/RingTheory/Spectrum/Maximal/Basic.lean 3 2 ['github-actions', 'themathqueen'] riccardobrasca
assignee:riccardobrasca
16-51248
16 days ago
91-71074
91 days ago
91-71019
91 days
0
43087 JX-Mo
author:JX-Mo
feat(RepresentationTheory): add Hecke/Basic.lean This file defines `HeckeModule` of a representation `ρ` as `Hom_G(k[G ⧸ H], ρ)` and identifies it with the space of `H`-invariants. We deliberately choose the intertwining model over the invariant model as the main API, for it has good defeq property when we define the mixed level Hecke action of Hecke operators which is just the composition of intertwining maps. This has significant technical advantage because it avoids proving associativity and compatibility combinarically which is nasty using the invariant model. It is an `abbrev` for maximally reusing API from `ofMulAction` and `IntertwiningMap`. We remark that the abstract boundary will be cut out at `HeckeAlgera` which will be a `def` instead and we will provide an instance `Module HeckeAlgebra HeckeModule`. Before that, we need to develop representation theoretic lemmas about `HeckeModule` and `HeckeBimodule` first so `HeckeModule` should stay transparent. new-contributor t-algebra
label:t-algebra$
84/0 Mathlib.lean,Mathlib/RepresentationTheory/Hecke/Basic.lean 2 8 ['JX-Mo', 'Whysoserioushah', 'github-actions'] riccardobrasca
assignee:riccardobrasca
16-51247
16 days ago
31-40254
31 days ago
90-3762
90 days
1
45724 vihdzp
author:vihdzp
feat: build equiv `SignType ≃ Ordering` The idea is that `orderingEquiv.symm (cmp x y)` is a more general way to write `sign (x - y)`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order t-data 86/1 Mathlib/Basic/Sign/Defs.lean 1 1 ['github-actions'] nobody
16-50626
16 days ago
16-51716
16 days ago
16-51661
16 days
0
39809 zcyemi
author:zcyemi
feat(LinearAlgebra/AffineSpace/Menelaus): add Menelaus' theorem Add Menelaus' theorem for both `AffineSpace` and `NormedAddTorsor`. The `AffineSpace` version includes both the forward and converse directions, while the `NormedAddTorsor` version currently includes the forward direction. For the converse direction in the `NormedAddTorsor` setting, I am still considering the most convenient formalization for future use. One possible approach is to use `sbtw` / `¬ sbtw` to distinguish the different positional cases for points on the edges of a triangle, but this seems too complicated under permutations of the triangle vertices. t-euclidean-geometry 373/0 Mathlib.lean,Mathlib/Algebra/Order/BigOperators/Ring/Finset.lean,Mathlib/Analysis/Convex/Between.lean,Mathlib/Analysis/Normed/Affine/Menelaus.lean,Mathlib/LinearAlgebra/AffineSpace/Menelaus.lean,docs/1000.yaml 6 11 ['github-actions', 'jsm28', 'zcyemi'] nobody
16-46344
16 days ago
16-68856
16 days ago
83-58712
83 days
0
45728 IvanRenison
author:IvanRenison
feat(Data/Holor): add order related instances to `Holor` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 83/0 Mathlib/Data/Holor.lean 1 1 ['github-actions'] nobody
16-14726
16 days ago
16-15191
16 days ago
16-15573
16 days
0
43519 harahu
author:harahu
chore(Order/Interval/Set/SuccPred): generalize lemmas We generalize five lemmas from `LinearOrder` to `Preorder` and three to `PartialOrder`. The motivation for the `Preorder` generalizations is to enable deprecation of the almost identical results in `Mathlib/Order/SuccPred/Basic.lean`. The results in that file are stated more generally, so we need to generalize in order to subsume them properly. --- We're aiming to keep the statements in the touched file rather than those in `SuccPred/Basic.lean` based on [this discussion](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/duplicate.20succ.20interval.20lemmas/with/621955635). This PR has significant overlap with #23810, but does not cover `Finset/SuccPred.lean`. The touched file in this PR asks to be kept in sync with the `Finset` sibling, but there is already a lot of divergence since the `Finset` file hasn't been treated with `to_dual` yet. I therefore suggest that `Finset/SuccPred.lean` and the other sibling files be brought up to date in a subsequent PR. The generalizations were performed by Claude Code, and thereafter reviewed and somewhat cleaned up by me. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 61/19 Mathlib/Order/Interval/Set/SuccPred.lean 1 4 ['github-actions', 'harahu', 'mathlib-merge-conflicts', 'vihdzp'] vihdzp
assignee:vihdzp
16-60
16 days ago
16-3315
16 days ago
74-85250
74 days
0
45738 seewoo5
author:seewoo5
chore(Analysis/Asymptotics): drop commutativity assumptions Remove commutativity assumptions for asymptotic APIs. Closes #19288 * `Asymptotics/Arith.lean`, `Basic.lean`, `Lemmas.lean`, `Prod.lean`, `SpecificAsymptotics.lean`, `Theta.lean`: weaken the file-level variables, reprove lemmas that used commutative rewrites (`add_iff_right`, `sub_iff_right`, `congr_of_sub`, `add_isBigOWith`, `right_isBigO_add'`). * Weaken `Module` assumptions on the smul lemmas to `SMulZeroClass`/`SMul`, which is all `norm_smul_le`/`norm_smul` need. * Move `norm_norm'`, `nnnorm_norm'`, `enorm_norm'`, `abs_norm_sub_norm_le'`, `norm_sub_norm_le'`, `dist_norm_norm_le'`, `nndist_nnnorm_nnnorm_le'` (and their additive versions) to the non-commutative `SeminormedGroup` section. * `BoundedAtFilter.add` and `BoundedAtFilter.neg` now only need `SeminormedAddGroup`. Finset sums, `isLittleO_pow_sub_pow_sub`, `isLittleO_pow_sub_sub` and `BoundedAtFilter.smul` still require commutativity. Generated with Claude Opus 5.5, and reviewed by myself. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated 75/73 Mathlib/Analysis/Asymptotics/Arith.lean,Mathlib/Analysis/Asymptotics/Basic.lean,Mathlib/Analysis/Asymptotics/Lemmas.lean,Mathlib/Analysis/Asymptotics/Prod.lean,Mathlib/Analysis/Asymptotics/SpecificAsymptotics.lean,Mathlib/Analysis/Asymptotics/Theta.lean,Mathlib/Analysis/Normed/Group/Basic.lean,Mathlib/Analysis/Normed/Group/Real.lean,Mathlib/Order/Filter/ZeroAndBoundedAtFilter.lean 9 1 ['github-actions'] nobody
15-71235
15 days ago
15-71235
15 days ago
15-71180
15 days
0
45742 vihdzp
author:vihdzp
chore: recursor for `SignType` using the simp-normal forms --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Co-authored by @plp127 tech debt t-data 39/10 Mathlib/Basic/Sign/Basic.lean,Mathlib/Basic/Sign/Defs.lean,Mathlib/Data/EReal/Inv.lean 3 1 ['github-actions'] nobody
15-69784
15 days ago
15-72430
15 days ago
15-72375
15 days
0
44754 ajirving
author:ajirving
feat(Analysis/Complex): existence of analytic logs and roots Extends the results in BranchLogRoot.lean to construct logs and nth roots of analytic functions. This required a new inverse function theorem lemma, analyticAt_comp_iff_right_of_deriv_ne_zero. This is similar to the existing analyticAt_comp_iff_of_deriv_ne_zero: the new result gives analyticity of the right factor of the composition whereas the existing result gives the left. Perhaps better names are needed to distinguish these two similar results. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 50/1 Mathlib/Analysis/Calculus/InverseFunctionTheorem/Analytic.lean,Mathlib/Analysis/Complex/BranchLogRoot.lean 2 2 ['github-actions'] nobody
15-66575
15 days ago
42-22177
42 days ago
42-22122
42 days
0
44967 ajirving
author:ajirving
feat(Analysis/Complex): generalise Borel-Caratheodory and prove derivative bound Replaces the existing proof of the Borel-Caratheodory theorem with a version which first bounds all the derivatives at the centre using circle averages. Then uses this to prove a bound for the derivative. I hesitated over removing the existing proof but the new version has several advantages: * Drops the condition 0 < M * Gives the derivative bound with a sharp constant * I also generalised to arbitrary centre rather than just the origin I've left the existing API for balls centred at the origin but I've deprecated those results in favour of the new more general versions. I did however change the old results to drop the no longer needed 0 < M and 0 < R hypotheses. Note that all the deleted results were private. Several more widely useful helper lemmas were added to TaylorSeries, MeanValue and CircleAverage. If helpful I could separate those into a smaller PR first. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 229/85 Mathlib/Analysis/Complex/BorelCaratheodory.lean,Mathlib/Analysis/Complex/MeanValue.lean,Mathlib/Analysis/Complex/TaylorSeries.lean,Mathlib/MeasureTheory/Integral/CircleAverage.lean,docs/1000.yaml 5 4 ['ajirving', 'github-actions'] nobody
15-66243
15 days ago
36-6232
36 days ago
36-6540
36 days
0
45224 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Clique): translate clique theorems to independent sets `Translate/ToCompl.lean` is essentially identical to `Translate/ToDual.lean` but with names/comments changed. Perhaps we should have some ``registerTranslationAttribute `to_foo`` that adds a new attribute without any boilerplate, like creating a new simp set. [#graph theory > Translating the clique API for independent sets](https://leanprover.zulipchat.com/#narrow/channel/252551-graph-theory/topic/Translating.20the.20clique.20API.20for.20independent.20sets/with/634485631) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-combinatorics 212/105 Mathlib.lean,Mathlib/Combinatorics/SimpleGraph/Clique.lean,Mathlib/Combinatorics/SimpleGraph/VertexCover.lean,Mathlib/Tactic.lean,Mathlib/Tactic/Translate/ToCompl.lean 5 2 ['SnirBroshi', 'github-actions'] nobody
15-64192
15 days ago
15-64192
15 days ago
15-64139
15 days
0
45737 grunweg
author:grunweg
feat: make `basify` handle WithTop ENat better - add many more tests about `basify` for ENat and `WithTop ENat` - add a few missing lemmas about `ofNat` in ENat and WithTop ENat, - prove that `a + ∞ = ∞` in WithTop ENat, when a is a natural number converted directly to WithTop ENat - tag `re_refl` with `basify_simps`, so cases such as `a + ∞ = ∞` are closed automatically. Some tests highlight further issues in basify's handling (such as, norm_cast not being idempotent, or `basify` making no progress at all on some goals). These are out of scope for this PR, but recording them as TODOs at least reminds us what needs to be done still. These questions appear when counting derivatives in differential geometry, as the degree of smoothness of functions is `WithTop ENat`-valued. This particular PR is from the project to prove smoothness of the Levi-Civita connection, as part of the project towards geodesics, curvature and Riemannian geometry. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> large-import 138/4 Mathlib/Data/ENat/Monoid.lean,Mathlib/Order/Defs/PartialOrder.lean,MathlibTest/Tactic/Basify.lean 3 1 ['github-actions'] nobody
15-56421
15 days ago
15-56467
15 days ago
15-56413
15 days
1
43037 kim-em
author:kim-em
feat(Tactic/NormNum): add `norm_num_simproc` and use it for `Nat.fib` Adds `norm_num_simproc` to share a numerical evaluator between `norm_num` and simproc sets, and uses it to make `Nat.fib` evaluation available to `simp` and `grind`. ```lean norm_num_simproc [simp, seval] evalNatFib (Nat.fib _) where eval {_ _} e := ... ``` This declares the simproc `evalNatFib` and the extension `evalNatFib.normNumExt`. The set list defaults to `[simp]`; an explicit list replaces it, with `[]` disabling automatic simproc registration. Both registrations support `local` and `scoped`. The extension retains recursive operand normalization for direct consumers such as `ring` and `positivity`. `Nat.fib` is a first example: around 30 existing extensions are candidates for conversion, including `Nat.factorial`, `Nat.Prime`, and the Jacobi and Legendre symbols. Each will need its own registration and performance assessment. :robot: prepared with Codex+Claude t-meta LLM-generated 316/9 Mathlib/Tactic/NormNum/Core.lean,Mathlib/Tactic/NormNum/NatFib.lean,MathlibTest/Tactic/NormNum/NatFib.lean,MathlibTest/Tactic/NormNum/SimprocMacro.lean 4 16 ['JovanGerb', 'github-actions', 'kim-em', 'thorimur'] eric-wieser
assignee:eric-wieser
15-51254
15 days ago
60-26679
60 days ago
92-38797
92 days
0
43973 grunweg
author:grunweg
feat: mvfderiv_const_smul and friends This specialises the lemma `mvfderiv_smul` to the case of the first factor being a constant. Proper version of #34262. This was developed as part of the path to the Levi-Civita connection, but wound up not being strictly necessary for its development. Co-authored-by: Patrick Massot [patrickmassot@free.fr](mailto:patrickmassot@free.fr) --- - [x] depends on: #43986 - [x] depends on: #43987 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-differential-geometry 31/0 Mathlib/Algebra/Group/Action/Pi.lean,Mathlib/Geometry/Manifold/MFDeriv/NormedSpace.lean 2 6 ['github-actions', 'grunweg', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] ocfnash
assignee:ocfnash
15-51250
15 days ago
32-11589
32 days ago
32-11642
32 days
0
43886 gabriel-turinici
author:gabriel-turinici
feat(Analysis/Asymptotics): add Filter.Tendsto.weighted_cesaro_smul Adds `Filter.Tendsto.weighted_cesaro_smul`, a weighted (Toeplitz-type) generalization of `Filter.Tendsto.cesaro_smul`: if `S k → L` and `w k ≥ 0` has divergent partial sums, the weighted running average of `S` w.r.t. `w` also tends to `L`. Recovers `cesaro_smul` as the `w ≡ 1` case. Also adds `weighted_cesaro`, the real-valued convenience wrapper mirroring `cesaro`. This is a small building block toward a planned follow-up PR formalizing Kronecker's lemma, at its turn needed in some stochastic analysis setting. --- **AI disclosure**: this proof was developed using formatting assistance, library search and code corrections from Claude Code (Claude Sonnet 5) and a personal LLM automation. Alternative, shorter, proofs can be obtained with `IsLittleO`-style but that style seems too recent for me now. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis new-contributor LLM-generated 81/0 Mathlib/Analysis/Asymptotics/SpecificAsymptotics.lean 1 2 ['github-actions'] nobody
15-50352
15 days ago
66-61632
66 days ago
66-61577
66 days
0
45748 joelriou
author:joelriou
chore(SetTheory): make `Cardinal.fact_isRegular_aleph0` a global instance See [#mathlib4 > Fact instances @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Fact.20instances/near/636383477) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 6/16 Mathlib/AlgebraicTopology/SimplicialSet/AnodyneExtensions/Basic.lean,Mathlib/AlgebraicTopology/SimplicialSet/AnodyneExtensions/Inner/Basic.lean,Mathlib/AlgebraicTopology/SimplicialSet/Presentable.lean,Mathlib/CategoryTheory/Presentable/Basic.lean,Mathlib/CategoryTheory/Presentable/Directed.lean,Mathlib/CategoryTheory/Presentable/Finite.lean,Mathlib/CategoryTheory/Presentable/IsCardinalFiltered.lean,Mathlib/CategoryTheory/Presentable/LocallyPresentable.lean,Mathlib/CategoryTheory/SmallObject/IsCardinalForSmallObjectArgument.lean,Mathlib/SetTheory/Cardinal/Regular.lean 10 7 ['github-actions', 'joelriou', 'leanprover-radar', 'vihdzp'] nobody
15-15025
15 days ago
15-58082
15 days ago
15-58027
15 days
0
45763 vihdzp
author:vihdzp
chore(SetTheory/ZFC/VonNeumann): add stacks attribute --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory 1/0 Mathlib/SetTheory/ZFC/VonNeumann.lean 1 1 ['github-actions'] nobody
15-9697
15 days ago
15-10154
15 days ago
15-10099
15 days
0
45290 Parcly-Taxel
author:Parcly-Taxel
feat: transitivity properties of graphs `isSymmetric_of_transitive_of_odd_degree` was first written by Codex (GPT-6.1 Sol), then heavily hand-optimised. The rest is entirely human-written. t-combinatorics LLM-generated 228/0 Mathlib.lean,Mathlib/Combinatorics/SimpleGraph/Maps.lean,Mathlib/Combinatorics/SimpleGraph/Transitive.lean,docs/references.bib 4 23 ['Parcly-Taxel', 'SnirBroshi', 'github-actions'] nobody
15-5301
15 days ago
26-86285
26 days ago
27-32259
27 days
1
42102 CoolRmal
author:CoolRmal
feat(Probability/Process): the pathwise variation process This PR adds the pathwise **variation process** `variationProcess` of a stochastic process `X` from a starting time `a`, together with its basic properties and the measurability / adaptedness of the variation process at each time. ## Main definitions * `variationProcess`: the pathwise variation of `X` from a starting time `a`, as a process. ## Main results * `variationProcess_nonneg`, `monotone_variationProcess`: nonnegativity (above the start time) and monotonicity of the variation process. * `MeasureTheory.StronglyAdapted.measurable_variationProcess_of_continuous`, `..._of_isRightContinuous` and `..._of_isLeftContinuous`: for `a ≤ t`, the value at time `t` of the variation process of a strongly adapted process is `𝓕 t`-measurable, assuming continuous / right-continuous / left-continuous paths respectively. The general ingredients are added to the topology library: * `eVariationOn.eq_iSup_fin` (`Topology/EMetricSpace/BoundedVariation`): the variation as a supremum over monotone tuples `Fin (n + 1) → α`, whose index type is countable when `s` is countable. * `eVariationOn.eq_of_dense_of_continuousOn`, `..._of_isRightContinuousOn`, `..._of_isLeftContinuousOn`: the variation of a (one-sided) continuous function over `s` can be computed on a dense subset of `s`, which in the one-sided cases must contain the one-sided isolated points. * `nhdsGT_subtype_eq_bot_iff` / `nhdsLT_subtype_eq_bot_iff` (`Topology/Order/LeftRightNhds`): being isolated on the right in the subspace `↥s` is the same as being isolated on the right within `s`. The continuous case uses hereditary separability of the index (`Set.separableSpace`) to compute the variation over a countable dense set of times; the one-sided cases use second countability through `countable_setOfPred_isolated_right_within`. The material was developed for the Brownian motion project (https://github.com/RemyDegenne/brownian-motion/pull/494). Created with the help of Claude Code, carefully reviewed and golfed by myself. - [x] depends on: #45544 (adds `IsRightContinuousOn`) brownian t-measure-probability 314/0 Mathlib.lean,Mathlib/Probability/Process/VariationProcess.lean,Mathlib/Topology/EMetricSpace/BoundedVariation.lean,Mathlib/Topology/Order/LeftRightNhds.lean 4 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
14-78736
14 days ago
14-79956
14 days ago
17-26588
17 days
0
45777 tb65536
author:tb65536
chore(GroupTheory/*): use `IsAddFG` and `IsMulFG` in various files This PR goes through various files and replaces the eight old finiteness predicates (e.g., `Group.FG`, `AddSubmonoid.FG`, etc...) with the two new finiteness predicates `IsAddFG` and `IsMulFG`. This will help prepare the way for the eventual deprecation of the old finiteness predicates. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra t-group-theory
label:t-algebra$
34/32 Mathlib/GroupTheory/Commutator/Finite.lean,Mathlib/GroupTheory/Descent.lean,Mathlib/GroupTheory/FinitelyPresentedGroup.lean,Mathlib/GroupTheory/Generators.lean,Mathlib/GroupTheory/Rank.lean,Mathlib/GroupTheory/Schreier.lean,Mathlib/GroupTheory/Torsion.lean 7 1 ['github-actions'] nobody
14-74906
14 days ago
14-74953
14 days ago
14-74899
14 days
0
45785 JonasReif
author:JonasReif
chore(Order/BooleanAlgebra/Set): derive `disjoint_sdiff_inter` from the Boolean algebra lemma `Set.disjoint_sdiff_inter` carried a TODO asking for a proof via a Boolean algebra lemma. The general lemma `disjoint_inf_sdiff` already exists, so the set version is now its `symm`. The statement is unchanged. --- Created with Claude Opus 5.5 in Claude Code. t-order new-contributor 1/3 Mathlib/Order/BooleanAlgebra/Set.lean 1 2 ['github-actions'] nobody
14-58359
14 days ago
14-62189
14 days ago
14-62134
14 days
0
42046 LegaSage
author:LegaSage
feat(Polynomial): add Wronskian linear dependence lemmas This extends the polynomial Wronskian API of Baek and Lee from the existing coprime case to arbitrary polynomials over a characteristic-zero field. It adds: * an explicit nontrivial scalar relation for any pair with zero Wronskian, including zero-polynomial edge cases; * scalar-multiple corollaries when either polynomial is nonzero; * the weighted derivative corollary that solutions of `a * f' - n * a' * f = 0` are scalar multiples of `a ^ n` when `a ≠ 0`. The proof factors out the polynomial gcd and applies the existing `IsCoprime.wronskian_eq_zero_iff` theorem. This PR makes no novelty claim; it packages standard consequences of the existing Baek–Lee coprime Wronskian API. ------- The implementation was prepared with assistance from OpenAI Codex and reviewed and submitted by LegaSage. t-ring-theory new-contributor large-import LLM-generated 96/1 Mathlib/RingTheory/Polynomial/Wronskian.lean 1 2 ['github-actions'] alreadydone
assignee:alreadydone
14-51253
14 days ago
121-49040
121 days ago
121-48985
121 days
0
44005 seewoo5
author:seewoo5
feat(MonotoneConvergence): strict versions of `ge_of_tendsto` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Strict versions of `Monotone.ge_of_tendsto` and similar theorems: `StrictMono.gt_of_tendsto`, `StrictMono.lt_of_tendsto`, `StrictAnti.lt_of_tendsto`, `StrictAnti.gt_of_tendsto`. These require extra hypothesis such as `NoMaxOrder β` or `NoMinOrder β`. Claude is used to find the hypothesis and write initial proofs. Context: In Sphere packing project, there is an inequality of the form $f(t) < L$ for a strictly decreasing function $f$ on $(0, \infty)$ with $\lim_{t \to 0^+} f(t) = L$. Currently, this is proved by $f(t) < f(t/2) \le L$, where the last step uses `ge_of_tendsto`. With new theorems in this PR, we don't need to consider $f(t/2)$ anymore (by using `StrictAnti.gt_of_tendsto`). [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-topology LLM-generated sphere-packing 28/0 Mathlib/Topology/Order/MonotoneConvergence.lean 1 1 ['github-actions'] ocfnash
assignee:ocfnash
14-51249
14 days ago
62-86290
62 days ago
62-86235
62 days
0
45550 user202729
author:user202729
refactor(AlgebraicGeometry/EllipticCurve): make baseChange transparent notation - Make `baseChange` an `abbrev`, so the user doesn't need to explicitly unfold `baseChange`. - Explicitly document that `W⁄A` is equivalent to `W.map <| algebraMap R A`, so users seeing a `map` lemma applied on `W⁄S` at a use site can see why. - Rename `S` to `A` for consistency. --- As discussed in https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Expose.20public.20section.20bad.3F/with/635418753 , `W⁄A` is meant to be transparent, so I think this change is appropriate. This explicitly changes the meaning of `baseChange`, making code that previously name `baseChange` explicitly backwards incompatible, but I think this is fine. The affected proofs are fixed. I think the impact is rather minimal. The four copies of the notation in fact return the same thing, but for example `Affine R` is defined to be an `abbrev` of `WeierstrassCurve R`, so if one writes `(W⁄S).map`, the method `map` is looked up in namespace `Affine`. Without the notation in namespace `Affine`, it would implicitly convert `W` to `WeierstrassCurve`, then lookup the method `map` in namespace `WeierstrassCurve`. The `name` is added to the notation that needs linking from `baseChangeAux` to make the link in the HTML page works. (Similar to https://github.com/leanprover-community/mathlib4/pull/45129) t-algebraic-geometry new-contributor 29/41 Mathlib/AlgebraicGeometry/EllipticCurve/Affine/Basic.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Jacobian/Basic.lean,Mathlib/AlgebraicGeometry/EllipticCurve/LFunction.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Projective/Basic.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Reduction.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Weierstrass.lean 6 7 ['JX-Mo', 'github-actions', 'user202729'] kim-em
assignee:kim-em
14-51241
14 days ago
21-39075
21 days ago
21-39020
21 days
0
44853 dkaysin
author:dkaysin
feat(Geometry/Group): relate the word metric to the Cayley graph distance This PR constructs the Cayley graph (realized as a `SimpleGraph`) for a group `G` with respect to a generating family `P : Group.Generators G ι`, implements the link between walks in the Cayley graph and words, and establishes equivalence of the word metric and the distance on the Cayley graph. --- Resolves TODO from [#43118](https://github.com/leanprover-community/mathlib4/pull/43118). Implementation details: * `SimpleGraph` was chosen vs `Quiver/Schreier` because it has a more comprehensive API at the moment. More context: [Zulip thread](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Relate.20the.20word.20metric.20to.20the.20distance.20in.20the.20Cayley.20graph/with/631376709). * To accommodate possible future implementation for `Quiver/Schreier`, I've included "Simple" in the names of definitions and theorems (e.g., `cayleySimpleGraph`). * Because simple graph has no loops, in several places we have to check that a letter/generator is not trivial. Use of AI: I used Claude Opus 5.5 to help me with gathering context, designing API and implementation of several proofs. * I used AI to brainstorm and compare API design ideas based on the context from previous Zulip threads and existing repo code. * I used AI for suggesting parts of the proofs for `exists_walk_of_word` and `exists_word_of_walk` lemmas. * I used AI for checking docstrings for consistency. All AI-generated content was reviewed and edited by me. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #45359 [additivization of dependencies] t-geometric-group-theory new-contributor LLM-generated 161/3 Mathlib.lean,Mathlib/Geometry/Group/CayleySimpleGraph.lean,Mathlib/Geometry/Group/README.md,Mathlib/Geometry/Group/WordMetric.lean 4 16 ['dkaysin', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'tb65536', 'vlad902'] nobody
14-50356
14 days ago
24-73184
24 days ago
38-11503
38 days
0
45786 matt-w-horn
author:matt-w-horn
feat(Probability/Distributions): head and tail mass of the geometric distribution For `p ≠ 0` the geometric distribution gives `Iio m` mass `1 - (1 - p) ^ m` and `Ici m` mass `(1 - p) ^ m`. Split out of #42381. --- Assisted-by: Claude Fable 5.1 (code), Gemini Argon (review); used in https://github.com/matt-w-horn/overload t-measure-probability LLM-generated new-contributor 23/0 Mathlib/Probability/Distributions/Geometric.lean 1 3 ['github-actions', 'matt-w-horn'] nobody
14-45941
14 days ago
14-46004
14 days ago
14-45949
14 days
1
42487 bocowgill
author:bocowgill
feat(Algebra/BigOperators/Group/Finset/Powerset): add nested powersetCard identities This PR adds product and sum identities for nested collections of fixed-cardinality subsets. For `r ≤ k`, each `r`-element subset of a finite set `s` is contained in exactly `Nat.choose (s.card - r) (k - r)` of the `k`-element subsets of `s`. Thus, a sum over the `r`-element subsets of every `k`-element subset reduces to this multiplicity, times a single sum over `s.powersetCard r`. The product version is the analogous power identity. The proof exchanges the order of the two big operators using `Finset.prod_comm'`. It then counts each fiber with `Finset.card_filter_powersetCard_subset`. The additive identities are generated with `to_additive`. The PR also provides the useful elementwise specialization `r = 1`. **Motivation**: These results provide reusable weighted double-counting tools for finite combinatorics. They are useful in arguments about uniform set systems, incidence relations, and sums or products over fixed-cardinality subsets. --- ### LLM disclosure For theorem planning and Lean implementation, I used OpenAI Codex substantially. I also used Codex to search Mathlib and open PRs for related results, suggest naming and documentation, iterate on the proofs, audit import dependencies, and validate the commits locally. I personally reviewed the mathematical statements and Lean code line-by-line, including the naming and API choices. I also confirmed that I can explain each step of the proofs. For the current revision, I ran a targeted build of `Mathlib.Algebra.BigOperators.Group.Finset.Powerset`, the style and environment linters, and `git diff --check`. I also inspected the generated additive declarations and axiom dependencies, and tested an alternative proof using explicit incidence finsets. The complete GitHub CI suite passes. This is one of my earliest Mathlib contributions. I welcome corrections and suggestions, and I am prepared to revise the PR and learn from the review. t-algebra new-contributor LLM-generated
label:t-algebra$
27/0 Mathlib/Algebra/BigOperators/Group/Finset/Powerset.lean 1 17 ['bocowgill', 'github-actions', 'pepamontero'] alreadydone
assignee:alreadydone
13-51255
13 days ago
69-43487
69 days ago
107-71789
107 days
0
44582 CBirkbeck
author:CBirkbeck
chore(Tactic/Inclusion): inline the dyadic midpoint using core's `Dyadic.shiftRight` Remove `Inclusion.IntervalDyadicReal.midpoint`, which re-implemented core's `Dyadic.shiftRight`, and write the midpoint in `binarySplitMap` as `(l + u) >>> 1`. --- The tactic's tests (`MathlibTest/Tactic/Inclusion/Basic.lean`) take the same time as with the old `midpoint`: about 3.6 s either way, over five runs each. <!--redteam:v1 {"owner":"AI-DOOM-97fce5ac-e255-4515-b311-12ecf245ce72","findings":["RT-20261006-3d9a05"],"patterns":["reimplements-core-function"],"severity":"MAJOR"}--> 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-meta LLM-generated 3/8 Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/BinarySplit.lean 1 4 ['DavidLedvinka', 'github-actions', 'tb65536'] thorimur
assignee:thorimur
13-51252
13 days ago
22-82774
22 days ago
22-84372
22 days
0
45287 JX-Mo
author:JX-Mo
feat(DoubleCoset): add `DoubleCoset.Quotient.inv` Add "the map sending `H₁gH₂` to `H₂g⁻¹H₁`" which is used to construct the involution of Hecke algebras. t-group-theory 32/0 Mathlib/GroupTheory/DoubleCoset.lean 1 1 ['github-actions'] riccardobrasca
assignee:riccardobrasca
13-51249
13 days ago
27-64180
27 days ago
27-64275
27 days
0
45702 mcdoll
author:mcdoll
feat(Analysis/Calculus): iterated derivatives of constant additions Mirroring the naming etc of the `fderiv` versions. Note that these don't assume that `f` is differentiable, so they cannot be deduced from `iteratedFDeriv_add`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 49/0 Mathlib/Analysis/Calculus/ContDiff/Operations.lean 1 2 ['github-actions', 'wwylele'] nobody
13-16273
13 days ago
17-40118
17 days ago
17-40063
17 days
0
45443 janbernloehr
author:janbernloehr
feat(Analysis/ODE): add variable-coefficient integral Grönwall Add `le_mul_exp_integral_of_le_const_add_integral`, the integral Grönwall inequality with a continuous nonnegative variable coefficient. If `f t ≤ c + ∫ s in a..t, β s * f s` on `[a, b]`, conclude `f t ≤ c * exp (∫ s in a..t, β s)`. Require continuity only on the interval, with no sign assumptions on `f` or `c`. Use interval FTC and derivative monotonicity on the dominating primitive times its integrating factor. Put the theorem in a separate integral module so existing importers of differential Grönwall do not acquire FTC dependencies. This lemma is used in the formalization of my dissertation for Volterra inverse bounds and stability estimates; one concrete use is the [Volterra inverse bound](https://github.com/janbernloehr/diss-lean/blob/2091dba5870425e38372f9e0a9106c4214a1dfbe/NLS/ZakharovShabat/ClassicalVolterraL2Bound.lean#L41). Keeping the coefficient's integral in the exponential matters when integral norms are controlled but pointwise bounds are not uniform. For another contribution arising from the same dissertation formalization, see [#45441](https://github.com/leanprover-community/mathlib4/pull/45441), on compact remainders under one-sided inverses. --- ## Related work The same integral statement was previously proposed in [#37287](https://github.com/leanprover-community/mathlib4/pull/37287), which was withdrawn and not merged. The stronger variable-forcing proposal [#38829](https://github.com/leanprover-community/mathlib4/pull/38829) is also closed unmerged. Open [#39871](https://github.com/leanprover-community/mathlib4/pull/39871) concerns uniform Grönwall; its internal exponential comparison is a potential consumer of this lemma. No PR dependencies. ## Validation Checked using Lean `v4.36.0-rc2`: - Affected-module build and direct source check with warnings treated as errors. - `mk_all --lib Mathlib --check` and `lint-style`. - Default semantic linters and documentation linters. - Axiom inspection: only `propext`, `Classical.choice`, `Quot.sound`. - Clean merge simulation, diff/whitespace checks, and separate Volterra-use examples. ## AI assistance OpenAI Codex was used to write the Lean implementation. The proof design was informed by downstream proofs and the earlier proposals linked above. t-analysis LLM-generated new-contributor 70/0 Mathlib.lean,Mathlib/Analysis/ODE/GronwallIntegral.lean 2 3 ['NousVolition', 'github-actions'] nobody
13-15462
13 days ago
24-59869
24 days ago
24-59814
24 days
0
39545 Hagb
author:Hagb
feat(Order/OrderIsoNat): some lemmas about `((· < ·) : ℕ → ℕ → Prop) ↪r r` This PR contains several lemmas about relation embedding from `<` in `Nat`, well order, and (in)finiteness. - `RelEmbedding.infinite_iff_nonempty_relEmbedding_of_isWellOrder`: a type with a well order relation is infinite iff there is such a relation embedding. - `RelEmbedding.finite_iff_empty_relEmbedding_of_isWellOrder`: a finite variant of `infinite_iff_nonempty_relEmbedding_of_isWellOrder` - `IsWellOrder.finite_of_isWellOrder_of_isWellOrder_swap`: a type with a linear order relation well founded on both directions is finite. - `instFiniteOfWellFoundedLTOfWellFoundedGT`: an instance variant of `IsWellOrder.finite_of_isWellOrder_of_isWellOrder_swap` on `WellFounded{LT,GT}`. - `RelEmbedding.infinite_iff_nonempty_relEmbedding_lt_or_nonempty_relEmbedding_gt`: a type with a linear order relation is infinite iff there are both relation embedding between `<` in `Nat` and this relation, and between `>` in `Nat` and this relation. - `RelEmbedding.finite_iff_isEmpty_relEmbedding_lt_and_isEmpty_relEmbedding_gt`: a finite variant of `infinite_iff_nonempty_relEmbedding_lt_or_nonempty_relEmbedding_gt`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) <details> <summary> Edit: remove the description on the original motivation since `WellQuasiOrdered` instead of theorems in this PR can be used for that goal. </summary> `RelEmbedding.finite_iff_empty_relEmbedding_of_isWellOrder` might be used for proof of ```lean example {α β γ} [LinearOrder α] [LinearOrder β] [WellFoundedLT α] [WellFoundedLT β] [LinearOrder γ] {f : α × β ≃ γ} (mono : Monotone f) : WellFoundedLT γ := sorry ``` The latter will be used for ```lean example {α β γ} [Finite α] [LinearOrder β] [WellFoundedLT β] [LinearOrder γ] {f : (α → β) ≃ γ} (mono : Monotone f) : WellFoundedLT γ := sorry ``` And the finial goal is the well-foundedness of monomial order when the index type `σ` is finite (under the definition in #39214). t-order 56/0 Mathlib/Order/OrderIsoNat.lean 1 16 ['Hagb', 'SnirBroshi', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts', 'vihdzp'] nobody
12-79680
12 days ago
12-82757
12 days ago
36-46777
36 days
1
45814 DavidLedvinka
author:DavidLedvinka
feat(Probability/MarkovChain): add Markov chain measures Define `Kernel.markovChainMeasure` which is the measure of paths of a Markov chain with the given transition kernel and starting distribution. AI Assistance Disclosure: LLMs were used to golf and suggest generalisations t-measure-probability 126/8 Mathlib.lean,Mathlib/Probability/Kernel/IonescuTulcea/Traj.lean,Mathlib/Probability/Kernel/MarkovChainMeasure.lean 3 2 ['bryangingechen', 'github-actions'] nobody
12-72697
12 days ago
12-73870
12 days ago
13-72715
13 days
0
45849 Whysoserioushah
author:Whysoserioushah
chore(Topology/Sheaves/Stalks): add implicit_reducible to stalk Extracted from [Stacks Project](https://github.com/AxiomMath/Stacks) formalization. co-authored-by: Axiom Formalization team --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt 4/9 Mathlib/Geometry/RingedSpace/PresheafedSpace.lean,Mathlib/Geometry/RingedSpace/Stalks.lean,Mathlib/Topology/Sheaves/Stalks.lean 3 1 ['github-actions'] nobody
12-67499
12 days ago
12-72629
12 days ago
12-72574
12 days
0
44490 staroperator
author:staroperator
feat(Order/Preorder/Chain): add `IsLEChain` and `IsLTChain` abbreviations `IsLEChain` and `IsLTChain` are abbreviations for `IsChain (· ≤ ·)` and `IsChain (· < ·)`. The motivation to add new abbreviations includes: - canonizing `to_dual` translation (currently `IsChain (· ≤ ·)` are translated into `IsChain (· ≥ ·)`, which is equivalent via `IsChain.symm`) - separating properties of `≤`-chain and `<`-chain under different namespaces (they are not equivalent in preorders, the former is strictly weaker, and the latter correspond to linearly ordered subsets) - (maybe) promoting the use of `<`-chain Feel free to discuss the design in [Zulip discussion](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Order.20dual.20tactic/near/628982679). As a TODO, Zorn's lemmas can be reproved under `<`-chains, which are more general in preorders. This PR does not add `IsMaxLEChain` for `IsMaxChain (· ≤ ·)`, considering they only have 10 usages so far, mainly associated with `Flag`. This PR adds `to_dual` to [`IsCoatomic.of_isChain_bounded`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Order/ZornAtoms.html#IsCoatomic.of_isChain_bounded). It also changes the signatures of existing [`zorn_ge`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Order/Zorn.html#zorn_ge) etc. from `IsChain (· ≥ ·)` into `IsChain (· ≤ ·)`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 186/128 Counterexamples/AharoniKorman.lean,Mathlib/Algebra/Module/Injective.lean,Mathlib/Analysis/Convex/Basic.lean,Mathlib/Analysis/Convex/Cone/Extension.lean,Mathlib/Data/Fin/FlagRange.lean,Mathlib/FieldTheory/Extension.lean,Mathlib/GroupTheory/Sylow.lean,Mathlib/LinearAlgebra/Basis/Flag.lean,Mathlib/Order/BourbakiWitt.lean,Mathlib/Order/Extension/Linear.lean,Mathlib/Order/OmegaCompletePartialOrder.lean,Mathlib/Order/OrderIsoNat.lean,Mathlib/Order/Preorder/Chain.lean,Mathlib/Order/Zorn.lean,Mathlib/Order/ZornAtoms.lean,Mathlib/RingTheory/Ideal/Maximal.lean,Mathlib/RingTheory/Ideal/MinimalPrime/Basic.lean,Mathlib/RingTheory/Ideal/Oka.lean,Mathlib/RingTheory/PrincipalIdealDomain.lean,Mathlib/RingTheory/UniqueFactorizationDomain/Kaplansky.lean,Mathlib/SetTheory/Cardinal/EventuallyConst.lean,Mathlib/Topology/ShrinkingLemma.lean 22 7 ['github-actions', 'mathlib-merge-conflicts', 'staroperator', 'vihdzp'] nobody
12-61085
12 days ago
12-62930
12 days ago
44-61232
44 days
2
45842 JovanGerb
author:JovanGerb
perf(Linter): move `setOption` linter to SyntaxBased This PR refactors the `setOption` linter to be part of the syntax based linters. This fixes some problems with the linter and gives a speedup. The interaction between this linter and `withSetOptionIn` is a bit awkward, because `withSetOptionIn` strips away the leading `set_option ... in` syntax, but we want to lint that syntax. So instead, we add our own version of `withSetOptionIn` that also calls the `setOption` linter. The following problems are fixed in this PR: - Due to the use of `withSetOptionIn`, the `setOption` linter used to not lint the `set_option ... in` in front of a command. - Due to the use of `Syntax.find?`, the `setOption` linter used to only look at the first `set_option` syntax in each command. - The `setOption` linter used to not differentiate between global and local options, so it would warn agains `tactic`/`term` uses of `set_option maxHeartbeats in`, with an error message saying that you need to use it with `in`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 102/137 Mathlib/AlgebraicTopology/FundamentalGroupoid/InducedMaps.lean,Mathlib/Tactic/Linter/Style.lean,Mathlib/Tactic/Linter/SyntaxBased.lean,MathlibTest/Linter/Style.lean 4 5 ['JovanGerb', 'bryangingechen', 'github-actions', 'leanprover-radar'] nobody
12-57265
12 days ago
12-73868
12 days ago
12-82169
12 days
0
45033 mkaratarakis
author:mkaratarakis
feat(Combinatorics/Quiver/Path): iterated composition of a loop `Quiver.Path.replicate`, the `n`-fold composition of a loop with itself, and its length. --- Split from #39916. t-combinatorics 46/0 Mathlib.lean,Mathlib/Combinatorics/Quiver/Path/Replicate.lean 2 4 ['YaelDillies', 'github-actions', 'mkaratarakis'] nobody
12-50354
12 days ago
33-76799
33 days ago
33-78042
33 days
0
45069 korbonits
author:korbonits
feat(Geometry/Manifold): the Riemann curvature of a covariant derivative Define the Riemann curvature `R(X, Y) Z = ∇_X ∇_Y Z - ∇_Y ∇_X Z - ∇_[X,Y] Z` of a covariant derivative on the tangent bundle, as an operator on vector fields, in a new file `CovariantDerivative/Curvature.lean` (alongside `Torsion.lean`). Main results: - `CovariantDerivative.curvature_swap`: antisymmetry in the first two arguments. - `curvature_smul_left/snd`, `curvature_add_left/snd`: function-linearity in the first two arguments, with explicit differentiability hypotheses. - `tensorialAt_curvature_fst/snd`: for a `C¹` covariant derivative and a `C²` field `Z`, the curvature is `TensorialAt` in each of its first two arguments. - `CovariantDerivative.mdifferentiableAt_apply`: for a `C¹` covariant derivative, `∇_X σ` is differentiable at `x` when `σ` is `C²` and `X` is differentiable at `x`. Most of the code I'm planning to upstream into mathlib4 is already proved in https://github.com/korbonits/ricci-flow-blueprint --- AI disclosure - level: Level 5 / Level 6 in [the link shared](https://www.visidata.org/blog/2026/ai/#self-assessed-ai-level-for-contributions) I feel confident about the math but I am still learning Lean itself - code: most of the Lean in this PR was drafted by Claude Code (statements, proofs, docstrings). - direction and review: I chose the contribution, made the decisions, reviewed every line, and wrote all GitHub/Zulip comments. new-contributor t-differential-geometry LLM-generated 167/0 Mathlib.lean,Mathlib/Geometry/Manifold/VectorBundle/CovariantDerivative/Curvature.lean 2 3 ['github-actions', 'korbonits'] ocfnash
assignee:ocfnash
12-28617
12 days ago
33-37447
33 days ago
33-37392
33 days
0
45858 pelicanhere
author:pelicanhere
feat(EReal): continuity of addition by real-valued functions Add continuity lemmas for addition of real-valued functions to `EReal`-valued functions. t-topology new-contributor 13/0 Mathlib/Topology/Instances/EReal/Lemmas.lean 1 2 ['github-actions'] nobody
12-8965
12 days ago
12-21929
12 days ago
12-21874
12 days
0
45857 wobniW
author:wobniW
feat(Computability/Primrec): add Primcodable instance for empty types Add a low-priority `Primcodable` instance for any type with `[IsEmpty α]`. ### Motivation `IsEmpty.toEncodable` already gives a blanket `Encodable` instance for `[IsEmpty α]`, and `Empty` already has a `Primcodable` instance. Any empty type should have a `Primcodable` instance too. Right now, users have to build the instance by hand, via `Primcodable.ofEquiv` or by writing the instance fields manually. ### Design notes - `ofEquiv` is still the right tool when an explicit equivalence is available and definitional transparency matters. However, instance synthesis can't pick it up on its own. This blanket instance fills a gap where `[IsEmpty α]` already exists. t-computability new-contributor 3/0 Mathlib/Computability/Primrec/Basic.lean 1 4 ['github-actions', 'grunweg', 'wobniW'] nobody
12-501
12 days ago
12-501
12 days ago
12-20402
12 days
0
45830 plp127
author:plp127
feat(Data/Finsupp/Lex): left congruence for finsupp lex and colex Prove left congruence for finsupp lex and colex, right congruence is not proved since it requires preserving `0`. Also some trivial generalizations in `Mathlib.Data.Finsupp.WellFounded` and `Mathlib.Data.DFinsupp.WellFounded`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order t-data 83/5 Mathlib/Data/DFinsupp/WellFounded.lean,Mathlib/Data/Finsupp/Lex.lean,Mathlib/Data/Finsupp/WellFounded.lean 3 13 ['Hagb', 'github-actions', 'plp127', 'vihdzp'] nobody
11-78438
11 days ago
12-69546
12 days ago
12-71113
12 days
0
45868 pelicanhere
author:pelicanhere
feat(Geometry/Convex): add subgradients Define proper functions and subgradients along bilinear pairings. Prove addition and linear pullback rules, convexity of subdifferentials, and Fermat's rule. --- t-convex-geometry new-contributor 336/0 Mathlib.lean,Mathlib/Geometry/Convex/Fun/Proper.lean,Mathlib/Geometry/Convex/Fun/Subgradient/Basic.lean 3 2 ['github-actions'] nobody
11-77896
11 days ago
11-78771
11 days ago
11-78716
11 days
0
45682 felixpernegger
author:felixpernegger
chore(Basic): deprecating (bad) trivial lemmas Removes unused hypothesis from #45673 in Basic. More precisely, during the run it was discovered that here we have some lemmas that are true in more generality; i.e. something like `example (p : NNReal) [ExampleClass p] : 0 \le p := sorry` which already holds since `p : NNReal` LLM-generated t-data 6/0 Mathlib/Basic/Real/ConjExponents.lean 1 5 ['felixpernegger', 'github-actions', 'plp127', 'vihdzp'] nobody
11-75880
11 days ago
17-47737
17 days ago
17-51071
17 days
1
42587 joelriou
author:joelriou
feat(AlgebraicTopology/SimplicialSet): the fundamental groupoid, as a pseudofunctor The main definition in this PR is the pseudofunctor `SSet.FundamentalGroupoid.pseudofunctor : LocallyDiscrete SSet.{u} ⥤ᵖ Cat.{u, u}` which sends a simplicial set to its fundamental groupoid. --- - [x] depends on: #42576 - [x] depends on: #42523 - [x] depends on: #42528 - [x] depends on: #42529 - [x] depends on: #42527 - [x] depends on: #42526 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebraic-topology 106/2 Mathlib.lean,Mathlib/AlgebraicTopology/SimplicialSet/FundamentalGroupoid/Basic.lean,Mathlib/AlgebraicTopology/SimplicialSet/FundamentalGroupoid/Pseudofunctor.lean 3 5 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
11-73213
11 days ago
38-68328
38 days ago
38-68274
38 days
0
44600 artie2000
author:artie2000
feat(Algebra/Ring): properties of semireal rings * Prove that real rings are semireal and that semireal fields are real * Prove that a ring has a preordering on it iff it's semireal * Clean up some documentation --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
64/1 Mathlib.lean,Mathlib/Algebra/Ring/IsFormallyReal.lean,Mathlib/Algebra/Ring/Semireal/Basic.lean,Mathlib/Algebra/Ring/Semireal/Defs.lean 4 11 ['artie2000', 'github-actions', 'mathlib-merge-conflicts', 'vihdzp'] nobody
11-55840
11 days ago
11-56354
11 days ago
45-61674
45 days
0
45288 JX-Mo
author:JX-Mo
feat(DoubleCoset): add `DoubleCoset.relPosition` This is used to analyze the decomposition of double coset. The main function is to switch the right coset to left coset. We have better API around left coset so it makes downstream proofs easier. If we doesn't want large import, we would have to give up `DoubleCoset.relPosition_smul`. But it seems reasonable here since `HgK` is the `H` orbit of `gK` and we will eventually want group action at some point. t-group-theory large-import 27/1 Mathlib/GroupTheory/DoubleCoset.lean 1 1 ['github-actions'] riccardobrasca
assignee:riccardobrasca
11-51251
11 days ago
27-63521
27 days ago
27-63650
27 days
0
45885 hawkrobe
author:hawkrobe
feat(LinearAlgebra/TensorProduct): graded pieces of a tensor product --- This PR gives the definition and the membership lemmas. #42365 shows these pieces form a decomposition. I split it off to unblock #39849, which only needs the definition. Claude Code was used to prepare this PR. t-algebra
label:t-algebra$
54/0 Mathlib/LinearAlgebra/TensorProduct/Decomposition.lean 1 1 ['github-actions'] nobody
11-48286
11 days ago
11-48754
11 days ago
11-48699
11 days
1
45579 lua-vr
author:lua-vr
feat(Topology/Instances/AddCircle): induced map between `AddCircle`s --- Suggested in #45360 AI-assisted (but reviewed). <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #45580 <!-- Message of single commit: --> LLM-generated t-topology 35/0 Mathlib/GroupTheory/QuotientGroup/Defs.lean,Mathlib/Topology/Instances/AddCircle/Defs.lean 2 2 ['github-actions', 'mathlib-dependent-issues', 'vihdzp'] nobody
11-43787
11 days ago
18-64507
18 days ago
18-65449
18 days
2
41721 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Hamiltonian): `(G ⊔ edge u v).IsHamiltonian` iff ```lean (G ⊔ edge u v).IsHamiltonian ↔ G.IsHamiltonian ∨ ∃ p : G.Walk u v, p.IsHamiltonian ∧ 2 ≤ p.length ``` This is sort-of the inverse of `IsHamiltonian.isHamiltonian_of_adj`, which takes in a Hamiltonian walk where the endpoints are adjacent and shows the graph is Hamiltonian: ``` p.IsHamiltonian → G.Adj u v → p.length ≠ 1 → G.IsHamiltonian ``` The iff is also true if we replace `2 ≤ p.length` with `p.length ≠ 1`, but since `IsHamiltonian.isHamiltonian_of_adj` exists I think making the forward direction stronger is better. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #41720 - [x] depends on: #41460 - [x] depends on: #41717 - [x] depends on: #41435 - [x] depends on: #41393 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 31/0 Mathlib/Combinatorics/SimpleGraph/Hamiltonian.lean,Mathlib/Combinatorics/SimpleGraph/Paths.lean 2 2 ['github-actions', 'mathlib-dependent-issues'] nobody
11-38887
11 days ago
11-56473
11 days ago
11-59333
11 days
1
45891 mcdoll
author:mcdoll
feat(Analysis/Calculus): characterization of elements of the tangent cone The result is actually an if and only iff, but the converse direction is way more involved (and not on mathlib level yet). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 46/0 Mathlib.lean,Mathlib/Analysis/Calculus/TangentCone/Deriv.lean 2 1 ['github-actions'] nobody
11-37683
11 days ago
11-38160
11 days ago
11-38105
11 days
0
42372 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph): `Fintype V → Fintype (SimpleGraph V)` without `DecidableEq V` Now this works: ```lean /-- info: 2 -/ #guard_msgs in #eval Fintype.card (SimpleGraph Prop) ``` Co-authored-by: Rob23oba <152706811+Rob23oba@users.noreply.github.com> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #42370 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 8/1 Mathlib/Combinatorics/SimpleGraph/Basic.lean,Mathlib/Combinatorics/SimpleGraph/Maps.lean 2 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
11-36681
11 days ago
11-37128
11 days ago
11-48298
11 days
0
38434 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Maps): `map` lemmas about support/top/bot --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #38432 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 13/4 Mathlib/Combinatorics/SimpleGraph/Maps.lean 1 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
11-34632
11 days ago
11-35110
11 days ago
72-57678
72 days
0
38231 NoneMore
author:NoneMore
feat(ModelTheory/Definablity): add syntax-to-definability bridge lemmas Add bridge lemmas from syntax to definability and refactor downstream proofs to use them. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-logic 104/55 Mathlib/ModelTheory/Definability.lean,Mathlib/ModelTheory/ElementarySubstructures.lean 2 4 ['github-actions', 'mathlib-merge-conflicts', 'staroperator'] nobody
11-32452
11 days ago
11-33213
11 days ago
108-28397
108 days
0
45889 vihdzp
author:vihdzp
refactor: rename `Cardinal.lt_aleph0_iff_finite` → `Cardinal.mk_lt_aleph0_iff` I claim that the older name is not good, since it doesn't mention `Cardinal.mk`. We also rename some similar surrounding theorems. This incidentally gets rid of two duplicate declarations. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory tech debt 88/94 Mathlib/Algebra/Module/SpanRank.lean,Mathlib/Combinatorics/Matroid/Rank/Cardinal.lean,Mathlib/Data/Set/Finite/Basic.lean,Mathlib/Data/W/Cardinal.lean,Mathlib/FieldTheory/CardinalEmb.lean,Mathlib/FieldTheory/FinTrdeg.lean,Mathlib/FieldTheory/Finiteness.lean,Mathlib/FieldTheory/IsAlgClosed/Classification.lean,Mathlib/LinearAlgebra/Dimension/ErdosKaplansky.lean,Mathlib/LinearAlgebra/Dimension/Finite.lean,Mathlib/LinearAlgebra/Dimension/FreeAndStrongRankCondition.lean,Mathlib/LinearAlgebra/Dimension/StrongRankCondition.lean,Mathlib/LinearAlgebra/FiniteDimensional/Basic.lean,Mathlib/ModelTheory/Algebra/Field/IsAlgClosed.lean,Mathlib/ModelTheory/Satisfiability.lean,Mathlib/Order/Filter/CardinalInter.lean,Mathlib/Order/Filter/Cocardinal.lean,Mathlib/RingTheory/Algebraic/Cardinality.lean,Mathlib/SetTheory/Cardinal/Basic.lean,Mathlib/SetTheory/Cardinal/CountableCover.lean,Mathlib/SetTheory/Cardinal/Finite.lean,Mathlib/SetTheory/Cardinal/Finsupp.lean,Mathlib/SetTheory/Cardinal/Subfield.lean,Mathlib/SetTheory/Ordinal/Basic.lean 24 1 ['github-actions'] nobody
11-32252
11 days ago
11-32291
11 days ago
11-32287
11 days
0
45843 SnirBroshi
author:SnirBroshi
feat(Order/Atoms): there are no pred-limits in strongly-atomic orders `¬IsPredLimit` for any element in `IsStronglyAtomic` (or `SuccOrder`, or `WellFoundedLT`, or `LocallyFiniteOrder`). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 24/8 Mathlib/Order/Atoms.lean 1 4 ['SnirBroshi', 'bryangingechen', 'github-actions', 'plp127', 'vihdzp'] nobody
11-30945
11 days ago
12-73865
12 days ago
12-81873
12 days
0
45893 vihdzp
author:vihdzp
chore: use `to_dual` for `IsStronglyAtomic` Note that the type signature of `IsStronglyCoatomic` has been changed slightly. The arguments of the conjunction were reordered so that they match `IsStronglyAtomic`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 42/72 Mathlib/Order/Atoms.lean,Mathlib/Order/Atoms/Finite.lean 2 1 ['github-actions'] nobody
11-24496
11 days ago
11-26377
11 days ago
11-27936
11 days
0
43166 WenrongZou
author:WenrongZou
feat(MvPowerSeries/pderiv): add `pderiv_map` and `pderiv_rename` In this PR, we prove `MvPowerSeries.map` and `MvPowerSeries.rename` commute with taking derivative. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) large-import t-ring-theory 29/2 Mathlib/RingTheory/MvPowerSeries/Derivative.lean 1 1 ['github-actions'] mattrobball
assignee:mattrobball
11-20120
11 days ago
11-20678
11 days ago
87-18203
87 days
1
45512 riccardobrasca
author:riccardobrasca
feat: add various lemmas about cyclotomic extensions --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 190/0 Mathlib/NumberTheory/NumberField/Cyclotomic/Basic.lean,Mathlib/NumberTheory/NumberField/Cyclotomic/Ideal.lean,Mathlib/NumberTheory/NumberField/Norm.lean,Mathlib/RingTheory/DedekindDomain/Factorization.lean,Mathlib/RingTheory/NormTrace.lean 5 12 ['github-actions', 'mathlib-merge-conflicts', 'riccardobrasca', 'xroblot'] nobody
11-16625
11 days ago
11-17100
11 days ago
22-22798
22 days
0
39774 Hagb
author:Hagb
feat(Order/WellFounded): `WellFounded` on subtype iff the relation restricted on the subtype is `WellFounded` Equivalence between `WellFounded` on a subtype and `WellFounded` on the underlying type with the relation restricted on the subtype. --- (It was a lemma for #39781, which has been closed since there would be a better proof.) <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 29/0 Mathlib/Order/WellFounded.lean 1 13 ['Hagb', 'SnirBroshi', 'bryangingechen', 'github-actions', 'plp127'] nobody
11-11573
11 days ago
12-67936
12 days ago
73-59375
73 days
2
45263 huntse
author:huntse
feat(Order/Filter/Cofinite): add `Filter.countable_sets_cofinite` My first attempt at a PR for mathlib so I apologize if I'm doing it wrong. I picked up a lemma in FLT that was marked as TODO to upstream into mathlib (there it is Filter.cofinite.sets.countable in FLT/Mathlib/Order/Filter/Cofinite.lean) and upstreamed it. - I used a name which seemed more in keeping with mathlib convention but please lmk if I should rename it. Both `countable_sets_cofinite` and `cofinite_sets_countable` seemed somewhat defensible. - I changed it to a theorem since the neighbouring code seems to all be theorems. - The actual lean proof is due to kbuzzard. I just copied it upstream and made the following tweaks: - `(ι : Type*)` was not needed as that's mentioned higher in the file in a `variable` line - I removed namespacing on Filter.cofinite as we're in that namespace here already - I didn't use AI to generate this PR or description but since it's my first PR to mathlib and I'm a bit nervous I did use AI to review the PR and give me suggestions. It suggested the name change and the removal of the redundant namespacing and type info. - FLT also has a Countable instance for ↥(cofinite).sets which I left there. Co-authored-by: kbuzzard t-order FLT new-contributor 5/0 Mathlib/Order/Filter/Cofinite.lean 1 5 ['github-actions', 'huntse', 'vihdzp'] nobody
11-10824
11 days ago
28-51354
28 days ago
28-51299
28 days
0
45898 WaterKing201030
author:WaterKing201030
feat(Data/List/Chain): exists nodup isChain of relationReflTransGen The existing theorem `List.exists_isChain_cons_of_relationReflTransGen` gives chain from ReflTransGen, but do not guarantee that its elements are distinct. Chains with no duplicates are useful in many settings. For example, `SimpleGraph.Walk.bypass` removes repeated elements while preserving its endpoints. But, the adjacency relations must be symmetric and irreflexive. Add the following three theorems for arbitrary relations: 1. `List.exists_isChain_cons_nodup_sublist_of_isChain` 2. `List.exists_isChain_cons_nodup_of_relationReflTransGen` 3. `List.exists_isChain_ne_nil_nodup_of_relationReflTransGen` --- Use of AI: I asked ChatGPT to check whether these theorems duplicate existing ones. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data new-contributor 43/0 Mathlib/Data/List/Chain.lean 1 2 ['github-actions'] nobody
11-10749
11 days ago
11-20661
11 days ago
11-20606
11 days
0
41935 martinamaggio
author:martinamaggio
feat(Probability/Independence): grouping an independent family by pairwise disjoint index sets If `m : ι → MeasurableSpace Ω` is an independent family of σ-algebras and `G : ι' → Set ι` is a pairwise disjoint family of index sets, then the family of grouped σ-algebras `fun i' ↦ ⨆ j ∈ G i', m j` is again independent. This is the indexed-family version of the existing two-group lemma `indep_iSup_of_disjoint`, from which it follows by induction on the finite subfamily, peeling off one group at a time against the union of the remaining ones. As usual it is proven for the kernel notion of independence (`Kernel.iIndep_iSup_of_disjoint`) and specialized to independence w.r.t. a measure (`iIndep_iSup_of_disjoint`) and to conditional independence (`iCondIndep_iSup_of_disjoint`). The lemma is the natural bridge from an independent family to block/grouping arguments — e.g. Markov-style properties of recursions driven by disjoint sets of randomness sources. It was developed for a formalization of end-to-end latency distributions of periodic task chains, where it establishes that successive chain states, being measurable w.r.t. σ-algebras of disjoint groups of an independent family, form an independent family themselves. t-measure-probability new-contributor 56/0 Mathlib/Probability/Independence/Basic.lean,Mathlib/Probability/Independence/Conditional.lean,Mathlib/Probability/Independence/Kernel/Indep.lean 3 6 ['bocowgill', 'github-actions', 'martinamaggio'] nobody
11-7167
11 days ago
11-51408
11 days ago
35-25494
35 days
0
45871 IvanRenison
author:IvanRenison
feat(Data/Holor): make `HolorIndex` an instance of `Fintype` In order to allow reductions over `Holor` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data large-import 35/2 Mathlib/Data/Holor.lean 1 6 ['IvanRenison', 'github-actions', 'vihdzp'] nobody
11-6180
11 days ago
11-20628
11 days ago
11-21338
11 days
1
41531 luigi-massacci
author:luigi-massacci
feat: scalar multiplication as a CLM on D^n Introduces for `TestFunction` the analogous results from `SchwartzMap`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #41485 - [x] depends on: #41324 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 55/4 Mathlib/Analysis/Distribution/TestFunction.lean 1 10 ['github-actions', 'luigi-massacci', 'luigimassacci-ax', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mcdoll'] urkud
assignee:urkud
11-4885
11 days ago
11-5446
11 days ago
65-86232
65 days
4
45887 CBirkbeck
author:CBirkbeck
fix(Data/Ordmap/Ordnode): repair `link`, `insertMin`, `splitAt`, `ofAscList`, `diff` and `inter` Fix six operations on `Ordnode` that do not do what their docstrings say: * `link`: keep the whole of the smaller tree when descending into the larger one, as Haskell's `link` does. It kept only a subtree and lost elements, e.g. `link {0, 1, 2, 3} 4 {5} = {0, 1, 2, 3, 4}`. The recursion on the right tree is a structural auxiliary `link.go`, not an `Ordnode.recOn`, whose compiled code evaluates both induction hypotheses at every node. * `insertMin`: rebalance with `balanceL`, since it is the left side that grows. With `balanceR` the tree came out unbalanced, and later operations went wrong on it: `erase 7 (insertMin 1 (insertMin 2 (ofList [7, 3, 6, 4, 5]))) = ∅`. * `splitAtAux`: return `l`, not `glue l r`, as the first half when the index is `size l`: `splitAt 1 {0, 1, 2}` was `({0, 2}, {1, 2})`. * `ofAscListAux₁`: recurse on the whole list with the bound halved, as Haskell's `create` does. It recursed on the tail with the bound doubled, so `ofAscList` kept at most four elements. * `diff` and `inter`: return `∅`, not the other argument, when the first (respectively the second) argument is empty. The recursion reaches these cases: `inter {1, 2} {2, 3} = {1, 2}`. Add `MathlibTest/Ordnode.lean`, which compares these operations and those built on them with list operations on small sets and checks that the results are balanced. Also correct the docstring examples of `insertMin`, `partition` and `map`, the precondition of `ofAscList`, and the complexity bound of `union`, `diff` and `inter` (Haskell's `n\/m` had been read as `n ∪ m`). --- On master, every check of the new test file fails except two controls. `merge` is also written with `Ordnode.recOn` and is slow in compiled code for the same reason; it is correct and verified, so it is left for another PR. Found by an automated search for definitions that contradict their documentation. The patch, the test and this description were written with Claude Code. 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-data LLM-generated 162/37 Mathlib/Data/Ordmap/Ordnode.lean,MathlibTest/Ordnode.lean 2 3 ['github-actions', 'tb65536', 'vihdzp'] nobody
11-1909
11 days ago
11-18264
11 days ago
11-18209
11 days
1
45844 teorth
author:teorth
feat(NumberTheory/LSeries/WeakPNT): the Möbius form of the prime number theorem This PR proves the Möbius form of the prime number theorem, `∑ n ≤ x, μ n = o(x)`, as `Mertens.tendsto_M_div_atTop` and `Mertens.isLittleO_M_id`. It applies the Wiener–Ikehara theorem to the nonnegative function `n ↦ 1 + μ n`, whose `L`-series is `ζ s + 1 / ζ s`. It is not a corollary of the other forms of the prime number theorem in `WeakPNT.lean`. It also adds: * the Mertens function `Mertens.M x = ∑ n ≤ x, μ n` in `Mathlib/NumberTheory/ArithmeticFunction/Moebius.lean`, for `x` in any `FloorSemiring`, together with `M_eq_sum_Icc` and the trivial bound `abs_M_le`; * `riemannZeta₁_ne_zero_of_one_le_re` in `Mathlib/NumberTheory/LSeries/Nonvanishing.lean`. This material was split off from #43238 at the request of the reviewers, and this version incorporates their comments on it. - [x] depends on: #43238 🤖 Generated with [Claude Code](https://claude.com/claude-code) LLM-generated 97/0 Mathlib/NumberTheory/ArithmeticFunction/Moebius.lean,Mathlib/NumberTheory/LSeries/Dirichlet.lean,Mathlib/NumberTheory/LSeries/Nonvanishing.lean,Mathlib/NumberTheory/LSeries/WeakPNT.lean,docs/1000.yaml 5 3 ['bryangingechen', 'github-actions', 'mathlib-dependent-issues'] nobody
10-71315
10 days ago
10-73566
10 days ago
10-73673
10 days
0
43082 WenrongZou
author:WenrongZou
feat(RingTheory/Henselian): add Hensel lemma for non-monic polynomials In a ring `R` that is Henselian at an ideal `I`, a simple root modulo `I` lifts to a root in `R` even when the polynomial is not monic. And for local ring, we prove two more equivalent description of the theorem [`HenselianLocalRing.TFAE`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/RingTheory/Henselian.html#HenselianLocalRing.TFAE), see stacks project [04GG](https://stacks.math.columbia.edu/tag/04GG). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 88/14 Mathlib/RingTheory/Henselian.lean 1 3 ['github-actions', 'mathlib-merge-conflicts'] mattrobball
assignee:mattrobball
10-70550
10 days ago
19-56895
19 days ago
84-76144
84 days
0
38472 Raph-DG
author:Raph-DG
feat(AlgebraicGeometry): The Weil divisor associated to an element of the function field on a locally Noetherian integral scheme In this PR we define and provide some basic API for principal Weil divisors, i.e. the Weil divisor associated to an element of the function field of a locally noetherian, integral scheme. - [x] depends on: #29774 - [x] depends on: #37985 - [x] depends on: #37901 - [x] depends on: #38002 - [x] depends on: #41317 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebraic-geometry 202/18 Mathlib.lean,Mathlib/AlgebraicGeometry/AlgebraicCycle/Basic.lean,Mathlib/AlgebraicGeometry/AlgebraicCycle/Principal.lean,Mathlib/AlgebraicGeometry/Noetherian.lean,Mathlib/AlgebraicGeometry/OrderOfVanishing/Basic.lean,Mathlib/Topology/LocallyFinsupp.lean 6 20 ['Brian-Nugent', 'Raph-DG', 'github-actions', 'joelriou', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] joelriou
assignee:joelriou
10-67918
10 days ago
10-68396
10 days ago
68-24357
68 days
1
45489 j-loreaux
author:j-loreaux
feat: star-orthogonality and the continuous functional calculus If `a ⋆⟂ c`, then `cfc f a ⋆⟂ c` for any `f` with `f 0 = 0` which is continuous on the spectrum of `a`. --- - [x] depends on: #45485 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 114/0 Mathlib.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Orthogonal.lean 2 6 ['github-actions', 'j-loreaux', 'mathlib-dependent-issues', 'themathqueen'] nobody
10-67214
10 days ago
10-73843
10 days ago
10-74071
10 days
0
42023 lakesare
author:lakesare
feat(Topology/Instances/AddCircle/Defs): add liftIco_coe_apply_of_periodic, liftIoc_coe_apply_of_periodic (5 more lemmas) **Upstreaming from Carleson: [/Carleson/ToMathlib/Topology/Instances/AddCircle/Defs.lean](https://github.com/fpvandoorn/carleson/blob/master/Carleson/ToMathlib/Topology/Instances/AddCircle/Defs.lean)** ___ ### Changes from carleson - **liftIco_coe_apply_of_periodic**, **liftIoc_coe_apply_of_periodic** - refactor ### Note There is a comment in the Carleson file suggesting renaming `liftIco_coe_apply_of_periodic`, `liftIoc_coe_apply_of_periodic`, `liftIco_coe_apply`, and `liftIoc_coe_apply` together ([here](https://github.com/fpvandoorn/carleson/blob/master/Carleson/ToMathlib/Topology/Instances/AddCircle/Defs.lean#L27)), but the intended names are not specified. In my mind the names are already fine, so I didn't change them. carleson t-topology 34/0 Mathlib/Topology/Instances/AddCircle/Defs.lean 1 10 ['github-actions', 'j-loreaux', 'lakesare', 'mathlib-bors', 'themathqueen'] nobody
10-56196
10 days ago
10-57612
10 days ago
52-56701
52 days
0
42670 harahu
author:harahu
chore(Combinatorics): tidy markdown headers Ensure files in `Mathlib/Combinatorics` have one and only one H1 header, thus enforcing the style guide. Newly created headers in this PR were authored by Claude Opus 5. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 11/5 Mathlib/Combinatorics/Enumerative/Catalan/Tree.lean,Mathlib/Combinatorics/Quiver/ConnectedComponent.lean,Mathlib/Combinatorics/Quiver/Subquiver.lean,Mathlib/Combinatorics/Quiver/Symmetric.lean,Mathlib/Combinatorics/SimpleGraph/Cayley.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/Connected.lean 6 1 ['Multramate', 'github-actions'] b-mehta
assignee:b-mehta
10-51249
10 days ago
102-19356
102 days ago
102-20864
102 days
0
42718 justinhalford
author:justinhalford
feat(Combinatorics/SetFamily): the linear algebra method and the Oddtown theorem Adds the basic form of the **linear algebra method** for set families (Babai–Frankl) together with its standard first application, the **Oddtown theorem** (Berlekamp, 1969). ### What's here - `linearIndependent_of_dotProduct_eq_ite` — a family of vectors whose pairwise dot products form the identity matrix is linearly independent. Stated over an arbitrary field, so it does not rely on positivity; this is the engine of the method. - `Finset.charVec` — the characteristic vector of a finset, valued in a semiring, with `charVec_apply`. - `Finset.charVec_dotProduct_charVec` — the dot product of two characteristic vectors is the cardinality of the intersection. - `Finset.card_le_card_of_odd_card_of_even_card_inter` — **Oddtown**: a family of finsets of odd cardinality, any two of which meet in an even number of elements, has at most `Fintype.card α` members. ### Why I could not find the linear algebra method anywhere in Mathlib. Searching for `Oddtown`, `Eventown`, Fisher's inequality, `RayChaudhuri` and `FranklWilson` returns nothing, and exactly one file under `Mathlib/Combinatorics/` uses `finrank`/`LinearIndependent` (`SimpleGraph/LapMatrix.lean`, for spectral graph theory). Since the technique underlies a large family of extremal results, the general lemma is stated separately from Oddtown so that Eventown, Fisher's inequality and Ray-Chaudhuri–Wilson can be added on top later. If this does already exist under a formulation I did not think to search for, I would be glad to be pointed at it. ### Verification Compiles against `master` (Lean 4.34.0-rc1) with no errors or warnings. `#print axioms` on each of the three results reports only `[propext, Classical.choice, Quot.sound]`. No `sorry`, no new axioms, no `set_option` overrides. ### Disclosure This file was written with AI assistance (Claude Opus 5) and then checked against the Lean kernel; that is noted in the module docstring as well. Every statement, proof and docstring has been read through by me before submission. Happy to adjust naming, generality or placement to whatever the maintainers prefer. ### Process note I am a first-time contributor and I am aware the usual convention is to raise a new file on Zulip before opening a PR. Apologies for going in the other order — I am glad to move the discussion to `#mathlib4` if that is preferred, or to close this if the material is not wanted. --- [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/leanprover-community/mathlib4) t-combinatorics new-contributor 144/0 Mathlib.lean,Mathlib/Combinatorics/SetFamily/Oddtown.lean 2 3 ['D-Thomine', 'github-actions'] b-mehta
assignee:b-mehta
10-51248
10 days ago
101-18505
101 days ago
101-18450
101 days
0
43205 wwylele
author:wwylele
feat(FieldTheory): extension is separable if its degree is less than the positive char This is a series of lemma analog to the existing CharZero lemma - `Polynomial.mem_support_derivative` -> `Polynomial.mem_support_derivative_of_isSMulRegular` (I used SMulRegular as this seems to be the right spelling for Semiring) - `Polynomial.degree_derivative` -> `Polynomial.degree_derivative_of_isSMulRegular` - `Polynomial.natDegree_derivative` -> `Polynomial.natDegree_derivative_of_isSMulRegular` - `Irreducible.separable` -> `Irreducible.separable_of_natCast_natDegree_ne_zero` - `IsSeparable.of_integral` -> `IsSeparable.of_integral_of_natCast_natDegree_ne_zero` - `Algebra.IsSeparable.of_integral` -> `Algebra.IsSeparable.of_integral_of_finrank_lt` & `Algebra.IsSeparable.of_integral_of_rank_lt` --- From https://github.com/wwylele/Compass <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
87/24 Mathlib/Algebra/Polynomial/Derivative.lean,Mathlib/FieldTheory/Separable.lean,Mathlib/LinearAlgebra/Dimension/Finite.lean 3 19 ['artie2000', 'copilot-pull-request-reviewer', 'github-actions', 'mathlib-merge-conflicts', 'wwylele'] mattrobball
assignee:mattrobball
10-51245
10 days ago
43-56994
43 days ago
84-53383
84 days
0
45214 YaelDillies
author:YaelDillies
feat(MeasureTheory): measurable group hom from locally compact to separable is continuous In fact null-measurable according to the inner) regular Haar measure is enough. This completes the existing result that a measurable group hom from a locally compact group to a normed space is continuous. Note that the existing mathlib statement assumed that the domain was normed, but I could remove this easily. Also note that neither result implies the other. There are other results of this form, see e.g. Kleppner, Adam, Measurable homomorphisms of locally compact groups. Proc. Amer. Math. Soc. 106 (1989), no. 2, 391–395. It unfortunately has heavier prerequisites, so I did not formalise it. My motivation is to show that a measurable unitary representation of a locally compact group is automatically continuous. The existing automatic continuity statement doesn't apply in this situation since the codomain, ie the space of unitary matrices of some dimension, isn't a normed space (it isn't even additive). From MeanFourier Generated by Claude Sonnet/Opus in many iterations as I was trying to find the greatest easily achievable generality. Assisted-by: Claude Sonnet 5.5 Assisted-by: Claude Opus 5.5 --- - [x] depends on: #45174 LLM-generated t-measure-probability 117/23 Mathlib/Analysis/Normed/Module/Basic.lean,Mathlib/MeasureTheory/Measure/Haar/Basic.lean,Mathlib/MeasureTheory/Measure/Haar/NormedSpace.lean 3 2 ['github-actions', 'mathlib-dependent-issues'] RemyDegenne
assignee:RemyDegenne
10-51241
10 days ago
11-54692
11 days ago
11-54656
11 days
0
41728 vaca22
author:vaca22
feat(GroupTheory): prove uniqueness of ℤᵐ⁰ automorphisms Prove that every order-preserving multiplicative automorphism of ℤᵐ⁰ is the identity. This also gives a Unique instance for its automorphism type and a Subsingleton instance for order-preserving multiplicative normalizations from G to ℤᵐ⁰. The proof transports an automorphism through WithZero.exp and WithZero.log to an additive automorphism of ℤ, then excludes negation by monotonicity. ------------ **AI disclosure**: this PR is primarily LLM-generated (Claude Code). t-group-theory new-contributor LLM-generated 58/0 Mathlib/GroupTheory/ArchimedeanDensely.lean 1 16 ['github-actions', 'grunweg', 'tb65536', 'vaca22', 'wwylele'] nobody
10-50356
10 days ago
77-85649
77 days ago
92-43736
92 days
0
43045 plp127
author:plp127
feat: `Dyadic` is a localization Prove that `Dyadic` is a localization of the integers generated by inverting `2`. --- - [x] depends on: #43038 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data tech debt 97/0 Mathlib.lean,Mathlib/Data/Dyadic/IsLocalization.lean 2 13 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'metakunt', 'plp127', 'vihdzp'] nobody
10-43065
10 days ago
11-73288
11 days ago
11-73560
11 days
0
42629 SnirBroshi
author:SnirBroshi
feat(Order/RelSeries): `FiniteDimensionalOrder` implies `WellFoundedLT` and `WellFoundedGT` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 11/0 Mathlib/Order/RelSeries.lean 1 13 ['Komyyy', 'SnirBroshi', 'github-actions', 'leanprover-radar', 'plp127', 'vihdzp'] Komyyy
assignee:Komyyy
10-39417
10 days ago
10-40813
10 days ago
102-36636
102 days
0
42815 korbonits
author:korbonits
feat(Analysis/Calculus/VectorField): the Lie bracket acts as a derivation on functions Add `VectorField.lieBracket_apply_fun`: for a function `f` with derivative `f'` and vector fields `V`, `W`, D(f' W) V - D(f' V) W = f' [V, W] i.e. the familiar `[V, W] f = V (W f) - W (V f)`. The two second-derivative terms cancel by symmetry of the second derivative, leaving exactly the bracket. Placed beside the existing `lieBracket_smul_*` product rules. Needs no new import: `FDeriv.Symmetric` is already imported for `second_derivative_symmetric`, which supplies the symmetry and is the source of the `IsRCLikeNormedField` hypothesis. --- AI disclosure - level: Level 5 / Level 6 in [the link shared](https://www.visidata.org/blog/2026/ai/#self-assessed-ai-level-for-contributions) I feel confident about the math but I am still learning Lean itself - code: most of the Lean in this PR was drafted by Claude Code (statements, proofs, docstrings). - direction and review: I chose the contribution, made the decisions, reviewed every line, and wrote all GitHub/Zulip comments. t-analysis new-contributor LLM-generated t-differential-geometry 17/0 Mathlib/Analysis/Calculus/VectorField.lean 1 12 ['github-actions', 'korbonits', 'themathqueen'] nobody
10-37068
10 days ago
57-83532
57 days ago
98-28189
98 days
0
45824 vihdzp
author:vihdzp
refactor: deprecate `IsOrderConnected` The typeclass describes itself as an intuitionistic substitute of `IsTrans`. But Mathlib is not intuitionistic, so we might as well just use that instead. This also avoids confusion with `Set.OrdConnected`, which is unrelated. See [Zulip](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/IsOrderConnected/with/637402302). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 18/6 Mathlib/Data/List/Lex.lean,Mathlib/Order/RelClasses.lean 2 2 ['github-actions', 'plp127'] nobody
10-23991
10 days ago
10-26258
10 days ago
10-80042
10 days
0
43770 vlad902
author:vlad902
feat(AffineSpace/FiniteDimensional): generalize typeclasses A number of theorems/instances are stated at the top of the file for `DivisionRing`, but the assumption could be weakened to `Ring` with some theorems further requiring `Nontrivial`/`StrongRankCondition`/`OrzechProperty`. Weakening to `Ring` also requires renaming some `FiniteDimensional` assumptions to `Module.Finite`. This PR weakens moves around some theorems/instances to fit their new sections assumptions and renames some theorems/instances to match their new conclusions. No theorems are added/removed. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
183/125 Mathlib/LinearAlgebra/AffineSpace/FiniteDimensional.lean 1 8 ['github-actions', 'grunweg', 'leanprover-radar', 'mathlib-merge-conflicts', 'vlad902'] nobody
10-21322
10 days ago
10-21859
10 days ago
68-63470
68 days
0
45933 vihdzp
author:vihdzp
chore: deduplicate `IsSuccLimit` lemmas on `Cardinal` and `Ordinal` ...by reproving them for `IsBotZeroClass`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory 94/47 Mathlib/Algebra/Order/SuccPred.lean,Mathlib/Order/SuccPred/Limit.lean,Mathlib/SetTheory/Cardinal/Aleph.lean,Mathlib/SetTheory/Cardinal/Basic.lean,Mathlib/SetTheory/Cardinal/Cofinality/Ordinal.lean,Mathlib/SetTheory/Cardinal/Order.lean,Mathlib/SetTheory/Cardinal/Regular.lean,Mathlib/SetTheory/Ordinal/Arithmetic.lean,Mathlib/SetTheory/Ordinal/Exponential.lean,Mathlib/SetTheory/Ordinal/Principal.lean 10 1 ['github-actions'] nobody
10-13229
10 days ago
10-16409
10 days ago
10-16354
10 days
0
45938 IvanRenison
author:IvanRenison
feat(Control): define `liftA2` --- Zulip discussion: https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/liftA2/with/639419181 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 8/0 Mathlib/Control/Basic.lean 1 4 ['IvanRenison', 'github-actions', 'vihdzp'] nobody
10-701
10 days ago
10-4621
10 days ago
10-6798
10 days
0
45426 tb65536
author:tb65536
chore(RingTheory/DedekindDomain/AdicValuation/Ramification): remove usage of Ideal.ramificationIdx' This PR removes usages of `Ideal.ramificationIdx'` from `RingTheory/DedekindDomain/AdicValuation/Ramification`, preparing the way for the eventual deprecation of `Ideal.ramificationIdx'`. The generalization `multiplicity_map_eq_mul` was suggested by AI. It looks a bit strange, but is exactly what's needed here, and I couldn't find a cleaner generalization. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory t-algebra
label:t-algebra$
38/5 Mathlib/RingTheory/DedekindDomain/AdicValuation/Ramification.lean,Mathlib/RingTheory/DiscreteValuationRing/Basic.lean,Mathlib/RingTheory/Multiplicity.lean,Mathlib/RingTheory/RamificationInertia/Ramification.lean 4 1 ['github-actions'] riccardobrasca
assignee:riccardobrasca
10-456
10 days ago
24-76268
24 days ago
24-76215
24 days
0
45947 alainchmt
author:alainchmt
feat(FieldTheory/Finite): add Rabin's polynomial irreducibility test This PR adds Rabin's irreducibility test: a polynomial `f` of degree `n > 0` over a finite field of cardinality `q` is irreducible if and only if `f` divides `X ^ q ^ n - X` and `f` is coprime to `X ^ q ^ (n / p) - X` for every prime `p` dividing `n`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra new-contributor
label:t-algebra$
15/0 Mathlib/FieldTheory/Finite/Extension.lean 1 2 ['github-actions'] nobody
9-81242
9 days ago
9-85472
9 days ago
9-85417
9 days
0
44139 Nicola9Falciola
author:Nicola9Falciola
refactor(LinearAlgebra/Matrix/Transvection): generalize the pivot elimination step to commutative rings --- The elimination steps in the pivot algorithm in `Matrix.Pivot` reduce to a diagonal block the last row of a matrix using transvections only need the last diagonal coefficient to be a unit over the base ring not that the ring itself is field. This PR generalizes this step to work over a commutative ring `R` instead of a field. I also add the following API : - `listTransvecCol_mul_mul_listTransvecRow_last_diag`: the elimination does not change the last diagonal coefficient - `exists_isTwoBlockDiagonal_and_last_eq_of_isUnit` <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra LLM-generated
label:t-algebra$
130/108 Mathlib/LinearAlgebra/Matrix/Transvection.lean 1 3 ['Nicola9Falciola', 'github-actions', 'mathlib-merge-conflicts'] nobody
9-74084
9 days ago
26-19881
26 days ago
59-32661
59 days
1
45955 sgouezel
author:sgouezel
feat: with high probability, a measurable function takes its values in a compact subset --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability 88/0 Mathlib.lean,Mathlib/MeasureTheory/Function/AlmostCompactRange.lean 2 1 ['github-actions'] nobody
9-70083
9 days ago
9-70541
9 days ago
9-70486
9 days
1
36086 Multramate
author:Multramate
feat(Algebra): add liftEquiv for groups, rings, algebras, and adjoin roots --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
49/1 Mathlib/Algebra/Polynomial/Bivariate.lean,Mathlib/GroupTheory/QuotientGroup/Defs.lean,Mathlib/RingTheory/AdjoinRoot.lean,Mathlib/RingTheory/Ideal/Quotient/Operations.lean 4 10 ['CBirkbeck', 'Multramate', 'artie2000', 'dagurtomas', 'github-actions', 'mathlib-merge-conflicts'] mattrobball
assignee:mattrobball
9-51256
9 days ago
66-81175
66 days ago
82-12740
82 days
1
43258 ScottCarnahan
author:ScottCarnahan
feat(Algebra/MonoidAlgebra/PointwiseSMul): add smulAntidiagonal and API Given actions of `R` on `V` and `G` on `P`, the `smulAntidiagonal` of `f : MonoidAlgebra R G` and `x : P → V` at `p : P` is the finset in `G × P` whose elements scalar-multiply to `p` and whose components lie in the support of `f` and `x`. This PR defines the `smulAntidiagonal` and shows that convolutional scalar multiplication coincides with monoid algebra multiplication when `V = R` and `P = G`. --- [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
49/0 Mathlib/Algebra/MonoidAlgebra/PointwiseSMul.lean 1 1 ['github-actions'] mattrobball
assignee:mattrobball
9-51252
9 days ago
83-6773
83 days ago
83-6718
83 days
0
43042 grunweg
author:grunweg
feat: `ContMDiff.clm_bundle_of_apply` and friends Future PRs will add versions of these allowing for the loss of derivatives: let's start with these versions as the required modifications are straight-forward. We add the analogous lemmas for differentiability also (and comment when this requires further work out of this PR's scope). From the path towards smoothness of the Levi-Civita connection and Riemannian geometry. Co-authored-by: Patrick Massot <patrickmassot@free.fr> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-differential-geometry 137/2 Mathlib/Geometry/Manifold/VectorBundle/Hom.lean 1 4 ['github-actions', 'grunweg', 'mathlib-merge-conflicts'] nobody
9-50356
9 days ago
43-64230
43 days ago
91-57834
91 days
1
45969 wwylele
author:wwylele
fix(MeasureTheory): correct namespace of NullMeasurableSet.const_smul The previous name was "MeasureTheory. **Measure.** NullMeasurableSet.const_smu". The "Measure." part looks accidentally from the surrounding namespace. This prohibited dot notation There was also a note on top of this lemma. I chose to preserve it as it tells a more complicated story yet to fix: the `NullMeasurableSet` counterpart of `MeasurableSet.const_smul` has already entered Mathlib as `NullMeasurableSet.smul`. Meanwhile, the `MeasurableSet` counterpart of `NullMeasurableSet.const_smul` is `MeasurableSet.const_smul₀` with a vast generalization. The potential generalization of `NullMeasurableSet.const_smul` needs to take a hypothesis `(hμ : ∀ a : G₀, a ≠ 0 → QuasiMeasurePreserving (a • ·) μ μ)`, so that new lemma probably deserves the name `NullMeasurableSet.const_smul₀`. --- AI usage disclosure: this was motivated by findings from when I was using Claude to golf a downstream project. All code written here was manual by me <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> easy t-measure-probability 5/1 Mathlib/MeasureTheory/Measure/Lebesgue/EqHaar.lean 1 2 ['github-actions', 'wwylele'] nobody
9-41902
9 days ago
9-42482
9 days ago
9-42427
9 days
0
45971 WaterKing201030
author:WaterKing201030
feat(GroupTheory/Perm/Cycle/Basic): add some lemmas for Perm.SameCycle Add following lemmas: - `sameCycle_apply_left/right_self`: Inspired by `EqvGen.rel` - `SameCycle.map(_of_apply)`: Inspired by and generalized `SameCycle.conj` - `SameCycle.eq_of_invariant`: A function invariant under a permutation is constant on each cycle of permutation. - `sameCycle_iff_eqvGen`: `SameCycle` is equivalent to the equivalence closure of relation generated by the permutation. These simple lemmas appeared many times in proofs generated with AI assistance during my formalization work. I believe they are worth turning into an API. Therefore, I manually wrote the definitions and proofs for these lemmas. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-group-theory new-contributor 62/0 Mathlib/GroupTheory/Perm/Cycle/Basic.lean 1 2 ['github-actions'] nobody
9-22594
9 days ago
9-24562
9 days ago
9-24507
9 days
0
45945 WenrongZou
author:WenrongZou
chore(MeasureTheory/ContinuousMapDense): drop `NormalSpace` assumption Drop the `[NormalSpace α]` assumption from the four results on approximation in `ℒp` by compactly supported continuous functions (`MemLp.exists_hasCompactSupport_eLpNorm_sub_le` and its three variants). This theorem need `[RegularSpace α]`, which follows from `[WeaklyLocallyCompactSpace α]` and `[R1Space α]`. Since `μ` is regular, it suffices to separate a compact set from the complement of an open neighbourhood, which is [`exists_continuous_one_zero_of_isCompact`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Topology/UrysohnsLemma.html#exists_continuous_one_zero_of_isCompact) and needs no normality. The proof now uses this lemma directly instead of `exists_continuous_eLpNorm_sub_le_of_closed`. --- The bounded continuous versions still need `NormalSpace`: they are false without it. 🤖 Generated with [Claude Code](https://claude.com/claude-code). I reviewed it carefully. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated t-measure-probability 38/43 Mathlib/MeasureTheory/Function/ContinuousMapDense.lean 1 1 ['github-actions'] nobody
9-15443
9 days ago
10-172
10 days ago
10-117
10 days
1
37953 Thmoas-Guan
author:Thmoas-Guan
feat(RingTheory/Smooth): transcendental separable extension is formally smooth In this PR, we proved that transcendental separable extension is formally smooth via reduction to fg cases. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #37934 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 141/3 Mathlib/RingTheory/Smooth/Field.lean 1 4 ['Thmoas-Guan', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
9-12776
9 days ago
42-4256
42 days ago
76-68414
76 days
3
26216 Thmoas-Guan
author:Thmoas-Guan
feat(Algebra): depth of QuotSMulTop In this PR, we proved for a local ring `R` and a finitely generated `R` module `M N`, `IsSMulRegular M x` and `x ∈ Module.annihilator R N`, then `depth(N, M/xM) + 1 = depth(N, M)`, and its corollary for quotient regular seqence. --- <!-- The text above the `---` will become the commit message when your PR is merged. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. To indicate co-authors, include lines at the bottom of the commit message (that is, before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (that is, before the `---`) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #26214 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
260/0 Mathlib/RingTheory/Depth/Basic.lean 1 12 ['Thmoas-Guan', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mathlib4-merge-conflict-bot'] nobody
9-5831
9 days ago
9-6533
9 days ago
33-29018
33 days
15
41940 mcdoll
author:mcdoll
chore(Dynamics): deprecate `IsForwardInvariant` in favour of new `Set.IsInvariantOn` We define a predicate `Set.IsInvariantOn` that generalizes `IsInvariant` and as a special case contains `IsForwardInvariant`. The later is hence removed. We also move `IsInvariant` into the `Set` namespace to allow for dot-notation. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-dynamics dynsys 52/18 Mathlib/Dynamics/Flow.lean,Mathlib/Dynamics/OmegaLimit.lean 2 7 ['github-actions', 'mathlib-merge-conflicts', 'mcdoll', 'sgouezel'] nobody
8-82625
8 days ago
11-40909
11 days ago
107-49436
107 days
0
43464 gasparattila
author:gasparattila
fix(LinearAlgebra/Projectivization/Subspace): fix non-defeq `Min` instances The `CompleteLattice` instance of `Projectivization.Subspace` is currently defined using `completeLatticeOfInf`, which conflicts with the `Min` instance defined earlier. This PR fixes this by overriding the `inf` field. To avoid possible issues with `⊥` and `⊤`, they are also redefined to have good defeqs. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
17/20 Mathlib/LinearAlgebra/Projectivization/Subspace.lean 1 4 ['artie2000', 'gasparattila', 'github-actions'] nobody
8-80847
8 days ago
78-8574
78 days ago
78-8519
78 days
0
34716 CoolRmal
author:CoolRmal
feat(Probability): one-sided continuous strongly adapted processes are strongly progressive A strongly adapted process with right-continuous or left-continuous paths is strongly progressive, for any second-countable linearly ordered index type with the order topology. Both results use `OpensMeasurableSpace` on the time index and `PseudoMetrizableSpace` on the target. The proof uses simple-function approximations of time. Each approximating process is jointly strongly measurable by `stronglyMeasurable_uncurry_of_countable`; pathwise one-sided continuity then gives the pointwise limit. Main results: * `StronglyAdapted.isStronglyProgressive_of_isRightContinuous`. * `StronglyAdapted.isStronglyProgressive_of_isLeftContinuous`, with no bottom-element assumption on time. * `SimpleFunc.exists_seq_monotone_le_tendsto` and `SimpleFunc.exists_seq_monotone_ge_tendsto`: monotone simple-function approximations from above on an order with a top element, and from below on an order with a bottom element. These replace the unbundled `exists_seq_monotone_finite_range_le_tendsto` statement and live in `SimpleFuncDense.lean`. * `SimpleFunc.exists_seq_tendsto_nhdsLE`: simple-function approximations converging from below eventually on any nonempty second-countable linear order. An extra endpoint handles orders without a bottom; convergence ensures that the approximations eventually avoid it. This supplies the left-continuous proof on `Iic t`. The two independent prerequisites provide the countable uncurry lemma and the monotone/antitone finite-range simple-function constructors. The existing dependency #42164 supplies the countable one-sided dense subsets. Validation: targeted builds of `SimpleFunc`, `SimpleFuncDense`, `StronglyMeasurable.Basic`, and `Probability.Process.Adapted`; text-style checks; axiom checks for the new declarations. AI assistance: original work with Claude Code; this refactor and the left-continuous extension with Codex. - [x] depends on: #42164 - [x] depends on: #45492 - [x] depends on: #45493 brownian t-measure-probability LLM-generated 116/1 Mathlib/MeasureTheory/Function/SimpleFuncDense.lean,Mathlib/Probability/Process/Adapted.lean 2 8 ['CoolRmal', 'github-actions', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
8-76557
8 days ago
8-77249
8 days ago
8-79080
8 days
0
46000 plp127
author:plp127
feat(Topology/Algebra/IsUniformGroup): a uniform group is uniformly discrete iff it is topologically discrete Prove two theorems `IsLeftUniformGroup.discreteUniformity_iff` and `IsRightUniformGroup.discreteUniformity_iff` and their additive versions which say a uniform group is discrete as a uniform space iff it is discrete as a topological space. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology 16/0 Mathlib/Topology/Algebra/IsUniformGroup/Constructions.lean 1 1 ['github-actions'] nobody
8-65010
8 days ago
8-65974
8 days ago
8-65919
8 days
1
42353 sankalpsthakur
author:sankalpsthakur
feat(RingTheory): add nilpotence lemmas for zero sums In a semiring, adds: - `sq_eq_sq_of_add_eq_zero`: if `x + y = 0` then `x^2 = y^2` - `IsNilpotent.of_add_eq_zero_left`: if `x + y = 0` and `y` is nilpotent, so is `x` - `isNilpotent_iff_of_add_eq_zero`: under `x + y = 0`, `x` is nilpotent iff `y` is Motivated by #10539. --- ### Validation Built locally: `lake build Mathlib.RingTheory.Nilpotent.Basic` succeeds. ### AI/LLM disclosure AI coding tools were used to help draft this change and PR description. I reviewed the complete change, understand the reasoning, and verified the build locally before submitting. t-ring-theory new-contributor LLM-generated 51/0 Mathlib/RingTheory/Nilpotent/Basic.lean 1 33 ['artie2000', 'github-actions', 'sankalpsthakur', 'tb65536'] mattrobball
assignee:mattrobball
8-62937
8 days ago
8-64214
8 days ago
94-21215
94 days
0
41347 mkaratarakis
author:mkaratarakis
feat(Tactic/Polynomial): poly_dvd_cert, certificate-based polynomial divisibility The `poly_dvd_cert` tactic: prove `p ∣ q` for `Polynomial K` polyrith-style - search the quotient uncertified in compiled `MetaM` (pseudo-division, so the certified identity is division-free), then verify with `ring` and cancel the leading-coefficient unit. Works over any field with concrete or symbolic coefficients, for monic divisors over any commutative ring, and for unit leading coefficients. t-meta LLM-generated 303/0 Mathlib.lean,Mathlib/Tactic.lean,Mathlib/Tactic/ComputablePolynomial/DvdCert.lean,MathlibTest/ComputablePolynomial/PolyDvdCert.lean 4 8 ['JovanGerb', 'eric-wieser', 'github-actions', 'mkaratarakis'] Vierkantor
assignee:Vierkantor
8-51256
8 days ago
58-76021
58 days ago
119-46231
119 days
0
42165 bocowgill
author:bocowgill
feat(Probability/HasCondDistrib): characterize independence using conditional distributions This PR uses conditional distributions to characterize independence of two random variables. It adds eight public declarations to `Mathlib/Probability/HasCondDistrib.lean`, which is the only file modified: - `indepFun_iff_hasCondDistrib_const_of_hasLaw`: characterizes independence using a constant conditional-distribution kernel when the laws are specified. - `indepFun_iff_hasCondDistrib_const`: specializes this characterization to the marginal laws `P.map X` and `P.map Y`. - `IndepFun.hasCondDistrib_const`: the forward implication of the preceding equivalence. - `HasCondDistrib.indepFun_of_const`: the reverse implication. - `hasCondDistrib_condDistrib`: shows that the regular conditional distribution `condDistrib Y X P` satisfies `HasCondDistrib`. - `hasCondDistrib_iff_condDistrib_ae_eq`: characterizes finite kernels satisfying `HasCondDistrib` by almost-everywhere equality with `condDistrib`. - `indepFun_iff_condDistrib_ae_eq_const_of_hasLaw`: characterizes independence by almost-everywhere equality of `condDistrib` with the constant kernel at the specified law. - `indepFun_iff_condDistrib_ae_eq_const`: specializes this characterization to the marginal laws. The PR adds no new file and makes no change to the root `Mathlib.lean` imports. --- ### Motivation These results provide a basic building block for formalizing randomized experiments and causal identification. The main result provides a starting point for later ignorability and conditional-independence results in causal inference. ### LLM disclosure For theorem planning and Lean implementation, I substantially used Codex by OpenAI. I also used it for suggestions around naming and documentation, for iterating on the proofs, and for validating my commits locally. I manually searched for the best locations and earlier results to build upon. I personally reviewed both the mathematical statements and Lean code (line-by-line), as well as the suggestions around naming and API choices. I also reviewed and confirmed that I can explain each step of the results (both Mathematics and Lean syntax). To validate the change, I directly compiled the modified file and ran a targeted build. I also ran the style linter, and completed a full `lake build` and a full `lake test`. Please note: This is one of my first mathlib contributions. I welcome corrections or suggestions about all aspects of this PR. I'm prepared to revise it as necessary, and to learn from the review. t-measure-probability LLM-generated new-contributor large-import 63/3 Mathlib/Probability/HasCondDistrib.lean 1 43 ['CoolRmal', 'EtienneC30', 'bocowgill', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] RemyDegenne
assignee:RemyDegenne
8-51255
8 days ago
11-71932
11 days ago
85-18707
85 days
0
45221 Nicola9Falciola
author:Nicola9Falciola
feat(Algebra/Algebra/Subalgebra/Basic): `Algebra R (p.compatibleMaps p)` and `Module.End.restrictAlgHom` --- This PR resolves TODO in `Algebra/Module/Submodule/LinearMap` (line 242). It adds : - API lemmas for `compatibleMaps`. - The `SemiRing` and `Algebra` instances for `q.compatibleMaps.q` and relative API. - The `AlgHom` version of `LinearMap.restric` and relative API. - Fixes the docstring of `Submodule.compatibleMaps`, which referred to the wrong variable names and said "ring" instead of "semiring". <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
53/1 Mathlib/Algebra/Algebra/Subalgebra/Basic.lean,Mathlib/Algebra/Module/Submodule/LinearMap.lean 2 13 ['Nicola9Falciola', 'github-actions', 'mathlib-splicebot', 'ocfnash'] nobody
8-50356
8 days ago
29-80436
29 days ago
29-81985
29 days
0
44269 ROTARTSI82
author:ROTARTSI82
feat(Dynamics): periodic orbits must jump up and down If x is a periodic point and not a fixed point, there exists some b in its periodic orbit such that b < f b, and some b' such that f b' < b'. --- This change was motivated by the following proof, a special case of Sharkovskii's theorem: ```lean theorem exists_isFixedPt_of_continuous_of_mem_periodicPts' {α : Type*} [ConditionallyCompleteLinearOrder α] [TopologicalSpace α] [OrderTopology α] [DenselyOrdered α] {f : α → α} {x₀ : α} (hx₀ : x₀ ∈ periodicPts f) (hf : Continuous f) : ∃(c : α), IsFixedPt f c := by by_cases hfixed : IsFixedPt f x₀ · exact ⟨x₀, hfixed⟩ obtain ⟨a, _, ha⟩ := exists_lt_map_of_mem_periodicPts hx₀ hfixed obtain ⟨b, _, hb⟩ := exists_map_lt_of_mem_periodicPts hx₀ hfixed obtain ⟨c, _, hc⟩ := exists_mem_uIcc_isFixedPt hf.continuousOn ha.le hb.le exact ⟨c, hc⟩ ``` Would this theorem itself or something similar be wanted in mathlib? <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor t-dynamics 39/0 Mathlib/Dynamics/PeriodicPts/Lemmas.lean,Mathlib/Order/Monotone/Basic.lean 2 7 ['ROTARTSI82', 'github-actions', 'sgouezel'] sgouezel
assignee:sgouezel
8-44845
8 days ago
8-44845
8 days ago
55-661
55 days
0
45076 vdelbarc
author:vdelbarc
feat(Algebra/Lie/SemiDirect): add natural ideal and subalgebra; add equivalences Define the left ideal and right subalgebra of a semidirect product of Lie algebras. Give characterizations through natural inclusion/projection maps. Co-authored-by: Gustavo Infanti <g246337@dac.unicamp.br> Co-authored-by: Exequiel Rivas <exequiel.rivas@taltech.ee> Co-authored-by: Paul Schwahn <pschwahn@uni-muenster.de> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor t-algebra
label:t-algebra$
88/0 Mathlib/Algebra/Lie/SemiDirect.lean 1 2 ['github-actions'] nobody
8-24932
8 days ago
33-17369
33 days ago
33-17976
33 days
0
45608 vdelbarc
author:vdelbarc
feat(Algebra/Algebra): add ideals and quotients for non-unital non-associative algebras Introduce `NonUnitalNonAssocAlgebra.TwoSidedIdeal R A` as an `R`-submodule closed under multiplication by arbitrary elements of `A` on either side. This provides scalar-closed ideals for quotient constructions in non-unital, non-associative algebras. Add basic lemmas, together with a forgetful map to the existing ring-theoretic `TwoSidedIdeal A`. Construct the quotient `A ⧸ I` using the underlying submodule quotient. Equip it with non-unital, non-associative ring and module structures, and provide the quotient map as a non-unital algebra homomorphism, computation lemmas, and an induction principle. Show that `SMulCommClass R A A` and `IsScalarTower R A A`, when available, descend to the quotient. Co-authored-by: Gustavo Infanti <g246337@dac.unicamp.br> Co-authored-by: Exequiel Rivas <exequiel.rivas@taltech.ee> Co-authored-by: Paul Schwahn <pschwahn@uni-muenster.de> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra new-contributor
label:t-algebra$
262/0 Mathlib.lean,Mathlib/Algebra/Algebra/NonUnitalIdeal.lean 2 2 ['github-actions'] nobody
8-24892
8 days ago
19-15975
19 days ago
19-17247
19 days
0
45610 vdelbarc
author:vdelbarc
feat(Algebra/Algebra/Leibniz): introduce Leibniz rings and algebras Introduce the basic theory of right Leibniz rings and algebras. Define `IsLeibniz` by the identity `(x * y) * z = (x * z) * y + x * (y * z)`, and establish its basic consequences. Design choices were briefly discussed in https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Leibniz.20algebras/near/611073252 Define `IsSkew` for multiplication satisfying `x * x = 0`. Construct Lie ring and Lie algebra structures on Leibniz rings and algebras satisfying this condition. Conversely, show that every Lie ring satisfies the right Leibniz identity when its bracket is used as multiplication. More on two-sided ideals and quotients of Leibniz algebras to come after PR#45608 is merged, from which this PR is independent now. Co-authored-by: Gustavo Infanti <g246337@dac.unicamp.br> Co-authored-by: Exequiel Rivas <exequiel.rivas@taltech.ee> Co-authored-by: Paul Schwahn <pschwahn@uni-muenster.de> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra new-contributor
label:t-algebra$
218/0 Mathlib.lean,Mathlib/Algebra/Algebra/Leibniz/Basic.lean 2 7 ['Julian-Kuelshammer', 'github-actions'] nobody
8-24263
8 days ago
19-15447
19 days ago
19-15392
19 days
0
45944 rytjy
author:rytjy
feat(Probability): wilson score interval Adds the Wilson score interval for a binomial proportion: centre, half-width, endpoints, and the facts that the centre lies in [0, 1] and that the sample proportion always lies inside the interval. This is a small, self-contained start on a gap noted while using the interval: mathlib4 has no confidence-interval / Wilson-score notion. Main results: `wilsonCenter_mem_Icc`, `wilsonLo_le_wilsonHi`, `wilsonHi_nonneg`, `wilsonLo_le_one`, `wilson_contains`. Opened as a draft: happy to reshape the statement, add one-sided bounds, or move it under a different namespace after review. t-measure-probability new-contributor 245/0 Mathlib.lean,Mathlib/Probability/WilsonInterval.lean 2 4 ['github-actions', 'rytjy'] nobody
8-20699
8 days ago
9-12587
9 days ago
9-12532
9 days
0
45554 Thmoas-Guan
author:Thmoas-Guan
feat(Data/ENat): more lemma for WithBot ENat We plan to add more lemmas into this separate file, instead of only adding it in `ENat.Basic`. There would be a porting PR later. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 41/0 Mathlib.lean,Mathlib/Data/ENat/WithBot.lean,Mathlib/Order/WithBotTop.lean 3 12 ['SnirBroshi', 'Thmoas-Guan', 'github-actions', 'jjdishere', 'tb65536'] nobody
8-10091
8 days ago
8-10571
8 days ago
21-28495
21 days
27
44026 kim-em
author:kim-em
chore: remove backward.privateInPublic in category theory, topology and analysis This PR removes the `backward.privateInPublic` option in 6 files across category theory, topology and analysis. In each case a private definition appeared in the statement of a public declaration, so it was already part of the public interface in all but name. The fix is to drop `private` from those definitions (and from the auxiliary definitions their bodies depend on in exposed sections), adding docstrings where they were missing. In `Analysis/InnerProductSpace/OfNorm` the auxiliary inner product `inner_` moves into the `InnerProductSpaceable` namespace rather than becoming a root-level name; the public lemmas `inner_.norm_sq`, `inner_.conj_symm` and `Continuous.inner_` already carried its name. In `Topology/Category/Compactum` the helper `cl` gets a mathematical docstring, and the two lemmas about it that are only used in proofs stay private. Files where a private *lemma* appeared in a public statement, and the files with file-wide `public section` restructuring, are handled in #44032. Names are otherwise kept as they were; suggestions for better names are welcome but are not needed for this PR. 🤖 Prepared with Claude Code tech debt 19/63 Mathlib/Analysis/InnerProductSpace/OfNorm.lean,Mathlib/CategoryTheory/Monoidal/Internal/FunctorCategory.lean,Mathlib/FieldTheory/Galois/Profinite.lean,Mathlib/Topology/Category/Compactum.lean,Mathlib/Topology/Category/TopCat/Limits/Konig.lean,Mathlib/Topology/MetricSpace/GromovHausdorff.lean 6 3 ['github-actions', 'jjdishere'] nobody
7-83381
7 days ago
62-34478
62 days ago
62-34423
62 days
0
45972 YaelDillies
author:YaelDillies
feat(Analysis/Normed): lipschitzness of group operations and also of `rpow` and `cpow`. From MeanFourier --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 223/1 Mathlib.lean,Mathlib/Analysis/Normed/Field/Basic.lean,Mathlib/Analysis/Normed/Field/Lipschitz.lean,Mathlib/Analysis/Normed/Group/Lipschitz.lean,Mathlib/Analysis/Normed/Order/Lattice.lean,Mathlib/Analysis/Normed/Ring/Basic.lean,Mathlib/Analysis/Normed/Ring/Lipschitz.lean,Mathlib/Analysis/SpecialFunctions/Pow/Deriv.lean 8 3 ['YaelDillies', 'github-actions', 'wwylele'] nobody
7-77407
7 days ago
9-24251
9 days ago
9-24196
9 days
0
37279 imalinowskip
author:imalinowskip
feat(Probability): multivariate CLT --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> <!-- [ ] depends on: #40345 --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-measure-probability tech debt 210/18 Mathlib/MeasureTheory/Function/ConvergenceInDistribution.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/AEStronglyMeasurable.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/Basic.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/MeasureTheory/Measure/LevyConvergence.lean,Mathlib/MeasureTheory/Measure/ProbabilityMeasure.lean,Mathlib/Probability/CentralLimitTheorem.lean,Mathlib/Probability/CramerWold.lean,Mathlib/Probability/Distributions/Gaussian/Multivariate.lean,Mathlib/Probability/Moments/Variance.lean 10 66 ['EtienneC30', 'RemyDegenne', 'github-actions', 'imalinowskip', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] EtienneC30
assignee:EtienneC30
7-73413
7 days ago
11-70880
11 days ago
57-25019
57 days
0
43104 elazarg
author:elazarg
feat(InformationTheory/KullbackLeibler): finite Kullback-Leibler divergence Add finite-sum formulas for `InformationTheory.klDiv` on finite measurable spaces, including equal-mass and probability-measure specializations and formulas for sums of weighted Dirac measures. Provide both `ℝ≥0∞`-valued and `toReal` versions. Supporting API includes a formula for the Radon–Nikodym derivative at points of nonzero reference-measure mass, a finite-sum formula for the integral of the log-likelihood ratio, and singleton-mass and absolute-continuity lemmas for sums of weighted Dirac measures. --- Continuing #42584, another part of https://github.com/elazarg/kraft. Following review, this uses the existing `klDiv` instead of introducing `klDivFin`. The `toReal` formulas connect it to real-valued sums in downstream code. For measures of unequal mass, the formulas retain the correction term `ν.real univ - μ.real univ`. The KL formulas are in `KullbackLeibler/Basic.lean`; the supporting lemmas are in the corresponding measure-theory modules. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-measure-probability new-contributor LLM-generated 103/1 Mathlib/InformationTheory/KullbackLeibler/Basic.lean,Mathlib/MeasureTheory/Measure/Decomposition/RadonNikodym.lean,Mathlib/MeasureTheory/Measure/Dirac/Basic.lean,Mathlib/MeasureTheory/Measure/LogLikelihoodRatio.lean 4 13 ['DavidLedvinka', 'EtienneC30', 'elazarg', 'github-actions', 'vlad902'] urkud
assignee:urkud
7-64599
7 days ago
7-64631
7 days ago
77-39911
77 days
0
27707 amellendijk
author:amellendijk
feat(NumberTheory/SelbergSieve): define Selberg's weights and prove basic results This PR continues the work from #23635. Original PR: https://github.com/leanprover-community/mathlib4/pull/23635 - [x] depends on: #27702 t-number-theory 139/2 Mathlib/NumberTheory/Divisors.lean,Mathlib/NumberTheory/SelbergSieve.lean 2 38 ['AlexKontorovich', 'MichaelStollBayreuth', 'ajirving', 'amellendijk', 'felixpernegger', 'github-actions', 'loefflerd', 'mathlib-dependent-issues', 'mathlib4-merge-conflict-bot'] mariainesdff
assignee:mariainesdff
7-59397
7 days ago
136-12661
136 days ago
139-57333
139 days
0
41905 wwylele
author:wwylele
feat(FieldTheory): relrank lemma about sup The main lemma I want is `(A ⊔ C).relrank (B ⊔ C) ≤ A.relrank B`. Added some trivial lemma along the way. --- AI usage disclosure: this was originally drafted by Aristotle, then cleaned up by me. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra LLM-generated
label:t-algebra$
91/0 Mathlib/FieldTheory/Relrank.lean 1 15 ['copilot-pull-request-reviewer', 'eric-wieser', 'github-actions', 'sharky564', 'tb65536', 'wwylele'] ocfnash
assignee:ocfnash
7-57339
7 days ago
14-61937
14 days ago
115-45256
115 days
0
46034 grunweg
author:grunweg
chore: tag lemmas WithTop.coe_ofNat and ENNReal.toEReal_ofNat with no… …rm_cast The analogous lemmas ENNReal.coe_ofNat and NNReal.coe_ofNat already are. This fixes a `norm_cast` idempotency issue: prior to this PR, ``` example (k : ℕ) : ((k : ℕ∞) : WithTop ℕ∞) ≤ (k : ℕ∞) + 2 := by norm_cast lia ``` would fail (but running norm_cast twice would make it work). On the right hand side, the numeral 2 is cast to `WithTop ℕ∞` directly: this PR allows rewriting this to `((2: ℕ∞) : WithTop ℕ∞)`, so addition can be pulled inside the cast, `WithTop.coe_le_coe` can fire and both casts removed --- resulting in a goal in ℕ. ----- We add tests for all four cases, plus one more test about rewriting literals. A future PR should investigate if some of these should also be tagged basify_op. TODO: should WithBot.coe_ofNat also be tagged norm_cast? I'm happy to also add that. AI helped me debug this; all the code and text here are my own. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. --> t-algebra
label:t-algebra$
38/3 Mathlib/Algebra/Order/Monoid/Unbundled/WithTop.lean,Mathlib/Data/EReal/Basic.lean,MathlibTest/Tactic/NormCast.lean 3 3 ['github-actions', 'grunweg', 'leanprover-radar'] nobody
7-56102
7 days ago
7-56749
7 days ago
7-57490
7 days
0
39347 Sfgangloff
author:Sfgangloff
feat(SymbolicDynamics): refactor of Pattern and shift-invariance of shape languages for subshifts ## Summary This PR refactors Pattern.mulShift in Mathlib/Dynamics/SymbolicDynamics/Basic.lean and uses the cleaner definition to prove shift-invariance of the language of a subshift on a finite shape. ## Changes Pattern.mulShift now returns a Pattern instead of a configuration (more natural). - Old type: Pattern.mulShift : Pattern A G → G → (G → A) - New type: Pattern.mulShift : Pattern A G → G → Pattern A G - The result carries its support (p.support.image (v * ·)) and the default-outside-support proof, so callers don't have to re-derive them. The [IsLeftCancelMul G] hypothesis is moved to the lemmas that actually use it. - The definition Pattern.mulShift itself no longer needs left-cancellation (it only chooses a preimage noncomputably). - The hypothesis is now stated on mulShift_config_apply_mul_left_of_mem and mulOccursInAt_eq_cylinder directly, instead of being a section-level variable. Renames following the type change. - mulShift_apply_mul_left_of_mem → mulShift_config_apply_mul_left_of_mem (because we now write (p.mulShift v).config instead of p.mulShift v). New @[simp] and @[ext] lemmas for Pattern. - Pattern.ext: two patterns are equal iff their supports agree and their configurations agree on the support. - Pattern.mulShift_support: the support of p.mulShift v is p.support.image (v * ·). - Pattern.fromConfig_support: the support of fromConfig x U is U. - Pattern.fromConfig_config_of_mem: on its support, fromConfig x U agrees with x. New lemma Pattern.fromConfig_mulShift. For a left inverse g' * g = 1, shifting the pattern fromConfig x U by g equals fromConfig (mulShift g' x) (U.image (g * ·)). New theorem MulSubshift.languageOn_image_mulShift. For a subshift Y and elements g, g' with g * g' = 1 and g' * g = 1: (fun p => p.mulShift g) '' Y.languageOn U = Y.languageOn (U.image (g * ·)) i.e. the language on the translated shape is exactly the image of the language on U under the pattern-shift map. This gives a bijection between Y.languageOn U and Y.languageOn (U.image (g * ·)), with inverse p ↦ p.mulShift g'. Stated for left-cancellative monoids with an invertible element. Updated docstrings for Pattern.mulShift and the renamed lemma to reflect the bundled-Pattern return type and clarify which results need [IsLeftCancelMul G]. t-dynamics new-contributor 144/47 Mathlib/Dynamics/SymbolicDynamics/Basic.lean 1 13 ['Sfgangloff', 'github-actions', 'mathlib-merge-conflicts', 'sgouezel'] ADedecker
assignee:ADedecker
7-51257
7 days ago
39-27994
39 days ago
99-65460
99 days
0
42283 YaelDillies
author:YaelDillies
feat(RingTheory): diagonalisable Hopf algebras Define diagonalisable Hopf algebras as those that are isomorphic to some group algebra. We will prove in a later PR that they are closed under tensor product. From Toric --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory toric 168/1 Mathlib.lean,Mathlib/LinearAlgebra/Finsupp/LinearCombination.lean,Mathlib/LinearAlgebra/LinearIndependent/Defs.lean,Mathlib/RingTheory/HopfAlgebra/Basic.lean,Mathlib/RingTheory/HopfAlgebra/Diagonalisable.lean 5 1 ['github-actions'] jjdishere
assignee:jjdishere
7-51255
7 days ago
114-28573
114 days ago
114-28570
114 days
1
42724 kim-em
author:kim-em
feat(RingTheory/Polynomial/Hermite): derivatives and the generating function This PR adds the classical derivative identities, three-term recurrence, parity, and exponential generating function for the probabilists' Hermite polynomials. The algebraic results include `derivative_hermite`, `iterate_derivative_hermite`, `hermite_add_two`, and polynomial and evaluated forms of parity; the analytic results prove `∑' n, Hₙ(x) * tⁿ / n! = exp (x * t - t² / 2)` in complex and real `HasSum` forms, with a real `tsum` corollary. The algebraic and analytic developments live in separate files. This contribution originated in the [Tau Ceti project](https://github.com/TauCetiProject/TauCeti), an AI-written mathematics repository; it was adapted for Mathlib with Claude Code and reviewed with OpenAI Codex, supervised by Kim Morrison. :robot: Prepared with OpenAI Codex t-ring-theory LLM-generated TauCeti 259/0 Mathlib.lean,Mathlib/RingTheory/Polynomial/Hermite/Derivative.lean,Mathlib/RingTheory/Polynomial/Hermite/GeneratingFunction.lean 3 3 ['b-mehta', 'github-actions', 'kim-em'] jjdishere
assignee:jjdishere
7-51252
7 days ago
80-43169
80 days ago
80-43114
80 days
0
45604 JovanGerb
author:JovanGerb
refactor(GRewrite): `mctx`/`lctx` management This PR refactors the way `grw` deals with local contexts/metavariable contexts. Previously, this was integrated in the congruence loop (the big `mutual` block). After this PR, it is part of the function that applies the rewrite lemma. This refactor is necessary in order to support equality congruence in `grw` using `Lean.Meta.Simp.main`. The new implementation works as follows. We keep a state of whether any rewrite has occurred. To rewrite for the first time, we update the local contexts of the meta variables to match the current local context. If we succeed, then we keep this updated metavariable context. We also check which free variables appear in the metavariable assignments. The rewrite only makes sense when these variables are in scope. So, to keep track of this, we store the *maximal free varaible*, i.e. the used free variable with the largest index in the local context. At any later point, we check whether the rewrite makes sense by checking if this maximal free variable is in scope. This PR also fixes a few issues around synthesizing instances under binders, and adds tests for them: - The function `postprocessAppMVars` needs to be run in the local context of the rewrite (with `withLCtx`). Otherwise, we can get an unknown free variable error. Thanks to Aaron Liu for reporting this failure. - The returned local context of a rewrite is now the maximal one instead of the minimal one, so that type class search has more available local instances. This is useful for synthesizing instances under e.g. a `[...] → _` binder. - When modifying the local context of a metavariable, we now also update the local instances. This is similarly useful for rewriting under a `[...] → _` binder. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-meta 141/76 Mathlib/Tactic/GRewrite/Core.lean,Mathlib/Tactic/GRewrite/Elab.lean,MathlibTest/Tactic/GRewrite.lean 3 4 ['JovanGerb', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] eric-wieser
assignee:eric-wieser
7-51250
7 days ago
10-52543
10 days ago
18-15325
18 days
0
46016 vihdzp
author:vihdzp
chore(Geometry/Euclidean/Volume/Triangle): fix small typos And also note the Wiedijk theorem number. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-euclidean-geometry 2/2 Mathlib/Geometry/Euclidean/Volume/Triangle.lean 1 1 ['github-actions', 'wwylele'] jsm28
assignee:jsm28
7-51248
7 days ago
8-24906
8 days ago
8-24851
8 days
0
42588 sharky564
author:sharky564
fix(Tactic/Linarith): attribute `linarith?` suggestions to the correct hypotheses `runLinarith` returned indices into the post-preprocessing fact list, but `linarithUsedHyps` applies them to the pre-preprocessing hypothesis list, so `linarith?` could suggest the wrong hypotheses or fail outright. Fixed this by tagging each fact with the indices of the original hypotheses it was derived from (`TaggedProof`), threaded through all preprocessors. --- This addresses and closes the issue raised in #41471. This was broken because the old code passed indices of a list around, without updating when the list was modified by preprocessor dropped, split or synthesised facts. No index-fix could recover this, besides just carrying through the index. Keeping the `Origin` a set rather than a single index is necessary since preprocessors can combine hypotheses. However this does mean the preprocessors no longer act on `Expr`s but rather `TaggedProof`s - I'm not the greatest fan of this, but I couldn't come up with an easy solution that preserved this behaviour. I've also provided additional tests which highlight the issues that would've previously arisen. AI disclosure: I did have AI assistance (Claude Opus/Fable) with this, but this was for me to learn more Lean syntax not typically seen in writing proofs. The diagnosis and idea for the solution was mine, and debugging and documentation was with AI assistance. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-meta LLM-generated 368/189 Mathlib/Tactic/Linarith/Datatypes.lean,Mathlib/Tactic/Linarith/Frontend.lean,Mathlib/Tactic/Linarith/NNRealPreprocessor.lean,Mathlib/Tactic/Linarith/Preprocessing.lean,MathlibTest/Tactic/Linarith/Basic.lean,MathlibTest/Tactic/Linarith/NNReal.lean 6 14 ['github-actions', 'kbuzzard', 'leanprover-radar', 'mathlib-merge-conflicts', 'sharky564'] nobody
7-50356
7 days ago
29-44869
29 days ago
96-9296
96 days
0
45968 Ruizsolveall
author:Ruizsolveall
feat(Analysis/Convex): convex bodies are determined up to homeomorphism by their dimension This PR shows that a convex body in a finite-dimensional real normed space is determined up to homeomorphism by the dimension of its affine span (`ConvexBody.nonempty_homeomorph`). The closed-ball versions follow as special cases. --- I looked at both `Mathlib/Analysis/Convex` and `Mathlib/Geometry/Convex/ConvexSpace` before deciding where to put this. I went with `Analysis/Convex`, since the proof uses radial rescaling (`gaugeRescale`), which needs an ambient vector space. A few notes: * `Convex.nonempty_homeomorph_closedBall` is close to `exists_homeomorph_image_interior_closure_frontier_eq_unitBall`. I kept it since it's the form people usually look for, but I can drop it. * Only one direction is proved; the converse needs invariance of dimension. I'd like this to be a step towards Brouwer's fixed point theorem: once Brouwer is known for a ball or a simplex, this transfers it to any convex body, including lower-dimensional ones like a triangle in ℝ³. I used AI (Claude Code) to explore the API, try out code quickly, and split up the argument. I understand the work and can explain it. Thanks to the Xena community for helping me get up to speed on the math and the design choices. new-contributor t-analysis 126/0 Mathlib.lean,Mathlib/Analysis/Convex/HomeomorphClosedBall.lean 2 3 ['github-actions', 'wwylele'] nobody
7-44547
7 days ago
9-45356
9 days ago
9-45301
9 days
0
45959 j-loreaux
author:j-loreaux
feat: precomposing with the quotient map preserves the operator norm The key lemma in this PR is that if `f : E →L[𝕜] E'` has dense range and the induced map `E ⧸ f.ker →L[𝕜] E'` is `K`-antilipschitz then the operator norm of any `g : E' →SL[σ] F` is bounded by `K * ‖g.comp f‖`. Since the quotient map satisfies this property with `K := 1`, and also because the quotient map has norm bounded by 1, the operator norm of a map from a quotient coincides with the norm of the corresponding map from the prequotient. For reasons of practicality, we actually prove this in the reverse order. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology 131/0 Mathlib.lean,Mathlib/Analysis/Normed/Group/Quotient.lean,Mathlib/Analysis/Normed/Operator/Basic.lean,Mathlib/Analysis/Normed/Operator/Quotient.lean,Mathlib/Topology/Algebra/Module/ContinuousLinearMap/Quotient.lean 5 3 ['github-actions', 'j-loreaux', 'wwylele'] nobody
7-41539
7 days ago
9-65854
9 days ago
9-65799
9 days
0
45958 j-loreaux
author:j-loreaux
feat: quotients by dense subgroups have the indiscrete topology This PR characterizes when a quotient by a subobject has the indiscrete (and also the nontrivial) topology in terms of the topological closure of the subobject. We implement this characterization for pretransitive actions, subgroups, submodules and ideals. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology 131/0 Mathlib/Topology/Algebra/ConstMulAction.lean,Mathlib/Topology/Algebra/Group/Quotient.lean,Mathlib/Topology/Algebra/Group/Subgroup.lean,Mathlib/Topology/Algebra/Module/Basic.lean,Mathlib/Topology/Algebra/Ring/Ideal.lean 5 3 ['github-actions', 'j-loreaux', 'plp127'] nobody
7-40464
7 days ago
9-66625
9 days ago
9-66570
9 days
1
42786 rshlyakh
author:rshlyakh
feat(Data/Finsupp/NatCard): count finsupps of bounded degree Adds the formula that the number of finitely-supported functions `α →₀ ℕ` with degree less than or equal to `n` is equal to `Nat.choose (Nat.card α + n) n`. The proof is by establishing an equivalence `Sym (Option α) n ≃ {f : α →₀ ℕ // f.degree ≤ n}` and using the stars-and-bars formula `Sym.equivNatSum.` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data new-contributor 69/0 Mathlib.lean,Mathlib/Data/Finsupp/NatCard.lean 2 4 ['eric-wieser', 'github-actions'] eric-wieser
assignee:eric-wieser
7-35691
7 days ago
7-36104
7 days ago
91-33809
91 days
0
45808 vihdzp
author:vihdzp
feat(GroupTheory/Coxeter/Basic): add theorems for `CoxeterMatrix.simple` These match and help golf existing theorems on `CoxeterSystem.simple`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> I'm unsure on whether we want to be reproving things for `CoxeterMatrix.simple` and `CoxeterSystem.simple`. See [Zulip](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Design.20of.20Coxeter.20systems/with/638594141). - [x] depends on: #45806 tech debt t-group-theory 42/13 Mathlib/GroupTheory/Coxeter/Basic.lean 1 4 ['github-actions', 'mathlib-dependent-issues', 'wwylele'] nobody
7-26184
7 days ago
11-25897
11 days ago
11-26443
11 days
1
44995 WenrongZou
author:WenrongZou
feat(RingTheory/MvFormalGroup): multivariate formal group definition This PR defines multivariate (including infinite dimensional) formal group laws over a commutative ring `R`. Main definitions: - `MvFormalGroup σ R`: a family `F = (F_i)_{i : σ}` of power series in two sets of variables `X, Y`, with zero constant coefficient, linear term `X_i + Y_i`, and associativity `F(F(X, Y), Z) = F(X, F(Y, Z))`. - `MvFormalGroup.IsComm`: the commutativity condition `F(X, Y) = F(Y, X)`. Main results: - `zero_add`, `add_zero`: `F(0, X) = X` and `F(X, 0) = X`. --- - [x] depends on: #44942 - [x] depends on: #44996 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory tech debt 289/0 Mathlib.lean,Mathlib/RingTheory/MvFormalGroup/Basic.lean 2 9 ['WenrongZou', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'wwylele'] nobody
7-22783
7 days ago
8-79354
8 days ago
8-81377
8 days
0
46020 WenrongZou
author:WenrongZou
feat(Topology/OpenSubgroup): locally compact subgroups are closed Add the instance `Subgroup.isClosed_of_locallyCompactSpace` (and its additive version `AddSubgroup.isClosed_of_locallyCompactSpace`): if `G` is a Hausdorff topological group and `H : Subgroup G` is locally compact in the subspace topology, then `H` is closed in `G`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology 20/0 Mathlib/Topology/Algebra/OpenSubgroup.lean 1 2 ['WenrongZou', 'github-actions', 'vihdzp'] nobody
7-22549
7 days ago
7-83933
7 days ago
7-83878
7 days
0
45946 GoldenPhysicsProject
author:GoldenPhysicsProject
feat(Analysis/Analytic): add Pringsheim's theorem **Disclosure (per Mathlib's AI policy):** this is a resubmission of #44790, which was closed in October because the original submission, prepared and sent by Claude, an AI assistant working in my project (the Golden Physics Project), did not disclose the AI involvement. This version is submitted by me, Daniel Toupin, the account holder, with the disclosure stated here: the code was AI-generated under my direction and review, in my library GPPVerify (https://github.com/GoldenPhysicsProject/GPPVerify), where it is Lean-checked with zero sorry and only the standard axioms. I stand behind the content and will make any changes you ask for. --- Add Pringsheim's theorem (Vivanti–Pringsheim): a power series `∑ aₙ zⁿ` with nonnegative real coefficients whose sum continues analytically to a neighbourhood of the positive point `R` of its circle of convergence in fact converges beyond `R`. Equivalently, such a series is singular at the positive point of its circle of convergence. Main result: `Pringsheim.exists_gt_summable_mul_pow_of_analyticAt`. The proof re-expands the series at `t = R − e/4`, identifies the re-expanded coefficients with the Cauchy power series of the continuation by uniqueness of power series, and transfers summability back to the original series by a rearrangement in `ℝ≥0∞` that needs no convergence hypotheses. The auxiliary lemmas are `private`. --- Contributed by Daniel Toupin (Golden Physics Project), with AI assistance from Claude (Anthropic) in writing the formalization. It was first developed and machine-checked in the Golden Physics Project's verification library against Mathlib v4.33.1. It was then ported to the module system and rebuilt cleanly against current `master` (48192e0, Lean v4.35.0-rc4), with zero warnings under Mathlib's linters and axioms only `propext`, `Classical.choice` and `Quot.sound`. Happy to rename or restructure to fit Mathlib's API (for example, stating it in terms of `FormalMultilinearSeries.ofScalars` and `radius`) if reviewers prefer. t-analysis new-contributor LLM-generated 279/0 Mathlib.lean,Mathlib/Analysis/Analytic/Pringsheim.lean 2 2 ['github-actions'] nobody
7-19631
7 days ago
9-86078
9 days ago
9-86023
9 days
0
45825 GoldenPhysicsProject
author:GoldenPhysicsProject
feat: explicit orthogonal projection onto the span of two vectors This adds a short file, `Mathlib/Analysis/InnerProductSpace/Projection/SpanPair.lean`, with explicit formulas for the orthogonal projection onto the span of two vectors in a real inner product space. Main results: * `InnerProductSpace.starProjection_span_pair`: the projection of `x` onto `span ℝ {u, v}`, evaluated by Cramer's rule for the two-by-two Gram matrix. The coefficients are the entries of the inverse Gram matrix applied to `(⟪u, x⟫, ⟪v, x⟫)`, under the single hypothesis that the Gram determinant is nonzero. * `InnerProductSpace.norm_sub_starProjection_span_pair_sq`: the squared distance from `x` to the span, as `‖x‖ ^ 2` minus the quadratic form of the inverse Gram matrix evaluated at `(⟪u, x⟫, ⟪v, x⟫)`. The file is self-contained: it depends only on `Mathlib.Analysis.InnerProductSpace.Projection.Basic` and proves both results from the existing `Submodule.starProjection` API. The `HasOrthogonalProjection` instance for the pair span is taken as an instance argument; in practice it is discharged from `FiniteDimensional.span_of_finite` together with `FiniteDimensional.completeSpace`. Provenance: the file comes from the GPPVerify library (GoldenPhysicsProject/GPPVerify, Apache-2.0), where it is staged in `GppVerify/Upstream/`, and is contributed here under the same license and copyright (Daniel Toupin) t-analysis new-contributor LLM-generated 113/0 Mathlib.lean,Mathlib/Analysis/InnerProductSpace/Projection/SpanPair.lean 2 5 ['GoldenPhysicsProject', 'github-actions', 'grunweg'] nobody
7-19562
7 days ago
7-19562
7 days ago
7-20042
7 days
0
45862 tb65536
author:tb65536
refactor: clean up `NumberField.HeightOneSpectrum.adicAbv` The declaration `NumberField.HeightOneSpectrum.adicAbv` has a few issues. First, it ought to be called `IsDedekindDomain.HeightOneSpectrum.adicAbv` since its main argument is `v : IsDedekindDomain.HeightOneSpectrum`. Second, the `[Ring.HasFiniteQuotients R]` hypothesis can be removed by choosing an arbitrary base when the quotient is infinite. This PR renames: - `IsDedekindDomain.HeightOneSpectrum.adicAbv` -> `IsDedekindDomain.HeightOneSpectrum.adicAbv'` - `NumberField.HeightOneSpectrum.adicAbv` -> `IsDedekindDomain.HeightOneSpectrum.adicAbv` (and move to earlier file) API that holds in this new general setting has been moved over to the earlier file. The large import is relatively minor, and will only go down once the large file `RingTheory.Ideal.Norm.AbsNorm` is split into defs vs basic. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra t-ring-theory t-number-theory large-import
label:t-algebra$
88/42 Mathlib/NumberTheory/NumberField/Completion/FinitePlace.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Valuation.lean 2 7 ['github-actions', 'xroblot'] nobody
7-7030
7 days ago
7-79558
7 days ago
12-2665
12 days
0
31884 Thmoas-Guan
author:Thmoas-Guan
feat(RingTheory): definition of Gorenstein local ring In this PR, we gave basic definition of Gorenstein local ring and Gorestein ring and prove that they are stable under ring equiv. --- <!-- The text above the `---` will become the commit message when your PR is merged. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #41885 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 74/0 Mathlib.lean,Mathlib/RingTheory/Gorenstein/Defs.lean 2 24 ['Thmoas-Guan', 'github-actions', 'jjdishere', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mathlib4-merge-conflict-bot'] jjdishere
assignee:jjdishere
7-3488
7 days ago
7-3956
7 days ago
121-16426
121 days
7
43894 JX-Mo
author:JX-Mo
feat(RepresentationTheory): add Burnside's theorem for matrix algebras This PR adds Burnside's theorem: If `V` is simple module of a `k`-algebra `A` where `k` is an algebraically closed field `k`, then the algebra map `A → End_k(V)` is surjective. The proof is a combination of Schur's lemma and Jacobson density theorem, both of which are already in Mathlib. t-algebra
label:t-algebra$
12/4 Mathlib/RepresentationTheory/AlgebraRepresentation/Basic.lean 1 29 ['JX-Mo', 'artie2000', 'github-actions', 'mathlib-splicebot', 'themathqueen'] nobody
6-56164
6 days ago
8-80626
8 days ago
65-83221
65 days
0
45560 artie2000
author:artie2000
feat(Algebra/Order): bijections between order structures and positive cones * Bundle the constructors between pointed (and also spanning) submonoids and subsemirings - ie, group and ring cones - and (linear) order structures on groups and rings, respectively, into equivalences. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
102/0 Mathlib/Algebra/Order/Group/Cone.lean,Mathlib/Algebra/Order/Ring/Cone.lean 2 10 ['artie2000', 'github-actions', 'wwylele'] nobody
6-52097
6 days ago
20-76044
20 days ago
20-76086
20 days
0
42494 JadAbouHawili
author:JadAbouHawili
feat(Combinatorics/SimpleGraph/Connectivity): add edge reachability and connectivity numbers Define edge reachability and connectivity numbers with some basic API Partially solves #34961 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics 81/2 Mathlib/Combinatorics/SimpleGraph/Connectivity/EdgeConnectivity.lean,Mathlib/Order/CompleteLattice/Lemmas.lean 2 169 ['JadAbouHawili', 'SnirBroshi', 'github-actions', 'grunweg', 'mathlib-merge-conflicts'] nobody
6-50356
6 days ago
28-34761
28 days ago
78-51492
78 days
0
43216 JadAbouHawili
author:JadAbouHawili
feat(Combinatorics/SimpleGraph/Clique): independence number is zero iff the graph has no vertices --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics 62/11 Mathlib/Combinatorics/SimpleGraph/Clique.lean 1 66 ['JadAbouHawili', 'SnirBroshi', 'github-actions', 'mathlib-merge-conflicts'] nobody
6-50354
6 days ago
28-32737
28 days ago
73-65447
73 days
0
42959 gasparattila
author:gasparattila
feat: add `fun_simp` tactic This PR adds a tactic and simp set `fun_simp` for simplifying bundled morphisms. The main use case is simplifying functions before calling `fun_prop`. In the future, this tactic could be added to `fun_prop` itself as a preprocessing step. --- The idea of this tactic is based on #42516 by @mcdoll. Unlike #42516, which simply uses a simp set, this implementation has a preprocessing step to allow using applied forms of lemmas without eta-expanding. The tests were written using Codex. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-meta LLM-generated 485/0 Mathlib.lean,Mathlib/Tactic.lean,Mathlib/Tactic/FunSimp.lean,Mathlib/Tactic/FunSimp/Attr.lean,MathlibTest/FunSimp.lean 5 2 ['gasparattila', 'github-actions'] nobody
6-50353
6 days ago
29-1913
29 days ago
29-1858
29 days
0
43095 plp127
author:plp127
chore(Data/PFunctor): reduce defeq abuse around `PFunctor.W` Reduce the defeq abuse around `PFunctor.W` by adding some API. --- - [x] depends on: #43056 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data tech debt 88/52 Mathlib/Data/PFunctor/Multivariate/W.lean,Mathlib/Data/PFunctor/Univariate/Basic.lean,Mathlib/Data/QPF/Univariate/Basic.lean 3 6 ['github-actions', 'mathlib-dependent-issues', 'plp127', 'vihdzp'] nobody
6-44532
6 days ago
79-82261
79 days ago
79-83043
79 days
0
45236 ScottCarnahan
author:ScottCarnahan
feat(RingTheory/FilteredAlgebra): passage between filtrations and gradings This PR adds some API for passing between filtered and graded ring structures. --- t-ring-theory t-algebra
label:t-algebra$
105/9 Mathlib.lean,Mathlib/LinearAlgebra/DFinsupp.lean,Mathlib/RingTheory/FilteredAlgebra/Graded.lean,Mathlib/RingTheory/FilteredAlgebra/Lattice.lean 4 3 ['ScottCarnahan', 'github-actions', 'wwylele'] nobody
6-38599
6 days ago
12-24058
12 days ago
12-24003
12 days
0
44885 3y3y3y-huaiji
author:3y3y3y-huaiji
feat(Combinatorics/Quiver/Monotone): define Monotone and StrictMono Define `Quiver.Monotone` and `Quiver.StrictMono` for functions from the vertices of a quiver into a preorder, and deduce that `Quiver.Reachable` is a partial order when a strictly monotone function exists. --- > [!NOTE] > **LLM Disclosure / AI Use**: This PR was prepared with the assistance of an LLM (`LLM-generated`). All proofs and statements have been formally verified by Lean 4 and checked with linters. t-combinatorics LLM-generated new-contributor 69/0 Mathlib.lean,Mathlib/Combinatorics/Quiver/Monotone.lean 2 15 ['3y3y3y-huaiji', 'github-actions', 'joelriou', 'leanprover-radar', 'vihdzp'] nobody
6-32694
6 days ago
6-32997
6 days ago
26-73588
26 days
0
44039 Nicola9Falciola
author:Nicola9Falciola
feat(LinearAlgebra/Matrix/GeneralLinearGroup/Card): add the cardinality of `GL n R` given `f : R →+* S` a local ring hom --- Add a new section `IsLocalHom`, given a local ring hom `f : R →+* S` we have that: - The induced map on `GL n R →* GL n S` is surjective - We can explicitly express its kernel - We can thus write `Nat.card GL n R = Nat.card (RingHom.ker f) ^ (n ^ 2) * Nat.card GL n S` This is needed to prove the formula for `GL n ZMod N`. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #43845 - [x] depends on: #43898 - [x] depends on: #43945 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 53/0 Mathlib/LinearAlgebra/Matrix/GeneralLinearGroup/Card.lean,Mathlib/LinearAlgebra/Matrix/GeneralLinearGroup/Defs.lean,Mathlib/LinearAlgebra/Matrix/NonsingularInverse.lean 3 11 ['Nicola9Falciola', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'wwylele'] nobody
6-12813
6 days ago
6-13926
6 days ago
25-28181
25 days
1
37838 Thmoas-Guan
author:Thmoas-Guan
feat(FieldTheory): basic theories about transcendental separable extension The formalization of [Stacks 030W] via [Stacks 030U]. Current design of instance would be very subtle only using separable, thus we would deal with this in the coming PR #39141 using `IsGeometricallyReduced`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #37934 - [x] depends on: #39138 - [x] depends on: #39740 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra large-import
label:t-algebra$
457/15 Mathlib/FieldTheory/SeparablyGenerated.lean,Mathlib/FieldTheory/TranscendentalSeparable.lean,Mathlib/RingTheory/LocalProperties/Reduced.lean 3 63 ['Multramate', 'Thmoas-Guan', 'github-actions', 'jjdishere', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
6-9960
6 days ago
9-14375
9 days ago
64-59478
64 days
1
46068 Thmoas-Guan
author:Thmoas-Guan
chore(RingTheory): move `RingTheory.AdicCompletion.Noetherian` This PR makes `Mathlib.Topology.Algebra.Ring.Ideal` a folder and move `RingTheory.AdicCompletion.Noetherian` to `Mathlib.Topology.Algebra.Ring.Ideal.Noetherian`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> file-removed t-topology 5/5 Mathlib.lean,Mathlib/Analysis/Normed/Ring/Units.lean,Mathlib/Topology/Algebra/Ring/Compact.lean,Mathlib/Topology/Algebra/Ring/Ideal/Basic.lean,Mathlib/Topology/Algebra/Ring/Ideal/Noetherian.lean,Mathlib/Topology/Algebra/UniformRing.lean 6 2 ['Thmoas-Guan', 'felixpernegger', 'github-actions'] nobody
6-3592
6 days ago
6-3592
6 days ago
6-4873
6 days
5
40010 Hagb
author:Hagb
refactor({Algebra,RingTheory}/MvPolynomial): restate kinds of degrees in `MvPolynomial` with `AddMonoidAlgebra.supDegree` This PR copied lemmas of `AddMonoidAlgebra.{supDegree,leadingCoeff,Monic}` to `MvPolynomial`, restates some definitions about `MvPolynomial` with them, and simplifies some proofs with their lemmas. The following definitions are restated with `supDegree`, of which original definitions are definitionally equal to the new definitions (except `MonomialOrder.withBotDegree`): - `MvPolynomial.totalDegree` - `MvPolynomial.degrees` - `MvPolynomial.weightedTotalDegree` - `MvPolynomial.weightedTotalDegree'` - `MonomialOrder.degree` - `MonomialOrder.withBotDegree` The following definitions are not changed directly, while provided lemmas that express them with `supDegree`, `leadingCoeff` or `Monic`, since their original definitions are not definitionally equal to their `supDegree` versions. - `MvPolynomial.degreeOf` - `MonomialOrder.leadingCoeff` - `MonomialOrder.Monic` The following lemma is complained by `simpNF` linter that it can be solved by `simp only [*, @AddMonoidAlgebra.monic_one]`, while it is not true. ``` @[simp, nolint simpNF] theorem monic_one (hD : D.Injective) : (1 : MvPolynomial σ R).Monic D := AddMonoidAlgebra.monic_one hD ``` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> #### Maybe helpful dependency relations - `Mathlib/Algebra/MonoidAlgebra/Degree.lean`: an upstream of all other modified modules. It contains definitions and lemmas of `AddMonoidAlgebra.{supDegree,leadingCoeff,Monic}`, with some lemmas generalized or added for use of downstream proofs; - `Mathlib/Algebra/MvPolynomial/SupDegree.lean`: a downstream of the previous one, an upstream of other modified modules. - `Mathlib/Algebra/MvPolynomial/Degrees.lean`, `Mathlib/RingTheory/MvPolynomial/MonomialOrder.lean`, `Mathlib/RingTheory/MvPolynomial/WeightedHomogeneous.lean`: downstream modules of the previous one with definitions and statement of theorems modified, and upstream modules of other modified modules. #### The above two lists with hyperlinks - [`MvPolynomial.totalDegree`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MvPolynomial.totalDegree#doc) - [`MvPolynomial.degrees`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MvPolynomial.degrees#doc) - [`MvPolynomial.weightedTotalDegree`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MvPolynomial.weightedTotalDegree#doc) - [`MvPolynomial.weightedTotalDegree'`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MvPolynomial.weightedTotalDegree'#doc) - [`MonomialOrder.degree`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MonomialOrder.degree#doc) - [`MonomialOrder.withBotDegree`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MonomialOrder.withBotDegree#doc) and - [`MvPolynomial.degreeOf`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MvPolynomial.degreeOf#doc) - [`MonomialOrder.leadingCoeff`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MonomialOrder.leadingCoeff#doc) - [`MonomialOrder.Monic`](https://leanprover-community.github.io/mathlib4_docs/find/?pattern=MonomialOrder.Monic#doc) [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory increases-technical-debt 250/209 Mathlib.lean,Mathlib/Algebra/MonoidAlgebra/Degree.lean,Mathlib/Algebra/MvPolynomial/CommRing.lean,Mathlib/Algebra/MvPolynomial/Degrees.lean,Mathlib/Algebra/MvPolynomial/Equiv.lean,Mathlib/Algebra/MvPolynomial/SchwartzZippel.lean,Mathlib/Algebra/MvPolynomial/SupDegree.lean,Mathlib/Data/Finsupp/MonomialOrder.lean,Mathlib/RingTheory/MvPolynomial/Homogeneous.lean,Mathlib/RingTheory/MvPolynomial/MonomialOrder.lean,Mathlib/RingTheory/MvPolynomial/Symmetric/Defs.lean,Mathlib/RingTheory/MvPolynomial/Symmetric/FundamentalTheorem.lean,Mathlib/RingTheory/MvPolynomial/WeightedHomogeneous.lean,Mathlib/RingTheory/MvPowerSeries/Trunc.lean,Mathlib/RingTheory/NoetherNormalization.lean 15 29 ['Hagb', 'faenuccio', 'github-actions', 'mathlib-merge-conflicts'] faenuccio
assignee:faenuccio
6-2950
6 days ago
9-76210
9 days ago
11-72092
11 days
0
46050 YijunYuan
author:YijunYuan
feat(NumberTheorey/Padics/Complex): prove the p-adic algebraic closure is not complete The ultimate goal of this PR is to show that the algebraic closure `PadicAlgCl p` of the field `ℚ_[p]` of p-adic rational numbers is not complete with respect to the p-adic norm. To do so, I prove the following results: 1. Let K be a complete non-trivially normed ultrametric field. If a normed extension E of K is perfect and is a Baire space, then E must be finite-dimensional over K 2. As a result of the above result, the algebraic closure of K is a Baire space w.r.t. the spectral norm if and only if it is of finite dimension over K. 3. As a corollary, the algebraic closure of K is a complete space w.r.t. the spectral norm if and only if it is of finite dimension over K. 4. `PadicAlgCl p` is of infinite dimension over `ℚ_[p]`. 5. By the above results, `PadicAlgCl p` is not a Baire space and is not complete w.r.t. the p-adic norm. Several reusable helper results are also supplied. new-contributor t-number-theory 252/1 Mathlib.lean,Mathlib/Analysis/Normed/Field/Baire.lean,Mathlib/FieldTheory/Minpoly/Bounds.lean,Mathlib/NumberTheory/Padics/Complex.lean 4 15 ['YijunYuan', 'github-actions', 'vihdzp', 'wwylele'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
6-2421
6 days ago
6-85317
6 days ago
7-1606
7 days
0
41957 YijunYuan
author:YijunYuan
feat(NumberTheory/Padics/Complex): add densely normed field and separable space instances Equip the field `ℂ_[p]` of `p`-adic complex numbers and its dense subfield `PadicAlgCl p` (the algebraic closure of `ℚ_[p]`) with two further standard typeclass instances. Main additions: * `DenselyNormedField (PadicAlgCl p)`: the norm takes values dense in the positive reals. The witness between two given bounds `a < b` is built from an `n`-th root `z` of `p` (which exists since `PadicAlgCl p` is algebraically closed): choosing `n` so that `(a / b) ^ n < ‖p‖` gives `a / b < ‖z‖ < 1`, and some integer power `z ^ m` then has norm strictly between `a` and `b`. * `SeparableSpace (PadicAlgCl p)`: the elements algebraic over `ℚ` form a countable dense subset. Density follows from continuity of roots — `α` is a root of its minimal polynomial `f` over `ℚ_[p]`, and approximating the coefficients of `f` by a polynomial `g` over the dense subfield `ℚ` yields a root `β` of `g` (hence algebraic over `ℚ`) arbitrarily close to `α`. * The corresponding instances `DenselyNormedField ℂ_[p]` and `SeparableSpace ℂ_[p]` are then inferred, `ℂ_[p]` being the completion of `PadicAlgCl p`. Supporting general instance: * `DenselyNormedField (UniformSpace.Completion A)` for a densely normed field `A` with `CompletableTopField A`, since the norm on the completion extends the norm on `A`. The existing `NontriviallyNormedField` instances on `PadicAlgCl p` and `ℂ_[p]` are simplified to `inferInstance`, as they now follow from the new `DenselyNormedField` instances. new-contributor t-number-theory t-algebra large-import
label:t-algebra$
196/12 Mathlib.lean,Mathlib/Analysis/Normed/Field/Separable.lean,Mathlib/Analysis/Normed/Module/Completion.lean,Mathlib/Analysis/Normed/Unbundled/SpectralNorm.lean,Mathlib/NumberTheory/Padics/Complex.lean,Mathlib/NumberTheory/Padics/PadicNumbers.lean,Mathlib/Topology/Algebra/Field.lean 7 23 ['YijunYuan', 'github-actions', 'jjdishere', 'mathlib-merge-conflicts', 'pechersky', 'riccardobrasca'] jjdishere
assignee:jjdishere
6-2282
6 days ago
6-2282
6 days ago
112-72970
112 days
0
44762 Julian-Kuelshammer
author:Julian-Kuelshammer
feat(Combinatorics/Enumerative/Catalan/BracketingFunction): adds Huang-Tamari's bracketing functions This PR defines bracketing functions, an elementary description of the Tamari lattice. This PR is intentially kept short and just adds the definition and a bit of basic API. There are potential follow-ups proving that these are counted by the Catalan numbers and giving the lattice instance, for a preview see https://github.com/Julian-Kuelshammer/ExtensionClosedSubcategoriesOfAn/blob/main/ExtensionClosedSubcategoriesOfAn/BracketingFunctions.lean A first version of the file was created with the help of Aristotle and Claude. In this PR a large percentage of proofs has been rewritten afterwards. The docstring is entirely human-written except for the ASCII art. --- new-contributor t-combinatorics LLM-generated 102/0 Mathlib.lean,Mathlib/Combinatorics/Enumerative/Catalan/BracketingFunction.lean 2 4 ['Julian-Kuelshammer', 'github-actions'] nobody
5-85708
5 days ago
42-6586
42 days ago
42-6925
42 days
0
43852 ZRTMRH
author:ZRTMRH
feat(Combinatorics/Quiver/Schreier): add Schreier Cayley basics Defined Cayley graph as a coset Schreier graph. Proved connectivity and vertex-transitivity on Cayley graphs, as promised in #38310. Follow-up to #38310, this is the 3rd split pr from #35467. This PR was written with AI assistance (Claude). The code has been reviewed by the author. P.S. cayley_subsingleton_weaklyConnectedComponent's proof is generic and I can extract it to Quiver/ConnectedComponent.lean as a weak-connectivity lemma, if it is wanted. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics large-import LLM-generated 278/7 Mathlib/Combinatorics/Quiver/Schreier.lean 1 10 ['SnirBroshi', 'ZRTMRH', 'github-actions', 'mathlib-merge-conflicts', 'vlad902'] nobody
5-84788
5 days ago
55-4194
55 days ago
67-53354
67 days
0
45631 Nicola9Falciola
author:Nicola9Falciola
feat(LinearAlgebra/Matrix/ExtendSubmatrix): add a way to update a submatrix along functions and relative api This PR adds `Matrix.extendSubmatrix eₙ eₘ A B`: given maps `eₙ : n → o` and `eₘ : m → p`, a matrix `A : Matrix n m α` and a matrix `B : Matrix o p α`, it is the matrix obtained from `B` by replacing the entries at positions `(eₙ i, eₘ j)` with `A i j`. It is defined via `Function.extend` and generalizes the existing `Matrix.updateRow` and `Matrix.updateCol`. It also adds the general lemma `Function.extend_comp_self : extend f (g ∘ f) g = g` to `Mathlib/Logic/Function/Basic.lean`, which is used in several proofs. The construction is meaningful when `eₙ` and `eₘ` are injective, but it is stated for arbitrary maps: each lemma only assumes the injectivity it actually needs (e.g. only `eₙ` for `updateRow_extendSubmatrix`, only the row maps for `extendSubmatrix_comm_of_disjoint_left`, none for `_add`, `_map` or `_submatrix_self`). Together with the definition I add the main API lemmas such as `_trans`, `_refl` , `_submatrix`, `_apply_embedding` , `_apply_of_notMem_left`, `_apply_of_notMem_right`, ` ext_..._iff`, ecc.. I have also added API relative to how this definition behave compared to already existing constructions such has taking the transposition, composing with `Matrix.map`, `fromBlocks` and `.inl` or `.inr` and `toSquareBlockProp` . There is the sufficent API to compare the new definition with the existing `updateRow`, `updateColums` and with `reindex`. I add also the `_add`, `_smul` and `_zero` API to define the bundled versions as ` Matrix n m α × Matrix o p α →+ Matrix o p α` and `Matrix n m α × Matrix o p α →ₗ[R] Matrix o p α`. --- It is my plan to follow up this PR with the relative construction for `GL` and `SL` and by cleaning up the already existing [Matrix.TransvectionStruct.sumInl](https://leanprover-community.github.io/mathlib4_docs/Mathlib/LinearAlgebra/Matrix/Transvection.html#Matrix.TransvectionStruct.sumInl), this will allow to construct induction arguments over the index type `n` for `GL` and `SL` and in the future introduce `GL R` and `SL R` as the colimits over the inclusion `Fin n ↦ Fin (n + 1)`. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
425/2 Mathlib.lean,Mathlib/LinearAlgebra/Matrix/Block.lean,Mathlib/LinearAlgebra/Matrix/ExtendSubmatrix.lean,Mathlib/Logic/Function/Basic.lean 4 36 ['Nicola9Falciola', 'eric-wieser', 'github-actions', 'tb65536', 'themathqueen'] nobody
5-80482
5 days ago
8-85309
8 days ago
17-72779
17 days
3
40871 justus-springer
author:justus-springer
feat(AlgebraicGeometry/Birational): add birational maps We add birational maps between irreducible schemes (dominant rational maps with an inverse). We provide a group structure on birational automorphisms and the subgroup of birational maps that are defined over a base. We also prove that partial isomorphisms give rise to birational maps (leaving the converse as future work). - [x] depends on: #39122 - [x] depends on: #39445 - [x] depends on: #42402 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebraic-geometry large-import increases-technical-debt 251/4 Mathlib.lean,Mathlib/AlgebraicGeometry/Birational/Birational.lean,Mathlib/AlgebraicGeometry/Birational/BirationalMap.lean,Mathlib/AlgebraicGeometry/Birational/Composition.lean,Mathlib/AlgebraicGeometry/Birational/RationalMap.lean,Mathlib/AlgebraicGeometry/Restrict.lean 6 14 ['chrisflav', 'github-actions', 'justus-springer', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'tb65536'] chrisflav
assignee:chrisflav
5-79912
5 days ago
5-80525
5 days ago
10-5139
10 days
0
45581 tb65536
author:tb65536
chore(Data/Nat/PadicValNat): deprecate `padicValNat` This PR deprecates `padicValNat` in favor of `multiplicity`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-number-theory t-algebra
label:t-algebra$
42/36 Mathlib/Analysis/Normed/Algebra/Logarithm.lean,Mathlib/Data/Nat/Factorization/Defs.lean,Mathlib/Data/Nat/MaxPowDiv.lean,Mathlib/Data/Nat/Multiplicity.lean,Mathlib/Data/Nat/PadicValNat.lean,Mathlib/NumberTheory/Padics/PadicVal/Defs.lean,Mathlib/NumberTheory/SumTwoSquares.lean,MathlibTest/MaxPowDiv.lean 8 11 ['github-actions', 'tb65536', 'xroblot'] nobody
5-77092
5 days ago
20-9365
20 days ago
20-9312
20 days
0
46004 danderson70-UNL
author:danderson70-UNL
feat(Data/List/Destutter): add lemmas about `List.destutter.head` and `List.destutter.getLast` These proofs have a version for `List.destutter'` as well as for `List.destutter`. The `getLast` proofs don't apply in general, such as for `[5, 6, 2].destutter (<) = [5, 6]`, and I don't believe that there is a clean way to maintain the generality without adding complex hypotheses. The documentation for [`List.destutter`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/List/Defs.html#List.destutter) suggests that `List.destutter` is usually used with the `≠` relation, so I think that the lemmas I created may still have general use. I wasn't sure whether to mark these lemmas with `@[simp]`. I think it could be useful to include them, but I didn't know how to check for infinite loops and other issues that could arise from adding the `@[simp]` tag. (I also forgot to include them in my commits.) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data new-contributor 36/0 Mathlib/Data/List/Destutter.lean 1 2 ['github-actions'] nobody
5-74027
5 days ago
8-58610
8 days ago
8-58555
8 days
0
46088 Hagb
author:Hagb
feat(Order/KrullDimension): generalize and simplify `height_coe_withTop` `height_coe_withTop` can be generalized to and proved by the version of `Order.height` on `α ⊕ₗ β`: `height_toLex_sum_inr : Order.height (toLex (Sum.inl a : α ⊕ β)) = Order.height a`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> If we had also ``` lemma height_toLex_sum_inr {α β : Type*} [Preorder α] [Preorder β] {b : β} : Order.height (toLex (Sum.inr b : α ⊕ β)) = (Order.krullDim α + 1).unbotD 0 + Order.height b ``` Then we would be able to prove `height_coe_withBot (x : α) : height (x : WithBot α) = height x + 1` similarly. But I haven't find a short proof of it. t-order 12/23 Mathlib/Order/KrullDimension.lean 1 1 ['github-actions'] nobody
5-68932
5 days ago
5-75855
5 days ago
5-75800
5 days
0
46090 JovanGerb
author:JovanGerb
chore: deal with more duplicate declarations This PR fixes some more issues found by the duplicate declaration linter in https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/duplicate.20declarations/with/547121755 - Instance for `Max Rat` and `Min Rat` already exist in core, so can be removed - lemmas about `sup`/`inf` on `Min`/`MaxTropical` are deprecated in favour of the `max`/`min` variants. This is because the order in question is a linear order, so the sup/inf is actually a max/min. - `IsCompact.closedBall_div` is modified to match the name - it used to be a duplicate of `IsCompact.closedBall_mul` - `rpow_sub_intCast` is modified to talk about `intCast` instead of `natCast`. - some duplicates like `Real.rpow_le_of_le_log` had the wrong name and are deprecated. - `BAll.imp_right` and `BEx.imp_right` are deprecated in favour of the more general `forall₂_imp` and `Exists₂.imp` - `Filter.Germ.const_nsmul` is deprecated in favour of `Filter.Germ.const_smul`, as it doesn't involve `Nat`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 20/16 Mathlib/Algebra/Order/Ring/Unbundled/Rat.lean,Mathlib/Algebra/Tropical/Basic.lean,Mathlib/Analysis/Normed/Group/Pointwise.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Analysis/SpecialFunctions/Pow/Real.lean,Mathlib/Basic/Logic/Basic.lean,Mathlib/Order/Filter/Germ/Basic.lean 7 3 ['JovanGerb', 'github-actions', 'vihdzp'] nobody
5-68214
5 days ago
5-72335
5 days ago
5-72280
5 days
0
33821 JohnnyTeutonic
author:JohnnyTeutonic
feat(LinearAlgebra/Matrix/Hermitian): add IsSkewHermitian predicate Adds `IsSkewHermitian` predicate for matrices satisfying Aᴴ = -A. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra will-close-soon
label:t-algebra$
70/0 Mathlib/LinearAlgebra/Matrix/Hermitian.lean 1 23 ['JohnnyTeutonic', 'eric-wieser', 'github-actions', 'j-loreaux', 'themathqueen'] kim-em
assignee:kim-em
5-60332
5 days ago
5-66828
5 days ago
32-67587
32 days
0
46071 user202729
author:user202729
chore: replace 'cases … inductionOn' with 'induction … inductionOn' For consistency. Rough estimation: ``` [mathlib4]$ rg 'cases.*inductionOn' Mathlib|wc -l 6 [mathlib4]$ rg 'induction.*inductionOn' Mathlib|wc -l 251 ``` --- (Partly also for further discussion.) We might want to make a lint rule for this, but `induction` might not make sense for every types? Only for recursively-defined inductive types. This one mostly affect `Quotient`, but `Quotient`'s definition isn't recursive. Even for this specific case: ``` [mathlib4]$ rg 'induction.*Quotient\.inductionOn' Mathlib|wc -l 138 ``` There's also ``` [mathlib4]$ rg 'refine.*inductionOn' Mathlib|wc -l 91 ``` We might consider making a lint rule, but since either works, perhaps the lint rule has to detect whether the method name contains `inductionOn`…? 6/6 Mathlib/Analysis/Asymptotics/TVS.lean,Mathlib/GroupTheory/GroupAction/Quotient.lean,Mathlib/SetTheory/Cardinal/Cofinality/Ordinal.lean 3 3 ['felixpernegger', 'github-actions', 'user202729', 'vihdzp'] nobody
5-52215
5 days ago
5-85393
5 days ago
5-85338
5 days
0
43565 Parcly-Taxel
author:Parcly-Taxel
refactor(Archive/FriendshipGraphs): golf everything Also remove the file's `set_option`s and `@[expose]`. Like #43434, no deprecations are added since this is a leaf file in Archive. tech debt 103/292 Archive/Wiedijk100Theorems/FriendshipGraphs.lean 1 9 ['Parcly-Taxel', 'SnirBroshi', 'github-actions', 'mathlib-merge-conflicts'] jjdishere
assignee:jjdishere
5-51256
5 days ago
14-73955
14 days ago
75-40756
75 days
0
46092 wwylele
author:wwylele
feat(Geometry/Euclidean): mapping Simplex.volume with an affine map This gives a second `Simplex.map` lemma on `Simplex.volume`, where the map is not necessarily isometric but the source simplex is required to have max dimension. --- Split from #44252 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> large-import t-euclidean-geometry 39/1 Mathlib/Analysis/InnerProductSpace/NormDet.lean,Mathlib/Geometry/Euclidean/Volume/Basic.lean 2 2 ['github-actions', 'wwylele'] jsm28
assignee:jsm28
5-51251
5 days ago
5-68919
5 days ago
5-68864
5 days
0
41729 vaca22
author:vaca22
feat(RingTheory/DedekindDomain): add divisor group core Add the divisor group of a Dedekind domain as a formal-sum model, together with the additive equivalence to the multiplicative group of nonzero fractional ideals. **Relation to what Mathlib already has.** As pointed out on Zulip, Mathlib already knows that fractional ideals factor: `FractionalIdeal.count` gives the exponent of a height-one prime, and `ClassGroup` is built from fractional ideals directly. This PR does not re-prove any of that — it reuses `count` and `finite_factors` verbatim. What it adds is the *additive* packaging: * `IsDedekindDomain.Divisor R := HeightOneSpectrum R →₀ ℤ`, so a divisor is a finitely supported integer-valued function and one can write `D₁ + D₂`, `-D`, `D v`, and use the whole `Finsupp` API (`support`, `sum`, induction on the support); * `FractionalIdeal.divisorEquiv`, an `AddEquiv` from `(FractionalIdeal R⁰ K)ˣ` to `Divisor R`, turning ideal multiplication into divisor addition. The multiplicative view is the right one for the class group; the additive one is what divisor-theoretic arguments are written in, where one constantly forms `D - D'`, compares coefficients prime by prime, and does induction over `D.support`. Having both, related by a single `AddEquiv`, means neither side has to be re-derived. **Downstream use.** This is the bottom layer of a formalization of Riemann–Roch for algebraic function fields (announced in `#AI authored projects > Riemann–Roch for function fields`): `L(D)`, `deg D`, and the statement `ℓ(D) = deg D + 1 - g + ℓ(W - D)` are all phrased in terms of additive divisors, and the degree map is defined by summing coefficients over `D.support`. Happy to reshape the API — in particular whether `Divisor` should be an `abbrev` or a structure, and whether this belongs next to `Factorization` rather than in its own file. AI usage: LLM-generated, disclosed per the AI policy. t-ring-theory new-contributor LLM-generated 100/0 Mathlib.lean,Mathlib/RingTheory/DedekindDomain/Divisor.lean 2 4 ['github-actions', 'grunweg', 'vaca22'] nobody
5-50356
5 days ago
128-61223
128 days ago
130-58371
130 days
0
42775 hawkrobe
author:hawkrobe
feat(RingTheory/HopfAlgebra): construct Hopf algebras from primitive generators Upgrade a bialgebra generated by primitive elements to a Hopf algebra (`HopfAlgebra.ofPrimitives`), given an anti-algebra hom `S : A →ₐ[R] Aᵐᵒᵖ` negating each generator, and show that such an `S` is the antipode (`HopfAlgebra.eq_antipodeAlgHomOp_of_primitives`). Both build on `HopfAlgebra.ofAntipodeOfAdjoin` from #41828, which superseded the generators construction this PR originally carried. Split out of #39841. Claude Code was used to prepare this revision. t-ring-theory new-contributor 31/4 Mathlib/RingTheory/HopfAlgebra/Primitive.lean 1 3 ['github-actions'] nobody
5-50355
5 days ago
26-78768
26 days ago
97-47345
97 days
1
42833 YaelDillies
author:YaelDillies
feat(Combinatorics/SimpleGraph/Connectivity): efficient decidability instances Currently, the `DecidableRel G.Reachable` instance provided by mathlib works by enumerating *all* walks from `u` to `v` of length less than `Fintype.card V`, which takes time exponential in the number of vertices. Currently also, the `Decidable G.Preconnected` and `Decidable G.Connected` instances build on the `DecidableRel G.Reachable` one and suffer from the same exponential slowdown. This PR reworks those instances to use breadth-first search, which is polynomial in the number of vertices. Since the BFS doesn't depend on the starting vertex, we wrap it in `Trunc` to cut down an unnecessary factor of `Fintype.card V` (this makes a difference only if the graph is NOT preconnected). This showed up in FormalConjectures because a contributor used `decide +native` to prove that some concrete graph on 11 vertices was connected. Their proof timed out while I was bumping the repo to v4.30. Also make `G` implicit in a bunch of non-rewriting lemmas. From FormalConjectures Generated by Claude Opus following my idea, largely rewritten manually afterwards. Assisted-by: Claude Opus 4.8 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics LLM-generated 343/31 Mathlib/Combinatorics/SimpleGraph/Connectivity/Finite.lean,Mathlib/Combinatorics/SimpleGraph/Tutte.lean,Mathlib/Data/Fintype/Basic.lean,Mathlib/Data/List/Nodup.lean,MathlibTest/SimpleGraph.lean 5 9 ['SnirBroshi', 'YaelDillies', 'b-mehta', 'github-actions'] nobody
5-50354
5 days ago
64-7732
64 days ago
66-24562
66 days
0
42895 cameronfreer
author:cameronfreer
feat(SetTheory/Ordinal): add lift_sSup and lift_iSup Show that an initial segment embedding between conditionally complete linear orders with bottom preserves bounded suprema (`InitialSeg.map_csSup`, `InitialSeg.map_ciSup`). Specializing to `Ordinal.liftInitialSeg` gives `Ordinal.lift_sSup` and `Ordinal.lift_iSup`. `Ordinal.lift_sSup` assumes `[Small.{u} s]`, while `Ordinal.lift_iSup` assumes `BddAbove (Set.range f)` rather than a small index type. --- 🤖 This PR was developed with assistance from Claude and GPT models, using [lean4-skills](https://github.com/cameronfreer/lean4-skills) and [lean-lsp-mcp](https://github.com/oOo0oOo/lean-lsp-mcp). t-set-theory new-contributor LLM-generated 27/1 Mathlib/Order/IsNormal.lean,Mathlib/SetTheory/Cardinal/Cofinality/Ordinal.lean,Mathlib/SetTheory/Ordinal/Family.lean 3 34 ['bryangingechen', 'cameronfreer', 'github-actions', 'jjdishere', 'leanprover-radar', 'plp127', 'vihdzp'] jjdishere
assignee:jjdishere
5-47981
5 days ago
7-54976
7 days ago
84-33476
84 days
0
43815 SnirBroshi
author:SnirBroshi
feat(Data/Sym/Sym2): `Sym2.map` lifts equivalences `Sym2.map : (α → β) → (Sym2 α → Sym2 β)` preserves injectivity / surjectivity / bijectivity, and can lift `α ≃ β` to `Sym2 α ≃ Sym2 β`. --- Is this what people might call "functoriality of `Sym2.map`"? Or maybe of `Sym2`? Or does `Sym2.map` itself already demonstrates that `Sym2` is functorial? Not sure <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data 45/3 Mathlib/Combinatorics/SimpleGraph/Maps.lean,Mathlib/Data/Sym/Sym2.lean 2 4 ['chiyunhsu', 'eric-wieser', 'github-actions'] eric-wieser
assignee:eric-wieser
5-40243
5 days ago
68-50289
68 days ago
68-52654
68 days
1
41892 Ljon4ik4
author:Ljon4ik4
feat: mapOfCompatibleSMul is the same map independently of S The `mapOfCompatibleSMul : M ⊗[A] N →ₗ[S] M ⊗[R] N` is the same map independently of `S`. This PR adds two lemmas asserting that (one for the underlying AddHom, one for the kernels). I am not quite sure whether the second one is in the optimal shape: It was the shape useful to me, but maybe there is some better way to phrase it or it should be omitted completely (since it follows from the first one...). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
25/11 Mathlib/LinearAlgebra/TensorProduct/Basic.lean 1 32 ['Ljon4ik4', 'Ruben-VandeVelde', 'eric-wieser', 'github-actions', 'mathlib-merge-conflicts', 'ocfnash', 'themathqueen'] eric-wieser
assignee:eric-wieser
5-28791
5 days ago
5-28891
5 days ago
121-60350
121 days
0
45014 GoldenPhysicsProject
author:GoldenPhysicsProject
feat(Analysis/SpecialFunctions/Trigonometric): infinite product formula for sinh Transfers the absolutely convergent Euler product for sine (`euler_sineTerm_tprod`) to the hyperbolic sine, in `Mathlib/Analysis/SpecialFunctions/Trigonometric/Cotangent.lean` next to the sine statement: * `multipliable_one_add_sq_div`: `Multipliable fun n : ℕ ↦ 1 + x ^ 2 / (n + 1) ^ 2` for every `x : ℂ`. * `euler_sinh_tprod`: for `x * I ∈ ℂ_ℤ`, `∏' n : ℕ, (1 + x ^ 2 / (n + 1) ^ 2) = Complex.sinh (π * x) / (π * x)`. This follows a review comment by @wwylele on the first version of this PR, which was a separate file with the conditionally convergent `Tendsto` form. I searched master and the open PRs for an existing hyperbolic-sine product and found none. ----- AI-assistance disclosure: this PR was written and submitted by Claude Code (Anthropic) at the request of the account owner. The account owner has not reviewed the code line by line. The file builds against current master, `lake exe lint-style` is clean, and `#print axioms` shows only `propext`, `Classical.choice` and `Quot.sound`. Please review it as AI-generated. t-analysis new-contributor LLM-generated 19/0 Mathlib/Analysis/SpecialFunctions/Trigonometric/Cotangent.lean 1 11 ['GoldenPhysicsProject', 'github-actions', 'themathqueen', 'wwylele'] nobody
5-19779
5 days ago
33-66605
33 days ago
33-80108
33 days
0
45399 Thmoas-Guan
author:Thmoas-Guan
feat(RingTheory): depth is finite Depth over Noetherian ring is finite. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory 84/0 Mathlib.lean,Mathlib/RingTheory/Depth/Finite.lean,Mathlib/RingTheory/KrullDimension/Module.lean,Mathlib/RingTheory/KrullDimension/Regular.lean 4 7 ['Thmoas-Guan', 'github-actions', 'jjdishere', 'vihdzp'] nobody
5-14607
5 days ago
5-14607
5 days ago
8-48440
8 days
18
32840 joelriou
author:joelriou
refactor(CategoryTheory): remove the old Ext API As it is now possible to compute `Ext`-groups (defined using the derived category) using an injective resolution #32105 or a projective resolution #32816, the old `Ext` API (based on left derived functors) is removed. --- - [x] depends on: #44124 - [x] depends on: #44190 - [x] depends on: #32816 - [x] depends on: #32105 - [x] depends on: #32814 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-category-theory large-import tech debt 283/29 Mathlib.lean,Mathlib/Algebra/Homology/Embedding/Basic.lean,Mathlib/Algebra/Homology/Embedding/CochainComplex.lean,Mathlib/Algebra/Homology/HomotopyCategory/HomComplexIsStrictlyGE.lean,Mathlib/Algebra/Homology/LinearYonedaObj.lean,Mathlib/Algebra/Homology/LocalCohomology.lean,Mathlib/CategoryTheory/Abelian/Ext.lean,Mathlib/CategoryTheory/Linear/Yoneda.lean,Mathlib/RepresentationTheory/Homological/GroupCohomology/Basic.lean,Mathlib/RepresentationTheory/Homological/Resolution.lean 10 9 ['github-actions', 'joelriou', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mathlib4-merge-conflict-bot'] nobody
5-12473
5 days ago
5-13044
5 days ago
27-45379
27 days
0
46049 Thmoas-Guan
author:Thmoas-Guan
feat(RingTheory): lemmas for `reesAlgebra` and associated graded ring This PR add some lemma about `reesAlgebra` and associated graded ring, as a preparation for adic completion of Noetherian ring is Noetherian. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory 67/0 Mathlib/RingTheory/ReesAlgebra.lean 1 1 ['github-actions'] nobody
5-9717
5 days ago
5-14027
5 days ago
5-14948
5 days
5
45931 vihdzp
author:vihdzp
chore(SetTheory/Ordinal/CantorNormalForm): miscellaneous cleanup This PR does a few small things: * Give better names to the arguments of `CNF.rec`, as per our convention on recursors. * Use the `induction` tactic instead of applying `CNF.rec` explicitly. * Generalize `coeff_zero_left` and `coeff_one_left` syntactically, by proving the unapplied versions instead. * Remove a redundant argument from `CNF.opow_mul_add`, and from some theorems that depended on it. * Golf a few other proofs slightly. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #45930 t-set-theory tech debt 79/81 Mathlib/SetTheory/Ordinal/CantorNormalForm.lean 1 2 ['github-actions', 'mathlib-dependent-issues'] nobody
5-1740
5 days ago
5-6845
5 days ago
5-7545
5 days
1
41630 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Paths): a closed walk is a cycle iff `getVert` is injective - `p.IsCycle ↔ Set.InjOn p.getVert (.Iio p.length) ∧ 3 ≤ p.length` - `p.IsCycle ↔ Set.InjOn p.getVert (.Ioc 0 p.length) ∧ 3 ≤ p.length` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #41432 - [x] depends on: #41433 - [x] depends on: #41460 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 42/30 Mathlib/Combinatorics/SimpleGraph/Paths.lean 1 5 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
4-86189
4 days ago
5-5456
5 days ago
5-8559
5 days
0
46135 Lxsoftroxs
author:Lxsoftroxs
feat(Data/{Nat,Int}/ModEq): solvability criterion for two congruences Add the solvability criterion for a pair of congruences, over `ℕ` and `ℤ`: * `Nat.modEq_gcd_of_modEq_of_modEq`, `Int.modEq_gcd_of_modEq_of_modEq`: if `k ≡ a [MOD n]` and `k ≡ b [MOD m]`, then `a ≡ b [MOD gcd n m]`; * `Nat.exists_modEq_and_modEq_iff`, `Int.exists_modEq_and_modEq_iff`: `(∃ k, k ≡ a [MOD n] ∧ k ≡ b [MOD m]) ↔ a ≡ b [MOD gcd n m]`. No assumptions are made on the moduli (zero moduli, and negative moduli over `ℤ`, are allowed). `Nat.chineseRemainder'` already constructs a solution under `a ≡ b [MOD gcd n m]`. Mathlib does not yet state that this condition is also necessary, or the resulting `iff`. Over `ℤ` there is currently no existence statement for two moduli: users go through `Ideal.exists_forall_sub_mem_ideal`, which needs pairwise coprime ideals, or through `ZMod`. The `ℤ` existence proof uses Bézout directly: if `b - a = gcd n m * q`, then `b - m * q * gcdB n m` is a solution. --- **AI disclosure.** These lemmas were found and first proved with an automated pipeline. It used a local LLM prover (BFS-Prover-V2-7B), retrieval over Mathlib and a symbolic certificate search. Each machine proof was checked with `lake env lean`, and the statements with `comparator`. The proofs in this PR were then rewritten in Mathlib style, with Claude's help, and re-checked the same way. I have read and understood the code and will respond to review. The duplicate search, done before opening this PR, found no equivalent: - `exact?` closes none of the statements. - Loogle finds no declaration mentioning both `Nat.ModEq, Nat.gcd, Exists` or `Int.ModEq, Int.gcd, Exists`. - No open or merged PR adds them. #13306, #7532 and #29761 are the ideal-level and `ZMod` versions. - Related Zulip thread (#new-members, "How to use chinese remainder theorem for mutliple modulos"): CRT is noted to be available only for `ℕ`. Checked locally against `master` (`883bd4c`): - both modules build; - `runLinter` and `lint-style` pass; - the 13 direct importers rebuild. Possible conflict: #28631 also edits `Mathlib/Data/Nat/ModEq.lean`. Naming is open to suggestions: e.g. `ModEq.modEq_gcd` for dot notation on the necessity lemma. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01LX9nkpL1i1ovEWvsCPWZZM t-data new-contributor 30/0 Mathlib/Data/Int/ModEq.lean,Mathlib/Data/Nat/ModEq.lean 2 2 ['github-actions'] nobody
4-62040
4 days ago
4-64718
4 days ago
4-64663
4 days
0
46099 DanielJHorton
author:DanielJHorton
feat(LinearAlgebra/PiTensorProduct/Basis): add Free instance for PiTensorProduct This PR adds an instance showing that the tensor product of a finite family of free modules is free, and updates the module docstring in `LinearAlgebra/PiTensorProduct/Basis`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
9/1 Mathlib/LinearAlgebra/PiTensorProduct/Basis.lean 1 2 ['github-actions', 'themathqueen'] nobody
4-58998
4 days ago
5-57390
5 days ago
5-57450
5 days
0
45963 marco-david
author:marco-david
feat(Algebra/Homology/AInfinity): define A-infinity categories Co-authored-by: Zhan Shi <lennox08@tutanota.com> Co-authored-by: Annie Yao <annie.z.yao@gmail.com> Co-authored-by: Justin Mu <justinmu2007@gmail.com> Co-authored-by: Jasper van de Kreeke <jasper.kreeke@berkeley.edu> --- We add the definition of an A∞ category, and introduce a general `Grading` typeclass for its morphism spaces that generalizes Z-gradings and bi- or multigradings. This is a minimal self-contained piece that shows the full stack of new definitions, carved out from the larger development at [marco-david/ainfinity-lean](https://github.com/marco-david/ainfinity-lean), following @joelriou's feedback on #40984, which this PR now supersedes. In order to keep its size reasonable, this PR does not include any examples of the new definition, but in [marco-david/ainfinity-lean](https://github.com/marco-david/ainfinity-lean) we show that our definition is non-vacuous. We show that every dg-category (defined via `EnrichedCategory`) is an A∞-category and that every linear category, concentrated in degree 0, is also an example. Follow-up PRs can add a variety of things to this library: We expect the examples cited above to be useful, so we plan to add them to Mathlib. For our custom type `Grading` we have also developed additional API that allows users to construct product grading types such as ℤ × ℤ, ℤ × ℤ/2ℤ to match their grading conventions. Finally, we have also developed A∞ functors, and are working on A∞ natural transformations and the categorical homotopy transfer theorem. Among the primary producers and consumers of these categories are symplectic geometers, but they also arise in algebraic topology and representation theory. This development will be useful to many formalization efforts in those field. **N.B.:** We are not sure if the file `GradedMultilinearMap` should be placed into the new `AInfinity` folder, or elsewhere, and would appreciate your advice. We are also open to feedback on the new namespace `AInfinity`. **AI Disclosure:** These files were developed throughout many in-person human-to-human meetings and conversations, with LLM feedback and input on many design decisions. Every addition in our separate repository was reviewed by at least one human who wasn't the original author, and these internal reviews, too, were assisted by LLMs. We have further used LLMs to draft initial sketches, help with refactoring, write mechanical proofs, and carve out this minimal set of files and declarations for the first Mathlib PR. (Tools used: GitHub Copilot, Codex Sol / Astra and Claude Opus / Fable, among them primarily Claude Code. I would say "LLM-edited" is a more accurate label than "LLM-generated".) Discussion on [this Zulip thread](https://leanprover.zulipchat.com/#narrow/channel/144837-PR-reviews/topic/Towards.20A.E2.88.9E.20categories.20.28.2340984.29/with/608915845). t-algebra new-contributor LLM-generated
label:t-algebra$
1022/0 Mathlib.lean,Mathlib/Algebra/Homology/AInfinity/AInfinityCategory.lean,Mathlib/Algebra/Homology/AInfinity/AInfinityCategoryStruct.lean,Mathlib/Algebra/Homology/AInfinity/GradedLinearQuiver.lean,Mathlib/Algebra/Homology/AInfinity/GradedMultilinearMap.lean,Mathlib/Algebra/Homology/AInfinity/Grading.lean,Mathlib/Algebra/Homology/AInfinity/Stasheff.lean,Mathlib/Algebra/Homology/AInfinity/StasheffIndex.lean,docs/references.bib 9 2 ['github-actions'] nobody
4-57541
4 days ago
9-59495
9 days ago
9-59440
9 days
0
46078 Hagb
author:Hagb
feat(Order/Hom/Basic): add order isomorphism between subtypes Like `Equiv.subtypeEquivRight` and `Subtype.orderEmbedding`. It is used in #46081 to make life easier, or otherwise it can also be done by `rw!` or `convert`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 11/0 Mathlib/Order/Hom/Basic.lean 1 2 ['github-actions', 'themathqueen'] nobody
4-54974
4 days ago
5-75471
5 days ago
5-78334
5 days
1
43556 teorth
author:teorth
feat(Analysis/SpecialFunctions/Gamma/Digamma): the real digamma function, its asymptotics, and Gauss' series This extends the digamma file with the real digamma function, its logarithmic asymptotics, and Gauss' series for `ψ`. --- Main additions: `Mathlib/Analysis/SpecialFunctions/Gamma/Digamma.lean` * `Real.digamma`, the real digamma function `logDeriv Real.Gamma`, and its real functional equations (`Real.digamma_apply_add_one`, `..._add_nat`, `..._nat_add_one`, `..._one_sub`, `..._two_mul`), obtained from the complex versions via the bridge below. * `Complex.digamma_ofReal : Complex.digamma x = Real.digamma x` (a `simp` lemma, unconditional thanks to matching junk values at the non-positive integers), and `Complex.digamma_eq_re`. * Real asymptotics: `Real.monotoneOn_digamma` (monotone on `Ioi 0`, via log-convexity of `Γ`), `Real.digamma_le_log_le` (`ψ x ≤ log x ≤ ψ (x + 1)`), and `Real.abs_digamma_sub_log_le` (`|ψ x - log x| ≤ 1 / x`). * `Complex.gammaAnalyticSet`, the complement of the non-positive integers, with `isOpen_gammaAnalyticSet`, `isPreconnected_gammaAnalyticSet`, `Complex.differentiableOn_Gamma`, and `Complex.differentiableOn_digamma`. * **Gauss' series** `ψ(s) = -γ + ∑ₙ (1/(n+1) - 1/(s+n))` (`Complex.digamma_eq_gaussSeries`, `Real.digamma_eq_gaussSeries`, `summable_gaussSeries`). The error is shown to vanish on the positive reals (a finite partial-sum identity together with `abs_digamma_sub_log_le`) and to be analytic off the poles, hence zero everywhere by the identity theorem. `Mathlib/Analysis/Complex/RealDeriv.lean` * `logDeriv_comp_ofReal`, `logDeriv_ofReal_comp`, relating the real and complex logarithmic derivatives along the reals. `Mathlib/Analysis/SpecialFunctions/Gamma/Deriv.lean` * Real analogues of the existing complex lemmas: `Real.continuousAt_Gamma`, and non-continuity/non-differentiability of `Real.Gamma` at the non-positive integers. Several complex analysis imports were added to `Digamma.lean` in order to justify the proof of the Gauss identity in the complex case. The code was initially generated by an AI, and then heavily golfed and reviewed by the author. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 464/25 Mathlib/Analysis/Complex/RealDeriv.lean,Mathlib/Analysis/SpecialFunctions/Gamma/BohrMollerup.lean,Mathlib/Analysis/SpecialFunctions/Gamma/Deriv.lean,Mathlib/Analysis/SpecialFunctions/Gamma/Digamma.lean,Mathlib/Data/Nat/Cast/Order/Ring.lean 5 11 ['GoldenPhysicsProject', 'github-actions', 'grunweg', 'mathlib-merge-conflicts', 'metakunt', 'teorth'] urkud
assignee:urkud
4-54677
4 days ago
43-54197
43 days ago
74-62645
74 days
0
31981 jsm28
author:jsm28
feat(Geometry/Euclidean/Incenter): `tangentSet` and `tangentsFrom` lemmas Add lemmas relating the faces of a simplex to `tangentSet` and `tangentsFrom` for an exsphere, in particular for a triangle that any two side lines are the `tangentsFrom` their shared vertex to the insphere or any exsphere. --- <!-- The text above the `---` will become the commit message when your PR is merged. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #31733 - [x] depends on: #31891 - [x] depends on: #31892 - [x] depends on: #31893 - [x] depends on: #31978 - [x] depends on: #31979 - [x] depends on: #31980 - [x] depends on: #32296 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-euclidean-geometry 95/0 Mathlib/Geometry/Euclidean/Incenter/Basic.lean 1 18 ['Parcly-Taxel', 'github-actions', 'jsm28', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'pepamontero', 'wwylele'] YaelDillies
assignee:YaelDillies
4-51257
4 days ago
41-15275
41 days ago
85-79370
85 days
1
38223 Deicyde
author:Deicyde
feat(Geometry/Manifold): add `MfldCat`, the category of `C^n` manifolds Defines `MfldCat 𝕜 n`: the category of `C^n` manifolds over a field `𝕜`, in which the model with corners is allowed to vary between objects. An object bundles a model vector space `E`, a model space `H`, a model with corners `I : ModelWithCorners 𝕜 E H` and a term of `ModelWithCorners.MfldCat I n`--see #41109. This includes manifolds with boundary / corners. For more discussion see this Zulip thread: [#PR reviews > #38223 The Category of C^n Manifolds](https://leanprover.zulipchat.com/#narrow/channel/144837-PR-reviews/topic/.2338223.20The.20Category.20of.20C.5En.20Manifolds/with/587038032) Also added: `ContMDiffMap.id_apply`, `.coe_id` and `.coe_comp` which are comparable to `ContinuousMap` API. ### Future work - ✅ Define a Monoidal structure via product manifolds, analogous to `Manifold.Topology.Category.TopCat.Monoidal` #38560 - ✅ Define the tangent functor: `M ↦ TM`, `F ↦ F.tangentMap` from `MfldCat (n+1) 𝕜` to `MfldCat n 𝕜` #38270 - Functor `FGModuleCat 𝕜 ⥤ MfldCat 𝕜 n` sending a finite-dimensional `𝕜`-vector space to the manifold modeled on itself. Left as `TODO`. - Define `FGModuleCat 𝕜` as an enriched category over `MfldCat n 𝕜`. Then _smooth functors_ can be realized as endofunctors on the enriched category. This is the main motivation for this construction. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #41109 [The category of `C^n` manifolds on a fixed model] [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-differential-geometry new-contributor t-category-theory 210/0 Mathlib.lean,Mathlib/Geometry/Manifold/Category/MfldCat/Basic.lean,Mathlib/Geometry/Manifold/ContMDiffMap.lean 3 63 ['Deicyde', 'chrisflav', 'dagurtomas', 'github-actions', 'idontgetoutmuch', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'peabrainiac'] mattrobball
assignee:mattrobball
4-51254
4 days ago
73-12351
73 days ago
132-52535
132 days
2
42041 FrankieNC
author:FrankieNC
feat(Topology/MetricSpace): minkowski (box-counting) dimension Define the lower and upper Minkowski (box-counting) dimensions of a set in a pseudo-emetric space via covering numbers, prove the basic API (monotonicity, closure invariance, unions, finite sets), and show `dimH s ≤ lowerMinkowskiDim s ≤ upperMinkowskiDim s` (Falconer, Fractal Geometry, Ch. 3). t-topology 354/0 Mathlib.lean,Mathlib/Topology/MetricSpace/Cover.lean,Mathlib/Topology/MetricSpace/CoveringNumbers.lean,Mathlib/Topology/MetricSpace/MinkowskiDimension.lean,docs/references.bib 5 5 ['github-actions', 'wwylele'] alreadydone
assignee:alreadydone
4-51252
4 days ago
75-19633
75 days ago
120-62082
120 days
0
42113 LAC1213
author:LAC1213
feat(RingTheory/Noetherian): injective modules over a Noetherian ring… … surject onto localizations by powers of an element. [Hartshorne III.3.3] Disclaimer: I used Claude to help me find the names of useful lemmas and definitions and explain lean errors to me. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory new-contributor LLM-generated 114/0 Mathlib.lean,Mathlib/Algebra/Module/Torsion/Basic.lean,Mathlib/RingTheory/Noetherian/InjectiveModule.lean 3 46 ['LAC1213', 'NoahW314', 'github-actions', 'robin-carlier', 'tb65536'] alreadydone
assignee:alreadydone
4-51251
4 days ago
118-4416
118 days ago
118-29089
118 days
0
43099 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph): `IsSubwalk` is a partial order and more relation properties --- The instances for `Symm` and `Irrefl` let us use `symm`/`irrefl` and any other mathlib theorems that expect these properties as typeclass arguments. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 31/4 Mathlib/Combinatorics/SimpleGraph/Basic.lean,Mathlib/Combinatorics/SimpleGraph/CompleteMultipartite.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/Connected.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/EdgeConnectivity.lean,Mathlib/Combinatorics/SimpleGraph/Subgraph.lean,Mathlib/Combinatorics/SimpleGraph/Walk/Subwalks.lean 6 1 ['github-actions', 'vlad902'] YaelDillies
assignee:YaelDillies
4-51250
4 days ago
58-77251
58 days ago
88-23570
88 days
1
45034 mkaratarakis
author:mkaratarakis
feat(Combinatorics/Quiver/Path): simple paths, cycles and acyclic quivers `Quiver.Path.IsSimple` and `Quiver.Path.IsCycle`, plus `Quiver.IsAcyclic`, modelled on what we already have for `SimpleGraph.Walk`. The main result is that a path revisiting a vertex can be shortened by cutting out the loop. In particular, a shortest nontrivial loop is a cycle. --- Split from #39916. t-combinatorics 142/0 Mathlib.lean,Mathlib/Combinatorics/Quiver/Path/Cycle.lean 2 11 ['Jun2M', 'YaelDillies', 'github-actions', 'mkaratarakis'] b-mehta
assignee:b-mehta
4-51246
4 days ago
33-76798
33 days ago
33-78614
33 days
1
45999 joelriou
author:joelriou
feat(Geometry/Convex/ConvexSpace): the subdivision operator on affine chains If `Y` is a convex space, we define a subdivision endomorphism `Convexity.ConvexSpace.toSSet.sd` of the chain complex of the simplicial set `toSSet ℝ Y` (i.e. the chain complex of *affine* singular chains). We define `sd` by modifying the identity by a null homotopic map given by a sequence of morphisms (from affine `n`-chains to affine `(n + 1)`-chains) which we define by induction on `n`. Then, by its very definition, we know that `sd` is a chain map that is homotopic to the identity. The lemma `ConvexSpace.toSSet.ι_sd_f_eq_sum` computes the image of a `n`-simplex `s` as an alternating sum (indexed by the symmetric group in `n + 1` letters) of simplices obtained by subdividing `s`. From https://github.com/joelriou/excision --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebraic-topology t-category-theory t-convex-geometry 358/5 Mathlib.lean,Mathlib/Geometry/Convex/ConvexSpace/Barycenter.lean,Mathlib/Geometry/Convex/ConvexSpace/Subdivision.lean 3 1 ['github-actions'] robin-carlier
assignee:robin-carlier
4-51243
4 days ago
8-65342
8 days ago
8-65830
8 days
0
45437 zblore
author:zblore
feat(Analysis/Normed/Module): projective space is Hausdorff and compact This shows `ℙ K V` is Hausdorff when continuous linear forms separate the points of `V`. Here `K` is Hausdorff with continuous multiplication and each unit of `K` acts continuously on `V`. It also shows `ℙ K V` is compact when `V` is a finite-dimensional topological vector space over a locally compact nontrivially normed field like ℝ, ℂ or the p-adics. Hausdorff uses the open quotient map from #44117. Two nonzero vectors span the same line exactly when `f v * g w = f w * g v` for all continuous linear forms `f` and `g`. The same-line relation is an intersection of closed sets. Compactness goes through the compact shell in a proper normed space and then a basis. It also adds an instance that continuous linear forms separate points in a finite-dimensional Hausdorff topological vector space over a complete nontrivially normed field. Mathlib's existing instances need ℝ or ℂ. With it `ℙ K V` is compact and Hausdorff for every finite-dimensional Hausdorff topological vector space `V` over a complete locally compact nontrivially normed field. The Hausdorff part is adapted from the Tau Ceti project's [projective space file](https://github.com/TauCetiProject/TauCeti/blob/06c598245d42977f79bf09aafd3154dd215c23cd/TauCeti/Topology/Algebra/Projectivization.lean). The compactness proof and the separating dual instance are new. This covers the compactness and Hausdorff instances for real projective space in #25999 but not its main result. This is the next step towards the Fubini-Study metric and measure. I asked on Zulip whether this file is in the right place: https://leanprover.zulipchat.com/#narrow/id/634983707 --- I used Claude to draft the Lean against the existing Mathlib API. I used Codex and Claude to review it. I've reworked and checked every line myself and can explain all of it. t-topology t-analysis LLM-generated new-contributor 151/0 Mathlib.lean,Mathlib/Analysis/Normed/Module/Projectivization.lean 2 3 ['github-actions', 'zblore'] nobody
4-50343
4 days ago
24-68231
24 days ago
24-68176
24 days
0
45350 JovanGerb
author:JovanGerb
chore: decapitalize types in theorems According to the naming convention, types need to be decapitalized in theorem names. This PR fixes a few violations. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 69/35 Mathlib/AlgebraicTopology/SimplexCategory/Basic.lean,Mathlib/CategoryTheory/Extensive.lean,Mathlib/CategoryTheory/Monoidal/Comon_.lean,Mathlib/FieldTheory/IsAlgClosed/Classification.lean,Mathlib/GroupTheory/CosetCover.lean,Mathlib/MeasureTheory/Measure/PreVariation.lean,Mathlib/MeasureTheory/VectorMeasure/Variation/Basic.lean,Mathlib/Order/KrullDimension.lean,Mathlib/RingTheory/Regular/RegularSequence.lean,Mathlib/SetTheory/Cardinal/Embedding.lean 10 5 ['github-actions', 'grunweg'] nobody
4-50340
4 days ago
25-50384
25 days ago
25-50576
25 days
0
42093 DrDMT-VR
author:DrDMT-VR
feat(Topology/Algebra/Ring): topological closure of a two-sided ideal Defines `TwoSidedIdeal.closure`, the topological closure of a two-sided ideal in a topological ring, together with its basic API. This mirrors the existing one-sided `Ideal.closure` (`Mathlib/Topology/Algebra/Ring/Ideal.lean`), but is stated in the generality of non-unital non-associative topological rings (`IsTopologicalRing` over `NonUnitalNonAssocRing`), where one-sided ideals are unavailable. New declarations (namespace `TwoSidedIdeal`): `closure`, `coe_closure`, `mem_closure_iff`, `le_closure`, `closure_mono`, `closure_minimal`, `isClosed_closure`, `closure_eq_of_isClosed`, `closure_closure`, `closure_top`, and `closure_ne_top` (in a unital ring whose units are open, e.g. a Banach algebra via `Units.isOpen`, the closure of a proper two-sided ideal is proper). Mathlib has no topological-closure API for `TwoSidedIdeal`. Closed two-sided ideals are the basic objects of C*-algebra ideal theory, and `closure_ne_top` is the standard first step toward "maximal two-sided ideals are closed". ------ - should the definition be called `topologicalClosure` instead? (The current name matches `Ideal.closure`.) - Claude was utilized throughout the project. It helped with coding, syntax and running repetitive testing. t-topology new-contributor LLM-generated 127/0 Mathlib.lean,Mathlib/Topology/Algebra/Ring/TwoSidedIdeal.lean 2 16 ['DrDMT-VR', 'FractalDevTeam', 'github-actions', 'grunweg', 'j-loreaux'] nobody
4-50339
4 days ago
25-64488
25 days ago
63-56564
63 days
0
43539 abhijitaj1997
author:abhijitaj1997
feat(CategoryTheory/Monoidal/Cartesian/Endomorphism): add ring and semiring structures Given two monoidal object in a nice enough category, this show that the monoidal morphisms between then forms an additive group. This additive group is part of a larger semiring structure. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-category-theory 133/0 Mathlib.lean,Mathlib/CategoryTheory/Monoidal/Cartesian/Endomorphism.lean 2 41 ['Multramate', 'abhijitaj1997', 'alreadydone', 'github-actions', 'joelriou', 'robin-carlier'] nobody
4-50337
4 days ago
25-69080
25 days ago
74-28218
74 days
0
41882 theebayuser
author:theebayuser
feat(Data/List): decidability of HasPeriod and periods of repeated lists Hello, this PR extends `Mathlib/Data/List/PeriodicityLemma.lean` with: * a `Decidable (List.HasPeriod w p)` instance (it is a prefix test), and * two directions that relate periods to repetition: * `hasPeriod_flatten_replicate` — `(replicate n l).flatten` has period `l.length` * `eq_flatten_replicate_of_hasPeriod` — a word with period `p` and length `r * p` is the `r`-fold repetition of its length-`p` prefix. This characterizes `r`-th powers of words by a period plus a length constraint, which a future follow-up PR that I plan to work on will use. AI disclosure: This code was mostly generated by Claude Fable 5 and Opus 4.8 as part of my larger project on combinatorics on words, which I then reviewed and revised to contribute to mathlib. t-data LLM-generated new-contributor 56/1 Mathlib/Data/List/PeriodicityLemma.lean 1 8 ['SnirBroshi', 'github-actions', 'theebayuser'] nobody
4-50335
4 days ago
43-36253
43 days ago
127-27950
127 days
0
38745 FordUniver
author:FordUniver
refactor(Combinatorics/SimpleGraph/Copy): align copy count with underlying types Renames `copyCount` to `unlabeledCopyCount` and `labelledCopyCount` to `copyCount` to align them with the underlying `Copy` and `UnlabeledCopy` types. The reuse of `copyCount` is a breaking change without deprecation warning. Co-authored-by: Malte Jackisch <45597826+MaltyBlanket@users.noreply.github.com> --- **Step 2/5 of the `Copy` / `InducedCopy` refactor-feat stack.** Originally motivated by [a discussion](https://github.com/leanprover-community/mathlib4/pull/38631#discussion_r3163732684) in #38631 by @SnirBroshi that the British spelling of `labelled` is deprecated; see also discussion on Zulip ([#general > SimpleGraph.Copy is labeled but copyCount is not](https://leanprover.zulipchat.com/#narrow/channel/113489-new-members/topic/SimpleGraph.2ECopy.20is.20labeled.20but.20copyCount.20is.20not)). The addition of the new `UnlabeledCopy` type was separated into #39307 as a requirement to keep the diff somewhat readable. I also adjusted some docstrings. The double move that results in redefining the meaning of `copyCount` from unlabeled to labeled is not ideal, but [allowed by the style guide](https://mathlib.org/contribute/style.html#deprecation:~:text=We%20allow%2C%20but%20discourage). I think this may be a rare case where it is necessary. - [x] depends on: #39307 t-combinatorics 58/47 Mathlib/Combinatorics/SimpleGraph/Copy.lean 1 26 ['FordUniver', 'SnirBroshi', 'YaelDillies', 'github-actions', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mitchell-horner'] nobody
4-19342
4 days ago
4-21569
4 days ago
15-74248
15 days
5
46149 mcdoll
author:mcdoll
chore(Analysis/Distribution/Sobolev): simplify some proofs Some of the proofs had some issues with `simp [← Lp.toTemperedDistributionCLM_apply, hf, hg]` not working previously. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 26/40 Mathlib/Analysis/Distribution/Sobolev.lean 1 1 ['github-actions'] nobody
4-16646
4 days ago
4-17225
4 days ago
4-17170
4 days
0
41675 joelriou
author:joelriou
feat(AlgebraicTopology): pushout diagrams in the filtration of `Δ[p] ⊗ Δ[1]` This will be used in #42295 in order to construct morphisms from `Δ[p] ⊗ Δ[1]` out of the data of the images of the nondegenerate `(p + 1)`-simplices of `Δ[p] ⊗ Δ[1]`. --- - [x] depends on: #41656 - [x] depends on: #41655 - [x] depends on: #41624 - [x] depends on: #41617 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebraic-topology tech debt 244/13 Mathlib/AlgebraicTopology/SimplicialSet/AnodyneExtensions/UnionProd.lean,Mathlib/AlgebraicTopology/SimplicialSet/ProdStdSimplex.lean,Mathlib/AlgebraicTopology/SimplicialSet/ProdStdSimplexOne.lean,Mathlib/AlgebraicTopology/SimplicialSet/StdSimplex.lean,Mathlib/AlgebraicTopology/SimplicialSet/Subcomplex.lean,Mathlib/CategoryTheory/Monoidal/FunctorCategory.lean 6 19 ['github-actions', 'joelriou', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'robin-carlier'] nobody
4-15555
4 days ago
35-81357
35 days ago
75-9040
75 days
2
43871 manman4
author:manman4
feat(PowerSeries): add Lagrange inversion formula ## What this PR adds This PR formalizes the Lagrange inversion formula for formal power series over commutative rings without additive torsion (`HasUniqueDiv R`), together with divided versions over characteristic-zero fields. For formal power series `P`, `Y`, and `H` over such a ring, suppose `Y = X * P.subst Y`. Then, for every natural number `n`, the Lagrange–Bürmann formula states: ``` (n + 1)[X^{n + 1}]H(Y) = [X^n](H' P^{n + 1}). ``` The brackets denote coefficient extraction, and `H'` denotes the formal derivative of `H`. Over a characteristic-zero field, dividing by `n + 1` gives the usual coefficient formula. ## Proof and scope The proof follows the inductive argument of Surya and Warnke. The torsion-free assumption is used to cancel multiplication by positive natural numbers. Following the review suggestions, this PR is restricted to the torsion-free version. ## Motivation Lagrange inversion is a classical tool in enumerative combinatorics, treated for example in Section 5.4 of Richard P. Stanley’s *Enumerative Combinatorics*, Volume 2. It gives coefficient formulas for implicitly defined generating functions, with applications to counting rooted trees and other recursively defined combinatorial structures. My motivation was to make this tool, which is also used in competitive programming, available in Mathlib. ## LLM We (Julian and I) used Aristotle and Codex for code generation and ChatGPT and Claude for cleanup. t-ring-theory new-contributor LLM-generated 212/0 Mathlib.lean,Mathlib/RingTheory/PowerSeries/Basic.lean,Mathlib/RingTheory/PowerSeries/Derivative.lean,Mathlib/RingTheory/PowerSeries/LagrangeInversion.lean,Mathlib/RingTheory/PowerSeries/Substitution.lean,docs/references.bib 6 126 ['JX-Mo', 'Julian-Kuelshammer', 'github-actions', 'manman4', 'wwylele'] nobody
4-14224
4 days ago
22-14354
22 days ago
67-2860
67 days
0
46007 SnirBroshi
author:SnirBroshi
feat(Topology/Order/ScottTopology): generalize some `IsScott` lemmas from `univ` to any set --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology t-order 89/42 Mathlib/Topology/Order/LawsonTopology.lean,Mathlib/Topology/Order/ScottTopology.lean 2 9 ['SnirBroshi', 'github-actions', 'vihdzp'] nobody
4-13002
4 days ago
8-41619
8 days ago
8-42027
8 days
0
44920 plp127
author:plp127
feat(Algebra/CharP): `natCast_pow_expChar` Prove lemmas `natCast_pow_expChar` and `intCast_pow_expChar`. Also reorganize the `variable`s to be more consistent. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
44/14 Mathlib/Algebra/CharP/Lemmas.lean,Mathlib/Data/Nat/Choose/Lucas.lean,Mathlib/FieldTheory/PurelyInseparable/Exponent.lean 3 3 ['github-actions', 'plp127', 'themathqueen', 'vihdzp'] nobody
4-9899
4 days ago
37-69619
37 days ago
37-70879
37 days
1
46159 Hagb
author:Hagb
feat(Data/List/Sort): generalize the correctness of insertion sort to total relation `IsChain` is preserved by insertion sort with a total relation (not necessarily transitive). --- It was proved but finally unused in favor of #46156 when I tried to proving #46158. I still submitted it since the it is a generalization of existing lemmas. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 23/15 Mathlib/Data/List/Sort.lean 1 1 ['github-actions'] nobody
4-7848
4 days ago
4-11358
4 days ago
4-11303
4 days
0
45811 YaelDillies
author:YaelDillies
feat(Tactic/Positivity): avoid assuming extensions are run with an order The `positivity` extensions for `Nat`-valued functions assume they are run with `q(PartialOrder ℕ)`, which is not necessarily the case: The extension for `Nat.cast` didn't call `core` when run without an order. There are two solutions to this: 1. avoid assuming extensions are run with an order; 2. always run extensions with an order if there is an order. This PR implements option 1 because it makes the extensions cheaper (they need fewer TC searches) and simpler (only touches the `positivity` extensions for concrete-type-valued functions, instead of every call to `core`). Written by Claude Sonnet, reviewed line-by-line by myself. Assisted-by: Claude Sonnet 5.5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) LLM-generated t-meta 141/105 Mathlib/Algebra/Order/Floor/Ring.lean,Mathlib/Analysis/Complex/BorelCaratheodory.lean,Mathlib/Analysis/Complex/Order.lean,Mathlib/Analysis/Complex/UpperHalfPlane/Basic.lean,Mathlib/Combinatorics/Enumerative/DyckWord.lean,Mathlib/Combinatorics/SimpleGraph/Regularity/Bound.lean,Mathlib/Data/Nat/Choose/Multinomial.lean,Mathlib/Data/Nat/Factorial/DoubleFactorial.lean,Mathlib/Data/Nat/Totient.lean,Mathlib/NumberTheory/Height/NumberField.lean,Mathlib/NumberTheory/LucasLehmer.lean,Mathlib/NumberTheory/ModularForms/QExpansion.lean,Mathlib/Tactic/Positivity/Basic.lean,Mathlib/Tactic/Positivity/Finset.lean,MathlibTest/Tactic/Positivity.lean 15 2 ['github-actions', 'mathlib-merge-conflicts'] kim-em
assignee:kim-em
4-4241
4 days ago
4-6169
4 days ago
13-78255
13 days
0
44591 r-irbe
author:r-irbe
feat(Analysis/SpecificLimits/Cesaro): cesaro means of geometrically dominated sequences in normed spaces Adding this because the Cesaro-mean step appears inside ergodic and mixing arguments constantly + mathlib's `SpecificLimits` files do not carry it. It proves that a sequence has convergent Cesaro means with an explicit rate via the following four lemmas: - `norm_sum_range_smul_le_of_norm_le_geometric`: `‖a k‖ ≤ C * r ^ k → ‖n⁻¹ • ∑ a k‖ ≤ (C / (1 - r)) * n⁻¹` in any normed space; - `tendsto_sum_range_smul_nhds_zero_of_norm_le_geometric`: the means tend to zero, via `squeeze_zero_norm'`; The real-valued forms are worked out as full examples in `MathlibTest/Cesaro.lean`, alongside further usage examples including the orbit-average case and serve as documentation for users :) Disclaimer: I used AI for proof golfing. Every proof is kernel-checked and I take full responsibility for the mathematics. t-analysis new-contributor 176/0 Mathlib.lean,Mathlib/Analysis/SpecificLimits/Cesaro.lean,MathlibTest/Cesaro.lean 3 3 ['github-actions'] nobody
4-2637
4 days ago
4-3292
4 days ago
4-3237
4 days
0
43261 YaelDillies
author:YaelDillies
feat(Geometry/Convex): cancellative convex spaces Define cancellative convex spaces as those space where non-trivial convex combinations are injective in any of their inputs. Show that modules, affine spaces, products of cancellative convex spaces, subspaces of cancellative convex spaces... are cancellative convex spaces. Cancellative convex spaces are the correct setting for a large number of convexity concepts. Such a convex space embeds into some (canonical) affine space and therefore satisfies the geometrically intuitive properties of convexity. Non-cancellative convex spaces are pathological from the point of view of polytope theory. [nLab](https://ncatlab.org/nlab/show/convex+space) Generated by Claude Opus, reviewed and golfed by myself. From the Polytopes in Berlin workshop, where participants were confused whether they could generalise their results from affine spaces to convex spaces. Assisted-by: Claude Opus 5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-convex-geometry LLM-generated 210/14 Mathlib/Algebra/Order/GroupWithZero/Basic.lean,Mathlib/Data/Finsupp/Basic.lean,Mathlib/Geometry/Convex/ConvexSpace/AffineSpace.lean,Mathlib/Geometry/Convex/ConvexSpace/Defs.lean,Mathlib/Geometry/Convex/ConvexSpace/Module.lean,Mathlib/Geometry/Convex/ConvexSpace/Prod.lean,Mathlib/Geometry/Convex/Set.lean 7 18 ['YaelDillies', 'b-mehta', 'github-actions', 'martinwintermath', 'mathlib-merge-conflicts', 'ooovi'] nobody
4-1667
4 days ago
20-26640
20 days ago
75-12979
75 days
2
45815 SnirBroshi
author:SnirBroshi
feat(Algebra/GroupWithZero/NonZeroDivisors): `nonZeroDivisors` is a lower set w.r.t. divisibility --- We could also add a `|ᵣ` version (and matching versions for left/right when the monoid is commutative), but I think it's peculiar to use `RightDvd`/`nonZeroDivisorsLeft`/`nonZeroDivisorsRight` when there's commutativity. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
17/0 Mathlib/Algebra/GroupWithZero/NonZeroDivisors.lean 1 3 ['SnirBroshi', 'github-actions', 'jcommelin'] nobody
4-1608
4 days ago
13-70060
13 days ago
13-70005
13 days
0
43983 JX-Mo
author:JX-Mo
chore(RepresentationTheory/Rep/Res): remove a layer on `Rep.res` Define directly `abbrev res (f : H →* G) (A : Rep k G) := of (A.ρ.comp f)` and golf. t-algebra
label:t-algebra$
11/13 Mathlib/RepresentationTheory/Coinduced.lean,Mathlib/RepresentationTheory/Homological/GroupHomology/Functoriality.lean,Mathlib/RepresentationTheory/Rep/Res.lean 3 13 ['JX-Mo', 'Whysoserioushah', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] nobody
3-85027
3 days ago
3-85799
3 days ago
62-64761
62 days
3
36327 themathqueen
author:themathqueen
feat(Analysis/CStarAlgebra/Extreme): a C⋆-algebra is unital iff there exists an extreme point in the closed unit ball In a nonunital C⋆-algebra, the extreme points of the closed unit ball is nonempty iff the C⋆-algebra is unital. Our main reference for this is Sakai's "C⋆-algebras and W⋆-algebras" 1.6.1. The proof however is a _franken-proof_ from both Sakai and Pederson's "C⋆-algebras and their automorphism groups". Co-authored-by: Jon Bannon <59937998+JonBannon@users.noreply.github.com> Co-authored-by: Jireh Loreaux <loreaujy@gmail.com> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #35997 - [x] depends on: #36201 - [x] depends on: #36407 - [x] depends on: #36408 - [x] depends on: #36416 - [x] depends on: #36603 - [x] depends on: #41923 - [x] depends on: #42309 - [x] depends on: #42310 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 233/2 Mathlib/Analysis/CStarAlgebra/Extreme.lean 1 47 ['ADedecker', 'eric-wieser', 'github-actions', 'j-loreaux', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'themathqueen'] YaelDillies
assignee:YaelDillies
3-80636
3 days ago
3-81671
3 days ago
98-65499
98 days
0
46055 WenrongZou
author:WenrongZou
chore(MvPowerSeries): avoid `DefEq` abuse In this PR, we try to fix the `backward.isDefEq.respectTransparency` in `MvPowerSeries` folder --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory tech debt 70/130 Mathlib/RingTheory/MvPowerSeries/Basic.lean,Mathlib/RingTheory/MvPowerSeries/Equiv.lean,Mathlib/RingTheory/MvPowerSeries/Expand.lean,Mathlib/RingTheory/MvPowerSeries/LinearTopology.lean,Mathlib/RingTheory/MvPowerSeries/Order.lean,Mathlib/RingTheory/MvPowerSeries/PiTopology.lean,Mathlib/RingTheory/MvPowerSeries/Substitution.lean,Mathlib/RingTheory/MvPowerSeries/Trunc.lean 8 1 ['github-actions'] nobody
3-79698
3 days ago
6-58830
6 days ago
6-58775
6 days
0
45513 PSchwahn
author:PSchwahn
feat(Data/Fin/Tuple): add Fin.cons_cons_swap `Fin.cons_cons_swap` shows that composing `cons x (cons y q)` with the transposition swapping 0 and 1 yields `cons y (cons x q)`. --- t-data new-contributor 13/0 Mathlib/Data/Fin/Tuple/Basic.lean 1 7 ['PSchwahn', 'github-actions', 'themathqueen'] nobody
3-79524
3 days ago
22-68299
22 days ago
22-68244
22 days
0
46177 WenrongZou
author:WenrongZou
feat(MvPowerSeries/Substitution): order of a difference of substitutions Add lower bounds for the (weighted) order of `f.subst a - f.subst b`. The bound is `n` if every `a s - b s` has order at least `n`. See `le_weightedOrder_subst_sub_subst`. It improves to `n + k` if moreover every `a s` and `b s` has order at least `k`, and for each `s` either `f` has no `X s` term or `a s - b s` has order at least `n + k`. See `add_le_weightedOrder_subst_sub_subst`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory 51/1 Mathlib/RingTheory/MvPowerSeries/Substitution.lean 1 1 ['github-actions'] nobody
3-79484
3 days ago
3-80061
3 days ago
3-80006
3 days
1
45775 Parcly-Taxel
author:Parcly-Taxel
chore: deprecate `NumberTheory.Basic` …by reproving `dvd_sub_pow_of_dvd_sub` (using Codex, with the result hand-golfed) in `Algebra.Ring.GeomSum`. `dvd_geom_sum₂_self` naturally falls out of the proof and is moved back accordingly. t-algebra LLM-generated
label:t-algebra$
22/47 Mathlib/Algebra/Ring/GeomSum.lean,Mathlib/NumberTheory/Basic.lean,Mathlib/NumberTheory/Multiplicity.lean,Mathlib/RingTheory/WittVector/Frobenius.lean,Mathlib/RingTheory/WittVector/StructurePolynomial.lean 5 6 ['Parcly-Taxel', 'github-actions', 'mathlib-merge-conflicts', 'xroblot'] nobody
3-77949
3 days ago
14-51732
14 days ago
14-69264
14 days
0
46180 Nicola9Falciola
author:Nicola9Falciola
chore(Algebra/Module/Submodule/Invariant): remove all the `set_option` in the fille and api This PR removes all the defeq abuse in the file and adds small API lemmas such as the compatibility between `invtSubmodule` and `compatibleMaps`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt
label:t-algebra$
21/14 Mathlib/Algebra/Module/Submodule/Invariant.lean 1 8 ['Nicola9Falciola', 'github-actions', 'themathqueen'] nobody
3-73810
3 days ago
3-77893
3 days ago
3-77838
3 days
0
46182 DanielJHorton
author:DanielJHorton
chore(LinearAlgebra/Prod): deprecate `fst_sup_snd` and `fst_inf_snd` In #46131 the proofs of `Submodule.fst_sup_snd` and `fst_inf_snd` were both reduced to a single call to the `IsCompl` API. This PR deprecates these two theorems. The reasoning is: - Now that we have `Submodule.isCompl_fst_snd` an end-user can simply replace `fst_sup_snd R M N` with `(isCompl_fst_snd R M N).sup_eq_top` and `fst_inf_snd R M N` with `(isCompl_fst_snd R M N).inf_eq_bot`, so these theorems no longer provide that much value. - If we were to keep these theorems, then (to my mind) the natural follow up is to look at the rest of the `IsCompl` API. One could envision other theorems like `fst_ne_snd ... := (isCompl_fst_snd ...).ne`, `disjoint_fst_snd ... := (isCompl_fst_snd ...).disjoint`, `codisjoint_fst_snd ... := (isCompl_fst_snd ...).codisjoint`, etc... Copying over the whole `IsComl` API would obviously be far too much code duplication, so why give these two theorems special treatment? --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
2/0 Mathlib/LinearAlgebra/Prod.lean 1 1 ['github-actions'] nobody
3-73229
3 days ago
3-74914
3 days ago
3-74859
3 days
0
45312 Nicola9Falciola
author:Nicola9Falciola
feat(LinearAlgebra): add det and charpoly of an endomorphism preserving complementary submodules and simplify proofs This PR adds the formulas for computing the determinant and the `charpoly` of a linear map when there exist two complementary sub-modules stable with respect of that map. With this new lemmas I simplify the proof of `finrank_maxGenEigenspace_zero_eq ` that do not require anymore the choice of a basis. It also adds the description of an endomorphism `f ` via the conjugation by `prodEquivOfIsCompl` as the product map of the restriction of `f` on the complementary sub-modules. It also adds missing API for `.reflection` proving a simplification of the proof of `det_reflection` that do not requires the choice of a basis anymore. Changes per file : - Analysis/InnerProductSpace/Projection/FiniteDimensional : goofing of the proof of `det_reflection` - Analysis/InnerProductSpace/Projection/Reflection : add missing API for the description of `K.reflection.toLinearMap` on `K` and its orthogonal complement and its restriction on the them. - LinearAlgebra/Charpoly/ToMatrix : add the formula describing the charateristic polynomial of and endomorphism in terms of the product of the charateristic polynomials of its restrictions. - LinearAlgebra/Determinant : add the formula describing the determinant of and endomorphism in terms of the product of the determinats of its restrictions. - LinearAlgebra/Eigenspace/Zero : goofing the proof of `finrank_maxGenEigenspace_zero_eq`. - LinearAlgebra/Projection : add the description of conjugation of the equivalence `prodEquivOfIsCompl.symm` on the endomorphisms of `E`. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
61/29 Mathlib/Analysis/InnerProductSpace/Projection/FiniteDimensional.lean,Mathlib/Analysis/InnerProductSpace/Projection/Reflection.lean,Mathlib/LinearAlgebra/Charpoly/ToMatrix.lean,Mathlib/LinearAlgebra/Determinant.lean,Mathlib/LinearAlgebra/Eigenspace/Zero.lean,Mathlib/LinearAlgebra/Projection.lean 6 29 ['Nicola9Falciola', 'github-actions', 'riccardobrasca', 'themathqueen'] nobody
3-72628
3 days ago
4-22882
4 days ago
26-31112
26 days
1
46178 DanielJHorton
author:DanielJHorton
feat(LinearAlgebra/PiTensorProduct/Generators): add theorems relating `equivPiTensorComplSingletonTensor` and `map` This PR adds three new theorems which provide identities relating the composition of `equivPiTensorComplSingletonTensor` (and its inverse) with `PiTensorProduct.map`. These new theorems do not require any backwards compatibility options, but they do depend on `equivPiTensorComplSingletonTensor_tprod` which does (see adaption note for more details). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
25/0 Mathlib/LinearAlgebra/PiTensorProduct/Generators.lean 1 1 ['github-actions'] nobody
3-70622
3 days ago
3-73575
3 days ago
3-73982
3 days
0
43139 plp127
author:plp127
feat: make `MvPFunctor` universe-polymorphic We mirror what is done for the univariate `PFunctor` and make `MvPFunctor` universe-polymorphic. Certain declarations are kept not universe polymorphic for now, including `MvQPF` and many things relating to the `W` and `M` types being fixpoints. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data increases-technical-debt 131/106 Mathlib/Data/PFunctor/Multivariate/Basic.lean,Mathlib/Data/PFunctor/Multivariate/M.lean,Mathlib/Data/PFunctor/Multivariate/W.lean,Mathlib/Data/QPF/Multivariate/Basic.lean,Mathlib/Data/QPF/Multivariate/Constructions/Cofix.lean,Mathlib/Data/QPF/Multivariate/Constructions/Fix.lean 6 6 ['eric-wieser', 'github-actions', 'mathlib-merge-conflicts', 'plp127'] eric-wieser
assignee:eric-wieser
3-69654
3 days ago
4-10307
4 days ago
87-59903
87 days
0
45602 vihdzp
author:vihdzp
feat: `ClosedIicTopology` on partial order is T0 We can't guarantee T1, take e.g. the Sierpinski topology. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology t-order maintainer-merge 10/40 Mathlib/Topology/Order/LowerUpperTopology.lean,Mathlib/Topology/Order/OrderClosed.lean,Mathlib/Topology/Order/ScottTopology.lean 3 4 ['github-actions', 'leanprover-radar', 'themathqueen', 'vihdzp'] nobody
3-69356
3 days ago
19-45939
19 days ago
19-46021
19 days
0
41289 D-Thomine
author:D-Thomine
feat(Dynamics): recurrents set and refactoring of conservative maps This PR deals mostly with `Dynamics.Conservative`. The notion of *recurrent set* is introduced: a set `s` is recurrent if almost every point in `s` returns to `s`. Most properties of conservative maps actually apply to recurrent sets. The definition of conservative map is changed to align with this notion of recurrent set (a map is conservative if every measurable set is recurrent). Theorem `MeasureTheory.conservative_iff_exists_mem_iterate_mem` expresses the equivalence of the new definition with the older one. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-dynamics 331/113 Mathlib/Dynamics/Ergodic/Conservative.lean,Mathlib/Dynamics/Ergodic/MeasurePreserving.lean,Mathlib/MeasureTheory/Measure/QuasiMeasurePreserving.lean,Mathlib/Order/Filter/CountableInter.lean,Mathlib/Order/Interval/Finset/Basic.lean 5 33 ['D-Thomine', 'github-actions', 'mathlib-merge-conflicts', 'mcdoll'] urkud
assignee:urkud
3-68844
3 days ago
3-71901
3 days ago
123-10732
123 days
0
44230 wwylele
author:wwylele
feat(Geometry/Euclidean): prove Euler's theorem in geometry This proves https://en.wikipedia.org/wiki/Euler%27s_theorem_in_geometry --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #44060 - [x] depends on: #44102 - [x] depends on: #44148 (this is not really using Heron's formula, but it is appending to the same file so I made it a code dependency) t-euclidean-geometry 111/0 Mathlib/Geometry/Euclidean/Incenter/Basic.lean,Mathlib/Geometry/Euclidean/Volume/Incenter.lean,Mathlib/Geometry/Euclidean/Volume/Triangle.lean,docs/1000.yaml 4 9 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'vihdzp', 'wwylele'] jsm28
assignee:jsm28
3-68161
3 days ago
3-68637
3 days ago
4-77173
4 days
1
45498 ShirinShafaie
author:ShirinShafaie
feat(LinearAlgebra): identify Sp₂(R) with SL₂(R) This PR resolves the TODO in `Mathlib.LinearAlgebra.SymplecticGroup`: > For `n = 1` the symplectic group coincides with the special linear group. I formalised this as an explicit group isomorphism between the two-dimensional symplectic group and `SL₂(R)`, over any commutative ring. The proof is developed in five steps: 1. **Determinant formula.** I first established the two-by-two determinant formula for matrices indexed by `ι ⊕ m`, with a chosen index in each of the two subsingleton types. This gives the reusable public theorem `Matrix.det_subsingleton_sum_subsingleton`. 2. **Symplectic characterisation.** Using this formula and the existing block-matrix characterisation of symplectic matrices, I proved that a matrix indexed by `ι ⊕ ι` for a subsingleton `ι` is symplectic if and only if its determinant is one. This gives `SymplecticGroup.mem_subsingleton_iff_det_eq_one`. 3. **Group equivalence.** The determinant-one characterisation then gives `subsingletonEquivSpecialLinear`, a group equivalence between the symplectic group and the special linear group on `m ⊕ m` for any finite subsingleton `m`, without changing the underlying matrices. 4. **Reindexing to `Fin 2`.** The symplectic matrices are indexed by `Fin 1 ⊕ Fin 1`, while the usual `SL₂(R)` is indexed by `Fin 2`. I initially implemented the required general reindexing equivalence for special linear groups in [PR 45495](https://github.com/leanprover-community/mathlib4/pull/45495). It was then pointed out that [PR 44094](https://github.com/leanprover-community/mathlib4/pull/44094) was already developing a more general `Matrix.SpecialLinearGroup.reindex` API, so PR 45495 was closed in favour of that work. Now that PR 44094 has merged, this PR uses the resulting `SpecialLinearGroup.reindex` equivalence directly. Composing it with `subsingletonEquivSpecialLinear R (Fin 1)` gives `finOneEquivSL2`, closing the original TODO. 5. **Supporting lemmas and integration.** I added simp lemmas describing the forward and inverse equivalences, replaced the original TODO with a pointer to the new result, and included the new module in `Mathlib.lean`. I came across this TODO while taking the Shared Graduate Course, *Elements of Mathematical Formalization and Auto-Formalization with Lean*, at the Fields Institute. I started working on it as a project alongside the course exercises, and discussed an earlier version in a private review. That feedback led me to investigate several alternatives, including the generalisation to singleton index types. Throughout the project, I worked with OpenAI Codex and GPT-6 to explore proof approaches, work through Lean implementation details and test alternative formulations. I evaluated these against the mathematics and the existing mathlib definitions, made the final choices about the theorem statements, proof structure and supporting lemmas, and personally ran the builds and verification in VS Code. I take responsibility for the final formalisation and the code submitted here. **Checks:** `lake build Mathlib.LinearAlgebra.SymplecticGroup.SpecialLinearGroup`, `lake exe mk_all --check`, and `lake exe lint-style` all passed. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #44094 LLM-generated t-algebra new-contributor
label:t-algebra$
129/2 Mathlib.lean,Mathlib/LinearAlgebra/Matrix/Determinant/Basic.lean,Mathlib/LinearAlgebra/SymplecticGroup.lean,Mathlib/LinearAlgebra/SymplecticGroup/SpecialLinearGroup.lean 4 20 ['ShirinShafaie', 'github-actions', 'mathlib-dependent-issues', 'themathqueen'] nobody
3-66979
3 days ago
3-67734
3 days ago
19-21789
19 days
0
45001 TJHeeringa
author:TJHeeringa
feat(Analysis/InnerProductSpace): add polar_li The polar of a continuous linear map T is the partial linear isometry U which satisfies T = U|T|. This PR adds the map U as an isometry on the part that it is a linear isometry. --- This PR is split of from #44525, which is a draft for the Schatten operators. The API I put here is limited as this is all what is needed to define the full polar and the Schatten p-norms. If more is desired in this PR, then I'd be happy to add it. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #44997 t-analysis 100/0 Mathlib.lean,Mathlib/Analysis/InnerProductSpace/Polar.lean 2 7 ['TJHeeringa', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'themathqueen'] nobody
3-66233
3 days ago
3-68245
3 days ago
3-72514
3 days
2
45952 marcelolynch
author:marcelolynch
ci: add a Merge checks job for mathlib-ci pins and usage This PR adds a "Merge checks" job to `build_template.yml`. Bors requires it. Rule violations fail the job on `staging` and `trying`. Other runs report warnings so PRs can test unmerged changes. The job reads PR files under `.github/` and runs no PR code. It checks: - Pinned mathlib-ci commits belong to mathlib-ci `master`. Unmerged commits can expose mathlib4 secrets when other jobs execute them. - Literal `$CI_SCRIPTS_DIR/<path>` references exist at the default mathlib-ci commit pinned by the PR. - Workflows use `get-mathlib-ci` for mathlib-ci checkouts. These usage checks replace `validate_mathlib_ci_paths.yml`. 🤖 CI 174/240 .github/workflows/build_template.yml,.github/workflows/validate_mathlib_ci_paths.yml,bors.toml,docs/workflows.md 4 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
3-65507
3 days ago
3-69684
3 days ago
9-61053
9 days
0
45175 marcelolynch
author:marcelolynch
chore(scripts): use the module system in scripts Convert eight `scripts/*.lean` files to the module system and remove `allowNonModules` from the `mk_all` and `check_title_labels` executables. 45/23 Mathlib/Util/GetAllModules.lean,lakefile.lean,scripts/autolabel.lean,scripts/check-title-labels.lean,scripts/create_deprecated_modules.lean,scripts/extract-unique-nonascii.lean,scripts/find_command_range.lean,scripts/mk_all.lean,scripts/nightly-testing-checklist.lean 9 6 ['github-actions', 'grunweg', 'marcelolynch', 'mathlib-merge-conflicts'] grunweg
assignee:grunweg
3-65262
3 days ago
3-69635
3 days ago
26-23717
26 days
0
46190 WenrongZou
author:WenrongZou
feat: continuous characters of profinite groups have open kernel In this PR, we add - `Circle.isOpen_ker_of_continuous`: a continuous homomorphism from a profinite group to `Circle` has open kernel. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 12/0 Mathlib/Analysis/SpecialFunctions/Complex/Circle.lean 1 1 ['github-actions'] nobody
3-64845
3 days ago
3-65369
3 days ago
3-65314
3 days
0
45280 themathqueen
author:themathqueen
feat(LinearAlgebra): complexification of real spaces This provides the basic framework for complexifying spaces (module structures, star structures, and algebra structures). We also provide some API for complexifying linear operators. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
353/0 Mathlib.lean,Mathlib/LinearAlgebra/Complexification/Basic.lean,docs/references.bib 3 18 ['eric-wieser', 'faenuccio', 'github-actions', 'j-loreaux', 'themathqueen'] j-loreaux
assignee:j-loreaux
3-61641
3 days ago
16-69862
16 days ago
17-44363
17 days
2
45625 grunweg
author:grunweg
chore(Geometry/Manifold/VectorBundle): rename iff lemmas about differentiability to mention iff All these lemmas characterise differentiability using a trivialization, hence could mention `iff` as part of their name. They should, since there exist conceivable statements of the same name without the `iff` (e.g., about some section being differentiable). This also increases naming consistency: a number of similar lemmas in that file already use the `iff` naming. Zulip discussion supporting this: [#mathlib4 > Naming convention @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Naming.20convention/near/636496147) Continuation of #45588. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-differential-geometry 34/22 Mathlib/Geometry/Manifold/VectorBundle/ContinuousAlternatingMap.lean,Mathlib/Geometry/Manifold/VectorBundle/Hom.lean,Mathlib/Geometry/Manifold/VectorBundle/MDifferentiable.lean,Mathlib/Geometry/Manifold/VectorBundle/Riemannian.lean 4 2 ['github-actions', 'mathlib-merge-conflicts'] ocfnash
assignee:ocfnash
3-60056
3 days ago
3-60560
3 days ago
18-26010
18 days
1
45791 JonasReif
author:JonasReif
chore: remove obsolete proof workarounds Several proofs still carried workarounds marked by TODOs, porting notes, an adaptation note, or `erw`, for problems that have since been fixed: the missing lemmas now exist, or Lean no longer needs the hint. This PR removes those workarounds. Only proofs change; every statement stays the same. - `PullbackCone.isLimitOfFactors`: use `t.condition_assoc h` instead of the manual reassoc workaround - `Scheme.basicOpen_add_le`: use `Opens.mem_sup` (resolves the TODO) - `Cardinal.toNat_congr`: use `mk_congr_lift`, dropping the universe hint - `LieIdeal.map_of_image`: replace `erw [h]` with `exact h.subset` - `isPullback_inl_inl_coprodMap`: plain `simp` works now that `Scheme.Hom.mem_opensRange` exists (resolves the TODO) - `Proj.fromOfGlobalSections_preimage_basicOpen`: use `Scheme.Hom.mem_preimage` (resolves the TODO) - `Tuple.graph.card`: one-line injectivity proof - `StarModule.decomposeProdAdjoint`: drop the `erw` and its outdated note - `skyscraperPresheaf_isSheaf`: the universe annotation is no longer needed --- Created with Claude Opus 5.5 in Claude Code. 🤖 Generated with [Claude Code](https://claude.com/claude-code) tech debt new-contributor 11/29 Mathlib/Algebra/Lie/Ideal.lean,Mathlib/Algebra/Star/Module.lean,Mathlib/AlgebraicGeometry/Limits.lean,Mathlib/AlgebraicGeometry/ProjectiveSpectrum/Basic.lean,Mathlib/AlgebraicGeometry/Scheme.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/Mono.lean,Mathlib/Data/Fin/Tuple/Sort.lean,Mathlib/SetTheory/Cardinal/ToNat.lean,Mathlib/Topology/Sheaves/Skyscraper.lean 9 9 ['JonasReif', 'Parcly-Taxel', 'github-actions', 'grunweg'] nobody
3-57803
3 days ago
3-60552
3 days ago
4-8480
4 days
0
44802 wwylele
author:wwylele
feat(MeasureTheory/Lebesgue): one-dimensional Brunn–Minkowski theorem This is the starting point of upstreaming https://github.com/hojonathanho/isoperimetric (with author's permission at https://github.com/hojonathanho/isoperimetric/issues/1) for the general Brunn–Minkowski theorem. The proof strategy follows https://terrytao.wordpress.com/2011/09/16/the-brunn-minkowski-inequality-for-nilpotent-groups/, which goes like: 1-d Brunn–Minkowski -> 1-d Prékopa-Leindler -> n-d Prékopa-Leindler -> n-d Brunn–Minkowski Co-authored-by: Jonathan Ho <hojonathanho@gmail.com> --- ~~As far as I know, no AI was used (except for my request for copilot review below, which returned nothing)~~ There was a major revision to this PR. The first version was written without AI, which proved the statement `MeasurableSet A -> MeasurableSet B -> nonemptiness -> volume A + volume B ≤ volume (A + B)`. This was then re-written using an Aristotle generated proof (see https://github.com/leanprover-community/mathlib4/pull/44802#issuecomment-6146960763), which removes the measurability hypothesis and generalize the theorem to partially ordered monoid + pull-back (sub-)invariant measure (so this would also work on e.g. NNReal). The AI-generated proof has been restructured by me manually. On the topic of generalization of the ` μ A + μ B ≤ μ (A + B)`-like inequality, there is also [Kemperman's theorem](https://terrytao.wordpress.com/2011/12/26/a-variant-of-kempermans-theorem/) which holds for locally compact connected groups, which includes `Real`. The proof of this is beyond my ability at the moment, plus it still generally requires measurability, plus it requires a group instead of a just a magma. So the generalization to ordered magma is an interesting one on its own, and I chose to go in that direction in this PR <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability LLM-generated 76/4 Mathlib/MeasureTheory/Measure/Interval.lean,Mathlib/MeasureTheory/Measure/Lebesgue/Basic.lean,Mathlib/Topology/Order/Basic.lean 3 17 ['SnirBroshi', 'copilot-pull-request-reviewer', 'github-actions', 'wwylele'] RemyDegenne
assignee:RemyDegenne
3-57401
3 days ago
38-394
38 days ago
38-78815
38 days
1
43461 mcdoll
author:mcdoll
feat(Analysis/SchwartzMap): missing lemmas about inverse Fourier transform Adds lemmas that are already present for the Fourier transform, plus a pair of lemmas for the relation to the `L1` Fourier transform. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 55/1 Mathlib/Analysis/Distribution/SchwartzSpace/Fourier.lean 1 7 ['github-actions', 'mcdoll', 'sgouezel'] sgouezel
assignee:sgouezel
3-53095
3 days ago
78-12926
78 days ago
78-12871
78 days
1
46150 vihdzp
author:vihdzp
feat: more precise characterizations of `IsLUB s (sSup s)` for `s : Set (WithTop α)` Used in the CGT repo. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 51/14 Mathlib/Order/ConditionallyCompleteLattice/WithTop.lean 1 2 ['astrainfinita', 'github-actions'] nobody
3-51410
3 days ago
4-14321
4 days ago
4-14266
4 days
0
42630 will1491
author:will1491
feat(Analysis/Complex): define Wirtinger derivatives Define the Wirtinger derivatives `Complex.wirtingerDeriv` and `Complex.wirtingerDerivBar` from `fderiv ℝ`, and prove: the Cauchy-Riemann characterization of complex differentiability (pointwise and on open sets), agreement of `wirtingerDeriv` with `deriv` for holomorphic functions, additivity, Leibniz product rules, conjugation identities, both Wirtinger chain rules, and the Wirtinger decomposition of a real-linear map `ℂ →L[ℝ] ℂ`. Extracted from https://github.com/will1491/RiemannDynamics, where it underlies the Beltrami-equation and Cauchy/Beurling-transform theory used in the proof of the measurable Riemann mapping theorem. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis new-contributor 253/0 Mathlib.lean,Mathlib/Analysis/Complex/Wirtinger.lean 2 6 ['Maldooor', 'github-actions', 'mathlib-merge-conflicts', 'will1491'] j-loreaux
assignee:j-loreaux
3-51257
3 days ago
72-65340
72 days ago
103-40926
103 days
0
42912 justin-palumbo
author:justin-palumbo
feat(Topology/GDelta): a completely metrizable subspace of a T6 space is Gδ Adds TopologicalSpace.IsCompletelyMetrizableSpace.isGδ: a completely metrizable subspace of a T6 space is Gδ This is one direction of a foundational fact in descriptive set theory --- the Polish subspaces of a Polish space are exactly the Gδ subsets. The proof here is modeled on the exposition in Anush Tserunyan's descriptive set theory notes https://www.math.mcgill.ca/atserunyan/Teaching_notes/dst_lectures.pdf, with one adjustment; to make the formalization easier and avoid having multiple distance metrics instantiated at the same time, instead of directly defining open `U_n` with `s = ⋂ n, U` define them such that `s = closure s ∩ ⋂ n, U n` and then appeal to the fact closed sets are Gδ in a perfectly normal space. --- - [x] depends on: #42896 [which fixes buggy naming present in Topology/Metrizable/CompletelyMetrizable] This can be viewed as a companion to #42693, which - under the stronger assumption of the ambient space being Polish - establishes the other direction --- a Gδ subspace of a Polish space is itself Polish. Together, these give Alexandrov's theorem, characterizing the Polish subspaces of an ambient Polish space as exactly the Gδ ones, and (via `Metric.PiNatEmbed.exists_embedding_to_hilbert_cube`) Polish spaces as exactly the Gδ subsets of the Hilbert cube. If and when both these PRs are committed, I anticipate adding these consequences to Topology/MetricSpace/Polish.lean LLM usage: I wrote the initial version myself, while using Google's free "AI mode" to help me find relevant lemma names in the codebase, and afterward used helped Claude Opus to review, which led to simplifying some of the arguments. I take full responsibility for the code here t-topology new-contributor 91/0 Mathlib.lean,Mathlib/Topology/GDelta/CompletelyMetrizable.lean 2 8 ['github-actions', 'justin-palumbo', 'mathlib-dependent-issues', 'plp127'] j-loreaux
assignee:j-loreaux
3-51255
3 days ago
95-8038
95 days ago
95-8280
95 days
0
43440 Raph-DG
author:Raph-DG
feat(AlgebraicGeometry): serre's R_k condition for schemes In this PR, we define Serre's R_k condition. We also show that R_1 is equivalent to all local rings in codimension one being DVRs, though we show this under the assumption that the local rings are all domains. This assumption can be dropped once #28683 is merged. AI disclosure: assisted by claude opus 5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebraic-geometry 104/0 Mathlib.lean,Mathlib/AlgebraicGeometry/RegularInCodimension.lean 2 14 ['Brian-Nugent', 'Raph-DG', 'github-actions', 'justus-springer'] alreadydone
assignee:alreadydone
3-51254
3 days ago
68-62333
68 days ago
78-45085
78 days
0
43478 plp127
author:plp127
feat(Data/PFunctor): pointfree lemmas for map Prove `PFunctor.map_id` and `PFunctor.map_comp_map`, pointfree analogues of `PFunctor.id_map` and `PFunctor.map_map`. The names are chosen to match the corresponding lemmas for `LawfulFunctor`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data easy 5/0 Mathlib/Data/PFunctor/Univariate/Basic.lean 1 1 ['github-actions'] TwoFX
assignee:TwoFX
3-51251
3 days ago
77-41902
77 days ago
77-41989
77 days
0
46147 felixpernegger
author:felixpernegger
perf(CategoryTheory): write down some universe parameters explicitly --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-category-theory 9/6 Mathlib/CategoryTheory/Sites/SheafCohomology/Basic.lean,Mathlib/CategoryTheory/Sites/SheafCohomology/ExactSequences.lean,Mathlib/CategoryTheory/Sites/SheafCohomology/MayerVietoris.lean 3 8 ['felixpernegger', 'github-actions', 'leanprover-radar', 'robin-carlier'] joelriou
assignee:joelriou
3-51246
3 days ago
4-38309
4 days ago
4-38276
4 days
0
42142 philipp-svinger
author:philipp-svinger
feat(Analysis/ODE): peano existence theorem, Tonelli approximation 1 Add Tonelli approximation method for ODEs. Implement the structure IsPeano similar to IsPicardLindelof. Construct a sequence of approximations using Tonelli technique. First step towards Peano existence Co-authored-by: Florian Grube <fgrube@math.uni-bielefeld.de> Co-authored-by: Paul Niessner <pniessner@math.uni-bielefeld.de> Co-authored-by: Julian Rolfes <jrolfes@math.uni-bielefeld.de> Co-authored-by: Luke Schleef <lschleef@math.uni-bielefeld.de> Co-authored-by: Philipp Svinger <psvinger@math.uni-bielefeld.de> --- We want to add the proof of the Peano existence theorem for ODEs, using Tonelli approximations. This will be a series of PRs working towards this goal. In this first PR, we implement the structure IsPeano similar to IsPicardLindelof and construct a sequence of approximations using Tonelli technique. See our further PRs for more information, last: #42148 --- The statements, definitions and proofs were written without AI. AI was used afterwards to help us to adapt our code to the style and naming conventions. We also used it in the process of writing a documentation. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis new-contributor 207/0 Mathlib.lean,Mathlib/Analysis/ODE/Peano.lean 2 24 ['github-actions', 'mcdoll', 'philipp-svinger', 'sgouezel'] nobody
3-50352
3 days ago
57-69688
57 days ago
114-32670
114 days
5
46202 gloges
author:gloges
feat(Analysis/InnerProductSpace): inner products for `PiTensorProduct` Following up on #45819, adds inner products for pi tensor products `⨂[𝕜] i : ι, E i` of 𝕜-inner product spaces `E i`. This follows [Mathlib.Analysis.InnerProductSpace.TensorProduct](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Analysis/InnerProductSpace/TensorProduct.html) fairly closely. - The inner product is defined by lifting the product of the component inner products, so that `⟪⨂ₜ[𝕜] i, x i, ⨂ₜ[𝕜] i, y i⟫ = ∏ i, ⟪x i, y i⟫`. - `exists_finite_submodule_of_setFinite` (which itself depends on `range_map_mono` and `range_mapIncl_mono`) is required for `InnerProductSpace.Core`, following the proof strategy used for [TensorProduct.instNormedAddCommGroup](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Analysis/InnerProductSpace/TensorProduct.html#TensorProduct.instNormedAddCommGroup) in which `inner_self` relies on having finite orthonormal bases. - Includes linear isometry (equivelence) versions of `PiTensorProduct.map`, `PiTensorProduct.congr`, `PiTensorProduct.mapIncl`, `PiTensorProduct.reindex`, `PiTensorProduct.isEmptyEquiv`, `PiTensorProduct.subsingletonEquiv`, and their basic properties. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor 344/0 Mathlib.lean,Mathlib/Analysis/InnerProductSpace/PiTensorProduct.lean,Mathlib/LinearAlgebra/PiTensorProduct/Basic.lean,Mathlib/LinearAlgebra/PiTensorProduct/Finite.lean 4 3 ['github-actions', 'gloges'] nobody
3-48589
3 days ago
3-49081
3 days ago
3-49026
3 days
0
45870 ocfnash
author:ocfnash
feat: generalise `AddCircle.ae_empty_or_univ_of_forall_vadd_ae_eq_self` I asked Sébastien Gouëzel how to prove this in Leiden in July 2023 and he showed me on a blackboard. I've been meaning to PR it ever since. Claude made it so easy I no longer had an excuse! --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-dynamics 64/43 Mathlib/Dynamics/Ergodic/AddCircle.lean 1 1 ['github-actions'] mcdoll
assignee:mcdoll
3-45497
3 days ago
11-75546
11 days ago
11-75491
11 days
0
45950 kac3pro
author:kac3pro
feat: defining the Gauss map and gauss measure This PR defines the Gauss map and the Gauss measure on [0,1). This is the beginning of the work on connecting the theory of continued fractions to dynamics. LLM usage: LLMs were used primarily as a way to quickly search for relevant lemmas/techniques in the mathlib. All the code is human written. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-dynamics new-contributor 124/0 Mathlib.lean,Mathlib/Dynamics/Ergodic/GaussMap.lean 2 4 ['EtienneC30', 'github-actions', 'lua-vr'] mcdoll
assignee:mcdoll
3-45390
3 days ago
9-83272
9 days ago
9-83217
9 days
0
35561 Thmoas-Guan
author:Thmoas-Guan
feat(RingTheory): power series over regular local ring In this PR, we proved that power series over regular local ring is again regular local ring. Same for finite multivariable power series. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #28682 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 63/0 Mathlib.lean,Mathlib/RingTheory/RegularLocalRing/PowerSeries.lean 2 6 ['github-actions', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] mattrobball
assignee:mattrobball
3-43342
3 days ago
78-42217
78 days ago
88-83135
88 days
2
46213 mcdoll
author:mcdoll
feat(Analysis/SchwartzMap): integration by parts with inner product Adds definitions for the (continuous) bilinear inner product over a `RCLike` inner product space (morally this is restriction of `innerSL`) and proves the integration by parts formula for line derivatives and laplacian. We also do some slight variable and section reorder, because they were in slightly weird places. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 73/12 Mathlib/Analysis/Distribution/SchwartzSpace/Deriv.lean,Mathlib/Analysis/InnerProductSpace/LinearMap.lean 2 1 ['github-actions'] nobody
3-41393
3 days ago
3-42124
3 days ago
3-42069
3 days
0
46211 vihdzp
author:vihdzp
refactor(SetTheory/Ordinal/Basic): specialize universes in lift lemmas We create more convenient versions of `Ordinal.lift_{eq/le/lt}` which specialize a universe parameter Lean cannot infer on its own. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> #39807 would make it so that we didn't have to think about any of this ;) t-set-theory 26/9 Mathlib/SetTheory/Ordinal/Basic.lean,Mathlib/SetTheory/Ordinal/Univ.lean 2 1 ['github-actions'] nobody
3-40749
3 days ago
3-42578
3 days ago
3-42641
3 days
0
45895 mcdoll
author:mcdoll
chore(Analysis/SchwartzSpace): simplify three proofs using `calc` Use `calc` block and better tactics to make three proofs more readable. The last one is slightly longer (in terms of line count), but I think it is better than the previous version. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 68/75 Mathlib/Analysis/Distribution/SchwartzSpace/Basic.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
3-39399
3 days ago
3-41315
3 days ago
3-62810
3 days
0
43868 JovanGerb
author:JovanGerb
feat(ClickSuggestions): suggest normalizing tactics This PR extends `#click_suggestions` with a new feature: suggestions for normalization tactics like `simp` and `ring_nf`. We dedicate a single thread for this, and leave the other threads to do the rest of the `#click_suggestions` computations. The results are shown as soon as they are ready, so if one normalizing tactic takes a long time to evaluate, the ones that were evaluated before that are already shown. In order to keep `#click_suggestions` low in the import hierarchy, I implemented an extensible mechanism, and use that to register more import-heavy tactics like `ring_nf`. When a subexpression is selected, the `conv` tactic is used to zoom in to that expression, so that the normalization is localized. Some tactics do not currently have a `conv` variant. In that case we don't use `conv`, which I think is fine. Some notes about the supported tactics: - `push +distrib Not` is only suggested if it acts differently from `push Not` - `dsimp` is only suggested if it acts differently from `dsimp only`, and similarly `simp` for `dsimp`. - `abel_nf` and `noncomm_ring` are not suggested for commutative rings, because then `ring_nf` is better - `module_nf` is not suggested when the inferred base ring is `Nat` or `Int`, because then `abel_nf` suffices. - I made the unnatural choice to suggest `norm_num1` instead of `norm_num`. This is because `norm_num` also runs `simp`, and it would be weird to suggest `norm_num` in places where `simp` does the same. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #44894 - [x] depends on: #44895 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-meta large-import 521/45 Mathlib.lean,Mathlib/Tactic.lean,Mathlib/Tactic/Abel.lean,Mathlib/Tactic/ClickSuggestions.lean,Mathlib/Tactic/ClickSuggestions/Normalize.lean,Mathlib/Tactic/ClickSuggestions/Util.lean,Mathlib/Tactic/FieldSimp.lean,Mathlib/Tactic/Group.lean,Mathlib/Tactic/ModuleNF.lean,Mathlib/Tactic/NoncommRing.lean,Mathlib/Tactic/NormNum/Core.lean,Mathlib/Tactic/Ring/RingNF.lean,MathlibTest/ClickSuggestions/Normalize.lean,MathlibTest/ClickSuggestions/Test.lean 14 11 ['JovanGerb', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] thorimur
assignee:thorimur
3-33296
3 days ago
3-67109
3 days ago
30-84807
30 days
0
43719 Thmoas-Guan
author:Thmoas-Guan
feat(LinearAlgebra): add API for exterior algebra of ring itself In this PR, we added some API for handling `ExteriorAlgebra R R`. AI disclosure: the proof in section "self" is generated by AI after providing the final target definition and characterizing lemma. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
61/0 Mathlib/LinearAlgebra/ExteriorAlgebra/Basic.lean 1 1 ['github-actions'] nobody
3-22761
3 days ago
72-2996
72 days ago
72-2941
72 days
3
43708 Thmoas-Guan
author:Thmoas-Guan
feat(RingTheory): definition of Koszul complex Definition of Koszul cocomplex. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 188/0 Mathlib.lean,Mathlib/RingTheory/KoszulComplex/Complex.lean 2 3 ['Whysoserioushah', 'github-actions'] nobody
3-22348
3 days ago
3-22807
3 days ago
42-23572
42 days
4
43707 Thmoas-Guan
author:Thmoas-Guan
feat(RingTheory): definition of Koszul cocomplex Definition of Koszul complex. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 167/0 Mathlib.lean,Mathlib/RingTheory/KoszulComplex/Cocomplex.lean 2 1 ['github-actions'] nobody
3-22094
3 days ago
72-16259
72 days ago
72-16204
72 days
3
45451 Parcly-Taxel
author:Parcly-Taxel
chore: remove transparency `set_option`s in `SimpleGraph`, part 1 These should be less controversial changes from #45430. tech debt t-combinatorics 14/33 Mathlib/Combinatorics/SimpleGraph/AdjMatrix.lean,Mathlib/Combinatorics/SimpleGraph/Clique.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/Finite.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/Subgraph.lean,Mathlib/Combinatorics/SimpleGraph/Ends/Defs.lean,Mathlib/Combinatorics/SimpleGraph/Finite.lean,Mathlib/Combinatorics/SimpleGraph/StronglyRegular.lean,Mathlib/Combinatorics/SimpleGraph/Subgraph.lean 8 1 ['github-actions'] SnirBroshi
assignee:SnirBroshi
3-21698
3 days ago
3-22211
3 days ago
24-46714
24 days
1
45453 Parcly-Taxel
author:Parcly-Taxel
chore: remove transparency `set_option`s in `SimpleGraph`, part 2 More fixes from #45430. * `ConnectedComponent.lift` now has `Reachable` in its hypotheses, which allows removing a `set_option`. * There was a long-standing typo in the statement of `Walk.ofBoxProdRight_boxProdRight`, which has been corrected. Equational lemmas for `Walk.ofBoxProd{Left,Right}` have been added too. * The golfed proof of `free_killCopies` was done by GPT-6.1 Sol, then hand-optimised. tech debt t-combinatorics LLM-generated 52/67 Mathlib/Combinatorics/SimpleGraph/Connectivity/Connected.lean,Mathlib/Combinatorics/SimpleGraph/Copy.lean,Mathlib/Combinatorics/SimpleGraph/Ends/Defs.lean,Mathlib/Combinatorics/SimpleGraph/LapMatrix.lean,Mathlib/Combinatorics/SimpleGraph/Prod.lean,Mathlib/Combinatorics/SimpleGraph/Subgraph.lean 6 1 ['github-actions'] SnirBroshi
assignee:SnirBroshi
3-21219
3 days ago
3-22034
3 days ago
24-41429
24 days
1
46166 tb65536
author:tb65536
feat(Analysis/Normed/Unbundled/GelfandRadiusNorm): the Gelfand radius norm is bounded below by any power-multiplicative norm This PR proves that the Gelfand radius norm is bounded below by any power-multiplicative norm. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #46162 t-analysis 41/0 Mathlib/Analysis/Normed/Algebra/GelfandRadius.lean,Mathlib/Analysis/Normed/Unbundled/GelfandRadiusNorm.lean 2 2 ['github-actions', 'mathlib-dependent-issues'] nobody
3-18160
3 days ago
3-21206
3 days ago
3-21155
3 days
0
45988 EtienneC30
author:EtienneC30
feat: characterize infinite product measures through product of sets in a pi system Provide a version of [pi_eq_generateFrom](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Topology/Constructions.html#pi_eq_generateFrom) for `infinitePi`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability 80/19 Mathlib/Probability/Independence/InfinitePi.lean,Mathlib/Probability/ProductMeasure.lean 2 1 ['github-actions'] nobody
3-18107
3 days ago
8-73486
8 days ago
8-78482
8 days
3
45987 mathlib-splicebot
author:mathlib-splicebot
feat: applying Bernoulli measures to singletons This PR was automatically created from PR #37794 by @EtienneC30 via a [review comment](https://github.com/leanprover-community/mathlib4/pull/37794#discussion_r4565268983) by @EtienneC30. t-measure-probability 20/0 Mathlib/Probability/Distributions/Bernoulli.lean 1 15 ['DavidLedvinka', 'EtienneC30', 'eric-wieser', 'github-actions'] nobody
3-17878
3 days ago
8-84391
8 days ago
8-84336
8 days
2
46231 EtienneC30
author:EtienneC30
feat: tag interval inclusion lemmas with simp --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 20/22 Mathlib/Analysis/Calculus/ParametricIntervalIntegral.lean,Mathlib/Order/Interval/Finset/Basic.lean,Mathlib/Order/Interval/Set/Basic.lean 3 1 ['github-actions'] nobody
3-14948
3 days ago
3-17875
3 days ago
3-17864
3 days
2
43948 JX-Mo
author:JX-Mo
chore(RepresentationTheory/Coinduced): tech debt Remove five `backward.isDefEq.respectTransparency.types` and add a CoeFun instance for `coindV` to justify the existing `coe`-named lemmas. https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/.60CoeFun.60.20or.20.60.2Eval.60/with/630026437 t-algebra tech debt easy
label:t-algebra$
22/17 Mathlib/RepresentationTheory/Coinduced.lean 1 38 ['JX-Mo', 'Whysoserioushah', 'github-actions', 'jcommelin', 'jjdishere', 'leanprover-radar', 'mathlib-bors', 'mathlib-merge-conflicts'] nobody
3-12202
3 days ago
3-13226
3 days ago
50-83538
50 days
4
43705 joelriou
author:joelriou
feat(Category/Abelian/Projective): interaction between `ProjectiveResolution.extMk` and the connecting morphism This is the dual result to #43224. Obtaining the dual version required introducing more API for the mapping cocone. --- - [x] depends on: #43224 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-category-theory tech debt increases-technical-debt 408/20 Mathlib/Algebra/Homology/DerivedCategory/Basic.lean,Mathlib/Algebra/Homology/DerivedCategory/ShortExact.lean,Mathlib/Algebra/Homology/DerivedCategory/SingleTriangle.lean,Mathlib/Algebra/Homology/DerivedCategory/SmallShiftedHom.lean,Mathlib/Algebra/Homology/HomotopyCategory/HomComplexShift.lean,Mathlib/Algebra/Homology/HomotopyCategory/HomComplexSingle.lean,Mathlib/Algebra/Homology/HomotopyCategory/MappingCocone.lean,Mathlib/Algebra/Homology/HomotopyCategory/Shift.lean,Mathlib/Algebra/Homology/HomotopyCategory/ShortExact.lean,Mathlib/CategoryTheory/Abelian/Injective/Ext.lean,Mathlib/CategoryTheory/Abelian/Projective/Ext.lean,Mathlib/CategoryTheory/Abelian/Projective/Extend.lean 12 7 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
3-11173
3 days ago
3-11831
3 days ago
34-25345
34 days
0
29281 plp127
author:plp127
doc: `Fin.natAdd_castLEEmb` Change the docstring of `Fin.natAdd_castLEEmb` which confused me when I read it so I rewrote it. Also rename to follow naming conventions. --- <!-- The text above the `---` will become the commit message when your PR is merged. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. To indicate co-authors, include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" When merging, all the commits will be squashed into a single commit listing all co-authors. If you are moving or deleting declarations, please include these lines at the bottom of the commit message (that is, before the `---`) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data 26/22 Mathlib/Data/Fin/Embedding.lean,Mathlib/GroupTheory/Perm/Fin.lean 2 4 ['github-actions', 'mathlib-merge-conflicts', 'mathlib4-merge-conflict-bot', 'urkud'] nobody
3-7896
3 days ago
3-10094
3 days ago
34-10430
34 days
0
44610 plp127
author:plp127
chore: dualize `HeytingAlgebra` more Use `to_dual_for` to connect `GeneralizedHeytingAlgebra.mk` and `GeneralizedHeytingAlgebra.le_himp_iff` with their duals. Also dualize some `BiheytingAlgebra` declarations. --- - [x] depends on: #44608 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 37/84 Mathlib/Order/Heyting/Basic.lean 1 3 ['github-actions', 'mathlib-dependent-issues', 'plp127'] nobody
3-7862
3 days ago
42-16359
42 days ago
42-16557
42 days
2
41540 plp127
author:plp127
chore: rename arguments of `Nat.strong_induction_on` Name the motive `motive` and name the minor premises according to the case. Also rename for `Fin.strong_induction_on`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data 37/39 Mathlib/Algebra/Lie/LieTheorem.lean,Mathlib/Algebra/Polynomial/Derivative.lean,Mathlib/Algebra/Polynomial/RuleOfSigns.lean,Mathlib/Analysis/Analytic/Inverse.lean,Mathlib/Analysis/Analytic/Uniqueness.lean,Mathlib/Combinatorics/Enumerative/Bell.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/Subgraph.lean,Mathlib/Computability/Language.lean,Mathlib/Data/Fin/Basic.lean,Mathlib/Data/Fintype/Basic.lean,Mathlib/Data/Fintype/Card.lean,Mathlib/Data/Nat/Choose/Central.lean,Mathlib/Data/Nat/Digits/Lemmas.lean,Mathlib/Data/Nat/Nth.lean,Mathlib/FieldTheory/Separable.lean,Mathlib/GroupTheory/SpecificGroups/Cyclic.lean,Mathlib/ModelTheory/Arithmetic/Presburger/Semilinear/Defs.lean,Mathlib/NumberTheory/Bernoulli.lean,Mathlib/NumberTheory/BernoulliPolynomials.lean,Mathlib/NumberTheory/ModularForms/LevelOne/DimensionFormula.lean,Mathlib/Order/Fin/Basic.lean,Mathlib/RingTheory/Ideal/Quotient/Nilpotent.lean,Mathlib/RingTheory/LittleWedderburn.lean,Mathlib/RingTheory/Polynomial/Basic.lean,Mathlib/RingTheory/Polynomial/Cyclotomic/Basic.lean,Mathlib/RingTheory/Polynomial/Cyclotomic/Eval.lean,Mathlib/RingTheory/Polynomial/Nilpotent.lean,Mathlib/RingTheory/WittVector/Frobenius.lean,Mathlib/SetTheory/Cardinal/NatCard.lean 29 6 ['github-actions', 'mathlib-merge-conflicts'] TwoFX
assignee:TwoFX
3-6470
3 days ago
3-9997
3 days ago
102-31787
102 days
0
46212 vihdzp
author:vihdzp
feat(Ordinal): order isos preserve order type We also rename `RelIso.ordinal_lift_type_eq` → `RelIso.lift_ordinalType_congr` to match the existing `RelIso.ordinalType_congr`. (It'd be a bad idea to call this `lift_type_congr`, since we might want to prove a similar theorem for `OrderType` later.) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory 12/5 Mathlib/SetTheory/Ordinal/Basic.lean 1 3 ['SnirBroshi', 'github-actions', 'vihdzp'] nobody
3-5956
3 days ago
3-42194
3 days ago
3-42139
3 days
0
46240 justus-springer
author:justus-springer
feat(Algebra/Module/Lattice): map/comap of lattices Adds API for transporting `Submodule.IsLattice` and `Submodule.IsFullLattice` along linear maps. This is part of the lattice refactor (see [Zulip](https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Definitions.20of.20lattices/with/620077176)), where these will eventually replace `ZLattice.comap`, among other things. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
87/0 Mathlib/Algebra/Module/Lattice/Basic.lean,Mathlib/Algebra/Module/Lattice/Full.lean 2 1 ['github-actions'] nobody
3-1820
3 days ago
3-2336
3 days ago
3-2281
3 days
2
46241 justus-springer
author:justus-springer
feat(Algebra/Module/Lattice): lattices and spans Adds basic API relating `Submodule.IsLattice` to spans of linearly independent families. This PR is part of the lattice refactor, see the [Zulip thread](https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Definitions.20of.20lattices/with/620077176). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
60/1 Mathlib/Algebra/Module/Lattice/Basic.lean,Mathlib/Algebra/Module/Lattice/Full.lean 2 1 ['github-actions'] nobody
3-1501
3 days ago
3-2088
3 days ago
3-2033
3 days
1
45528 joelriou
author:joelriou
chore(CategoryTheory/Limits): remove set_option for multiequalizers --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-category-theory tech debt 36/80 Mathlib/CategoryTheory/Limits/Preserves/Shapes/Multiequalizer.lean,Mathlib/CategoryTheory/Limits/Shapes/Equalizers.lean,Mathlib/CategoryTheory/Limits/Shapes/Multiequalizer.lean,Mathlib/Order/CompleteLattice/MulticoequalizerDiagram.lean 4 1 ['github-actions'] nobody
3-224
3 days ago
22-14851
22 days ago
22-14796
22 days
6
45727 pleich
author:pleich
feat(Order/WellFoundedSet): PWO iff well-founded with finite antichains Add `Set.partiallyWellOrderedOn_iff_wellFoundedOn_and_finite_antichains`: For preorder `r`, a set is partially well-ordered iff the strict part of `r` is well-founded on it and all antichains are finite. This removes the open TODO in the module docstring. Additionally, prove theorem `IsAntichain.finite_of_partiallyWellOrderedOn` by reusing the analog theorem (`IsAntichain.finite_of_wellQuasiOrdered `) for well-quasi orders and remove the corresponding TODO. This commit has been assisted by Claude Code with Opus 5.5. --- This is my first PR to the mathlib project, and I am welcome for any feedback. If these TODOs are already assigned to others, feel free to close the PR. Claude has been used to create this PR, in particular to help me understand the relevant definitions, make the proofs more concise, adhering to the mathlib style and to review my proposed changes afterwards. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order new-contributor 19/6 Mathlib/Order/WellFoundedSet.lean 1 5 ['SnirBroshi', 'github-actions', 'mathlib-merge-conflicts', 'pleich'] nobody
2-86352
2 days ago
3-2171
3 days ago
16-10558
16 days
0
46243 justus-springer
author:justus-springer
feat(LinearAlgebra/): `Basis.equiv` to the standard basis Adds two very simple `simp` lemma about the interaction of `Basis.equiv` with the standard bases `Pi.basisFun` and `Finsupp.basisSingleOne`. This PR is part of the lattice refactor, see the [Zulip thread](https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Definitions.20of.20lattices/with/620077176). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
12/0 Mathlib/LinearAlgebra/Finsupp/VectorSpace.lean,Mathlib/LinearAlgebra/StdBasis.lean 2 1 ['github-actions'] nobody
2-86168
2 days ago
3-955
3 days ago
3-900
3 days
0
46244 justus-springer
author:justus-springer
feat(Topology/Algebra/Module/Equiv/Basic): add (pre)image_frontier lemmas Add lemmas `image_frontier` and `preimage_frontier` in the `ContinuousLinearEquiv` namespace. This is then used to slightly simplify some proofs. This PR is part of the lattice refactor, see the [Zulip thread](https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Definitions.20of.20lattices/with/620077176). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 13/7 Mathlib/Algebra/Module/ZLattice/Covolume.lean,Mathlib/Analysis/Complex/ReImTopology.lean,Mathlib/NumberTheory/NumberField/Ideal/Asymptotics.lean,Mathlib/Topology/Algebra/Module/Equiv/Basic.lean 4 1 ['github-actions'] nobody
2-85799
2 days ago
3-740
3 days ago
3-685
3 days
0
44214 ZRTMRH
author:ZRTMRH
feat(Analysis/SpecialFunctions): taylor series bounds for sin and cos Adds `Mathlib/Analysis/SpecialFunctions/Trigonometric/SeriesBounds.lean` with three groups of results: 1. Remainder bounds on the unit disc at every order: `Complex.sin_series_bound`, `Complex.cos_series_bound` and their real forms. Ported from #29355, taken over with the author's agreement. This PR supersedes #29355, which can be closed when this lands. 2. `Real.sum_lt_sin_of_pos`, `Real.sin_lt_sum_of_pos`, `Real.sum_lt_cos_of_pos`, and `Real.cos_lt_sum_of_pos`: `sin x` and `cos x` lie between consecutive partial sums of their Taylor series. Yury posted on Zulip in October 2025 with a request that someone open a PR for it ([Upper and Lower Bounds of Cosine](https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/Upper.20and.20Lower.20Bounds.20of.20Cosine/near/546287708)), it had not been opened. 4. Six low-order corollaries, as completion to `one_sub_sq_div_two_lt_cos` and `sin_gt_sub_cube` which Mathlib already has: `cos_lt/le_one_sub_sq_div_two_add_pow_four`, `sin_lt/le_sub_cube_add_pow_five`, and `sub_cube_add_pow_five_lt/le_sin` for negative arguments. The 6 low-order corollaries and the docstrings were written with AI assistance (Claude). The code has been reviewed by the author. Co-authored-by: Geoffrey Irving <irving@naml.us> Co-authored-by: Yury G. Kudryashov <urkud@urkud.name> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated new-contributor t-analysis 288/0 Mathlib.lean,Mathlib/Algebra/BigOperators/Ring/Finset.lean,Mathlib/Analysis/SpecialFunctions/Trigonometric/SeriesBounds.lean 3 63 ['SnirBroshi', 'ZRTMRH', 'github-actions', 'luigi-massacci', 'wwylele'] nobody
2-83831
2 days ago
2-83831
2 days ago
50-74572
50 days
0
46246 EtienneC30
author:EtienneC30
chore: deprecate `IsSetBernoulli` This is unnecessarily redundant with the `HasLaw` API. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability 8/7 Mathlib/Probability/Distributions/SetBernoulli.lean 1 1 ['github-actions'] nobody
2-83741
2 days ago
2-84211
2 days ago
2-84156
2 days
0
46176 Nicola9Falciola
author:Nicola9Falciola
chore(LinearAlgebra/Matrix/FixedDetMatrices): remove all the `set_option` in the file due to defeq abuse This PR adds a `_.mk` for `FixedDetMatrix` and small API lemmas to avoid defeq abuse later in the file removing all the remaining `set_options`. I have modified a couple of proofs also to save heartbeats. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt
label:t-algebra$
29/17 Mathlib/LinearAlgebra/Matrix/FixedDetMatrices.lean 1 1 ['github-actions'] nobody
2-82827
2 days ago
2-85175
2 days ago
3-60191
3 days
0
46121 ldiedering
author:ldiedering
feat(MeasureTheory): add more API for `NoAtoms` Main additions: - `NoAtoms` implies `NullSingletonClass` under mild assumptions, which however cannot be dropped (`instNullSingletonClass`, `instNullSingletonClass_of_sfinite`). - The restriction of a nonatomic measure is again nonatomic under mild assumptions (`restrict`, `Measure.restrict.instNoAtoms`). - API for the interaction of `IsAtom` and `NoAtoms` with `MeasurableEquiv`. This PR builds directly on the new definition of `NoAtoms` introduced in #45666. --- Use of AI: A first version of the new API was written manually as part of the Carleson project. Claude Code was then used to create a plan for upstreaming, suggest additional lemmas, golf proofs and write documentation. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability new-contributor LLM-generated 136/3 Mathlib/MeasureTheory/Measure/Typeclasses/NoAtoms.lean 1 12 ['felixpernegger', 'github-actions', 'ldiedering', 'lua-vr', 'wwylele'] nobody
2-82477
2 days ago
3-84176
3 days ago
4-10013
4 days
0
43232 Parcly-Taxel
author:Parcly-Taxel
refactor: `TrivSqZeroExt` extending `Prod` Define à la `Unitization` ([#mathlib4 > TrivSqZeroExt as a 2-field structure @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/TrivSqZeroExt.20as.20a.202-field.20structure/near/620183663)) ```lean structure TrivSqZeroExt (R : Type u) (M : Type v) extends R × M ``` This PR came out of investigating the source of the `DualQuaternion` slowdown in #43078. (`DualNumber R` is an abbrev for `TrivSqZeroExt R R`.) `Topology.Instances.TrivSqZeroExt` and `Analysis.Normed.Algebra.TrivSqZeroExt` were filled in with significant help from GPT-6.1 Sol. t-algebra tech debt LLM-generated
label:t-algebra$
360/290 Mathlib/Algebra/DualNumber.lean,Mathlib/Algebra/DualQuaternion.lean,Mathlib/Algebra/TrivSqZeroExt/Basic.lean,Mathlib/Algebra/TrivSqZeroExt/Ideal.lean,Mathlib/Analysis/Normed/Algebra/TrivSqZeroExt.lean,Mathlib/LinearAlgebra/ExteriorAlgebra/Basic.lean,Mathlib/LinearAlgebra/Matrix/DualNumber.lean,Mathlib/LinearAlgebra/TensorAlgebra/Basic.lean,Mathlib/RingTheory/DualNumber.lean,Mathlib/Topology/Instances/TrivSqZeroExt.lean 10 10 ['Parcly-Taxel', 'github-actions', 'mathlib-merge-conflicts', 'plp127'] nobody
2-80210
2 days ago
16-48358
16 days ago
25-68319
25 days
0
46248 felixpernegger
author:felixpernegger
chore(Basic): unsqueeze terminal `simp only`s Per style guide. A few terminal `simp only` remain, but they have to, due to stuff looping wrongly etc --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-data 90/91 Mathlib/Basic/Complex/Basic.lean,Mathlib/Basic/ENNReal/Action.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Basic/ENNReal/BigOperators.lean,Mathlib/Basic/ENNReal/Inv.lean,Mathlib/Basic/ENNReal/Operations.lean,Mathlib/Basic/ENNReal/Real.lean,Mathlib/Basic/ExistsUnique.lean,Mathlib/Basic/IsEmpty/Basic.lean,Mathlib/Basic/Logic/Basic.lean,Mathlib/Basic/NNReal/Basic.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/Basic/NNReal/Star.lean,Mathlib/Basic/Nontrivial/Basic.lean,Mathlib/Basic/Nontrivial/Defs.lean,Mathlib/Basic/PEquiv.lean,Mathlib/Basic/Real/Basic.lean,Mathlib/Basic/Real/Pointwise.lean,Mathlib/Basic/Sign/Basic.lean,Mathlib/Basic/Sign/Defs.lean 20 3 ['felixpernegger', 'github-actions', 'leanprover-radar'] nobody
2-79663
2 days ago
2-82924
2 days ago
2-82961
2 days
0
43465 TJHeeringa
author:TJHeeringa
feat(Analysis/InnerProductSpace/Reproducing): add bilinearform for Mercer's theorem Mercer's theorem provides a spectral representation to kernels satisfying an integrability condition. The proof builds on a Hilbert-Schmidt operator. This PR introduces the bilinear form used to define that operator. --- PR #42003 introduces the corresponding integral operator. AI: Claude and Mistral have helped me get up to speed with how to do the measurability proofs in lean. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 142/0 Mathlib.lean,Mathlib/Analysis/InnerProductSpace/Reproducing/Mercer.lean 2 8 ['TJHeeringa', 'github-actions', 'mathlib-merge-conflicts', 'mcdoll'] j-loreaux
assignee:j-loreaux
2-77089
2 days ago
3-68564
3 days ago
76-24367
76 days
1
46041 j-loreaux
author:j-loreaux
feat: `ContinuousFunctionalCalculus` instance for `Unitization 𝕜 A` Given a non-unital `𝕜`-algebra (`𝕜 := ℝ` or `𝕜 := ℂ`) with a non-unital continuous functional calculus instance, this adds a continuous functional calculus instance for `Unitization 𝕜 A`. For technical reasons, we can't do this as an *instance* for `RCLike 𝕜`, but must do `ℝ` and `ℂ` individually. --- - [x] depends on: #46036 - [x] depends on: #46037 - [x] depends on: #46038 - [x] depends on: #46039 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> maintainer-merge t-analysis 148/0 Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Instances.lean 1 15 ['github-actions', 'j-loreaux', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'themathqueen'] nobody
2-76323
2 days ago
3-73897
3 days ago
3-74419
3 days
1
44964 tb65536
author:tb65536
feat: results in unramified extensions of rings This PR proves that if `S/R` is an unramified extension of rings satisfying `Algebra.IsInvariant R S G` (e.g., if `G` is a Galois group for `S/R`), and if `I` is an ideal of `R` fixed by the action of `G`, then `(I.under R).map (algebraMap R S) = I`. --- I don't really understand how this magic `cosetIdempotentSum` works. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #44965 - [x] depends on: #44966 - [x] depends on: #45158 - [x] depends on: #45180 - [x] depends on: #45181 - [x] depends on: #45183 - [x] depends on: #45390 - [x] depends on: #45499 - [x] depends on: #45630 - [x] depends on: #45781 - [x] depends on: #46136 - [x] depends on: #46137 - [x] depends on: #46138 t-ring-theory t-algebra LLM-generated t-number-theory large-import
label:t-algebra$
74/0 Mathlib/GroupTheory/GroupAction/Quotient.lean,Mathlib/LinearAlgebra/TensorProduct/Lift.lean,Mathlib/RingTheory/Unramified/Finite.lean 3 18 ['Nicola9Falciola', 'github-actions', 'mathlib-dependent-issues', 'riccardobrasca', 'tb65536'] riccardobrasca
assignee:riccardobrasca
2-68061
2 days ago
3-76540
3 days ago
3-77359
3 days
0
46261 SHW715
author:SHW715
feat(MeasureTheory/Function/Holder): add `ContinuousLinearMap.norm_lpPairing_le` Add `ContinuousLinearMap.norm_lpPairing_le`: `‖B.lpPairing μ p q‖ ≤ ‖B‖`. This is the analogue for `lpPairing` of `ContinuousLinearMap.norm_holderL_le` earlier in this file. --- I need this inequality for showing that `B.lpPairing` is an isometry when `B` is an isometry (under certain conditions). This is the straightforward direction of that result. The proof was written with the help of AI (Claude), which helped me find the relevant lemmas. t-measure-probability new-contributor 7/0 Mathlib/MeasureTheory/Function/Holder.lean 1 2 ['github-actions'] nobody
2-66775
2 days ago
2-67342
2 days ago
2-67287
2 days
0
45659 harahu
author:harahu
feat(GroupTheory/OreLocalization): add `Small` instance Add `OreLocalization.small : Small.{w} X[S⁻¹]` given `Small.{w} S` and `Small.{w} X` along with the additive version. This replaces a local instance in `Algebra/Category/ModuleCat/Localization.lean` and 8 hand-built `Small` instances in `RingTheory/LocalProperties/{Injective,Projective}Dimension.lean`. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code), with further refinement by Astra. t-ring-theory 35/20 Mathlib.lean,Mathlib/Algebra/Category/ModuleCat/Localization.lean,Mathlib/GroupTheory/OreLocalization/Small.lean,Mathlib/RingTheory/LocalProperties/InjectiveDimension.lean,Mathlib/RingTheory/LocalProperties/ProjectiveDimension.lean 5 4 ['github-actions', 'harahu', 'mathlib-merge-conflicts', 'plp127'] nobody
2-65858
2 days ago
2-66502
2 days ago
14-49266
14 days
0
46064 sgouezel
author:sgouezel
chore: change the definition of MemLp to use the inhomogeneous norm This is the next step in the refactor discussed at [#mathlib4 > eLpNorm junk value @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/eLpNorm.20junk.20value/near/600702321). We change the definition of `MemLp` by requiring that the inhomogeneous `L^p` norm is finite. This only changes the definition at `p=0`, where in the new definition the `L^0` functions are the ae strongly measurable functions with support of finite measure. We add convenience lemmas to make sure that most proofs can still be done in terms of the original `eLpNorm`. We add just the minimum of API to `inhmgELpNorm` to make sure that all statements on functions satisfying `MemLp` are proved in the proper generality (i.e., if they hold for `p = 0` with the new definition, then we prove them also for `p = 0`, and if this requires extending some lemmas from `eLpNorm` to `inhmgELpNorm` then we do it -- but otherwise we don't add anything new on `inhmgELpNorm`) We do *not* change other definitions or theorem statements done in terms of `eLpNorm` (and it's not planned for another PR): changing them would give genuinely different statements, there is no reason to do that unless the current version is not satisfactory. We do *not* change the definition of the norm on `L^p`. It is planned to replace it with `inhmgELpNorm` (notably to get a normed add comm group and a topology for all `p`), but this is not necessary for the current PR, so we haven't done it to keep the PR at a reasonable (?) size. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability 828/371 Mathlib/Analysis/Convolution.lean,Mathlib/Analysis/Distribution/SchwartzSpace/Basic.lean,Mathlib/Analysis/Distribution/Sobolev.lean,Mathlib/Analysis/Distribution/TemperedDistribution.lean,Mathlib/Basic/ENNReal/Holder.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/MeasureTheory/Function/AEEqOfIntegral.lean,Mathlib/MeasureTheory/Function/ConditionalExpectation/AEMeasurable.lean,Mathlib/MeasureTheory/Function/ConditionalExpectation/CondexpL2.lean,Mathlib/MeasureTheory/Function/ConditionalExpectation/Real.lean,Mathlib/MeasureTheory/Function/ConditionalExpectation/Unique.lean,Mathlib/MeasureTheory/Function/ContinuousMapDense.lean,Mathlib/MeasureTheory/Function/L1Space/Integrable.lean,Mathlib/MeasureTheory/Function/L2Space.lean,Mathlib/MeasureTheory/Function/LpSeminorm/Basic.lean,Mathlib/MeasureTheory/Function/LpSeminorm/CompareExp.lean,Mathlib/MeasureTheory/Function/LpSeminorm/Defs.lean,Mathlib/MeasureTheory/Function/LpSeminorm/Indicator.lean,Mathlib/MeasureTheory/Function/LpSeminorm/LpNorm.lean,Mathlib/MeasureTheory/Function/LpSeminorm/Monotonicity.lean,Mathlib/MeasureTheory/Function/LpSeminorm/SMul.lean,Mathlib/MeasureTheory/Function/LpSeminorm/TriangleInequality.lean,Mathlib/MeasureTheory/Function/LpSeminorm/Trim.lean,Mathlib/MeasureTheory/Function/LpSpace/Basic.lean,Mathlib/MeasureTheory/Function/LpSpace/Complete.lean,Mathlib/MeasureTheory/Function/LpSpace/CompleteOfCompleteLp.lean,Mathlib/MeasureTheory/Function/LpSpace/ContinuousCompMeasurePreserving.lean,Mathlib/MeasureTheory/Function/LpSpace/ContinuousFunctions.lean,Mathlib/MeasureTheory/Function/LpSpace/Indicator.lean,Mathlib/MeasureTheory/Function/LpSpace/InfiniteSum.lean,Mathlib/MeasureTheory/Function/SimpleFuncDenseLp.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/AEStronglyMeasurable.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/Lp.lean,Mathlib/MeasureTheory/Function/UnifTight.lean,Mathlib/MeasureTheory/Function/UniformIntegrable.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/MeasureTheory/Measure/Trim.lean,Mathlib/Probability/Distributions/Gaussian/Basic.lean,Mathlib/Probability/IdentDistrib.lean,Mathlib/Probability/Kernel/Disintegration/CDFToKernel.lean,Mathlib/Probability/Kernel/Disintegration/Density.lean,Mathlib/Probability/Martingale/Convergence.lean,Mathlib/Probability/Moments/CovarianceBilinDual.lean,Mathlib/Probability/Moments/IntegrableExpMul.lean,Mathlib/Probability/Moments/SubGaussian.lean,Mathlib/Probability/Moments/Tilted.lean,Mathlib/Probability/Moments/Variance.lean,Mathlib/Probability/Process/LimitProcess.lean 48 9 ['D-Thomine', 'adomani', 'bryangingechen', 'github-actions', 'mathlib-merge-conflicts', 'sgouezel'] nobody
2-65393
2 days ago
2-82717
2 days ago
3-77614
3 days
0
42578 harahu
author:harahu
chore: avoid lazy continuation lines in markdown This PR fixes Markdown lazy continuation lines in documentation. The bulk of the changes are: 1. Continuation lines of a list item are indented to the item's content column instead of sitting flush with the marker. 2. A blank line is inserted where a paragraph following a list was being absorbed into the final list item. This is done because lazy continuation can make it hard to understand the intent of the text when reading the raw source. It is also a source of flawed rendering, as in case 2 above. One other minor change is also included: - RingTheory/FormalGroup/Basic.lean: the qualifier "when F is a commutative formal group law" moves from AddMonoid to AddCommMonoid, which is where it belongs: instance : AddMonoid (F.Point σ) is unconditional, instance [F.IsComm] : AddCommMonoid (F.Point σ) is not. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) 136/121 Mathlib/Algebra/Category/ModuleCat/Presheaf/ColimitFunctor.lean,Mathlib/Algebra/Group/Subgroup/Basic.lean,Mathlib/Algebra/Homology/SpectralSequence/ComplexShape.lean,Mathlib/Algebra/Lie/LieTheorem.lean,Mathlib/Algebra/Lie/Prod.lean,Mathlib/Algebra/LieRinehartAlgebra/Subalgebra.lean,Mathlib/Algebra/Notation/Bracket.lean,Mathlib/AlgebraicGeometry/EllipticCurve/LFunction.lean,Mathlib/AlgebraicGeometry/Gluing.lean,Mathlib/AlgebraicGeometry/ProjectiveSpectrum/Scheme.lean,Mathlib/AlgebraicTopology/Reedy/Basic.lean,Mathlib/AlgebraicTopology/SimplicialSet/AnodyneExtensions/PushoutProduct.lean,Mathlib/AlgebraicTopology/SimplicialSet/Subdivision.lean,Mathlib/AlgebraicTopology/SimplicialSet/TopAdj.lean,Mathlib/Analysis/Calculus/UniformLimitsDeriv.lean,Mathlib/Analysis/Distribution/ContDiffMapSupportedIn.lean,Mathlib/Analysis/Normed/Field/Approximation.lean,Mathlib/Analysis/Normed/Field/Dense.lean,Mathlib/Analysis/Normed/Field/Krasner.lean,Mathlib/Analysis/Normed/Module/Bases.lean,Mathlib/Analysis/SpecialFunctions/Trigonometric/Chebyshev/Extremal.lean,Mathlib/CategoryTheory/Abelian/Preradical/Colon.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/ChosenPullback.lean,Mathlib/CategoryTheory/Sites/Point/OfIsCofiltered.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/Finite.lean,Mathlib/Dynamics/SymbolicDynamics/Basic.lean,Mathlib/GroupTheory/FinitelyPresentedGroup.lean,Mathlib/GroupTheory/Generators.lean,Mathlib/GroupTheory/GroupAction/Blocks.lean,Mathlib/GroupTheory/Perm/Fin.lean,Mathlib/Lean/Meta/RefinedDiscrTree/Basic.lean,Mathlib/LinearAlgebra/InvariantBasisNumber.lean,Mathlib/LinearAlgebra/LinearPMap.lean,Mathlib/LinearAlgebra/Matrix/Rank.lean,Mathlib/LinearAlgebra/SymplecticGroup.lean,Mathlib/Logic/Equiv/Array.lean,Mathlib/Logic/Equiv/Fin/Rotate.lean,Mathlib/NumberTheory/WellApproximable.lean,Mathlib/Probability/Process/Adapted.lean,Mathlib/RingTheory/FormalGroup/Basic.lean,Mathlib/Tactic/Algebra/Basic.lean,Mathlib/Tactic/Polynomial/Basic.lean,Mathlib/Topology/Category/LightProfinite/Injective.lean,Mathlib/Topology/Gluing.lean,Mathlib/Topology/MetricSpace/PiNat.lean,Mathlib/Topology/Sheaves/Presheaf.lean,Mathlib/Topology/Sion.lean 47 5 ['SnirBroshi', 'github-actions', 'harahu', 'mathlib-merge-conflicts'] nobody
2-63630
2 days ago
2-65481
2 days ago
44-42354
44 days
0
44294 harahu
author:harahu
doc(RepresentationTheory): add module doc headers for Equiv Add a H1 module doc header in `Mathlib/RepresentationTheory/Equiv.lean`. Split out from #42795 to allow the mechanical header cleanups to be merged separately. --- [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
2/0 Mathlib/RepresentationTheory/Equiv.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
2-62965
2 days ago
2-63599
2 days ago
42-19071
42 days
0
45658 harahu
author:harahu
feat(Logic/Relation): add `Equivalence.eqvGen_le` and `EqvGen.lift` Add `Equivalence.eqvGen_le`. This is the `Equivalence` counterpart of `EqvGen.eqvGen_le`. Add `EqvGen.lift`, mirroring `TransGen.lift` and `ReflTransGen.lift`. Deprecate `EqvGen.eqvGen_mono`, which duplicates `EqvGen.mono`. Use the new lemmas to golf 11 proofs. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) LLM-generated 40/84 Mathlib/Algebra/RingQuot.lean,Mathlib/CategoryTheory/Limits/Final.lean,Mathlib/CategoryTheory/Limits/IsConnected.lean,Mathlib/CategoryTheory/Limits/Types/Coequalizers.lean,Mathlib/CategoryTheory/Limits/Types/Filtered.lean,Mathlib/CategoryTheory/MorphismProperty/Quotient.lean,Mathlib/GroupTheory/FreeGroup/Basic.lean,Mathlib/Logic/Relation.lean,Mathlib/Order/Setoid/Basic.lean,Mathlib/Topology/Compactification/StoneCech.lean,Mathlib/Topology/Gluing.lean 11 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
2-62421
2 days ago
2-66153
2 days ago
15-85596
15 days
0
42766 harahu
author:harahu
chore(Order): tidy markdown headers This PR: - Ensures all files in `Mathlib/Order` have an H1 header. - Aligns some H2 headers with the examples in the documentation style guide. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 7/5 Mathlib/Order/Comparable.lean,Mathlib/Order/CompleteSublattice.lean,Mathlib/Order/Completion.lean,Mathlib/Order/Interval/Set/OrdConnectedLinear.lean,Mathlib/Order/Quotient.lean 5 2 ['Multramate', 'github-actions', 'mathlib-merge-conflicts'] nobody
2-62406
2 days ago
2-62833
2 days ago
87-33508
87 days
0
43250 WenrongZou
author:WenrongZou
chore(Valuation/Integers): rename `Valuation.Integers` to `Valuation.IsIntegers` I think [`Valuation.Integers`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/RingTheory/Valuation/Integers.html#Valuation.Integers) is the characteristic predicate. If this is not what we want, I am happy to add a characteristic predicate in this file. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 192/61 Mathlib/NumberTheory/Padics/Complex.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Completion.lean,Mathlib/RingTheory/DiscreteValuationRing/Basic.lean,Mathlib/RingTheory/Perfection.lean,Mathlib/RingTheory/Valuation/Archimedean.lean,Mathlib/RingTheory/Valuation/Discrete/Basic.lean,Mathlib/RingTheory/Valuation/Discrete/IsDiscreteValuationRing.lean,Mathlib/RingTheory/Valuation/Integers.lean,Mathlib/RingTheory/Valuation/Integral.lean,Mathlib/RingTheory/Valuation/ValuationRing.lean,Mathlib/RingTheory/Valuation/ValuationSubring.lean,Mathlib/Topology/Algebra/Valued/LocallyCompact.lean 12 21 ['WenrongZou', 'b-mehta', 'github-actions', 'jcommelin', 'mathlib-bors', 'mathlib-merge-conflicts', 'riccardobrasca'] nobody
2-61863
2 days ago
2-62410
2 days ago
36-76417
36 days
0
43122 harahu
author:harahu
chore(Tactic): tidy markdown headers This PR ensures files in `Mathlib/Tactic` have one and only one H1 header. In the cases where the file did not already have an obvious H1 header candidate, a new header was authored by Claude Opus 5. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) 57/33 Mathlib/Tactic/ApplyCongr.lean,Mathlib/Tactic/Bound.lean,Mathlib/Tactic/CategoryTheory/CheckCompositions.lean,Mathlib/Tactic/DSimpPercent.lean,Mathlib/Tactic/DeclarationNames.lean,Mathlib/Tactic/DepRewrite.lean,Mathlib/Tactic/FunProp/Attr.lean,Mathlib/Tactic/FunProp/Decl.lean,Mathlib/Tactic/FunProp/Elab.lean,Mathlib/Tactic/FunProp/FunctionData.lean,Mathlib/Tactic/FunProp/Mor.lean,Mathlib/Tactic/FunProp/Theorems.lean,Mathlib/Tactic/FunProp/ToBatteries.lean,Mathlib/Tactic/FunProp/Types.lean,Mathlib/Tactic/GuardGoalNums.lean,Mathlib/Tactic/GuardHypNums.lean,Mathlib/Tactic/Inhabit.lean,Mathlib/Tactic/Linarith.lean,Mathlib/Tactic/Linter/Style.lean,Mathlib/Tactic/Linter/TextBased.lean,Mathlib/Tactic/Linter/UpstreamableDecl.lean,Mathlib/Tactic/NormNum/Core.lean,Mathlib/Tactic/NormNum/OfScientific.lean,Mathlib/Tactic/NormNum/Pow.lean,Mathlib/Tactic/NormNum/Result.lean,Mathlib/Tactic/Positivity/Basic.lean,Mathlib/Tactic/Positivity/Core.lean,Mathlib/Tactic/Ring/NamePolyVars.lean,Mathlib/Tactic/Ring/NamePowerVars.lean,Mathlib/Tactic/SplitIfs.lean,Mathlib/Tactic/Tauto.lean,Mathlib/Tactic/ToAdditive.lean,Mathlib/Tactic/ToDual.lean,Mathlib/Tactic/Widget/CommDiag.lean 34 3 ['github-actions', 'mathlib-merge-conflicts'] nobody
2-59117
2 days ago
2-62670
2 days ago
60-65471
60 days
0
46222 j-loreaux
author:j-loreaux
feat: `NonnegSpectrumClass ℝ A` from a star order and a continuous functional calculus The argument that a C⋆-algebra satisfies `NonnegSpectrumClass ℝ A` may be generalized to any `StarOrderedRing` with a `NonUnitalContinuousFunctionalCalculus ℝ A IsSelfAdjoint` instance. We don't include this as an instance to avoid weird type class searches, but we prove it as a theorem. --- With #46041 this can be used to get a `NonnegSpectrumClass ℝ (Unitization ℝ A)` instance. t-analysis 23/27 Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Basic.lean,Mathlib/Analysis/SpecialFunctions/ContinuousFunctionalCalculus/PosPart/Basic.lean 2 6 ['github-actions', 'j-loreaux', 'themathqueen'] nobody
2-58628
2 days ago
3-23512
3 days ago
3-23511
3 days
0
44743 vihdzp
author:vihdzp
refactor(Wiedijk100Theorems/AreaOfACircle): delete file The area formula for circles exists within Mathlib already, and in fact we also have formulas for the volume of an n-sphere. So we delete the file on the archive, in favor for the Mathlib theorem. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Not sure if this is the right thing to do. Maybe we could change the link on 100.yaml, but still keep the archive file as an alternate proof of a similar result? t-measure-probability file-removed tech debt 13/140 Archive.lean,Archive/Wiedijk100Theorems/AreaOfACircle.lean,Mathlib/MeasureTheory/Measure/Lebesgue/VolumeOfBalls.lean,docs/100.yaml 4 4 ['Parcly-Taxel', 'github-actions', 'mathlib-merge-conflicts'] RemyDegenne
assignee:RemyDegenne
2-57891
2 days ago
2-58366
2 days ago
41-81841
41 days
0
40644 j-loreaux
author:j-loreaux
refactor: use `LinearMap.IsWeak` for `WeakBilin` This introduces `WeakBilin.linearEquiv : WeakBilin B ≃ₗ[𝕜] E` as the canonical map between a space `E` and its type synonym `WeakBilin B`, for `B : E →ₗ[𝕜] F →ₗ[𝕜] 𝕜`. This serves to provides an abstraction barrier between these defeq types. We then add `WeakBilin.pairing : WeakBilin B →ₗ[𝕜] F →ₗ[𝕜] 𝕜` as a copy of the bilinear map `B` where we exchange the domain via `LinearEquiv.arrowCongr`. Finally, we provide an instance of `LinearMap.IsWeak (WeakBilin.pairing B)`. This allows us to remove abuse of definitional equality in the API for `WeakBilin`, and to deprecate most of the basic results in favor of their `LinearMap.IsWeak` variants. The one result which we don't deprecate is `WeakBilin.continuous_of_continuous_eval`. This is because the specific version we can tag with `fun_prop`, but the more general version would not be suitable as a `fun_prop` lemma because the linear map `B` inducing the topology would be a metavariable, and cannot be inferred from the type. --- - [ ] depends on: #40489 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis t-topology tech debt maintainer-merge 220/118 Mathlib/Analysis/LocallyConvex/Polar.lean,Mathlib/Analysis/LocallyConvex/WeakDual.lean,Mathlib/Analysis/LocallyConvex/WeakSpace.lean,Mathlib/Analysis/Normed/Module/WeakDual.lean,Mathlib/MeasureTheory/Measure/FiniteMeasure.lean,Mathlib/Topology/Algebra/Module/Spaces/CharacterSpace.lean,Mathlib/Topology/Algebra/Module/Spaces/PointwiseConvergenceCLM.lean,Mathlib/Topology/Algebra/Module/Spaces/WeakBilin.lean,Mathlib/Topology/Algebra/Module/Spaces/WeakDual.lean 9 6 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mcdoll'] mcdoll
assignee:mcdoll
2-54629
2 days ago
23-25023
23 days ago
23-24969
23 days
0
43545 gasparattila
author:gasparattila
refactor(Algebra/Order/Ring/Idempotent): introduce bundled types This file currently has several instances defined for specific subtypes. This PR replaces these with bundled structures. This also fixes possible typeclass diamonds when the order defined here conflicts with the general one on subtypes. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory 254/126 Mathlib/Algebra/Order/Ring/Idempotent.lean,Mathlib/RingTheory/Spectrum/Prime/Topology.lean 2 4 ['github-actions', 'mathlib-merge-conflicts'] nobody
2-51895
2 days ago
2-52469
2 days ago
74-24411
74 days
0
41042 Raph-DG
author:Raph-DG
feat(Topology/CategoryTheory): the skyscraper sheaf as a sheaf of modules In this PR we define the skyscraper sheaf as a sheaf of modules --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
383/0 Mathlib.lean,Mathlib/Algebra/Category/ModuleCat/Sheaf/Skyscraper.lean 2 5 ['Raph-DG', 'attilavjda', 'chrisflav', 'github-actions', 'mathlib-merge-conflicts'] kim-em
assignee:kim-em
2-51256
2 days ago
100-27565
100 days ago
115-40852
115 days
0
42821 EtienneC30
author:EtienneC30
chore: deprecate PMF Deprecate [PMF](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Probability/ProbabilityMassFunction/Basic.html#PMF). The preferred spelling is to use [MeasureTheory.Measure.sum](https://leanprover-community.github.io/mathlib4_docs/Mathlib/MeasureTheory/Measure/MeasureSpace.html#MeasureTheory.Measure.sum) and [MeasureTheory.Measure.dirac](https://leanprover-community.github.io/mathlib4_docs/Mathlib/MeasureTheory/Measure/Dirac.html#MeasureTheory.Measure.dirac), see how [ProbabilityTheory.poissonMeasure](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Probability/Distributions/Poisson/Basic.html#ProbabilityTheory.poissonMeasure) and [ProbabilityTheory.geometricMeasure](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Probability/Distributions/Geometric.html#ProbabilityTheory.geometricMeasure) are defined for instance. This was discussed on Zulip among reviewers, and see also https://leanprover.zulipchat.com/#narrow/channel/113489-new-members/topic/generic.20shannon.20entropy.20formalization.20mathlib4/near/584361371 for pointers to some PRs where some discussion on the topic happened. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #42908 - [x] depends on: #42909 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-measure-probability large-import 258/175 Mathlib/Probability/ProbabilityMassFunction/Basic.lean,Mathlib/Probability/ProbabilityMassFunction/Binomial.lean,Mathlib/Probability/ProbabilityMassFunction/Constructions.lean,Mathlib/Probability/ProbabilityMassFunction/Integrals.lean,Mathlib/Probability/ProbabilityMassFunction/Monad.lean 5 7 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] urkud
assignee:urkud
2-51255
2 days ago
25-12814
25 days ago
44-71681
44 days
0
43327 JX-Mo
author:JX-Mo
feat(GroupTheory): add `LeftDecomposition` of double coset This PR is the first piece of #43286 for adding `Hecke/LeftFiniteDoubleCoset`. The main motivation is to describe the intertwining space `Hom_G(k[G/H₁], k[G/H₂])` as the free module double cosets with finite left-coset decomposition. In this PR we introduce only the left decomposition. We deliberately design two indexing types for the left-coset decomposition: the intrinsic LeftDecomposition and the computational LeftDecompQuotient. They are equivalent via toLeftDecompositionEquiv. The first is useful for coordinate-free definitions and proofs, which saves us from abusing Quotient.out everywhere (note that we have three quotients in Hecke theory: `G/H₂, H₁/H₁∩gH₂g⁻¹, H₁\G/H₂`) and avoids "choosing representative from decomposition in the def => proving the def does not depend the choice + repeating this kind of argument for comparing different representatives in many downstream proofs" pattern. The second LeftDecompQuotient carries a fixed base point `gH₂` and remains useful for concrete convolution product computation. t-algebra
label:t-algebra$
115/0 Mathlib.lean,Mathlib/RepresentationTheory/Hecke/LeftFiniteDoubleCoset.lean 2 1 ['github-actions'] joelriou
assignee:joelriou
2-51254
2 days ago
31-37750
31 days ago
81-44438
81 days
4
43358 EtienneC30
author:EtienneC30
feat: strong measurability of a path-valued random variable If `X` is a right-continuous strongly adapted stochastic process, then it is strongly measurable when seen as a path-valued random variable. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #43352 - [x] depends on: #43525 - [x] depends on: #45077 Co-authored-by: @RemyDegenne [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) brownian t-measure-probability 203/0 Mathlib.lean,Mathlib/Probability/Process/StronglyMeasurablePath.lean,Mathlib/Topology/NhdsWithin.lean 3 9 ['EtienneC30', 'github-actions', 'jvanwinden', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] urkud
assignee:urkud
2-51250
2 days ago
32-17517
32 days ago
53-25447
53 days
1
43409 gasparattila
author:gasparattila
doc: expand the documentation on `SMul ℕ` defeq issues --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
20/1 Mathlib/Algebra/Group/Monoid.lean 1 3 ['Vierkantor', 'gasparattila', 'github-actions'] joelriou
assignee:joelriou
2-51247
2 days ago
79-81683
79 days ago
79-81628
79 days
0
46104 urkud
author:urkud
feat(MeasureTheory): `comap` of s-finite and σ-finite measures * Add `MeasureTheory.nullMeasurableSet_sum` (tagged `@[simp]`). * Add `Measure.comap_sum`. * Add `Measure.FiniteSpanningSetsIn.comap` and `SigmaFinite.comap`. * Add instances `SFinite (μ.comap f)` and `SigmaFinite (μ.comap ((↑) : Subtype p → α))`. `Mathlib.MeasureTheory.Measure.Comap` now imports `Mathlib.MeasureTheory.Measure.Sum`. Upstreamed from the [SardMoreira](https://github.com/urkud/SardMoreira/) project. 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-measure-probability LLM-generated 54/0 Mathlib/MeasureTheory/Measure/Comap.lean,Mathlib/MeasureTheory/Measure/Sum.lean,Mathlib/MeasureTheory/Measure/Typeclasses/SFinite.lean 3 1 ['github-actions'] RemyDegenne
assignee:RemyDegenne
2-51246
2 days ago
4-80276
4 days ago
4-80221
4 days
0
39067 mbkybky
author:mbkybky
feat(Algebra/Module): define modules admitting finite free resolutions We say that an `R`-module `M` has a finite free resolution if there exists an exact sequence `0 ⟶ Eₙ ⟶ ⋯ ⟶ E₀ ⟶ M ⟶ 0` such that `Eᵢ` are finite free `R`-modules. - [x] depends on: #41880 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
171/0 Mathlib.lean,Mathlib/Algebra/Module/FiniteFreeResolution/Basic.lean 2 4 ['github-actions', 'joelriou', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
2-50356
2 days ago
62-10495
62 days ago
101-48978
101 days
2
43472 gasparattila
author:gasparattila
refactor: replace `SemilatticeSup.sup` with `max` This PR replaces the `sup` field of `SemilatticeSup` with `Max.max`. This will enable further refactors such as redefining `SemilatticeSup` using `Std.LawfulOrderSup` or making `LinearOrder` extend `Lattice`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #44002 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order 159/192 Archive/MinimalSheffer.lean,Archive/Robbins.lean,Mathlib/Algebra/Category/ModuleCat/Presheaf/Submodule.lean,Mathlib/Algebra/Category/ModuleCat/Sheaf/Submodule.lean,Mathlib/Algebra/Field/Subfield/Basic.lean,Mathlib/Algebra/Group/Subgroup/Lattice.lean,Mathlib/Algebra/Group/Submonoid/Basic.lean,Mathlib/Algebra/Group/Subsemigroup/Basic.lean,Mathlib/Algebra/Lie/Subalgebra.lean,Mathlib/Algebra/Module/Submodule/Lattice.lean,Mathlib/Algebra/Order/GroupWithZero/Canonical.lean,Mathlib/Algebra/Order/Kleene.lean,Mathlib/Algebra/Order/Ring/Idempotent.lean,Mathlib/Algebra/Ring/Subring/Basic.lean,Mathlib/Algebra/Ring/Subsemiring/Basic.lean,Mathlib/Algebra/Tropical/Lattice.lean,Mathlib/AlgebraicGeometry/IdealSheaf/Basic.lean,Mathlib/AlgebraicTopology/SimplicialComplex/Basic.lean,Mathlib/Analysis/BoxIntegral/Box/Basic.lean,Mathlib/Analysis/BoxIntegral/Partition/Basic.lean,Mathlib/Analysis/Convex/SimplicialComplex/Basic.lean,Mathlib/Analysis/Normed/Group/Seminorm.lean,Mathlib/Analysis/Normed/Module/MStructure.lean,Mathlib/Analysis/Normed/Module/Seminorm/Basic.lean,Mathlib/Basic/PEquiv.lean,Mathlib/Basic/Real/Basic.lean,Mathlib/CategoryTheory/Groupoid/Subgroupoid.lean,Mathlib/CategoryTheory/Limits/Preorder.lean,Mathlib/CategoryTheory/Sites/Coverage.lean,Mathlib/CategoryTheory/Sites/Grothendieck.lean,Mathlib/CategoryTheory/Sites/Pretopology.lean,Mathlib/CategoryTheory/Sites/Sieves/Basic.lean,Mathlib/CategoryTheory/Subfunctor/Basic.lean,Mathlib/CategoryTheory/Subfunctor/SubmonoidFunctor.lean,Mathlib/CategoryTheory/Subobject/Lattice.lean,Mathlib/Combinatorics/Graph/Lattice.lean,Mathlib/Computability/Reduce.lean,Mathlib/Data/DFinsupp/Order.lean,Mathlib/Data/Finset/Lattice/Basic.lean,Mathlib/Data/Multiset/UnionInter.lean,Mathlib/Data/Semiquot.lean,Mathlib/Data/Set/Basic.lean,Mathlib/Dynamics/Circle/RotationNumber/TranslationNumber.lean,Mathlib/Geometry/Convex/Cone/Face/Lattice.lean,Mathlib/Geometry/Manifold/StructureGroupoid.lean,Mathlib/GroupTheory/Congruence/Defs.lean,Mathlib/LinearAlgebra/AffineSpace/AffineSubspace/Defs.lean,Mathlib/LinearAlgebra/LinearPMap.lean,Mathlib/MeasureTheory/Function/AEEqFun.lean,Mathlib/MeasureTheory/Function/SimpleFunc.lean,Mathlib/ModelTheory/Substructures.lean,Mathlib/Order/BooleanSubalgebra.lean,Mathlib/Order/Booleanisation.lean,Mathlib/Order/Bounds/Basic.lean,Mathlib/Order/CompleteLattice/Defs.lean,Mathlib/Order/Copy.lean,Mathlib/Order/Defs/Lattice.lean,Mathlib/Order/Filter/Basic.lean,Mathlib/Order/Filter/Germ/Basic.lean,Mathlib/Order/FixedPoints.lean,Mathlib/Order/GaloisConnection/Basic.lean,Mathlib/Order/Heyting/Basic.lean,Mathlib/Order/Heyting/Regular.lean,Mathlib/Order/Hom/Order.lean,Mathlib/Order/Ideal.lean,Mathlib/Order/Interval/Basic.lean,Mathlib/Order/Lattice.lean,Mathlib/Order/Partition/Basic.lean,Mathlib/Order/Partition/Finpartition.lean,Mathlib/Order/Preorder/Finsupp.lean,Mathlib/Order/PropInstances.lean,Mathlib/Order/Setoid/Basic.lean,Mathlib/Order/Sublattice.lean,Mathlib/Order/Sum/Lattice.lean,Mathlib/Order/WithBot.lean,Mathlib/Probability/Process/Filtration.lean,Mathlib/RingTheory/Congruence/Basic.lean,Mathlib/RingTheory/Finiteness/Basic.lean,Mathlib/RingTheory/Finiteness/Small.lean,Mathlib/RingTheory/NonUnitalSubring/Basic.lean,Mathlib/RingTheory/NonUnitalSubsemiring/Basic.lean,Mathlib/RingTheory/TwoSidedIdeal/Lattice.lean,Mathlib/RingTheory/UniqueFactorizationDomain/FactorSet.lean,Mathlib/RingTheory/Valuation/ValuationSubring.lean,Mathlib/Topology/Algebra/Group/GroupTopology.lean,Mathlib/Topology/Algebra/Module/ClosedSubmodule.lean,Mathlib/Topology/Category/TopCat/OpenNhds.lean,Mathlib/Topology/LocallyFinsupp.lean,Mathlib/Topology/MetricSpace/BundledFun.lean,Mathlib/Topology/Sets/Compacts.lean,Mathlib/Topology/UniformSpace/Basic.lean,MathlibTest/DefEqAbuse.lean 92 12 ['JovanGerb', 'gasparattila', 'github-actions', 'leanprover-radar', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
2-50267
2 days ago
2-52142
2 days ago
47-31084
47 days
0
46268 j-loreaux
author:j-loreaux
feat: the convex cone underlying a pointed cone hull --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order t-algebra t-convex-geometry
label:t-algebra$
19/0 Mathlib/Geometry/Convex/Cone/Pointed.lean 1 1 ['github-actions'] nobody
2-46290
2 days ago
2-46970
2 days ago
2-46915
2 days
0
45823 SnirBroshi
author:SnirBroshi
feat(Order/DirSupClosed): a finite union of `DirSupClosed` sets is `DirSupClosed` --- I don't have a solution to `large-import` other than creating a new file. Although the large import is private, so maybe it's okay. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order large-import 63/0 Mathlib/Order/DirSupClosed.lean 1 1 ['github-actions', 'themathqueen'] nobody
2-44353
2 days ago
13-41216
13 days ago
13-41161
13 days
0
46235 mcdoll
author:mcdoll
chore(Algebra,RingTheory): golf proofs This came from a stale PR that tried to remove the bad `RingHomClass` coercion. These changes should be uncontroversial. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 15/38 Mathlib/Algebra/Algebra/Prod.lean,Mathlib/Algebra/Algebra/Spectrum/Basic.lean,Mathlib/Algebra/MvPolynomial/Equiv.lean,Mathlib/Algebra/Order/CompleteField.lean,Mathlib/Algebra/Polynomial/GroupRingAction.lean,Mathlib/LinearAlgebra/Dimension/Basic.lean,Mathlib/RingTheory/Adjoin/Polynomial/Basic.lean,Mathlib/RingTheory/MvPowerSeries/Basic.lean,Mathlib/Topology/Algebra/Algebra.lean 9 3 ['github-actions', 'leanprover-radar', 'mcdoll'] nobody
2-37628
2 days ago
3-10736
3 days ago
3-10681
3 days
0
38393 staroperator
author:staroperator
refactor(ModelTheory): add typeclasses for algebraic symbols `Language.ring` and `Language.presburger` share the same symbols `0`, `1` and `+` and have duplicated instances on `Term` and `realize` simp lemmas. This PR makes these symbols certain typeclasses (similar to [`Language.IsOrdered`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/ModelTheory/Order.html#FirstOrder.Language.IsOrdered)) and removes the duplication. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-logic tech debt 401/202 Mathlib.lean,Mathlib/ModelTheory/Algebra/Classes.lean,Mathlib/ModelTheory/Algebra/Field/IsAlgClosed.lean,Mathlib/ModelTheory/Algebra/Ring/Basic.lean,Mathlib/ModelTheory/Algebra/Ring/FreeCommRing.lean,Mathlib/ModelTheory/Arithmetic/Presburger/Basic.lean,Mathlib/ModelTheory/Arithmetic/Presburger/Definability.lean 7 10 ['fpvandoorn', 'github-actions', 'mathlib-merge-conflicts', 'staroperator'] fpvandoorn
assignee:fpvandoorn
2-33597
2 days ago
2-34005
2 days ago
55-44270
55 days
1
43859 kebekus
author:kebekus
feat: Jensen-Type Inequality for Circle Averages In preparation for the upcoming proof of Nevanlinna's "Lemma on Logarithmic Derivatives", establish a Jensen-type inequality for circle averages, where the positive part of the logarithm plays the role of the concave function. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-measure-probability LLM-generated 136/3 Mathlib.lean,Mathlib/Analysis/Complex/CauchyIntegral.lean,Mathlib/Analysis/Complex/Liouville.lean,Mathlib/Analysis/Complex/OpenMapping.lean,Mathlib/Analysis/Complex/PhragmenLindelof.lean,Mathlib/Analysis/Complex/RemovableSingularity.lean,Mathlib/Analysis/Complex/Schwarz.lean,Mathlib/Analysis/Complex/ValueDistribution/LogDerivLemma.lean,Mathlib/Analysis/Convex/SpecificFunctions/Basic.lean,Mathlib/Analysis/Normed/Algebra/GelfandFormula.lean,Mathlib/Analysis/SpecialFunctions/Bessel.lean,Mathlib/Analysis/SpecialFunctions/Elliptic/Weierstrass.lean,Mathlib/Analysis/SpecialFunctions/Gamma/Beta.lean,Mathlib/Analysis/SpecialFunctions/Integrals/PosLog.lean,Mathlib/Analysis/SpecialFunctions/Log/Basic.lean,Mathlib/MeasureTheory/Integral/CircleAverage.lean,Mathlib/MeasureTheory/Integral/CircleIntegral.lean,Mathlib/MeasureTheory/Measure/Typeclasses/Finite.lean,Mathlib/NumberTheory/Harmonic/ZetaAsymp.lean,Mathlib/NumberTheory/LSeries/DirichletContinuation.lean,Mathlib/NumberTheory/LSeries/ZMod.lean,Mathlib/Probability/Moments/ComplexMGF.lean 22 18 ['EtienneC30', 'github-actions', 'kebekus', 'mathlib-merge-conflicts'] urkud
assignee:urkud
2-32982
2 days ago
2-33662
2 days ago
62-76938
62 days
0
45794 ambrose-tang
author:ambrose-tang
feat(LinearAlgebra/Matrix/Cartan/Basic): submatrices and bonds of finite Cartan matrices This PR adds basic API for `Matrix.IsFiniteCartan`: * relabellings of finite Cartan matrices are finite Cartan matrices (`IsFiniteCartan.reindex`, `IsFiniteCartan.submatrix_equiv_iff`); * `IsFiniteCartan.mul_lt_four`: `Mᵢⱼ Mⱼᵢ < 4` for `i ≠ j`; * `CartanMatrix.bonds` (the five possible pairs `(Mᵢⱼ, Mⱼᵢ)` of non-zero off-diagonal entries), the predicate `CartanMatrix.IsBond` with the characterisation `CartanMatrix.isBond_iff`, and `IsFiniteCartan.apply_cases`; * `CartanMatrix.IsBond` and `IsFiniteCartan.apply_cases`: the five possible pairs `(Mᵢⱼ, Mⱼᵢ)` of non-zero off-diagonal entries; * the symmetries `CartanMatrix.A_submatrix_revPerm` and `CartanMatrix.D_submatrix_swap`. This is part 1 of 7 of the classification of finite Cartan matrices (`Matrix.IsFiniteCartan.exists_A_or_B_or_C_or_D_or_E_or_F_or_G`, see `Wanted/LinearAlgebra/Matrix/Cartan/Basic.lean`). t-algebra new-contributor
label:t-algebra$
100/1 Mathlib/LinearAlgebra/Matrix/Cartan/Basic.lean 1 19 ['ambrose-tang', 'github-actions', 'mathlib-merge-conflicts', 'vihdzp', 'wwylele'] nobody
2-25504
2 days ago
2-27267
2 days ago
10-67530
10 days
6
45828 aliquis11
author:aliquis11
feat(Analysis/InnerProductSpace/LinearPMap): characterise the adjoint domain Add a characterisation of the adjoint domain of a densely defined operator. The existing mem_adjoint_domain_of_exists gives one implication. The new result states that domain membership is equivalent to the existence of a vector satisfying the inner product identity. This standard characterisation from functional analysis is useful in constructing the Friedrichs extension. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis new-contributor 33/0 Mathlib/Analysis/InnerProductSpace/LinearPMap.lean,Mathlib/Topology/Algebra/Module/ContinuousLinearMap/Restrict.lean 2 19 ['aliquis11', 'github-actions', 'j-loreaux', 'lyw-ops', 'mcdoll'] nobody
2-20954
2 days ago
2-22824
2 days ago
8-70734
8 days
0
46133 thorimur
author:thorimur
chore: change uses of `TopologicalSpace.Opens.is_open'` to `TopologicalSpace.Opens.isOpen` This PR changes uses of the projection `TopologicalSpace.Opens` to `isOpen` and advises doing so more generally in that field's docstring. Note: it does not make `is_open'` private, though, as that would require making the constructor private too, preventing us from writing e.g. `{ carrier := ..., is_open' := ... }`. Moving to a smart constructor or linting against this projection is a larger change. --- - [x] depends on: #45389 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology tech debt 173/172 Mathlib/AlgebraicGeometry/AffineScheme.lean,Mathlib/AlgebraicGeometry/AffineTransitionLimit.lean,Mathlib/AlgebraicGeometry/Artinian.lean,Mathlib/AlgebraicGeometry/Birational/Birational.lean,Mathlib/AlgebraicGeometry/Birational/Composition.lean,Mathlib/AlgebraicGeometry/Birational/RationalMap.lean,Mathlib/AlgebraicGeometry/Cover/QuasiCompact.lean,Mathlib/AlgebraicGeometry/GammaSpecAdjunction.lean,Mathlib/AlgebraicGeometry/Group/Smooth.lean,Mathlib/AlgebraicGeometry/IdealSheaf/Basic.lean,Mathlib/AlgebraicGeometry/Modules/Tilde.lean,Mathlib/AlgebraicGeometry/Morphisms/Affine.lean,Mathlib/AlgebraicGeometry/Morphisms/ClosedImmersion.lean,Mathlib/AlgebraicGeometry/Morphisms/Constructors.lean,Mathlib/AlgebraicGeometry/Morphisms/Flat.lean,Mathlib/AlgebraicGeometry/Morphisms/FlatRank.lean,Mathlib/AlgebraicGeometry/Morphisms/OpenImmersion.lean,Mathlib/AlgebraicGeometry/Morphisms/QuasiCompact.lean,Mathlib/AlgebraicGeometry/Morphisms/QuasiSeparated.lean,Mathlib/AlgebraicGeometry/Morphisms/Smooth.lean,Mathlib/AlgebraicGeometry/Morphisms/SurjectiveOnStalks.lean,Mathlib/AlgebraicGeometry/Morphisms/UnderlyingMap.lean,Mathlib/AlgebraicGeometry/Morphisms/UniversallyClosed.lean,Mathlib/AlgebraicGeometry/Normalization.lean,Mathlib/AlgebraicGeometry/OpenImmersion.lean,Mathlib/AlgebraicGeometry/PointsPi.lean,Mathlib/AlgebraicGeometry/ProjectiveSpectrum/Scheme.lean,Mathlib/AlgebraicGeometry/Properties.lean,Mathlib/AlgebraicGeometry/QuasiAffine.lean,Mathlib/AlgebraicGeometry/Sites/SmallAffineZariski.lean,Mathlib/AlgebraicGeometry/Spec.lean,Mathlib/AlgebraicGeometry/SpreadingOut.lean,Mathlib/AlgebraicGeometry/Stalk.lean,Mathlib/AlgebraicGeometry/StructureSheaf.lean,Mathlib/AlgebraicGeometry/ZariskisMainTheorem.lean,Mathlib/Geometry/Manifold/HasGroupoid.lean,Mathlib/Geometry/Manifold/IsManifold/InteriorBoundary.lean,Mathlib/Geometry/Manifold/Sheaf/LocallyRingedSpace.lean,Mathlib/Geometry/RingedSpace/Basic.lean,Mathlib/Geometry/RingedSpace/LocallyRingedSpace/HasColimits.lean,Mathlib/MeasureTheory/Integral/RieszMarkovKakutani/Real.lean,Mathlib/MeasureTheory/Measure/Content.lean,Mathlib/RingTheory/Spectrum/Prime/Chevalley.lean,Mathlib/RingTheory/Spectrum/Prime/FreeLocus.lean,Mathlib/RingTheory/Spectrum/Prime/TensorProduct.lean,Mathlib/RingTheory/Spectrum/Prime/Topology.lean,Mathlib/Topology/Category/TopCat/Opens.lean,Mathlib/Topology/Constructible.lean,Mathlib/Topology/ContinuousMap/T0Sierpinski.lean,Mathlib/Topology/JacobsonSpace.lean,Mathlib/Topology/LocalAtTarget.lean,Mathlib/Topology/OpenPartialHomeomorph/Basic.lean,Mathlib/Topology/OpenPartialHomeomorph/Constructions.lean,Mathlib/Topology/Order/Category/FrameAdjunction.lean,Mathlib/Topology/Sets/Closeds.lean,Mathlib/Topology/Sets/CompactOpenCovered.lean,Mathlib/Topology/Sets/Compacts.lean,Mathlib/Topology/Sets/OpenCover.lean,Mathlib/Topology/Sets/Opens.lean,Mathlib/Topology/Sheaves/Points.lean,Mathlib/Topology/Sheaves/Presheaf.lean,Mathlib/Topology/Sheaves/Skyscraper.lean,Mathlib/Topology/Sheaves/Stalks.lean,Mathlib/Topology/Spectral/Prespectral.lean 64 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
2-18611
2 days ago
2-69568
2 days ago
4-828
4 days
0
43490 xroblot
author:xroblot
feat(NumberTheory/NumberField): quadratic fields and their discriminant This PR introduces quadratic fields, that is number fields of degree `2` over `ℚ` and relates them to the quadratic algebras. There is no new definition: a quadratic field is a field `K` of characteristic zero such that `Algebra.IsQuadraticExtension ℚ K` holds. The instance `NumberField K` is then automatic. The main results are: * the discriminant of `K` is a fundamental discriminant; * the ring of integers of `K` is isomorphic to `QuadraticAlgebra ℤ (discr K / 4) (discr K % 4)`; * `K` is isomorphic to `ℚ(√(discr K))`; * two quadratic fields are isomorphic if and only if they have the same discriminant. Along the way it also proves that `discr K` is not `1` and not a square, and that `√(discr K)` lies in `K`. Further results on the fields `ℚ(√d)` and on the real and complex embeddings will follow in later PRs. The mathematics and design are mine. Claude Code was used as a coding assistant and for the housekeeping around this PR. 🤖 --- - [x] depends on: #43088 - [x] depends on: #42554 - [x] depends on: #42297 t-number-theory t-algebra
label:t-algebra$
112/0 Mathlib.lean,Mathlib/NumberTheory/NumberField/QuadraticField/Basic.lean 2 13 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'tb65536', 'xroblot'] riccardobrasca
assignee:riccardobrasca
2-18166
2 days ago
10-21360
10 days ago
10-21389
10 days
3
41472 BryceT233
author:BryceT233
feat(Algebra/TotalMonoidAlgebra): add ring structures and canonical equivalences This PR is part of the broader plan on [reworking Finsupp, MonoidAlgebra, HahnSeries. PowerSeries](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Reworking.20Finsupp.2C.20MonoidAlgebra.2C.20HahnSeries.2E.20PowerSeries/with/608547586). We extend the algebraic hierarchy for `TotalMonoidAlgebra` with commutative semiring and ring structures. We also add some canonical maps and equivalences such as `R⟦M × N⟧ ≃+* R⟦N⟧⟦M⟧` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) - [x] depends on: #41521 - [x] depends on: #44654 - [x] depends on: #44655 - [x] depends on: #44656 - [x] depends on: #44814 - [x] depends on: #45570 t-algebra maintainer-merge
label:t-algebra$
258/1 Mathlib/Algebra/TotalMonoidAlgebra/Defs.lean 1 22 ['BryceT233', 'YaelDillies', 'github-actions', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'themathqueen'] nobody
2-17571
2 days ago
10-51344
10 days ago
49-14819
49 days
0
41915 theebayuser
author:theebayuser
feat(Data/List): infixes, the enumerator of contiguous factors This PR adds `List.infixes`, which is the list of all infixes of a list. --- AI disclosure: This code was mostly generated by Claude Fable 5 and Opus 4.8 as part of my larger project on combinatorics on words, which I then reviewed and revised to contribute to mathlib. t-data LLM-generated new-contributor 37/2 Mathlib/Data/List/Infix.lean 1 7 ['YaelDillies', 'github-actions', 'mathlib-merge-conflicts', 'theebayuser'] YaelDillies
assignee:YaelDillies
2-17407
2 days ago
3-22470
3 days ago
109-38672
109 days
0
45671 fbarroero
author:fbarroero
feat(NumberTheory/NumberField/Ostrowski): prove Ostrowski's theorem for number fields, archimedean case We prove the archimedean case of Ostrowski's theorem for number fields: every archimedean absolute value on a number field `K` is equivalent to the absolute value of a unique infinite place of `K`. Main results, in the new file `Mathlib/NumberTheory/NumberField/Ostrowski.lean`: - `NumberField.existsUnique_infinitePlace_isEquiv`: `∃! w : InfinitePlace K, v ≈ w.val` - `NumberField.exists_complexEmbedding_rpow_eq`: `v x = ‖σ x‖ ^ t` for some `σ : K →+* ℂ` and `0 < t` This PR was generated with the help of Codex. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated t-number-theory 150/0 Mathlib.lean,Mathlib/Analysis/Normed/Field/Ultra.lean,Mathlib/NumberTheory/NumberField/Ostrowski.lean,Mathlib/NumberTheory/Ostrowski.lean 4 2 ['copilot-pull-request-reviewer', 'github-actions'] nobody
2-16301
2 days ago
2-16301
2 days ago
2-16259
2 days
0
45324 joelriou
author:joelriou
feat(AlgebraicTopology): the model structure on Under categories This is dual to the existing construction for `Over` categories --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-category-theory maintainer-merge 118/3 Mathlib/AlgebraicTopology/ModelCategory/Over.lean,Mathlib/CategoryTheory/LiftingProperties/Over.lean,Mathlib/CategoryTheory/Limits/Over.lean,Mathlib/CategoryTheory/MorphismProperty/Comma.lean 4 3 ['FernandoChu', 'github-actions', 'mathlib-merge-conflicts', 'robin-carlier'] robin-carlier
assignee:robin-carlier
2-11566
2 days ago
11-71978
11 days ago
26-75478
26 days
0
45413 joelriou
author:joelriou
feat(CategoryTheory/Abelian): monoidal abelian categories with functorial flat resolutions If `A` is a monoidal category, we introduce a property of objects `ObjectProperty.Monoidal.flat : ObjectProperty A` which is satisfied by objects `X : A` such that both functors `tensorLeft X : A ⥤ A` and `tensorRight X : A ⥤ A` are exact (i.e. preserve both finite limits and finite colimits). Moreover, if `A` is an abelian category, we introduce a typeclass `Abelian.HasFunctorialFlatResolution A` which says that objects in `A` admit a functorial epimorphism from a flat object. --- - [x] depends on: #45418 - [x] depends on: #45417 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-category-theory maintainer-merge 116/4 Mathlib.lean,Mathlib/CategoryTheory/Abelian/Flat/Basic.lean,Mathlib/CategoryTheory/Limits/ExactFunctor.lean,Mathlib/CategoryTheory/ObjectProperty/Retract.lean 4 9 ['github-actions', 'joelriou', 'mathlib-dependent-issues', 'robin-carlier'] robin-carlier
assignee:robin-carlier
2-10168
2 days ago
2-10169
2 days ago
22-70114
22 days
0
45838 WenrongZou
author:WenrongZou
feat(Topology/PontryaginDual): additivize Pontryagin Dual In this PR, we additivize `PontryaginDual` to `AddPontryaginDual`, which is defined to be `A →ₜ+ Additive Circle` for `[AddMonoid A]`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology 220/21 Mathlib/Tactic/Translate/ToAdditive.lean,Mathlib/Topology/Algebra/PontryaginDual.lean 2 15 ['WenrongZou', 'github-actions', 'tb65536', 'vihdzp'] nobody
2-7844
2 days ago
12-84541
12 days ago
12-84486
12 days
1
45252 YaelDillies
author:YaelDillies
feat(Order): `ι →₀ α` is conditionally complete when `α` is ... and similarly for `DFinsupp`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 104/0 Mathlib.lean,Mathlib/Data/DFinsupp/Order.lean,Mathlib/Order/ConditionallyCompleteLattice/Finsupp.lean,Mathlib/Order/ConditionallyCompleteLattice/Indexed.lean,Mathlib/Order/Preorder/Finsupp.lean 5 4 ['YaelDillies', 'github-actions', 'mathlib-merge-conflicts', 'wwylele'] nobody
2-6117
2 days ago
17-18750
17 days ago
26-85977
26 days
1
45590 justus-springer
author:justus-springer
refactor(Geometry/Convex/): generalize `parallelepiped` to linearly ordered fields Mathlib's `parallelepiped` is currently only defined for families of vectors in a real vector space. This PR generalized the definition to arbitrary linearly ordered fields, along with most of its API. Moreover, several proofs were significantly shortened and some new API lemmas were added for convenience. New API lemmas: * `parallelepiped_of_isEmpty`: the parallelepiped of an empty family is `{0}` * `zero_mem_parallelepiped` * `parallelepiped_unique`: a parallelepiped spanned by a single vector is a segment * `parallelepiped_sumElim`: the parallelepiped of a family in `E × F` built from families in `E` and `F` is the product of the parallelepipeds * `LinearIndependent.sum_smul_mem_parallelepiped_iff`: a criterion for linear combination to be in the parallelepiped * `parallelepiped_basisFun`: the parallelepiped of the standard basis is a cube * `parallelepiped_subset_hull`: the parallelepiped is contained in the convex hull. Generative AI was used to find shorter proofs of the API lemmas. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-convex-geometry 162/198 Mathlib.lean,Mathlib/Algebra/Module/ZLattice/Basic.lean,Mathlib/Geometry/Convex/Parallelepiped.lean,Mathlib/Geometry/Euclidean/Volume/Measure.lean,Mathlib/MeasureTheory/Measure/Haar/InnerProductSpace.lean,Mathlib/MeasureTheory/Measure/Haar/OfBasis.lean,Mathlib/MeasureTheory/Measure/Lebesgue/Basic.lean,Mathlib/MeasureTheory/Measure/Lebesgue/EqHaar.lean 8 4 ['github-actions', 'mathlib-merge-conflicts', 'wwylele'] nobody
2-6048
2 days ago
11-67339
11 days ago
19-80496
19 days
2
41069 ymonbru
author:ymonbru
feat: adds the definition of the pushforward of a Ksheaf For f: X to Y a proper map between T2 spaces and Y being locally comapct, this files adds the pushforward of KSheaves: in particular one gets a functor from Ksheaf A X to Ksheaf A Y. In order to prove this lemma, we add the fact that the base changes of compact neighbourhoods of K to f^-1(K) is an initial functor. This require to know that if f is closed then kernImage f (the adjoint of the preimage) is Open. (Note that if f is open then kernImage f is closed, we thus add this lemma even though we do not use it there). We also add the ddefinition of the pushforward of a bicartesian square in order to define the pushforward. Maybe the `properPreimage`in l.101 of BasechngeNhds should go elsewhere but find_home told me to let it there. --- - [x] depends on: #40953 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-topology t-category-theory 99/2 Mathlib/Order/CompleteLattice/MulticoequalizerDiagram.lean,Mathlib/Topology/Sets/BaseChangeNhds.lean,Mathlib/Topology/Sheaves/KSheaf.lean 3 45 ['Multramate', 'github-actions', 'joelriou', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'ymonbru'] nobody
2-4095
2 days ago
2-4467
2 days ago
3-37904
3 days
0
45571 JovanGerb
author:JovanGerb
feat(ClickSuggestions): better pasting logic This PR makes `#click_suggestions` insert its suggestions in the correct place, even if the cursor is not in the place where the tactic should go. In particular, if the cursor is placed after a tactic, or at the start of a tactic, then the position of the insertion is made to align with that tactic syntax, instead of using the cursor position. What is more difficult is to determine the appropriate indentation level after a loose `by`. So, the user still needs to manually add the newline after a `by` before using `#click_suggestions`. This might be improved in a future PR. This PR adds a test file that tests the insertion behaviour. In addition to testing the new behaviour, we also tests some other behaviours that weren't previously tested. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-meta maintainer-merge 411/49 Mathlib/Tactic/ClickSuggestions.lean,Mathlib/Tactic/ClickSuggestions/Util.lean,MathlibTest/ClickSuggestions/Insertion.lean,MathlibTest/ClickSuggestions/TestImpl.lean 4 5 ['github-actions', 'joneugster'] joneugster
assignee:joneugster
2-3002
2 days ago
20-47559
20 days ago
20-47504
20 days
0
46221 j-loreaux
author:j-loreaux
feat: additional API for `List.TFAE` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 75/14 Mathlib/Algebra/Order/Star/Projection.lean,Mathlib/Data/List/Cycle.lean,Mathlib/Data/List/Pairwise.lean,Mathlib/Data/List/Rotate.lean,Mathlib/Data/List/TFAE.lean 5 9 ['github-actions', 'j-loreaux', 'jcommelin', 'mathlib-bors', 'themathqueen'] nobody
2-2793
2 days ago
3-25092
3 days ago
3-27896
3 days
0
46057 grunweg
author:grunweg
feat: fail_if_progress and fail_if_not_idempotent tactic combinators These will be used in #46048 to test for non-idempotent calls of `norm_cast` or `push_cast`. --- TODO: should we actually add the `fail_if_progress` combinator? I wrote this as an early draft, but it actually won't help for the use case I have in mind. TODO: I'm not convinced the goal handling is right yet (and #46048 has some warnings that look caused by this); a close look is appreciated. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-meta 136/15 Mathlib/Tactic/FailIfNoProgress.lean,MathlibTest/Tactic/FailIfNoProgress.lean 2 10 ['github-actions', 'grunweg', 'joneugster', 'thorimur'] thorimur
assignee:thorimur
2-775
2 days ago
6-53781
6 days ago
6-53726
6 days
1
46148 kirill-kondrashov
author:kirill-kondrashov
feat(LinearAlgebra/ExteriorPower): hodgeStar isometry Prove that, for any bijective bilinear form `B`, the Hodge star preserves the induced bilinear form on exterior powers up to a scalar: ``` Δ * B.exteriorPower l (hodgeStar B hB vol hkl x) (hodgeStar B hB vol hkl y) = B.exteriorPower k x y ``` where `Δ := B.exteriorPower (finrank R M) (vol.symm 1) (vol.symm 1)`. This removes the corresponding item from the `TODO` in `Mathlib/LinearAlgebra/ExteriorPower/HodgeStar.lean`. The proof was assisted by Claude Sonnet 5.5 Max in a multi-prompt session with manual adjustments and human review. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra LLM-generated new-contributor
label:t-algebra$
58/8 Mathlib/LinearAlgebra/ExteriorPower/BilinForm.lean,Mathlib/LinearAlgebra/ExteriorPower/HodgeStar.lean 2 6 ['github-actions', 'kirill-kondrashov', 'ocfnash'] nobody
2-188
2 days ago
2-680
2 days ago
2-85631
2 days
0
45529 joelriou
author:joelriou
feat(CategoryTheory/MorphismProperty): images of pushouts by functors If `P : MorphismProperty C` and `F : C ⥤ D` is a functor which preserves pushouts, we show `P.pushouts.map F ≤ (P.map F).pushouts`. Similar results are obtained for other shapes. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-category-theory maintainer-merge 123/2 Mathlib/CategoryTheory/MorphismProperty/Limits.lean,Mathlib/CategoryTheory/MorphismProperty/TransfiniteComposition.lean 2 4 ['github-actions', 'joelriou', 'robin-carlier'] robin-carlier
assignee:robin-carlier
1-85916
1 day ago
2-10096
2 days ago
22-9940
22 days
3
45813 DavidLedvinka
author:DavidLedvinka
refactor(Probability/Process/HittingTime): (re)define hitting times on deterministic paths Redefine hitting times initially on deterministic paths. The motivation for this PR can be found here: https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Propose.20refactor.20of.20hitting.20times.20.28and.20stochastic.20processes.29/with/638516122 AI-assistance disclosure: I started with a hand written new version of hitting time. I then asked an LLM to refactor mathlib to use it, but after trying this I decided it was better to start by more closely mirroring the current definitions and API of hitting times in Mathlib, only making some changes that I thought were significant improvements. This was done initially by an LLM but I reviewed the proofs and API and did some further refactoring by hand. LLM-generated t-measure-probability t-dynamics 641/420 Mathlib.lean,Mathlib/Dynamics/HittingTime.lean,Mathlib/Order/ConditionallyCompleteLattice/WithTop.lean,Mathlib/Probability/Martingale/BorelCantelli.lean,Mathlib/Probability/Martingale/OptionalStopping.lean,Mathlib/Probability/Martingale/Upcrossing.lean,Mathlib/Probability/Process/HittingTime.lean,docs/overview.yaml 8 3 ['github-actions', 'mathlib-merge-conflicts'] nobody
1-85772
1 day ago
4-12858
4 days ago
13-46535
13 days
0
46239 justus-springer
author:justus-springer
feat(Topology/Algebra/Group): cocompact subgroups Add `Subgroup.IsCocompact`, an abbreviation for `CompactSpace (G ⧸ H)`, with the characterization by compact sets of representatives and the fact that periodic continuous functions have compact range. This will be used in the lattice refactor (see [Zulip thread](https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Definitions.20of.20lattices/with/628121013)) to characterize full lattices as cocompact subgroups and to replace `IsZLattice.isCompact_range_of_periodic`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology 97/0 Mathlib.lean,Mathlib/Topology/Algebra/Group/Cocompact.lean,Mathlib/Topology/Compactness/LocallyCompact.lean 3 1 ['github-actions'] nobody
1-84156
1 day ago
3-2632
3 days ago
3-2577
3 days
2
41539 rmhi
author:rmhi
chore(RepresentationTheory/Homological/ContCohomology): refactor functoriality Currently, functoriality of continuous cohomology is given by `ContCohomology.map`, which takes a continuous group homomorphism \phi and an intertwining map f: res \phi X \to Y and returns a map from the continuous cohomology of X to the continuous cohomology of Y. The problem with this is that `ContCohomology.map` does not have a natural type such as Functor or NatTrans. In this PR, we split `ContCohomology.map` as a composition of `(continuousCohomologyFunctor _ _ _).map` and a restriction map in continuous cohomology, which is defined as a natural transformation `resNatTrans`. co-authored-by: Edison Xie @Whysoserioushah --- - [x] depends on: #45907 - [x] depends on: #45942 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
403/60 Mathlib/RepresentationTheory/Continuous/TopRep.lean,Mathlib/RepresentationTheory/Homological/ContCohomology/Functoriality.lean,Mathlib/RepresentationTheory/Homological/ContCohomology/Sha.lean 3 44 ['JX-Mo', 'Whysoserioushah', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'riccardobrasca', 'rmhi'] riccardobrasca
assignee:riccardobrasca
1-84053
1 day ago
2-7385
2 days ago
78-32953
78 days
1
44075 bjornsolheim
author:bjornsolheim
feat(Analysis/Convex): convex hull of a compact set with finite-dimensional vector span is compact Proves the following: `Set.convexHull_eq_range_sum_smul` - When `K` has a finite dimensional vector span, the convex hull of `K` is the range of weighted sums of `finrank 𝕜 E + 1` points of `K`, with nonnegative weights summing to one. `IsCompact.convexHull` - The convex hull of a compact set with finite-dimensional vector span is compact. Assisted by: Claude Fable 5.1 (used for research and to write or complete or improve some parts). Some parts are hence iteratively llm-generated based on my inputs. All lines are reviewed in full by me. --- [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis 87/0 Mathlib.lean,Mathlib/Analysis/Convex/Compact.lean 2 6 ['bjornsolheim', 'github-actions', 'themathqueen'] nobody
1-83996
1 day ago
3-59448
3 days ago
60-54769
60 days
2
43884 joelcanary
author:joelcanary
feat(NumberTheory/ArithmeticFunction): the gcd matrix and Smith's determinant This PR adds the GCD matrix `Matrix.gcdMatrix n f` (entry `f (gcd (i + 1) (j + 1))`) and proves **Smith's determinant** (1875): if `f m = ∑ d ∈ m.divisors, g d` for every `m ≥ 1` (i.e. `f = g * ζ` as arithmetic functions), then `det (gcdMatrix n f) = ∏ i, g (i + 1)`, over any commutative ring (`Matrix.det_gcdMatrix`). The classical case `det [gcd (i, j)] = φ 1 * φ 2 * ⋯ * φ n` is `Matrix.det_gcdMatrix_id`, from `Nat.sum_totient`. Proof: the factorisation `gcdMatrix n f = Zᵀ * (D * Z)` (`Matrix.gcdMatrix_eq_transpose_mul_mul`) with `Z = zetaMatrix R n` from #43758 and `D = diagonal (g (i + 1))`; entry-wise this is `∑ k, [k + 1 ∣ i + 1] [k + 1 ∣ j + 1] g (k + 1) = ∑ d ∣ gcd (i + 1) (j + 1), g d`, obtained from the reindexing lemma of #43880 with `a = 1` and `Nat.dvd_gcd_iff` (`Nat.sum_fin_dvd_dvd_eq_sum_divisors_gcd`). Then `det Z = 1` (`Matrix.det_zetaMatrix`) and `det_diagonal`. New file `Mathlib/NumberTheory/ArithmeticFunction/Smith.lean`, importing `Data.Nat.Totient` and `NumberTheory.ArithmeticFunction.ZetaMatrixInv`; `docs/references.bib` gets `smith1875`. The divisor-function instances are included as one-line corollaries: `Matrix.det_gcdMatrix_sigma` (`det [σ k (gcd i j)] = ∏ (i + 1) ^ k`, so `n!` for `k = 1`) and `Matrix.det_gcdMatrix_card_divisors` (`det [τ (gcd i j)] = 1`). The LCM matrix is left for a follow-up. AI use: the Lean code and this description were written with an AI agent (Claude) under my direction, from a proof in my own project; I reviewed every declaration, and the branch was checked locally with `lake build`, `lake exe lint-style`, `lake exe runLinter` and `scripts/lint-bib.sh` before pushing. - [x] depends on: #43880 t-number-theory LLM-generated new-contributor 531/0 Mathlib.lean,Mathlib/NumberTheory/ArithmeticFunction/Moebius.lean,Mathlib/NumberTheory/ArithmeticFunction/Redheffer.lean,Mathlib/NumberTheory/ArithmeticFunction/Smith.lean,Mathlib/NumberTheory/ArithmeticFunction/ZetaMatrixInv.lean,docs/references.bib 6 6 ['github-actions', 'joelcanary', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-83474
1 day ago
1-83477
1 day ago
1-84390
1 day
0
44773 justus-springer
author:justus-springer
doc(*): add bib entries for free-text references The result of an LLM-assisted audit to find free-text references with no entry in `references.bib`. Most bib entries come from zbmath (those have a `zbl` entry). A few didn't have an entry there, so they come from other sources. Some small notes: - I added the other authors to `boldetal2017`, - In `LinearAlgebra/Matrix/Polynomial.lean`, my LLM flagged that Section 5.3 is probably not the appropriate section to cite for this file, and in fact, it seems to be a historical artifact. I checked the paper and Proposition 2.2 fits much better here, so I changed it. - Wittlich's Master thesis is not available online, but the docstring came from a trustworthy source so I just used the details given there for the bib entry. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated documentation maintainer-merge 246/31 Mathlib/Analysis/CStarAlgebra/Module/Defs.lean,Mathlib/Analysis/InnerProductSpace/Defs.lean,Mathlib/Analysis/InnerProductSpace/Projection/Basic.lean,Mathlib/CategoryTheory/Adjunction/Lifting/Left.lean,Mathlib/CategoryTheory/Adjunction/Lifting/Right.lean,Mathlib/Combinatorics/Additive/AP/Three/Behrend.lean,Mathlib/Combinatorics/Additive/CauchyDavenport.lean,Mathlib/Combinatorics/Compactness.lean,Mathlib/Computability/AkraBazzi/AkraBazzi.lean,Mathlib/Computability/AkraBazzi/SumTransform.lean,Mathlib/Geometry/Euclidean/Angle/Oriented/Basic.lean,Mathlib/InformationTheory/Coding/Kraft.lean,Mathlib/InformationTheory/Coding/KraftMcMillan.lean,Mathlib/LinearAlgebra/Matrix/Adjugate.lean,Mathlib/LinearAlgebra/Matrix/Polynomial.lean,Mathlib/MeasureTheory/Measure/Haar/Basic.lean,Mathlib/Probability/Independence/Basic.lean,Mathlib/Topology/Algebra/InfiniteSum/Defs.lean,Mathlib/Topology/Category/Compactum.lean,docs/references.bib 20 16 ['Vierkantor', 'github-actions', 'grunweg', 'joneugster', 'justus-springer', 'mathlib-merge-conflicts'] nobody
1-82460
1 day ago
2-5540
2 days ago
33-18614
33 days
0
45072 HugLycan
author:HugLycan
refactor(Tactic/Positivity): add a cache This PR adds caching to `positivity`, following the implementation in `FunProp`. It is the first step towards #45305 . This does not speed up mathlib but is crucial for `positivity_lemma` attribute. The two test example in the newly created file `Positivity/Cache.lean` took 359 heartbeats and 641 heartbeats respectively before the PR, and 172 heartbeats and 568 heartbeats afterwards. We had to change many positivity extensions for two reasons: - The type of `PositvityExt` has changed from `MetaM` to `PositivityM`. - We have to return `.none` instead of failing to preserve the cache. Most of the positivity extensions will soon be replaced by the `positivity_lemma` attribute. --- <!-- Your PR title will become the first line of the commit messag In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor t-meta file-removed 526/343 Mathlib/Algebra/Order/Algebra.lean,Mathlib/Algebra/Order/BigOperators/Ring/Finset.lean,Mathlib/Algebra/Order/Floor/Extended.lean,Mathlib/Algebra/Order/Floor/Ring.lean,Mathlib/Algebra/Order/Interval/Basic.lean,Mathlib/Analysis/Complex/Exponential.lean,Mathlib/Analysis/Complex/Trigonometric.lean,Mathlib/Analysis/Complex/UpperHalfPlane/Basic.lean,Mathlib/Analysis/Normed/Algebra/GelfandRadius.lean,Mathlib/Analysis/Normed/Group/Basic.lean,Mathlib/Analysis/Real/Sqrt.lean,Mathlib/Analysis/SpecialFunctions/Gamma/Basic.lean,Mathlib/Analysis/SpecialFunctions/Log/Basic.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Analysis/SpecialFunctions/Pow/Real.lean,Mathlib/Analysis/SpecialFunctions/Trigonometric/Basic.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Basic/ENNReal/Real.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/Combinatorics/Enumerative/DyckWord.lean,Mathlib/Combinatorics/SimpleGraph/Regularity/Bound.lean,Mathlib/Combinatorics/SimpleGraph/Triangle/Removal.lean,Mathlib/Data/EReal/Basic.lean,Mathlib/Data/EReal/Inv.lean,Mathlib/Data/EReal/Operations.lean,Mathlib/Data/Nat/Choose/Multinomial.lean,Mathlib/Data/Nat/Totient.lean,Mathlib/Geometry/Convex/ConvexSpace/Defs.lean,Mathlib/Geometry/Euclidean/Altitude.lean,Mathlib/Geometry/Euclidean/Volume/Basic.lean,Mathlib/MeasureTheory/Covering/Besicovitch.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/NumberTheory/ArithmeticFunction/VonMangoldt.lean,Mathlib/NumberTheory/Chebyshev.lean,Mathlib/NumberTheory/Height/Basic.lean,Mathlib/NumberTheory/Height/NumberField.lean,Mathlib/NumberTheory/Height/Projectivization.lean,Mathlib/NumberTheory/LucasLehmer.lean,Mathlib/NumberTheory/SelbergSieve.lean,Mathlib/RingTheory/Radical/NatInt.lean,Mathlib/Tactic/LinearCombination.lean,Mathlib/Tactic/Positivity/Basic.lean,Mathlib/Tactic/Positivity/Core.lean,Mathlib/Tactic/Positivity/Finset.lean,Mathlib/Topology/Algebra/InfiniteSum/Order.lean,Mathlib/Topology/MetricSpace/Bounded.lean,Mathlib/Topology/MetricSpace/Pseudo/Defs.lean,MathlibTest/Tactic/Positivity/Basic.lean,MathlibTest/Tactic/Positivity/Cache.lean 49 15 ['HugLycan', 'JovanGerb', 'fpvandoorn', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] JovanGerb and fpvandoorn
assignee:fpvandoorn assignee:JovanGerb
1-82321
1 day ago
8-20678
8 days ago
13-30500
13 days
2
46066 plp127
author:plp127
chore(Data/Dyadic): move shift lemmas Move the shift lemmas added in #45421 back into `Data/`, since they are generally useful lemmas not specific to the `Inclusion` tactic. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 122/121 Mathlib/Data/Dyadic/Basic.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Dyadic.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Sqrt.lean 3 6 ['Rob23oba', 'github-actions', 'mathlib-merge-conflicts', 'plp127', 'vihdzp'] nobody
1-81704
1 day ago
2-71503
2 days ago
5-75961
5 days
1
43494 wrenna-robson
author:wrenna-robson
refactor: rename the `diag` name token to `diagonal` Per recent discussion on Zulip ([#mathlib4 > antidiagonal vs antidiag](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/antidiagonal.20vs.20antidiag/with/622080434)), we want to move away from using `diag` as a name token. This renames every declaration where `diag` abbreviates *diagonal* so that it is spelled out in full (`antidiag` → `antidiagonal`, `offDiag` → `offDiagonal`, `IsDiag` → `IsDiagonal`, `diagSet` → `diagonalSet`, …), with a `@[deprecated]` alias for each, including the lemmas generated by `@[simps]`. `Function.diag` becomes `Prod.diagonal` (still `protected`). A few names were tidied while being touched, e.g. `mapRange_finsuppAntidiag_{subset,eq}` → `map_finsuppAntidiagonal_mapRange_{subset,eq}`, `{Set,Finset}.offDiag_mono` → `offDiagonal_monotone`, `Finset.diag_mono` → `diagonal_monotone`, `edgeSet_sdiff_sdiff_isDiag` → `edgeSet_sdiff_sdiff_diagonalSet`, `LinearMap.rank_diagonal` → `rank_toLin'_diagonal`, and `Functor.initial_diag_of_isFiltered` → `Functor.initial_diagonal_of_isCofiltered` (its hypothesis is cofilteredness). Some renamed instances were made anonymous instead (no deprecation, as they are instances). I've tried to split it into reviewable commits by area (`Prod`/`offDiag`, `Sym2`/`Finset.diag`, `antidiag`, `CategoryTheory`, misc, leftovers). ## Left for follow-up PRs 1. **File and directory names.** Modules keep `Diag`/`Antidiag` in their paths (e.g. `Mathlib/Algebra/Order/Antidiag/`) so that git history is preserved; moving them (with deprecated module stubs) is a separate PR. 2. **`Set.diagonal` / `Prod.diagonalSet`**: #38380, which also adds a `Set.diagonal` matching `Finset.diagonal`. 3. **Diagonal entries of a matrix.** These are untouched pending a decision on the `Matrix.diag`/`Matrix.diagonal` naming: - `Matrix.diag`, `blockDiag`, `blockDiag'`, `IsDiag` and their API (`diag_*`, `isDiag_*`, `IsDiag.*`, `diagAddMonoidHom`, `diagLinearMap`, `Continuous.matrix_diag`, `HasSum.matrix_diag`, …); - the `Matrix.IsFiniteCartan` fields `diag`/`offDiag_nonpos`, and the Cartan matrix lemmas `{A,B,C,D,E,E₆,F₄,G₂}_diag`, `A_diag_eq_two` and `*_off_diag_nonpos`; - `IsAdjMatrix.apply_diag_ne`, `compl_apply_diag`, `diag_adjMatrix`, `incMatrix_{mul_transpose,transpose_mul}_diag`, `det_ne_zero_of_sum_{row,col}_lt_diag`, `rowScale_apply_diag_of_ne`, `LDL.diag*`; - determinant tactic internals: `certDiag`, `certifyDiagProd(List)`, `certifyLowerTriangularDiag(List)`, `diagProd`, `IsLowerTriangularDiagList`, `paper_eq3_eq5_off_diag`. 4. **`diag` meaning *diagram***, to be renamed to `diagram`: `(Co)limitPresentation.diag` and `changeDiag`, `Galois.EssSurj.quotientDiag` and `coconeQuotientDiag*`, `CommDiag`/`mkCommDiag`. 5. **Protecting `diagonal` defs.** Several namespaces now declare a `diagonal` (e.g. `TopPair.diagonal`); these could be made `protected` to avoid clashes under `open`. Not planned: `List.mapDiagM'` mirrors `List.mapDiagM` upstream and should stay in step with it. LLM-generated 1860/1017 Archive/Imo/Imo1998Q2.lean,Archive/Wiedijk100Theorems/BallotProblem.lean,Counterexamples/SorgenfreyLine.lean,Mathlib/Algebra/BigOperators/Group/Finset/Basic.lean,Mathlib/Algebra/BigOperators/Intervals.lean,Mathlib/Algebra/BigOperators/Sym.lean,Mathlib/Algebra/DirectSum/LinearMap.lean,Mathlib/Algebra/MonoidAlgebra/Defs.lean,Mathlib/Algebra/MvPolynomial/Basic.lean,Mathlib/Algebra/MvPolynomial/Coeff.lean,Mathlib/Algebra/Order/Antidiag/Finsupp.lean,Mathlib/Algebra/Order/Antidiag/FinsuppEquiv.lean,Mathlib/Algebra/Order/Antidiag/Nat.lean,Mathlib/Algebra/Order/Antidiag/Pi.lean,Mathlib/Algebra/Order/BigOperators/Group/LocallyFinite.lean,Mathlib/Algebra/Order/CauSeq/BigOperators.lean,Mathlib/Algebra/Polynomial/Coeff.lean,Mathlib/AlgebraicTopology/FundamentalGroupoid/InducedMaps.lean,Mathlib/AlgebraicTopology/ModelCategory/Cylinder.lean,Mathlib/AlgebraicTopology/ModelCategory/PathObject.lean,Mathlib/AlgebraicTopology/Quasicategory/StrictSegal.lean,Mathlib/AlgebraicTopology/SimplexCategory/Basic.lean,Mathlib/AlgebraicTopology/SimplicialObject/Basic.lean,Mathlib/AlgebraicTopology/SimplicialSet/FundamentalGroupoid/Homotopy.lean,Mathlib/AlgebraicTopology/SimplicialSet/StrictSegal.lean,Mathlib/Analysis/Calculus/FDeriv/Analytic.lean,Mathlib/Analysis/Calculus/UniformLimitsDeriv.lean,Mathlib/Basic/Finite/Prod.lean,Mathlib/CategoryTheory/Abelian/NonPreadditive.lean,Mathlib/CategoryTheory/Comma/Over/Basic.lean,Mathlib/CategoryTheory/Filtered/Final.lean,Mathlib/CategoryTheory/Limits/Shapes/BinaryProducts/BinaryProducts.lean,Mathlib/CategoryTheory/Limits/Sifted.lean,Mathlib/CategoryTheory/Monoidal/ExternalProduct/Basic.lean,Mathlib/CategoryTheory/Monoidal/Functor.lean,Mathlib/CategoryTheory/Monoidal/Limits/Colimits.lean,Mathlib/CategoryTheory/MorphismProperty/Representable.lean,Mathlib/CategoryTheory/Products/Basic.lean,Mathlib/CategoryTheory/Subterminal.lean,Mathlib/Combinatorics/Enumerative/Partition/Basic.lean,Mathlib/Combinatorics/Enumerative/Partition/GenFun.lean,Mathlib/Combinatorics/SimpleGraph/Acyclic.lean,Mathlib/Combinatorics/SimpleGraph/Basic.lean,Mathlib/Combinatorics/SimpleGraph/Copy.lean,Mathlib/Combinatorics/SimpleGraph/DeleteEdges.lean,Mathlib/Combinatorics/SimpleGraph/Finite.lean,Mathlib/Combinatorics/SimpleGraph/Operations.lean,Mathlib/Combinatorics/SimpleGraph/Regularity/Energy.lean,Mathlib/Combinatorics/SimpleGraph/Regularity/Increment.lean,Mathlib/Combinatorics/SimpleGraph/Regularity/Uniform.lean,Mathlib/Combinatorics/SimpleGraph/Subgraph.lean,Mathlib/Combinatorics/SimpleGraph/Triangle/Basic.lean,Mathlib/Combinatorics/SimpleGraph/Triangle/Removal.lean,Mathlib/Data/Fin/Tuple/NatAntidiagonal.lean,Mathlib/Data/Finset/Pi.lean,Mathlib/Data/Finset/Prod.lean,Mathlib/Data/Finset/Sym.lean,Mathlib/Data/Fintype/Pi.lean,Mathlib/Data/Fintype/Prod.lean,Mathlib/Data/List/OffDiag.lean,Mathlib/Data/Nat/Choose/Multinomial.lean,Mathlib/Data/Nat/Init.lean,Mathlib/Data/QPF/Multivariate/Constructions/Cofix.lean,Mathlib/Data/Set/Operations.lean,Mathlib/Data/Set/Prod.lean,Mathlib/Data/Sym/Card.lean,Mathlib/Data/Sym/NatCard.lean,Mathlib/Data/Sym/Sym2.lean,Mathlib/Data/Sym/Sym2/Card.lean,Mathlib/Data/TypeVec.lean,Mathlib/LinearAlgebra/ExteriorPower/Basis.lean,Mathlib/LinearAlgebra/Matrix/Cartan/Realisation.lean,Mathlib/LinearAlgebra/Matrix/Diagonal.lean,Mathlib/LinearAlgebra/Matrix/Rank.lean,Mathlib/LinearAlgebra/Matrix/SpecialLinearGroup.lean,Mathlib/LinearAlgebra/Pi.lean,Mathlib/LinearAlgebra/QuadraticForm/Basic.lean,Mathlib/LinearAlgebra/QuadraticForm/Basis.lean,Mathlib/Logic/Function/Defs.lean,Mathlib/MeasureTheory/MeasurableSpace/Constructions.lean,Mathlib/NumberTheory/Divisors.lean,Mathlib/NumberTheory/HeckeRing/Defs.lean,Mathlib/NumberTheory/Height/Basic.lean,Mathlib/Order/Filter/Prod.lean,Mathlib/Order/FixedPoints.lean,Mathlib/Order/Hom/Basic.lean,Mathlib/Probability/Combinatorics/BinomialRandomGraph/Defs.lean,Mathlib/Probability/Kernel/Basic.lean,Mathlib/Probability/Kernel/Composition/MeasureCompProd.lean,Mathlib/Probability/Kernel/Condexp.lean,Mathlib/Probability/Kernel/Deterministic.lean,Mathlib/Probability/Moments/SubGaussian.lean,Mathlib/RingTheory/Coalgebra/Basic.lean,Mathlib/RingTheory/Discriminant.lean,Mathlib/RingTheory/MatrixPolynomialAlgebra.lean,Mathlib/RingTheory/MvPowerSeries/Basic.lean,Mathlib/RingTheory/MvPowerSeries/Substitution.lean,Mathlib/RingTheory/PowerSeries/Basic.lean,Mathlib/RingTheory/WittVector/InitTail.lean,Mathlib/RingTheory/WittVector/IsPoly.lean 119 74 ['SnirBroshi', 'github-actions', 'grunweg', 'kim-em', 'mathlib-merge-conflicts', 'tb65536', 'themathqueen', 'wrenna-robson'] nobody
1-81308
1 day ago
2-83596
2 days ago
14-30431
14 days
1
46274 paulcadman
author:paulcadman
feat(Tactic/RealRootCount): a computational producer and certificate for Sturm sequences define the untrusted metacode producer of a Sturm sequence certificate associated with a polynomial with rational coefficients together with a certificate validator and root count computation that can be efficiently run in the kernel. In `Tactic/RealRootCount/SturmCertificate.lean`: * `SturmCertificate` - a certificate containing a polynomial with integer coefficients together with a sequence of steps that defined a Sturm sequence of it and its derivative unto positive factors. * `checkSturm` - a function that validates a certificate. * `realRootCount?` - a function that computes the number of distinct real roots of the polynomial in the certificate over the whole real line. * `realRootCountIoo?` - a function that computes the number of distinct real roots of the polynomial in the certificate over an open interval with rational endpoints. The definitions in `SturmCertificate.lean` are exposed so that `realRootCount? d = some n` can be checked using `Eq.refl` as a kernel computation. In `Tactic/RealRootCount/Core.lean`: * `SturmCertificate.fromCoeffList` - compute a certificate from a polynomial. --- This PR is part of a sequence providing a `eval_real_root_count` tactic. In particular a follow-up PR proves that `checkSturm cert = true` implies that `cert` is a certificate defining a valid Sturm sequence for the polynomial in the certificate. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-meta 252/0 Mathlib.lean,Mathlib/Tactic.lean,Mathlib/Tactic/RealRootCount/Core.lean,Mathlib/Tactic/RealRootCount/SturmCertificate.lean 4 9 ['github-actions', 'ocfnash'] nobody
1-80177
1 day ago
2-20507
2 days ago
2-20452
2 days
1
45720 DavidLedvinka
author:DavidLedvinka
refactor(Tactic/Inclusion): use the coercion from `Dyadic` to `Real` Refactor the inclusion tactic to use the coercion from `Dyadic` to `Real` obtained by composing the coercions from `Dyadic` to `Rat` and `Rat` to `Real` rather than an explicitly defined `toReal` function. This PR is intended to address the concern raised in this zulip thread: [#mathlib4 > Dyadic rationals in Mathlib @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Dyadic.20rationals.20in.20Mathlib/near/622684229). - [x] depends on: #43038 LLM-generated large-import 186/133 Mathlib/Data/Dyadic/Basic.lean,Mathlib/Deprecated/Aliases.lean,Mathlib/Tactic/Inclusion/Core/Elab.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Basic.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/BinarySplit.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Dyadic.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Exp.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Init.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Log.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Rational.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Sqrt.lean 11 14 ['DavidLedvinka', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'vihdzp'] nobody
1-80176
1 day ago
1-80372
1 day ago
10-56947
10 days
0
45670 user202729
author:user202729
chore(AlgebraicGeometry/EllipticCurve/Projective): remove `erw` in `Formula.lean` Reducing tech debt. The main reason why `erw` was needed in this file instead of `rw` is the following. - Background: Each point is represented by a function `P : Fin 3 → R`, and there's local notation `x` being `(0 : Fin 3)`, similar for `y` and `z`. So `P x` is the first coordinate of `P`. For a curve `W'` and a point `P`, `W'.dblXYZ P` is another point, its double i.e. `2 • P`. - There are functions to compute various operations on elliptic curves, for example, `W.dblY P` computes the `Y`-coordinate of `2 • P`. Of course, this can be equivalently written as `W.dblXYZ P y`. - The two forms `W.dblY P` and `W.dblXYZ P y` are not definitionally equal at the default transparency level. Depends on which lemma we want to apply, we need to convert the goal to use one form or the other. --- Personally, I think it's a better idea to normalize on the `W.dblXYZ P y` form, and keep the `W.dblY P` form as strictly an implementation detail if needed. In this case, the `XYZ` suffix wouldn't be needed either, and the main definitions would be: ``` * `WeierstrassCurve.Projective.neg`: The negation `-P` of a point `P`. * `WeierstrassCurve.Projective.dbl`: The double `2 • P` of a point `P`. * `WeierstrassCurve.Projective.negDbl`: The negated double `-(2 • P)` of a point `P`. ``` etc. Thoughts? Note that `W.dbl P y` is only 1 character longer than `W.dblY P`. Most lemmas that we want to apply are already stated in term of the point (except that many use `W.negY P` instead of `W.neg P y`, though currently `W.neg` doesn't exist). Also, there are (very) long `rw` chains. ([#mathlib4 > Is long &#96;rw&#96; chain bad?](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Is.20long.20.60rw.60.20chain.20bad.3F/with/637217759)) Ideas? Another idea: have a `array_index` tactic that evaluates `![a, b, c, d] 2` to `c` when the index is a known constant, for example. Currently there is `simp only [fin3_def_ext]` which obviously only works on length-3 arrays. new-contributor t-algebraic-geometry tech debt 59/24 Mathlib/AlgebraicGeometry/EllipticCurve/Projective/Formula.lean 1 5 ['Multramate', 'github-actions', 'tb65536'] nobody
1-79313
1 day ago
17-79115
17 days ago
17-79060
17 days
0
46249 Vierkantor
author:Vierkantor
chore(Algebra/Algebra): deduplicate `AlgHom.coe_mks` and `AlgHom.mk_coe` This PR removes the duplication between two `AlgHom` lemmas that are nearly the same: the only difference is `mk_coe` started out with an `AlgHom` and `coe_mks` started out with a plain function. But since we can generalize the condition for free in `mk_coe`, we can easily merge the two lemmas. Idem for `BialgHom`, `CoalgHom` and `GradedAlgHom`. I decided to keep `mk_coe` since its name makes more sense according to the naming conventions. Noticed while reviewing #45954. --- I'd like to bench this before merging in case the extra generality makes `simp` slower (I do not expect so since everything still is keyed on a whole pile of constructors). <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra t-ring-theory maintainer-merge
label:t-algebra$
20/30 Mathlib/Algebra/Algebra/Hom.lean,Mathlib/RingTheory/Bialgebra/Hom.lean,Mathlib/RingTheory/Coalgebra/Hom.lean,Mathlib/RingTheory/GradedAlgebra/AlgHom.lean,Mathlib/RingTheory/Localization/Basic.lean 5 8 ['Vierkantor', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts', 'themathqueen'] nobody
1-78035
1 day ago
2-15159
2 days ago
2-45977
2 days
0
46140 gasparattila
author:gasparattila
feat(Tactic/FunProp): add support for compositions in uncurried form This PR adds support for writing `fun_prop` lemmas about compositions in simple (uncurried) form. As an example, assume that we have functions `f : Y → Z` and `g : X → Y`, where `X` and `Z` are topological spaces. With this PR, we can have the following `fun_prop` lemma: ```lean @[fun_prop] theorem continuous_f_comp_g : Continuous (f ∘ g) := ... ``` Even though we could already write this lemma, it would not work properly: `fun_prop` could use it only if the goal was exactly `Continuous (f ∘ g)`, and it would fail to prove `Continuous h → Continuous (f ∘ g ∘ h)`. This is because it tried to decompose this function as `f ∘ (g ∘ h)`, but `f` is not necessarily continuous, and maybe `Y` does not even have a topology. The following changes are made to the implementation of `fun_prop`: * There is a new heuristic for deciding if a lemma is in uncurried or compositional form. Previously, a function was considered compositional if it could be decomposed in a non-trivial way, or if it could not be decomposed at all, for example, due to dependent types. The new heuristic checks if there an application where the head is an argument of the theorem, and one of the arguments of this application contains the function variable. * The `TheoremForm` type now tracks the number of arguments for lemmas in uncurried form. The is determined by finding the largest `n` such that the function argument is of the form `α₁ × … × αₙ` and every component of this tuple is used. This heuristic ensures that we consider `continuous_fst` and `continuous_snd` to have one argument. * When we apply a theorem in uncurried form, we first compose the function with a tuple of metavariables, then we unify the resulting term with the goal. For example, assume that we have a lemma about `fun x => x.1 + x.2`. We take the composition `(fun x => x.1 + x.2) ∘ (fun x => (?f x, ?g x)) = (fun x => ?f x + ?g x)`, then unify the term `fun x => ?f x + ?g x` with the goal. This allows us to decompose the goal such that the outer function is exactly the one in the lemma. These changes break a few proofs, mostly due to defeq abuse. We also need to untag multiple lemmas about `QuasiMeasurePreserving`. These lemmas are in uncurried form with multiple arguments. In one of the proofs, it would be possible for `fun_prop` to alternate between two of these lemmas, resulting in an infinite loop, which did not happen before because of the limitations of the earlier implementation. However, there is no product lemma for `QuasiMeasurePreserving`, so these lemmas would not be usable anyway unless the goal matched them exactly. A futher issue with `QuasiMeasurePreserving` is that its composition lemma always introduces a metavariable, which may or may not be solved by applying the function lemmas. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #46267 Because of an edge case in unification, the existing lemmas for `Unitization` can cause an infinite loop in `fun_prop`. increases-technical-debt t-meta 240/108 Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Restrict.lean,Mathlib/Analysis/Complex/UpperHalfPlane/Topology.lean,Mathlib/Analysis/LConvolution.lean,Mathlib/Analysis/SpecialFunctions/Complex/LogBounds.lean,Mathlib/Analysis/SpecialFunctions/Pow/Continuity.lean,Mathlib/MeasureTheory/Group/Prod.lean,Mathlib/MeasureTheory/Measure/WithDensity.lean,Mathlib/Probability/Distributions/Gaussian/Basic.lean,Mathlib/Tactic/FunProp/Core.lean,Mathlib/Tactic/FunProp/FunctionData.lean,Mathlib/Tactic/FunProp/Theorems.lean,Mathlib/Tactic/FunProp/ToBatteries.lean,Mathlib/Topology/Algebra/LinearMapCompletion.lean,MathlibTest/FunPropMinimal.lean 14 5 ['gasparattila', 'github-actions', 'leanprover-radar', 'mathlib-dependent-issues'] nobody
1-77251
1 day ago
2-3243
2 days ago
2-3188
2 days
0
46111 Hagb
author:Hagb
chore(Order/RelSeries): tag definitions providing `RelSeries` with `implicit_reducible` These definitions are sometimes applied with `Fin _` whose the type-correctness needs unfolding the definition. For example, ``` def ofLE (x : RelSeries r) {s : SetRel α α} (h : r ≤ s) : RelSeries s where length := x.length toFun := x step := ... ``` is used with `ofLE s h n` (i.e. `(ofLE s h).toFun n`) where `(ofLE s h).toFun` is a `Fin ((ofLE s h).length + 1) → α` and `n` is in `Fin (s.length + 1)` instead of `Fin ((ofLE s h).length + 1)`, unless w.r.t. higher transparency. It would be possible to cast these `Fin _` or use `Fin (EXPR.length + 1)` (where `EXPR` is the expression of a `RelSeries r` such as `ofLE s h`), which are painful. This PR tags these definitions with `@[implicit_reducible]` so that they can be unfolded in `implicit` transparency. As a result, `set_option backward.*` in `Mathlib.Order.RelSeries` can be removed. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-order 33/56 Mathlib/Order/JordanHolder.lean,Mathlib/Order/RelSeries.lean 2 4 ['Hagb', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] nobody
1-77132
1 day ago
1-78507
1 day ago
2-79550
2 days
0
46294 JovanGerb
author:JovanGerb
doc(Translate): improve some ducumentation This PR improves some documentation of `to_dual`/`to_additive` around some things that came up recently. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-meta 18/18 Mathlib/Tactic/Translate/Core.lean,Mathlib/Tactic/Translate/ToAdditive.lean,Mathlib/Tactic/Translate/ToDual.lean,MathlibTest/Attribute/ToAdditive/Basic.lean,MathlibTest/Attribute/ToDual.lean 5 1 ['github-actions'] nobody
1-70348
1 day ago
1-73879
1 day ago
1-73824
1 day
0
45053 tomaz1502
author:tomaz1502
feat(Analysis/Polynomial): the jump of a real rational function and the Cauchy index This PR defines `Polynomial.jumpVal p q x : ℤ`, the jump of the rational function `q / p` at a point `x`: `1` if it goes from `-∞` to `+∞`, `-1` if it goes from `+∞` to `-∞`, and `0` otherwise. The definition is algebraic: `q / p` changes sign at `x` exactly when `rootMultiplicity x p - rootMultiplicity x q` is odd, and the direction of the jump is then `signRight x (p * q)`. It develops the API of `jumpVal` needed for the Sturm–Tarski theorem: * `jumpVal_of_eval_ne_zero`, `jumpVal_of_rootMultiplicity_le`: there is no jump where `q / p` has no pole; * `jumpVal_mul_mul`: a common factor of `p` and `q` does not change the jump; * `jumpVal_mod`: `q` can be replaced by `q % p`; * `jumpVal_C_mul`: scaling `q` by `c` scales the jump by `sign c`; * `jumpVal_of_isCoprime`, `jumpVal_mul_one`: jumps of products of coprime polynomials; * `jumpVal_derivative_mul`: at a root `x` of `p`, the jump of `derivative p * q / p` is `sign (q.eval x)`. This is what links the Cauchy index to the signs of `q` at the roots of `p`. It also defines `Polynomial.rootsInInterval p a b`, the distinct roots of `p` in `(a, b)`, and the Cauchy index `Polynomial.cauchyIndex p q a b`, the sum of `jumpVal p q x` over those roots, with a few basic lemmas (`cauchyIndex_zero_left`, `cauchyIndex_zero_right`, `cauchyIndex_C`, `cauchyIndex_mul_mul`, `cauchyIndex_mod`, `cauchyIndex_C_mul`), which follow directly from the corresponding `jumpVal` lemmas. The main results about the Cauchy index (its relation to sign changes and to Tarski queries) will follow in the next PR of the series. One small addition to existing files: * `Polynomial.rootMultiplicity_C_mul` in `RingDivision.lean`: multiplying by a nonzero constant does not change root multiplicities; This is the fourth PR of a series formalising the Sturm-Tarski theorem, following #43783 (`List.signVariations`), #43954 (`Polynomial.sturmSeq`) and #44248 (`Polynomial.signRight`). Co-authored-by: Pedro Saccomani <psaccomani15@gmail.com> Co-authored-by: Sarah Pereira <sarahcomh@proton.me> --- The definitions and the original proofs, ported from Wenda Li's Isabelle/AFP entry, were written by hand. We used Claude to review the code, suggest improvements and help in the preparation of the PR. new-contributor t-analysis 248/0 Mathlib.lean,Mathlib/Analysis/Polynomial/CauchyIndex.lean 2 16 ['github-actions', 'mathlib-splicebot', 'ocfnash', 'tomaz1502', 'vihdzp'] ocfnash
assignee:ocfnash
1-67430
1 day ago
1-67736
1 day ago
11-25160
11 days
0
46289 themathqueen
author:themathqueen
chore(Matrix): generalize some `AlgEquiv` stuff now that it's nonunital Now that `AlgEquiv` is nonunital, we can generalize a lot of things! --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
52/49 Mathlib/Analysis/CStarAlgebra/CStarMatrix.lean,Mathlib/Data/Matrix/Basic.lean,Mathlib/Data/Matrix/Composition.lean,Mathlib/LinearAlgebra/Matrix/ConjTranspose.lean,Mathlib/LinearAlgebra/Matrix/Reindex.lean,Mathlib/LinearAlgebra/Matrix/Unique.lean 6 7 ['SnirBroshi', 'github-actions', 'leanprover-radar', 'themathqueen'] nobody
1-67300
1 day ago
1-77760
1 day ago
1-78663
1 day
0
46299 themathqueen
author:themathqueen
chore(Algebra): weakening `AlgEquiv` definitions to use nonunital --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt
label:t-algebra$
38/23 Mathlib/Algebra/Algebra/Equiv.lean,Mathlib/Algebra/Algebra/Opposite.lean,Mathlib/Algebra/Algebra/Pi.lean,Mathlib/Algebra/Algebra/Prod.lean 4 3 ['github-actions', 'leanprover-radar', 'themathqueen'] nobody
1-66899
1 day ago
1-68635
1 day ago
1-68580
1 day
0
44679 Altabeh
author:Altabeh
feat(LinearAlgebra/FiniteDimensional/Lemmas): dimension counts - `Function.Exact.finrank_range_add_finrank_range`: For an exact sequence `A → B → C` with maps `f` and `g`, proves that `finrank (range f) + finrank (range g) = finrank B`, assuming `B` is finite and the relevant ranges are free. - `Function.Exact.linearEquivQuotientRangeProdKer`: For an exact sequence `A → B → C → D → E` with maps `f`, `g`, `h`, and `j`, constructs a linear equivalence `C ≃ₗ[R] (B ⧸ range f) × ker j`, assuming `ker j` is projective. This generalizes the splitting of exact sequences. - `Function.Exact.finrank_eq_finrank_quotient_range_add_finrank_ker`: Establishes the corresponding dimension formula `finrank C = finrank (B ⧸ range f) + finrank (ker j)`, assuming `C` is finite and the quotient and kernel are free. These results apply in particular to finite-dimensional vector spaces and extend the existing API for working with exact sequences, linear maps, and dimension identities in Mathlib. **These are basic results that have been written by myself. The only use of AI was to write the comments and test.** t-algebra new-contributor
label:t-algebra$
57/0 Mathlib/LinearAlgebra/FiniteDimensional/Lemmas.lean 1 20 ['Altabeh', 'Nicola9Falciola', 'artie2000', 'github-actions', 'grunweg'] nobody
1-65780
1 day ago
1-66834
1 day ago
43-69635
43 days
0
46174 ldiedering
author:ldiedering
feat(MeasureTheory): add `of_innerRegularCompactLTTop` to get `NoAtoms` from `NullSingletonClass` `of_innerRegularCompactLTTop` is planned to be used as the main way to upgrade instances of `NullSingletonClass` to `NoAtoms`, applicable to most of the instances currently in mathlib. It complements the reverse direction added in #46121, which holds under much weaker assumptions. --- Use of AI: Based on a partial proof strategy, Claude Code was used to write write statements and proofs. Intermediate statements were then extracted manually, with proofs again supplied by AI <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability new-contributor LLM-generated 96/1 Mathlib.lean,Mathlib/MeasureTheory/Measure/Regular.lean,Mathlib/MeasureTheory/Measure/Typeclasses/NoAtoms.lean,Mathlib/MeasureTheory/Measure/Typeclasses/NoAtoms/Regular.lean 4 7 ['github-actions', 'lua-vr'] nobody
1-63939
1 day ago
3-83565
3 days ago
3-83510
3 days
0
36896 PieterCuijpers
author:PieterCuijpers
feat (Algebra/Order/Quantale): isMulLeftsided, isMulRightsided, isMulTwosided and strict versions * Adding definitions of quantale elements being leftsided, rightsided, and twosided, and strict versions The reason for adding those is because, like for example with IsIdempotent elements in a group or semigroup, or prime elements or compact elements, the leftsided and rightsided elements have a special status in Quantale theory. They don't really occur anywhere else, a.f.a.i.k., hence I think a definition in Quantale.lean makes sense. The central theorem on two-sided elements that should imo be in the library is that any frame is a quantale with only two-sided idempotent elements, and vice versa any quantale with only two-sided idempotent elements is a frame. This establishes quantales as a generalization of point-free topology. This PR prepares for that theorem and others. I'm not sure whether it would already make sense to start a separate Quantale directory and put these definitions in a separate file there. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra new-contributor
label:t-algebra$
102/13 Mathlib/Algebra/Order/Quantale.lean 1 8 ['NoahW314', 'PieterCuijpers', 'chrisflav', 'copilot-pull-request-reviewer', 'github-actions', 'mathlib-merge-conflicts'] mariainesdff
assignee:mariainesdff
1-63907
1 day ago
1-64716
1 day ago
40-82883
40 days
0
41111 erdkocak
author:erdkocak
feat(ModelTheory): add cardinal-generated substructure API This is the first PR in a sequence splitting #40561. It adds a `CardinalLTGenerated` predicate for substructures, basic closure and map lemmas, and the finitely generated specialization. Co-authored-by: Yağız Kaan Aydoğdu <y.kaan.aydogdu@gmail.com> Co-authored-by: Yusuf Demir <yusufdemir12610@gmail.com> Advised-by: Ayhan Günaydın <ayhan.gunaydin@bogazici.edu.tr> Advised-by: Metin Ersin Arıcan <metin.arican@bogazici.edu.tr> Please note that we utilized agentic AI tools (Claude Opus, ChatGPT Codex) during the development of this PR. Most of the proofs of the major theorems are direct translations from human-language source material (see the diff in `references.bib`) into Lean proofs using the mentioned AI tools. However, all design and formalization decisions were made by us. t-logic new-contributor LLM-generated 38/0 Mathlib/ModelTheory/FinitelyGenerated.lean,Mathlib/ModelTheory/Substructures.lean 2 23 ['NoahW314', 'erdkocak', 'felixpernegger', 'github-actions', 'iosephusferrum', 'mathlib-merge-conflicts', 'staroperator'] nobody
1-62165
1 day ago
18-30239
18 days ago
121-37027
121 days
5
46264 bjornsolheim
author:bjornsolheim
feat(Analysis/Convex): extreme subsets and intrinsic interiors Relate the extreme subsets of a convex set to intrinsic interiors, following Sections 6 and 18 of Rockafellar, *Convex Analysis*. * `Convex.mem_intrinsicInterior_iff`: in finite dimensions, a point `p` of a convex set `s` lies in its intrinsic interior iff every segment from a point of `s` to `p` extends beyond `p` inside `s`. * `Convex.isLeast_isExtreme_setOfPred_add_smul_sub_mem`: an explicit description of the least extreme subset of a convex set containing a given point. * `IsExtreme.subset_of_mem_intrinsicInterior`: an extreme subset of `K` containing a point of the intrinsic interior of a subset `S` of `K` contains `S`. * `Convex.existsUnique_isExtreme_mem_intrinsicInterior`: in finite dimensions, every point of a convex set lies in the intrinsic interior of a unique extreme subset. * `IsExtreme.finDim_affineSpan_lt` and `IsExtreme.isClosed`: in finite dimensions, a proper convex extreme subset has smaller affine dimension, and convex extreme subsets of closed sets are closed. `Set.Nonempty.intrinsicInterior` and `intrinsicInterior_nonempty` (by consequence) are generalized from normed spaces to finite-dimensional Hausdorff real topological vector spaces Assisted by: Claude Fable 5.2 and Opus 5.5 (used for research and to write or complete or improve some parts). Some parts are hence iteratively llm-generated/llm-modified based on my inputs. All lines are reviewed in full by me. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis LLM-generated 279/4 Mathlib.lean,Mathlib/Analysis/Convex/Extreme.lean,Mathlib/Analysis/Convex/Extreme/Intrinsic.lean,Mathlib/Analysis/Convex/Intrinsic.lean,docs/references.bib 5 1 ['github-actions'] nobody
1-61180
1 day ago
2-65166
2 days ago
2-65111
2 days
1
45771 darkhipo
author:darkhipo
feat(MeasureTheory): bochner product integral over Measure.infinitePi # PR — Bochner product integral over `Measure.infinitePi` The proof is a single new file, `Mathlib/MeasureTheory/Integral/InfinitePiProduct.lean`, carrying the Mathlib module header (`module` / `public import` / `public section`), the Apache 2.0 licence line with `Copyright (c) 2026 darkhipo`, and `namespace MeasureTheory`. --- ## Proposed title `feat(MeasureTheory): Bochner product integral over Measure.infinitePi` ## Proposed file placement `Mathlib/MeasureTheory/Integral/InfinitePiProduct.lean` Imports (verified sufficient — the module compiles with exactly these, under `set_option autoImplicit false`, in the modern `module`/`public import` form): ```lean public import Mathlib.Analysis.SpecialFunctions.Log.Summable public import Mathlib.MeasureTheory.Integral.DominatedConvergence public import Mathlib.MeasureTheory.Integral.Lebesgue.Map public import Mathlib.MeasureTheory.Integral.Pi public import Mathlib.Probability.ProductMeasure ``` Rationale for placement: it is the infinite-index companion of `MeasureTheory.integral_fintype_prod_eq_prod` (`Mathlib/MeasureTheory/Integral/Pi.lean`), and it integrates over `Measure.infinitePi` (`Mathlib/Probability/ProductMeasure.lean`). ## Main results ```lean theorem MeasureTheory.integral_finset_prod_infinitePi (hf : ∀ i, AEStronglyMeasurable (f i) (μ i)) (s : Finset ι) : ∫ x, ∏ i ∈ s, f i (x i) ∂(Measure.infinitePi μ) = ∏ i ∈ s, ∫ x, f i x ∂(μ i) theorem MeasureTheory.ae_summable_norm_sub_one_infinitePi (hf : ∀ i, AEStronglyMeasurable (f i) (μ i)) (hsum : ∑' i, ∫⁻ x, (‖f i x - 1‖₊ : ℝ≥0∞) ∂(μ i) ≠ ∞) : ∀ᵐ x ∂(Measure.infinitePi μ), Summable fun i => ‖f i (x i) - 1‖ -- the general form: a norm bound family instead of a flat 1 theorem MeasureTheory.hasProd_integral_tprod_infinitePi_of_norm_le (hf : ∀ i, AEStronglyMeasurable (f i) (μ i)) (hC0 : ∀ i, 0 ≤ C i) (hb : ∀ i, ∀ᵐ x ∂(μ i), ‖f i x‖ ≤ C i) (hC : Summable fun i => ‖C i - 1‖) (hsum : ∑' i, ∫⁻ x, (‖f i x - 1‖₊ : ℝ≥0∞) ∂(μ i) ≠ ∞) : HasProd (fun i => ∫ x, f i x ∂(μ i)) (∫ x, ∏' i, f i (x i) ∂(Measure.infinitePi μ)) -- the ≤ 1 case, kept as a corollary (this is the form the campaign consumes) theorem MeasureTheory.hasProd_integral_tprod_infinitePi (hf) (hb : ∀ i, ∀ᵐ x ∂(μ i), ‖f i x‖ ≤ 1) (hsum) : HasProd … theorem MeasureTheory.integral_tprod_infinitePi (hf) (hb) (hsum) : ∫ x, ∏' i, f i (x i) ∂(Measure.infinitePi μ) = ∏' i, ∫ x, f i x ∂(μ i) ``` (`ι` countable, `[∀ i, MeasurableSpace (X i)]`, `μ : (i : ι) → Measure (X i)` with `[∀ i, IsProbabilityMeasure (μ i)]`, `f : (i : ι) → X i → ℂ`, `C : ι → ℝ`.) ## Why it is not already there * finite index, product-measure form: `MeasureTheory.integral_fintype_prod_eq_prod`; * finite index, independence form: `ProbabilityTheory.iIndepFun.integral_prod_eq_prod_integral` (and the more general `iIndepFun.integral_fun_prod_comp` for functions of independent random variables), in `Mathlib/Probability/Independence/Integration.lean` — this is the closest existing relative of the present file, and it already contains the reduction of independence to the pi product measure (`iIndepFun.map_fun_eq_pi_map`) that the infinite-index statement takes as its starting point; * nonnegative integrands, infinite index: derivable from `lintegral_tsum` (monotone convergence); * Bochner/`ℂ` integrands, infinite index: **absent** — and monotone convergence does not apply, because the products are not nonnegative. The proof needs an honest convergence argument. ## Relation to `iIndepFun.integral_prod_eq_prod_integral` That theorem and its neighbors state the **finite-index** identity `μ[∏ i, X i] = ∏ i, μ[X i]` for a family of **mutually independent random variables** `X : (i : ι) → Ω → 𝓧 i` on a common probability space (`[Fintype ι]`, `iIndepFun X μ`, measurability only — at finite index no convergence content is even statable). The present file is the **countable-index, infinite-product, bare-product-measure** analogue, and the delta is exactly what finiteness hid: * **index**: `[Fintype ι]` there vs `[Countable ι]` with genuinely infinite `∏'` here — the conclusion is a `HasProd` convergence statement, so a.e. summability of `∑ i, ‖f i (x i) - 1‖` (Tonelli) and `multipliable_one_add_of_summable` enter, neither of which has a finite-index counterpart; * **framing**: there, hypotheses on a common probability space plus `iIndepFun`; here, no random-variable layer at all — the statement is directly about `Measure.infinitePi μ`, the product-measure form their `iIndepFun.map_fun_eq_pi_map` reduces independence to; * **bounds**: there, none needed; here, the `‖f i x‖ ≤ C i` bound family with `∑ i, ‖C i - 1‖` summable is what makes dominated convergence along `Finset ι` work ("Why the bound family is `∑ ‖C i - 1‖`" below). Conversely, neither statement subsumes the other: the independence file cannot state an infinite product, and this file does not require (or produce) the `iIndepFun` common-space packaging. ## Proof sketch (for the review) 1. **Finite subsets.** `(Measure.infinitePi μ).map (Finset.restrict s) = Measure.pi (μ|_s)` (`Measure.infinitePi_map_restrict`), then `integral_fintype_prod_eq_prod` and `measurePreserving_eval_infinitePi` for the single coordinates. 2. **A.e. summability of the deviations.** Tonelli: `∫⁻ x, ∑' i, ‖f i (x i) - 1‖` equals `∑' i, ∫⁻ x, ‖f i x - 1‖` (`lintegral_tsum` + `lintegral_map'`), finite by hypothesis, hence `∑ i, ‖f i (x i) - 1‖` is summable for a.e. `x`. 3. **A.e. multipliability.** `multipliable_one_add_of_summable` applied to `f i (x i) - 1`. 4. **Domination.** `‖∏ i ∈ s, f i (x i)‖ = ∏ i ∈ s, ‖f i (x i)‖ ≤ ∏ i ∈ s, C i`, and `C i ≤ exp (C i - 1)` for `C i ≥ 0` gives `∏ i ∈ s, C i ≤ exp (∑ i ∈ s, (C i - 1)) ≤ exp (∑' i, ‖C i - 1‖)` — a constant independent of `s`. 5. **Limit.** `tendsto_integral_filter_of_dominated_convergence` along `atTop : Filter (Finset ι)`, dominated by that constant, pointwise convergence from step 3; the finite-subset integrals are rewritten by step 1. `HasProd.tprod_eq` turns the convergence form into the equation form. ## Why the bound family is `∑ ‖C i - 1‖` and not `∑ C i` A product of bounds is not additive in them: a factor `C i < 1` scales the bound *down*, a factor `> 1` scales it *up*, so summability of `C` alone does not bound `∏ i ∈ s, C i` uniformly. The log-scale hypothesis `Summable fun i => ‖C i - 1‖` is exactly the statement that the family `C` is multipliable, made explicit; `exp (∑' i, ‖C i - 1‖)` is then the dominator. The flat case is `C ≡ 1` (where `∑ ‖C i - 1‖ = 0` and the dominator is `1`), which is the corollary above. ## Review-risk notes (honest) * The `𝕜`-generalization (any `RCLike 𝕜` / `NormedField` instead of `ℂ`) is **open**; `ℂ` is what the use case needs. The proofs use only the normed-field structure plus completeness of `ℂ`, so the generalization is plausible but not attempted here. * The summability hypothesis `∑' i, ∫⁻ x, ‖f i x - 1‖₊ ≠ ∞` is chosen because `multipliable_one_add_of_summable` consumes the real-valued `Summable fun i => ‖f i (x i) - 1‖` and `ENNReal.tsum_coe_ne_top_iff_summable` converts between them. A reviewer may prefer a hypothesis phrased through `Summable` on `ℝ≥0`-norms directly; the two are equivalent. * The bound family is not required to be *sharp* or to converge to `1`; `C i` may be any nonnegative family with `∑ ‖C i - 1‖` summable, including `C i < 1` for every `i`. * No `sorry`, no `native_decide`, no new axioms: every declaration reports `[propext, Classical.choice, Quot.sound]`, including the generalized theorem (receipt: `receipt/axcheck_infinitepiproduct.txt`, regenerated by `receipt/axcheck_infinitepiproduct.lean`). ## AI usage disclosure (Mathlib requires one) This contribution was produced by an AI agent (a large language model driven by the `opencode` harness) inside a human-directed formalization campaign; the human, darkhipo, reviewed and is submitting it. Every statement was checked by the Lean kernel; the proofs are machine-generated and human-readable but not human-written. The docstrings and this description were written by the agent. ## Checklist (Mathlib's) - [x] depends on no new axioms / `sorry`-free (kernel-verified, `#print axioms` receipt attached for all five declarations) - [x] builds with the narrowest import set that works (five `public import`s, each exercised) - [x] `set_option autoImplicit false` clean - [x] no linter warnings in this file (rebuilt clean: `lake build Pg182D2` reports no warning or error for `Pg182D2/InfinitePiProduct.lean`) - [x] docstrings on every declaration, module docstring present, `## Main results` section - [x] naming matches Mathlib conventions (`integral_*_prod_*`, `ae_*`, `hasProd_*`, `_of_norm_le`) - [x] Mathlib module form (`module`, `public import`, `public section`) - [x] licence header complete: `Copyright (c) 2026 darkhipo. All rights reserved.`, Apache 2.0, `Authors: darkhipo` - [ ] reviewed by a human Lean expert — **not done**. Nothing in this file has been read by a human with Lean expertise; the human submitting it has reviewed the *statement* and the campaign's use of it, not the proof scripts. - [ ] argued as `Mathlib`-worthy by a maintainer — that is the reviewers' call, not ours. ## Verification against upstream `master` at PR time Copied into `Mathlib/MeasureTheory/Integral/InfinitePiProduct.lean` on branch `infinite-pi-product`, based on `master` @ `71441a1480` (`chore: update Mathlib dependencies 2026-11-07`), toolchain `leanprover/lean4:v4.36.0-rc2`. * `lake exe cache get` + `lake build Mathlib.MeasureTheory.Integral.InfinitePiProduct` → `Build completed successfully`, **no warnings** (the build runs Mathlib's standard linter set, including `linter.style.longLine`, the header linter and `unusedSectionVars`). * `lake exe lint-style Mathlib.MeasureTheory.Integral.InfinitePiProduct` → exit code 0. * `lake exe mk_all` → the generated `Mathlib.lean` import line is byte-identical to the committed one. * `#print axioms` on the upstream copy: all five declarations depend only on `[propext, Classical.choice, Quot.sound]`, i.e. no `sorry` and no new axioms. Adaptations required by upstream `master` (the proof itself is unchanged from the version that compiled against the pin used during the campaign): 1. removed `set_option autoImplicit false` — `autoImplicit` is `false` globally in `lakefile.lean`; 2. `AEMeasurable.nnnorm` → `AEMeasurable.nnNorm` (two sites) and `coe_nnnorm` → `coe_nnNorm`, which are deprecated at `master`; 3. two lines reflowed to satisfy the 100-character `linter.style.longLine`; 4. added the import to `Mathlib.lean`. t-measure-probability new-contributor 224/0 Mathlib.lean,Mathlib/MeasureTheory/Integral/InfinitePiProduct.lean 2 3 ['github-actions'] nobody
1-58868
1 day ago
14-80665
14 days ago
14-80610
14 days
0
45906 darkhipo
author:darkhipo
feat(Analysis/Fourier): exactness of the periodic trapezoidal rule on characters ### The periodic trapezoidal rule is exact on characters New file `Mathlib/Analysis/Fourier/TrapezoidalRulePeriodic.lean` (also registered in `Mathlib.lean`). **What this adds.** The `n`-point periodic trapezoidal rule — the average of `F` over the `n` equally spaced nodes `2 * π * j / n` — reproduces the circle mean of every character `x ↦ e^{i m x}` *exactly*, except at the aliased nonzero frequencies `m ≠ 0, n ∣ m`, where the error is exactly `-1` (`PeriodicTrapezoidal.error_char`). The mechanism is algebraic: * `char_sum`: `∑_{j < n} e^{2 * π i m j / n} = n` if `n ∣ m`, else `0`; * `integral_char` / `circleMean_char`: `(1 / (2 * π)) ∫_0^{2 * π} e^{i m x} dx = 1` if `m = 0`, else `0`. Because the error functional `Eₙ = circleMean - mean` is additive and `ℂ`-homogeneous, these two facts give a **geometric convergence theorem** from a Fourier-decay hypothesis (`error_le_of_decay`): if `F` is uniformly `ε`-close on `[0, 2 * π]` to a partial character sum whose nonzero coefficients satisfy `‖cₖ‖ ≤ M * q ^ {|k|}` for some `q < 1`, then the `n`-point error is at most `M * q ^ n * (2 * K + 1) + 2 * ε`. **What is classical.** The trapezoidal rule, character orthogonality and the geometric-sum identity are all classical; the exponential accuracy of the periodic trapezoidal rule for periodic analytic integrands is the subject of Trefethen & Weideman, *The Exponentially Convergent Trapezoidal Rule*, SIAM Rev. 56 (2014). Nothing here is mathematically new; the contribution is the missing statement in Mathlib. **Relationship to existing API.** `intervalIntegral.trapezoidal_error_le` and `trapezoidal_error_le_of_c2` bound the error through derivative moduli and give rates polynomial in `N`, for any smooth integrand on an interval. This PR is the complementary regime: periodic integrands, coefficients instead of derivatives, geometric rate. Neither subsumes the other. The `2 * K + 1` factor is a deliberately crude cardinality bound on the frequencies that can alias (it counts the terms of the partial sum); a sharper tail could replace it at the cost of a stronger hypothesis on `K`. **The decay hypothesis is deliberately left abstract.** `error_le_of_decay` takes the coefficient decay as a hypothesis. It is classically supplied by analyticity of `F` in a strip around the real axis (the coefficients then decay like `e ^ (- a * |k|)`); we plan to contribute that contour-shift ingredient separately so the two compose into the fully classical statement. **Motivation from a use case (not a claim about Mathlib).** Consider a periodic integral that needs a `1.3 · 10⁻⁶` enclosure. The derivative-bound route, instantiated with realistic constants, needs `n ≥ 7.7 · 10¹⁷` panels there; the same integrand's Fourier tail under strip analyticity gives exponential accuracy at modest `n` — roughly 15 orders of magnitude apart at the node counts that matter. Mathlib's existing theorems are correct for their hypotheses; the gap is that the spectral mechanism, which is the standard reason one uses the periodic rule at all, had no statement to build on. new-contributor t-analysis 435/0 Mathlib.lean,Mathlib/Analysis/Fourier/TrapezoidalRulePeriodic.lean 2 3 ['darkhipo', 'github-actions'] nobody
1-58840
1 day ago
1-59325
1 day ago
1-61000
1 day
0
45909 darkhipo
author:darkhipo
feat(Analysis/Fourier): geometric decay of Fourier coefficients from strip analyticity ### What Adds the classical **strip decay of Fourier coefficients**: if `g : ℂ → ℂ` is holomorphic on the horizontal strip `{z | |z.im| < a}`, `T`-periodic there, and bounded there by `M`, and `f : AddCircle T → ℂ` agrees with `g` on the real axis, then ```lean theorem norm_fourierCoeff_le_of_strip ... (k : ℤ) : ‖fourierCoeff f k‖ ≤ M * Real.exp (-(2 * π * a / T) * |(k : ℝ)|) ``` For `T = 2 * π` this is the familiar `‖ĉ_k‖ ≤ M * exp (- a * |k|)`. ### Why this belongs in Mathlib `Analysis/Fourier/` has the `L²` theory (Parseval, inversion, `RiemannLebesgueLemma`) — i.e. *qualitative* decay — but no quantitative geometric coefficient bound, which is the entry point for spectral/quadrature accuracy results. This result is textbook classical (Cauchy estimates for Fourier/Laurent coefficients; Katznelson, *An Introduction to Harmonic Analysis*; Kahane, *Some Random Series of Functions*, 2nd ed., 1985; Trefethen & Weideman, SIAM Rev. 56 (2014), for the numerical corollary), so the contribution here is the formalization and the proof route, not the mathematics. ### The proof route Elementary, and deliberately so — it avoids annulus/Laurent machinery entirely: 1. `integral_eq_shift_of_periodic_of_differentiableOn` — the reusable piece: the period integral of a holomorphic `T`-periodic function is invariant under vertical shifts whose closed rectangle stays in the domain (on `Complex.integral_boundary_rect_eq_zero_of_differentiableOn`'s rectangle, the two vertical sides cancel by periodicity). 2. `norm_fourierCoeff_le_of_shift` — applying this to `z ↦ exp (2 * π * I * (-k) * z / T) * g z` scales the `k`-th coefficient by a factor of modulus `exp (2 * π * k * s / T)` at any height `|s| < a`. 3. The optimization over `|s| < a` is an **endpoint limit** (`le_of_tendsto_of_tendsto`), not a substitution: `e ^ (k * s)` is not bounded by its value at the strip edge at any interior `s`. ### Notes - A follow-up PR is planned for `trap_error_char` — the exactness of the `n`-point trapezoid rule on characters (the aliasing identity `Σ_{j<n} e^{2πimj/n} = n` when `n ∣ m`, else `0`) — which consumes this decay bound and gives the exponential-accuracy version of the periodic trapezoid rule. - Verified locally at current master (`2e9cd83`, toolchain `v4.36.0-rc2`): `lake build Mathlib` clean, the Batteries linter passes on this file, the module compiles twice from scratch with byte-identical `.olean`s, and `#print axioms` on all three declarations shows exactly `{propext, Classical.choice, Quot.sound}`. t-analysis new-contributor 272/0 Mathlib.lean,Mathlib/Analysis/Fourier/StripDecay.lean 2 2 ['github-actions'] nobody
1-58744
1 day ago
1-59314
1 day ago
1-60985
1 day
0
46273 Parcly-Taxel
author:Parcly-Taxel
feat: `Set.ncard_subsuperset_ncard` This is the `ncard` analogue of `Finset.card_filter_powersetCard_subset`. I came across this gap when extending #41802 to prove the fundamental parameter relations in block designs/Steiner systems. t-data 18/0 Mathlib/Data/Set/Card.lean 1 4 ['Parcly-Taxel', 'SnirBroshi', 'github-actions'] nobody
1-55935
1 day ago
2-25727
2 days ago
2-25672
2 days
0
44086 bjornsolheim
author:bjornsolheim
feat(Analysis/Convex/Strict): farthest points are exposed in strictly convex spaces Proves the following (in a real strictly convex normed space): `sphere_subset_exposedPoints_closedBall` - every point of a sphere is an exposed point of the corresponding closed ball `mem_exposedPoints_of_isMaxOn_dist` - a point `y ∈ S` that maximizes distance to a fixed center `z` is an exposed point of `S` `exposedPoints_closedBall_eq_sphere` - the exposed points of a closed ball are exactly its sphere Assisted by: Claude Fable 5.1 (used for research and to write or complete or improve some parts). All lines are written or reviewed by me. --- Optional comment t-analysis 77/0 Mathlib.lean,Mathlib/Analysis/Convex/Strict/Exposed.lean 2 2 ['github-actions'] j-loreaux
assignee:j-loreaux
1-51257
1 day ago
60-81166
60 days ago
60-81111
60 days
2
44275 seewoo5
author:seewoo5
feat(FourierTransform): linear equivariance --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Linear equivariance of Fourier transform: `𝓕 (f ∘ A) w = |A.toLinearMap.det|⁻¹ • 𝓕 f (A.symm.adjoint w)`. Proof is essentially by change of variable. Originally written by Opus 5, with additional golfs by myself. This was formalized while I was refactoring OpenAI's formalization on Cohn-Elkies bound and its optimal exponent. Note that one can generalize further (actually without much effort) to the case where the domain and codomain of `A` are different, by replacing determinant with [`LinearMap.normDet`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Analysis/InnerProductSpace/NormDet.html#LinearMap.normDet). But it seems that this would add a lot imports, and I may had to make a separate file (something like `Fourier/Linear.lean`?), but I'm not sure if this is a good idea. The general version can be found [here](https://github.com/seewoo5/cohn-elkies-refactor/blob/b5165ff7049114ce2c551f15b8c75d4aca5ab850/CohnElkiesForMathlib/Analysis/Fourier/FourierTransform.lean#L30). t-analysis LLM-generated 16/0 Mathlib/Analysis/Fourier/FourierTransform.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] j-loreaux
assignee:j-loreaux
1-51255
1 day ago
44-4902
44 days ago
55-21789
55 days
0
45523 kim-em
author:kim-em
feat(Tactic): add opt-in droppable hypothesis linter Add the opt-in `linter.droppableHypotheses` linter. Lean's unused-variable linter detects unused parameters; this also finds parameters the existing proof uses but can replace when re-elaborated. For example, after removing `[Nonempty α]`, `infer_instance` can derive it from `[Inhabited α]`. ```lean import Mathlib.Tactic.Linter.DroppableHypotheses set_option linter.droppableHypotheses true ``` Each trial deletes one theorem parameter and re-elaborates the unchanged statement and proof in isolated command state. Section variables and grouped binders are supported. Trials reject `sorry` dependencies and changed statements. Findings are independent; reported parameters may not all be removable together. Options control heartbeats and JSONL survey output. --- Known limitation: dropping a category instance in `CategoryTheory/Sites/Descent/IsPrestack.lean` triggers exponential metavariable dependency traversal in Lean and still times out. Large surveys need an external process timeout. A dependent-section guard avoids leanprover/lean4#16125. Arbitrary IO during replay is not undone. :robot: Prepared with Codex. LLM-generated t-linter 617/0 Mathlib.lean,Mathlib/Tactic.lean,Mathlib/Tactic/Linter/DroppableHypotheses.lean,MathlibTest/Linter/DroppableHypotheses.lean,MathlibTest/Linter/DroppableHypothesesCategoryTheory.lean 5 1 ['github-actions'] nobody
1-50356
1 day ago
22-43850
22 days ago
22-44342
22 days
0
45003 vihdzp
author:vihdzp
refactor(Algebra/Order/Archimedean/Basic): change `nat` → `natCast` in theorem statements --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> This came up in #44992. t-order 201/142 Counterexamples/SeparableNotSecondCountable.lean,Counterexamples/SorgenfreyLine.lean,Mathlib/Algebra/Order/Archimedean/Basic.lean,Mathlib/Algebra/Order/Archimedean/Hom.lean,Mathlib/Algebra/Order/Archimedean/Real/Basic.lean,Mathlib/Algebra/Order/CompleteField.lean,Mathlib/Analysis/AbsoluteValue/Equivalence.lean,Mathlib/Analysis/Calculus/FDeriv/Measurable.lean,Mathlib/Analysis/Calculus/UniformLimitsDeriv.lean,Mathlib/Analysis/Normed/Field/Lemmas.lean,Mathlib/Analysis/SpecialFunctions/Pow/Asymptotics.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/Basic/Real/Embedding.lean,Mathlib/Data/EReal/Basic.lean,Mathlib/GroupTheory/Sylow.lean,Mathlib/MeasureTheory/Constructions/BorelSpace/Real.lean,Mathlib/MeasureTheory/Function/AbsolutelyContinuous.lean,Mathlib/MeasureTheory/Function/SimpleFunc.lean,Mathlib/MeasureTheory/Measure/Decomposition/Lebesgue.lean,Mathlib/MeasureTheory/VectorMeasure/Decomposition/Hahn.lean,Mathlib/NumberTheory/Padics/PadicNumbers.lean,Mathlib/NumberTheory/Padics/RingHoms.lean,Mathlib/NumberTheory/Real/Irrational.lean,Mathlib/NumberTheory/Transcendental/Liouville/Measure.lean,Mathlib/Probability/Kernel/Disintegration/CDFToKernel.lean,Mathlib/Probability/Kernel/Disintegration/MeasurableStieltjes.lean,Mathlib/Probability/Kernel/Disintegration/StandardBorel.lean,Mathlib/Probability/Kernel/Representation.lean,Mathlib/Probability/Moments/SubGaussian.lean,Mathlib/Topology/Algebra/Order/Archimedean.lean,Mathlib/Topology/Instances/ENNReal/Lemmas.lean,Mathlib/Topology/Instances/EReal/Lemmas.lean,Mathlib/Topology/Instances/Rat.lean,Mathlib/Topology/Instances/Real/Lemmas.lean,Mathlib/Topology/MetricSpace/Pseudo/Defs.lean,Mathlib/Topology/Order/Real.lean 37 10 ['SnirBroshi', 'github-actions', 'mathlib-merge-conflicts', 'themathqueen', 'vihdzp'] nobody
1-49289
1 day ago
1-50204
1 day ago
27-40213
27 days
0
45210 dongxuelian2
author:dongxuelian2
feat(LinearAlgebra/Matrix/Charpoly): finite determination of matrix power sequences Add finite-determination criteria for matrix sequences `C * A ^ k * B`, allowing the two square matrices to have different index types. `Matrix.mul_pow_mul_eq_of_aeval_eq_zero` uses a common monic annihilating polynomial: agreement below its degree implies agreement at every natural exponent. `Matrix.mul_pow_mul_eq_of_lt_card_add` applies this to the product of the characteristic polynomials, giving the bound `Fintype.card ι + Fintype.card κ`. The statements work over commutative rings and allow empty state index types. The proof reduces `X ^ k` modulo the common polynomial and uses `Polynomial.sum_modByMonic_coeff`, which handles degree zero without a separate dimension case split. This adds two theorems to the existing matrix-power reduction API without introducing imports or definitions. The proof is adapted from [LeanForControl's finite-determination result](https://github.com/dongxuelian2/LeanForControl/blob/kalman-structural-completion/LeanForControl/LinearSystems/Realization/FiniteDetermination.lean). --- ### Validation Checked locally with Lean v4.36.0-rc1 against mathlib master `3d14fd9a313ac35ed4b5c653ed5d99157c9e29f6`: - `lake build Mathlib.LinearAlgebra.Matrix.Charpoly.Coeff` - `lake exe batteries/runLinter --no-build Mathlib.LinearAlgebra.Matrix.Charpoly.Coeff` - Direct invocation of the upstream text linters and module-name checks. - Separate local examples for the requested field/`Fin` statement, either or both dimensions zero, degree-zero and degree-one common annihilators, and matching nonzero sequences in dimensions 1 and 2. - `#print axioms` for both theorems reports only `propext`, `Classical.choice`, and `Quot.sound`. - `git diff --check`. The standalone `lint-style` launcher failed while loading Lake's workspace on Windows; its text linters passed when invoked directly. A clean full `lake shake` run was not obtained: the initial run needed uncached modules outside the targeted dependencies, and the forced run reported suggestions throughout the existing dependency closure. Imports are unchanged from upstream. No full-library build is claimed. ### AI use OpenAI Codex was used to audit nearby APIs and possible duplicates, extract and generalize the LeanForControl proof, write the Lean code and local examples, run validation, and prepare this PR description. t-algebra LLM-generated new-contributor
label:t-algebra$
44/0 Mathlib/LinearAlgebra/Matrix/Charpoly/Coeff.lean 1 4 ['dongxuelian2', 'github-actions', 'mathlib-merge-conflicts'] nobody
1-45337
1 day ago
1-46114
1 day ago
20-457
20 days
0
45432 emlis42
author:emlis42
feat(Tactic/Inclusion): add `rpow` support to the `inclusion`/`dyadic_interval` tactic This PR adds a `rpow` extension for the `dyadic_interval` tactic. --- - [x] depends on: #45427 t-meta 270/0 Mathlib.lean,Mathlib/Tactic.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Rpow.lean,MathlibTest/Tactic/Inclusion/Rpow.lean 4 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-43098
1 day ago
1-43557
1 day ago
1-44293
1 day
0
46005 plp127
author:plp127
feat(FieldTheory/IntermediateField/Adjoin): improve `induction_on_adjoin_fg` Make it so the motive can depend on `K.FG`, and add this hypothesis to the induction step. This makes `induction K, hK using induction_on_adjoin_fg` work. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
18/6 Mathlib/FieldTheory/IntermediateField/Adjoin/Algebra.lean,Mathlib/FieldTheory/IntermediateField/Adjoin/Defs.lean 2 4 ['github-actions', 'plp127', 'tb65536'] nobody
1-41896
1 day ago
1-42342
1 day ago
8-11966
8 days
0
44836 cmhsu2012
author:cmhsu2012
feat(NumberTheory/Legendre/Basic): the legendre symbol for p-adics Co-authored-by: María Inés de Frutos-Fernández 88536493+mariainesdff@users.noreply.github.com and Nirvana Coppola 58878663+NirvanaC93@users.noreply.github.com In the ongoing formalization of the Hasse-Minkowski Theorem on quadratic forms, we need the Legendre symbol for the p-adics. The following declarations were added to the basic.lean file: ```def compMonoidHom``` an auxiliary definition: the composition between multiplicative characters and a local homomorphism ```def legendreSym``` the definition of the Legendre symbol for Z_p: composition of the reduction from Z_p to Z mod p and the usual Legendre symbol ```def hom``` The Legendre symbol is a homomorphism The remaining lemmas are the API: ```lemma intCast``` ```theorem eq_pow``` ```theorem eq_on_or_neg_one``` ```eq_neg_one_iff_not_one``` ```theorem eq_zero_iff``` ```theorem sq_one``` ```theorem sq_one'``` ```theorem eq_one_iff``` ```theorem eq_neg_one_iff``` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-number-theory new-contributor 179/2 Mathlib.lean,Mathlib/Algebra/Ring/Int/Units.lean,Mathlib/NumberTheory/MulChar/Basic.lean,Mathlib/RingTheory/LocalRing/LegendreSymbol.lean 4 67 ['JX-Mo', 'NirvanaC93', 'cmhsu2012', 'github-actions', 'loefflerd', 'mariainesdff', 'tb65536'] loefflerd
assignee:loefflerd
1-40332
1 day ago
1-42572
1 day ago
17-34429
17 days
0
43536 SnirBroshi
author:SnirBroshi
feat(Order): `SupClosed`/`DirSupClosed`/`DirectedOn`/etc for set intervals For set intervals, prove the properties they satisfy among these `Set` properties: - `DirectedOn` - `CountableSupClosed` / `CountableInfClosed` - `DirSupClosed` / `DirSupClosedOn` - `DirSupInacc` / `DirSupInaccOn` - `SupClosed` / `InfClosed` and use them to conclude properties of order topologies, e.g. the Scott-Hausdorff topology on a lower-set is a `ClosedIicTopology`/`ClosedIciTopology`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-topology 250/23 Mathlib/Order/CountableSupClosed.lean,Mathlib/Order/DirSupClosed.lean,Mathlib/Order/Interval/Set/Image.lean,Mathlib/Order/SupClosed.lean,Mathlib/Topology/Order/ScottTopology.lean,Mathlib/Topology/Order/UpperLowerSetTopology.lean 6 20 ['SnirBroshi', 'github-actions', 'j-loreaux', 'mathlib-merge-conflicts', 'vihdzp'] alreadydone
assignee:alreadydone
1-38487
1 day ago
1-41440
1 day ago
32-29728
32 days
3
44672 JovanGerb
author:JovanGerb
feat(Algebra/Homology/HomologicalComplex): use `to_dual` This PR uses `to_dual` on `HomologicalComplex`, making `ChainComplex` dual to `CochainComplex`. - The type of `CochainComplex.ofHom` and `CochainComplex.mkHom` changed: the direction of the equality flipped to match with the dual. - `HomologicalComplex.Hom.sqFrom` gained a `simps!` attribute to replace two manually written lemmas. - `ChainComplex.mkAux` and `ChainComplex.mkHomAux` needed to use `to_dual existing`, because `to_dual` currently doesn't like recursive definitions that use a match for the recursion. - `mkXIso` and `mk'XIso` and a few theorems didn't have duals before this PR. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #43804 tech debt 159/351 Mathlib/Algebra/Homology/ComplexShape.lean,Mathlib/Algebra/Homology/HomologicalComplex.lean,Mathlib/AlgebraicTopology/AlternatingFaceMapComplex.lean,Mathlib/CategoryTheory/Abelian/Injective/Resolution.lean 4 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-37721
1 day ago
1-38281
1 day ago
1-39240
1 day
0
46306 mcdoll
author:mcdoll
chore(RingTheory/Coalgebra): fix a definition As per #31365 definitions should not take classes, but the concrete object. We fix this for `Repr.induced`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory maintainer-merge 1/3 Mathlib/RingTheory/Coalgebra/Hom.lean 1 3 ['github-actions', 'themathqueen'] nobody
1-36454
1 day ago
1-37764
1 day ago
1-37709
1 day
0
45788 JovanGerb
author:JovanGerb
chore: rename `nndist` to `nnDist` This PR renames `nndist` to `nnDist` to satisfy the new naming convention. The commits are as follows 1. replaces `nndist` by `nnDist` everywhere except in existing deprecations 2. adds deprecations for all declarations 3. changes `edist_nnDist` to `eDist_nnDist` to avoid a future deprecation 4. adds a deprecation for `NNDist.nndist` itself. 5. adds deprecations for lemmas created with the `alias ⟨_, _⟩ := _` syntax. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 832/479 Mathlib/Analysis/BoxIntegral/Box/Basic.lean,Mathlib/Analysis/BoxIntegral/Integrability.lean,Mathlib/Analysis/CStarAlgebra/Basic.lean,Mathlib/Analysis/Complex/AbsMax.lean,Mathlib/Analysis/Complex/Basic.lean,Mathlib/Analysis/Complex/Norm.lean,Mathlib/Analysis/Convex/MetricSpace.lean,Mathlib/Analysis/InnerProductSpace/PiL2.lean,Mathlib/Analysis/InnerProductSpace/Projection/Basic.lean,Mathlib/Analysis/InnerProductSpace/TensorProduct.lean,Mathlib/Analysis/LocallyConvex/Bounded.lean,Mathlib/Analysis/Normed/Affine/AddTorsor.lean,Mathlib/Analysis/Normed/Affine/Isometry.lean,Mathlib/Analysis/Normed/Algebra/Unitization.lean,Mathlib/Analysis/Normed/Field/Basic.lean,Mathlib/Analysis/Normed/Group/AddTorsor.lean,Mathlib/Analysis/Normed/Group/Basic.lean,Mathlib/Analysis/Normed/Group/Constructions.lean,Mathlib/Analysis/Normed/Group/Uniform.lean,Mathlib/Analysis/Normed/Lp/Finsupp.lean,Mathlib/Analysis/Normed/Lp/PiLp.lean,Mathlib/Analysis/Normed/Lp/ProdLp.lean,Mathlib/Analysis/Normed/MulAction.lean,Mathlib/Analysis/Normed/Operator/NNNorm.lean,Mathlib/Analysis/Normed/Ring/Lemmas.lean,Mathlib/Geometry/Convex/ConvexSpace/CompactSpaceStdSimplex.lean,Mathlib/Geometry/Euclidean/Projection.lean,Mathlib/InformationTheory/Hamming.lean,Mathlib/MeasureTheory/Constructions/BorelSpace/Metric.lean,Mathlib/MeasureTheory/Function/SimpleFuncDenseLp.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/MeasureTheory/Integral/Bochner/SumMeasure.lean,Mathlib/MeasureTheory/Integral/BoundedContinuousFunction.lean,Mathlib/MeasureTheory/Measure/FiniteMeasure.lean,Mathlib/MeasureTheory/Measure/Hausdorff.lean,Mathlib/MeasureTheory/Measure/Portmanteau.lean,Mathlib/MeasureTheory/VectorMeasure/Integral.lean,Mathlib/Probability/BrownianMotion/Basic.lean,Mathlib/Probability/BrownianMotion/GaussianProjectiveFamily.lean,Mathlib/Topology/Algebra/InfiniteSum/ENNReal.lean,Mathlib/Topology/Algebra/MetricSpace/Lipschitz.lean,Mathlib/Topology/ContinuousMap/Bounded/Basic.lean,Mathlib/Topology/ContinuousMap/Bounded/Normed.lean,Mathlib/Topology/ContinuousMap/Compact.lean,Mathlib/Topology/ContinuousMap/Ideals.lean,Mathlib/Topology/EMetricSpace/Weak.lean,Mathlib/Topology/Instances/Rat.lean,Mathlib/Topology/MetricSpace/Algebra.lean,Mathlib/Topology/MetricSpace/Antilipschitz.lean,Mathlib/Topology/MetricSpace/Basic.lean,Mathlib/Topology/MetricSpace/Cauchy.lean,Mathlib/Topology/MetricSpace/Congruence.lean,Mathlib/Topology/MetricSpace/Defs.lean,Mathlib/Topology/MetricSpace/Dilation.lean,Mathlib/Topology/MetricSpace/Holder.lean,Mathlib/Topology/MetricSpace/IsometricSMul.lean,Mathlib/Topology/MetricSpace/Isometry.lean,Mathlib/Topology/MetricSpace/Lipschitz.lean,Mathlib/Topology/MetricSpace/ProperSpace/Lemmas.lean,Mathlib/Topology/MetricSpace/Pseudo/Basic.lean,Mathlib/Topology/MetricSpace/Pseudo/Constructions.lean,Mathlib/Topology/MetricSpace/Pseudo/Defs.lean,Mathlib/Topology/MetricSpace/Pseudo/Pi.lean,Mathlib/Topology/MetricSpace/Similarity.lean,MathlibTest/Tactic/Basify.lean 65 7 ['JovanGerb', 'bryangingechen', 'github-actions', 'grunweg', 'joneugster', 'mathlib-merge-conflicts'] nobody
1-36409
1 day ago
2-85126
2 days ago
14-51649
14 days
0
40940 JovanGerb
author:JovanGerb
feat(CategoryTheory/Comma/StructuredArrow): use `to_dual` This PR generates declarations about `CostructuredArrow` from those about `StructuredArrow` using `to_dual`. This PR deprecates `hom_eq_iff` in favour of `ext_iff`/`hom_ext_iff`. `StructuredArrow.isoMk` and its dependencies are difficult to dualize for `to_dual`, so they are left as-is. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #40503 - [x] depends on: #42861 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-category-theory tech debt 157/423 Mathlib/CategoryTheory/Comma/Basic.lean,Mathlib/CategoryTheory/Comma/StructuredArrow/Basic.lean,Mathlib/CategoryTheory/Comma/StructuredArrow/CommaMap.lean,Mathlib/CategoryTheory/Filtered/Final.lean,Mathlib/CategoryTheory/Limits/Indization/ParallelPair.lean,Mathlib/Tactic/Translate/ToDual.lean,Mathlib/Topology/Category/Profinite/Extend.lean 7 9 ['JovanGerb', 'github-actions', 'joelriou', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-35956
1 day ago
1-38162
1 day ago
1-47458
1 day
0
46218 urkud
author:urkud
feat(Topology/MetricSpace/Bounded): add `Metric.ediam_closedBall_le` Add `Metric.ediam_closedBall_le : ediam (closedBall x r) ≤ 2 * ENNReal.ofReal r`, the `closedBall` analogue of `Metric.ediam_closedEBall_le`. Upstreamed from the https://github.com/urkud/SardMoreira project. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-topology easy maintainer-merge 15/0 Mathlib/Topology/MetricSpace/Bounded.lean,Mathlib/Topology/MetricSpace/Pseudo/Defs.lean 2 3 ['github-actions', 'themathqueen'] nobody
1-35306
1 day ago
2-39138
2 days ago
2-65513
2 days
2
46185 urkud
author:urkud
feat: add `NNReal.nnNorm_smul` etc From https://github.com/urkud/SardMoreira --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> <!-- Message of single commit: --> t-analysis 51/0 Mathlib/Analysis/Normed/Group/Real.lean,Mathlib/Analysis/Normed/MulAction.lean,Mathlib/Analysis/Normed/Ring/Basic.lean 3 1 ['github-actions'] nobody
1-29137
1 day ago
3-70232
3 days ago
3-70177
3 days
0
46063 urkud
author:urkud
refactor(LinearAlgebra): add `RankZeroSubsingleton`, move lemmas Move the lemmas about `Module.rank R M = 0` and `0 < Module.rank R M` to a new file `Mathlib/LinearAlgebra/Dimension/RankZero.lean` with minimal imports. Introduce the typeclass `Module.RankZeroSubsingleton R M` saying that a module of rank zero is trivial, with instances for free modules over any semiring (no `StrongRankCondition` needed) and for torsion free modules over a ring with `IsCancelMulZero`. Generalize `rank_zero_iff`, `rank_pos_iff_nontrivial`, `rank_pos`, `Submodule.rank_eq_zero`, `Module.finite_of_rank_eq_zero`, etc. to this typeclass, and deprecate `Module.rank_pos_of_free`, `Module.rank_pos_iff_of_free`, `Module.rank_zero_iff_of_free`. Also: - add `rank_eq_zero_iff_not_injective` for modules over semirings, and use it to golf the proof of `rank_eq_zero_iff`; - add `smul_left_injective_iff_smul_eq_zero`, `smul_left_injective_iff_ne_zero`, `linearIndependent_unique_iff_injective`, `linearIndepOn_singleton_iff_injective`, `LinearIndepOn.cardinal_le_rank`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> AI disclosure: I figured out the right assumptions and drafted most proofs. Claude moved code around, added deprecated aliases, and filled in a couple of proofs. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 276/143 Archive/Sensitivity.lean,Mathlib.lean,Mathlib/Algebra/Lie/Weights/Linear.lean,Mathlib/Algebra/Module/Torsion/Free.lean,Mathlib/Analysis/Normed/Module/Connected.lean,Mathlib/FieldTheory/CardinalEmb.lean,Mathlib/FieldTheory/SeparableClosure.lean,Mathlib/LinearAlgebra/AffineSpace/Dimension.lean,Mathlib/LinearAlgebra/Dimension/Basic.lean,Mathlib/LinearAlgebra/Dimension/Domain.lean,Mathlib/LinearAlgebra/Dimension/Finite.lean,Mathlib/LinearAlgebra/Dimension/Free.lean,Mathlib/LinearAlgebra/Dimension/RankNullity.lean,Mathlib/LinearAlgebra/Dimension/RankZero.lean,Mathlib/LinearAlgebra/Dimension/StrongRankCondition.lean,Mathlib/LinearAlgebra/Dimension/Torsion/Finite.lean,Mathlib/LinearAlgebra/LinearIndependent/Basic.lean,Mathlib/LinearAlgebra/LinearIndependent/Defs.lean,Mathlib/LinearAlgebra/Transvection/Basic.lean,Mathlib/NumberTheory/ModularForms/LevelOne/Basic.lean,Mathlib/NumberTheory/ModularForms/LevelOne/DimensionFormula.lean,Mathlib/NumberTheory/ModularForms/LevelOne/GradedRing.lean,Mathlib/RingTheory/AlgebraicIndependent/RankAndCardinality.lean,Mathlib/RingTheory/Length.lean,Mathlib/RingTheory/Unramified/Field.lean 25 1 ['github-actions'] nobody
1-26802
1 day ago
1-28159
1 day ago
5-67706
5 days
0
45108 thorimur
author:thorimur
feat: revamp `mk_all` internals This PR revamps `mk_all` to 1. correctly find the source directory and paths from the (already available) `lean_lib`s and rely on more robust Lake API more broadly 2. use a `Config` internally that accounts for the mathlib-specific exceptions, so that in the future downstream projects could read this from json instead 3. checks that we are not overwriting a file that includes more than just imports, and demands `--clobber` to do so 4. (misc.) allow multiple libraries/roots to be specified with `--lib Foo,Bar,Baz` This also generally refactors the code somewhat to make it more principled and (hopefully) maintainable. We also change the behavior of API in `Mathlib.Util.GetAllModules` as appropriate in order to rely on more robust paths. --- - [x] depends on: #45107 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-meta 271/110 Mathlib/Util/GetAllModules.lean,lakefile.lean,scripts/README.md,scripts/mk_all.lean 4 12 ['github-actions', 'grunweg', 'joneugster', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'thorimur'] kim-em
assignee:kim-em
1-23732
1 day ago
1-26201
1 day ago
29-2633
29 days
0
45220 xroblot
author:xroblot
feat(RingTheory/Polynomial/Cyclotomic/Eval): when is `ζ - 1` a unit For a primitive `n`-th root of unity `ζ` in a domain, `ζ - 1` is a unit precisely when the `n`-th cyclotomic polynomial takes a unit value at `1`. Consequently `ζ - 1` is a unit when `n > 1` is not a prime power, and, when `algebraMap ℤ R` is a local homomorphism (e.g. for rings of integers), only then. We also add `eval_one_cyclotomic_of_not_isPrimePow`, stated with `IsPrimePow`, and deprecate `eval_one_cyclotomic_not_prime_pow` in its favour. The hypothesis of `IsPrimitiveRoot.norm_toInteger_sub_one_eq_one` is restated with `IsPrimePow`. :robot: This PR was extracted from the [SKW project](https://github.com/xroblot/SKW) by Claude. t-ring-theory 86/27 Mathlib/NumberTheory/NumberField/Cyclotomic/Basic.lean,Mathlib/RingTheory/Polynomial/Cyclotomic/Eval.lean,Mathlib/RingTheory/RootsOfUnity/CyclotomicUnits.lean 3 11 ['github-actions', 'mathlib-merge-conflicts', 'tb65536', 'xroblot'] nobody
1-5106
1 day ago
1-5695
1 day ago
26-81303
26 days
1
42272 xroblot
author:xroblot
feat(Algebra/QuadraticAlgebra): the degenerate cases over a field Complete the classification of `QuadraticAlgebra K a b` over a field by describing the two degenerate case. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #42708 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra
label:t-algebra$
111/0 Mathlib/Algebra/QuadraticAlgebra/Basic.lean,Mathlib/Algebra/QuadraticAlgebra/Discriminant.lean 2 9 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'tb65536', 'xroblot'] nobody
1-4871
1 day ago
50-22735
50 days ago
67-62421
67 days
0
46277 wrenna-robson
author:wrenna-robson
chore(GroupTheory/Perm/Support): split into smaller files Part of the `Equiv.Perm.support` refactor discussed on [Zulip](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/support.20of.20permutations.20on.20Type.20instead.20of.20Fintype/near/640706043): #46119 (move `IsSwap` and pow-apply lemmas) → #46277 (split `Support.lean`) → #46082 (rename to `supportFinset`) → #46126 (`Set`-valued `support`). This prepares for a `Set`-valued definition of `Equiv.Perm.support`, which needs no `Fintype` or `DecidableEq` assumptions. Splitting the file first separates the material that needs no finiteness assumptions from the current `Finset`-valued `support`, so that the later changes stay small and easy to review. Some splits have also been made to reduce unnecessary imports. Split `Mathlib/GroupTheory/Perm/Support.lean` into: * `Support/Basic.lean`: the `set_support_*` lemmas, with no finiteness assumptions; * `Support/Disjoint.lean`: the `Equiv.Perm.Disjoint` API that does not involve `support`; * `Support/Finset/Basic.lean`: the `Finset`-valued `Equiv.Perm.support` and its API; * `Support/Finset/Card.lean`: lemmas about the cardinality of `support`, including `fixed_point_card_lt_of_ne_one`; * `Support/NoncommProd.lean`: lemmas about `Finset.noncommProd` of permutations. This is a pure move: no declarations are renamed or restated. An LLM has been used in the preparation of this PR but as it contains no new content - i.e. it is just a move - I am omitting the LLM-generated tag. - [x] depends on: #46119 tech debt t-group-theory 733/601 Mathlib.lean,Mathlib/Algebra/Order/Rearrangement.lean,Mathlib/GroupTheory/Perm/ClosureSwap.lean,Mathlib/GroupTheory/Perm/Cycle/Factors.lean,Mathlib/GroupTheory/Perm/Finite.lean,Mathlib/GroupTheory/Perm/List.lean,Mathlib/GroupTheory/Perm/Sign.lean,Mathlib/GroupTheory/Perm/Support.lean,Mathlib/GroupTheory/Perm/Support/Basic.lean,Mathlib/GroupTheory/Perm/Support/Disjoint.lean,Mathlib/GroupTheory/Perm/Support/Finset/Basic.lean,Mathlib/GroupTheory/Perm/Support/Finset/Card.lean,Mathlib/GroupTheory/Perm/Support/NoncommProd.lean,Mathlib/LinearAlgebra/Matrix/SemiringInverse.lean 14 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-4683
1 day ago
1-5909
1 day ago
1-15204
1 day
2
46234 xroblot
author:xroblot
feat(NumberTheory/NumberField/Basic): add `SMulCommClass G (𝓞 K) (𝓞 L)` instance This PR adds the instance `SMulCommClass G (𝓞 K) (𝓞 L)` for a group `G` acting on `L` and commuting with the action of `K`. :robot: This result is used in the proof of Stickelberger's theorem in #46022. It was extracted by Claude from the [SKW project](https://github.com/xroblot/SKW). t-ring-theory maintainer-merge 24/1 Mathlib/NumberTheory/NumberField/Basic.lean 1 15 ['github-actions', 'leanprover-radar', 'tb65536', 'xroblot'] nobody
1-4642
1 day ago
2-4063
2 days ago
3-233
3 days
1
42811 xroblot
author:xroblot
chore(RingTheory/FractionalIdeal): define `FractionalIdeal.absNorm` without a `ℤ`-basis `FractionalIdeal.absNorm I` is now defined as `Ideal.absNorm I.num / Ideal.absNorm (span {I.den})` rather than `Ideal.absNorm I.num / |Algebra.norm ℤ I.den|`, so it also makes sense over rings with no `ℤ`-basis. The two agree for a finite free `ℤ`-module, see `absNorm_eq`, and the results that need a basis keep their current statements, so nothing downstream changes. In passing, `absNorm_eq_zero_iff` and `abs_det_basis_change` lose their `[IsDomain K]` hypothesis, which is automatic here. The mathematics and design are mine. Claude Code was used as a coding assistant and for the housekeeping around this PR. 🤖 --- - [x] depends on: #42790 t-ring-theory 59/35 Mathlib/RingTheory/FractionalIdeal/Norm.lean 1 7 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'wwylele', 'xroblot'] nobody
1-4636
1 day ago
8-82324
8 days ago
8-83945
8 days
0
46233 xroblot
author:xroblot
feat(FieldTheory/Galois): naturality of restrictHom and comparison with restrictNormalHom This PR shows that `IsGaloisGroup.restrictHom` is characterized by its compatibility with `algebraMap B C`, that it does not depend on the tower used to define it, and that, for fields, it is equal to `AlgEquiv.restrictNormalHom`. :robot: This result is used in the proof of Stickelberger's theorem in #46022. It was extracted by Claude from the [SKW project](https://github.com/xroblot/SKW). t-ring-theory t-algebra maintainer-merge
label:t-algebra$
34/0 Mathlib/FieldTheory/Galois/IsGaloisGroup.lean 1 2 ['github-actions', 'tb65536'] nobody
1-4568
1 day ago
3-12002
3 days ago
3-13350
3 days
1
46181 xroblot
author:xroblot
feat(NumberTheory/NumberField/Discriminant): prove Stickelberger's theorem We prove Stickelberger's theorem: the discriminant of a number field is congruent to `0` or `1` modulo `4`. The proof uses the permanent of the matrix of embeddings: the determinant and the permanent are congruent modulo `2`, and the permanent is an integer since it is invariant under Galois action. Along the way, the instance `IsFractionRing (𝓞 K) K` is generalized from number fields to algebraic extensions of `ℚ`. Note that the large import is due to the import of the determinant in the permanent file which is a leaf life. The mathematics and design are mine. Claude Code was used as a coding assistant and for the housekeeping around this PR. 🤖 large-import 66/2 Mathlib/LinearAlgebra/Matrix/Permanent.lean,Mathlib/NumberTheory/NumberField/Basic.lean,Mathlib/NumberTheory/NumberField/Discriminant/Basic.lean 3 2 ['github-actions'] riccardobrasca
assignee:riccardobrasca
1-4541
1 day ago
3-75957
3 days ago
3-75902
3 days
0
44588 xroblot
author:xroblot
feat(RingTheory/RootsOfUnity): generalize Ideal.rootsOfUnityMapQuot to commutative rings The morphism from the roots of unity of order `n` to the units of a quotient ring is currently stated for the ring of integers of a number field, although nothing about it needs more than a commutative ring. It is moved to a new file and stated in that generality. It is injective as soon as `n` does not lie in the ideal, for any domain. :robot: This PR was extracted from the [SKW project](https://github.com/xroblot/SKW) by Claude. t-ring-theory 132/58 Mathlib.lean,Mathlib/NumberTheory/NumberField/Ideal/Basic.lean,Mathlib/RingTheory/RootsOfUnity/Quotient.lean 3 3 ['github-actions', 'tb65536', 'xroblot'] nobody
1-4422
1 day ago
8-5672
8 days ago
23-29802
23 days
2
44427 xroblot
author:xroblot
feat(Tactic/NormNum): norm_num extension for Squarefree Add a `norm_num` extension deciding `Squarefree n` for numerals `n` in `ℕ` and `ℤ`. If `n` is not squarefree, the proof uses a witness `a > 1` with `a * a ∣ n`, found with `Nat.minSqFac`. If `n` is squarefree, the proof is a trial division of `n` by the odd numbers `k = 3, 5, 7, …`, keeping the invariant that every prime divisor of the cofactor is at least `k`. This is adapted from the Mathlib 3 extension by Mario Carneiro (mathlib#11666), which was left commented out in `Mathlib.Data.Nat.Squarefree` during the port. This commented-out code is removed, and the corresponding tests are restored. As for the `Nat.Prime` extension, the proof is a certificate rather than a kernel evaluation of `Nat.minSqFac` via `Nat.squarefree_iff_minSqFac`. The certificate is also faster to check, but, as for `Nat.Prime`, large numbers need a higher `maxRecDepth`. **Note**. I have read and checked the ordinary Lean statements and their proofs, but I am not familiar with metaprogramming, so I cannot really vouch for the meta code itself, which was written with the help of an LLM. A review by someone who is comfortable with `norm_num` extensions would be very welcome. Created with Claude Code 🤖 --- tech debt t-meta LLM-generated 198/204 Mathlib.lean,Mathlib/Data/Nat/Squarefree.lean,Mathlib/Tactic.lean,Mathlib/Tactic/NormNum/Squarefree.lean,MathlibTest/Tactic/NormNum/Ext.lean 5 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
1-4414
1 day ago
10-20861
10 days ago
49-7250
49 days
0
43924 xroblot
author:xroblot
feat(NumberTheory/NumberField): generalize isTotallyReal_sup Generalize `NumberField.isTotallyReal_sup` and `NumberField.isTotallyReal_iSup` so they no longer require the ambient field to be of characteristic zero and algebraic over `ℚ`: a compositum of totally real subfields of any field is totally real. :robot: This PR was extracted from the [SKW project](https://github.com/xroblot/SKW) by Claude. --- - [x] depends on: #43925 t-number-theory maintainer-merge 22/14 Mathlib/NumberTheory/NumberField/InfinitePlace/TotallyRealComplex.lean 1 7 ['MichaelStollBayreuth', 'github-actions', 'mathlib-dependent-issues', 'tb65536', 'xroblot'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
1-4402
1 day ago
5-12370
5 days ago
5-14017
5 days
0
45300 xroblot
author:xroblot
refactor(RingTheory/Ideal): generalize some absNorm lemmas and move primesEquiv This is the clean-up part of #42567, extracted so that the summability work can build on it. Two divisibility and positivity results about the absolute norm of an ideal are generalized from `ℤ` to a Dedekind domain, and from prime ideals to proper ideals, with the earlier versions deprecated. The equivalence between the height-one prime ideals of the integral closure of `ℤ` in `ℚ` and the prime numbers is moved to the Dedekind domain files, where it belongs, and redefined through the absolute norm rather than through a generator of the corresponding ideal of `ℤ`. It now assumes less, and the auxiliary API it used to be built from is deprecated without replacement. Finally, the equivalence between the height-one spectra of two isomorphic rings is reworked so that the surjectivity proofs have the expected type, which removes the need for a `backward.isDefEq` option. The mathematics and design are mine. Claude Code was used as a coding assistant and for the housekeeping around this PR. 🤖 tech debt 134/72 Mathlib/NumberTheory/NumberField/Completion/FinitePlace.lean,Mathlib/NumberTheory/Padics/HeightOneSpectrum.lean,Mathlib/RingTheory/DedekindDomain/Ideal/Lemmas.lean,Mathlib/RingTheory/Ideal/Int.lean,Mathlib/RingTheory/Ideal/Norm/AbsNorm.lean 5 9 ['github-actions', 'mathlib-merge-conflicts', 'tb65536', 'xroblot'] nobody
1-4374
1 day ago
3-7679
3 days ago
24-67471
24 days
1
45976 xroblot
author:xroblot
refactor(RingTheory/DedekindDomain/Factorization): use multiplicity for ideals The exponent of a maximal ideal `v` in the factorization of an ideal `I` is currently expressed as `(Associates.mk v.asIdeal).count (Associates.mk I).factors`. The goal of this refactor is to express it in terms of `multiplicity`. The refactor is done in two steps and this PR is the first step: it defines `maxPowDividing` using `multiplicity` and develops the corresponding API. It also deprecates most of the lemmas for integral ideals stated with `Associates.count` in favor of the `multiplicity` versions and adapts the downstream uses. Some lemmas had also to be moved. `FractionalIdeal.count` is not changed in this PR. A side benefit is that many hypotheses `I ≠ 0` can be dropped since the convention `multiplicity a 0 = 0` matches `normalizedFactors 0 = 0`. The second step (#45939) redefines `FractionalIdeal.count` using `multiplicity`, on top of the API introduced here, and deprecates the remaining `Associates.count` statements. New results: - `count_associates_factors_eq_multiplicity`: the exponent of `p` in the factors of `Associates.mk I` is `multiplicity p I`. This is used to derive the deprecated statements from the new ones. - `finprod_heightOneSpectrum_zpow_multiplicity`: a nonzero ideal `I` is the product of the `v ^ multiplicity v I` in `FractionalIdeal R⁰ K`. It will be used in the second step. Lemmas stated with `Associates.count` deprecated in favor of their `multiplicity` versions: - `Associates.finite_factors` is replaced by `Ideal.eventually_multiplicity_eq_zero`. - `Ideal.hasFiniteMulSupport_coeIdeal` is replaced by `Ideal.hasFiniteMulSupport_zpow_multiplicity`. - `Ideal.hasFiniteMulSupport_inv` is replaced by `Ideal.hasFiniteMulSupport_zpow_neg_multiplicity`. - `Ideal.finprod_not_dvd` is replaced by `Ideal.pow_multiplicity_add_one_not_dvd_finprod`. - `Ideal.finprod_count` is replaced by `Ideal.multiplicity_finprod_maxPowDividing`. The mathematics and design are mine. Claude Code was used as a coding assistant and for the housekeeping around this PR. 🤖 --- t-ring-theory 195/136 Mathlib/Algebra/Module/Torsion/PrimaryComponent.lean,Mathlib/NumberTheory/NumberField/Completion/FinitePlace.lean,Mathlib/NumberTheory/NumberField/ProductFormula.lean,Mathlib/RingTheory/DedekindDomain/Factorization.lean,Mathlib/RingTheory/UniqueFactorizationDomain/FactorSet.lean,Mathlib/Topology/Algebra/Ring/Compact.lean 6 22 ['github-actions', 'mathlib-merge-conflicts', 'tb65536', 'xroblot'] nobody
1-4119
1 day ago
1-18372
1 day ago
6-73821
6 days
1
45465 xroblot
author:xroblot
feat(FieldTheory/Finite): sum of the powers of the elements of a finite field For `i ≠ 0`, the sum of `x ^ i` over all the elements `x` of a finite field with `q` elements is `-1` if `q - 1` divides `i`, and `0` otherwise. As a special case, the sum of all the elements of a finite field is `1` if it has two elements and `0` otherwise. The PR also adds, for a finite group with zero, the identification of a product (or a sum) over the nonzero elements with a product over the units, and fixes the docstring of `sum_pow_units` and the module docstring, which gave the value `q - 1` instead of `-1`. :robot: This PR was extracted from the [SKW project](https://github.com/xroblot/SKW) by Claude. t-algebra
label:t-algebra$
38/17 Mathlib/Algebra/GroupWithZero/Units/Fintype.lean,Mathlib/FieldTheory/Finite/Basic.lean 2 4 ['SnirBroshi', 'github-actions', 'xroblot'] nobody
1-3798
1 day ago
24-1709
24 days ago
24-1698
24 days
1
46097 xroblot
author:xroblot
feat(NumberTheory/ArithmeticFunction): bundle Euler's totient as an arithmetic function This PR defines Euler's totient function as an arithmetic function, `ArithmeticFunction.totient`, in a new file `NumberTheory/ArithmeticFunction/Totient.lean`. It proves that it is multiplicative, that its Dirichlet convolution with `ζ` is the identity and that the convolution of `μ` with the identity is the totient. It also proves that `φ (lcm m n) * φ (gcd m n) = φ m * φ n`. This supersedes #28676, which was closed by its author. In the discussion there, it was suggested that the bundled version could replace `Nat.totient` altogether, but there did not seem to be a consensus, so this PR keeps both, with `ArithmeticFunction.totient` unfolding to `Nat.totient`. The replacement can be done in a follow-up PR if desired. :robot: This result is used in the proof of Stickelberger's theorem in #46022. It was extracted by Claude from the [SKW project](https://github.com/xroblot/SKW). t-number-theory LLM-generated 73/1 Mathlib.lean,Mathlib/Data/Nat/Totient.lean,Mathlib/NumberTheory/ArithmeticFunction/Totient.lean 3 10 ['SnirBroshi', 'github-actions', 'xroblot'] nobody
1-3785
1 day ago
4-23608
4 days ago
4-23740
4 days
1
46305 plp127
author:plp127
feat(FieldTheory/IntermediateField): `AlgHom.fieldEqualizer` We define `AlgHom.fieldEqualizer`, the `IntermediateField` analogue to `AlgHom.equalizer`, and prove some basic properties. Suggested by @tb65536 in https://github.com/leanprover-community/mathlib4/pull/36239#discussion_r4565924077. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
45/0 Mathlib/FieldTheory/IntermediateField/Adjoin/Defs.lean,Mathlib/FieldTheory/IntermediateField/Basic.lean 2 2 ['github-actions', 'xroblot'] nobody
1-3739
1 day ago
1-39231
1 day ago
1-39176
1 day
1
45872 joelriou
author:joelriou
feat(CategoryTheory): finally small full subcategories More lemmas are added in order to dualize initially/finally small categories, to identify final/initial inclusion functors of full subcategories, to show that certain full subcategories are (co)filtered or `κ`-filtered and to show that `κ`-filtered finally small categories are exactly the categories with a final functor from a `κ`-filtered small category. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-category-theory large-import 275/9 Mathlib/CategoryTheory/EssentialImage.lean,Mathlib/CategoryTheory/Filtered/Final.lean,Mathlib/CategoryTheory/Limits/Final.lean,Mathlib/CategoryTheory/Limits/FinallySmall.lean,Mathlib/CategoryTheory/ObjectProperty/Basic.lean,Mathlib/CategoryTheory/ObjectProperty/ClosedUnderIsomorphisms.lean,Mathlib/CategoryTheory/ObjectProperty/Equivalence.lean,Mathlib/CategoryTheory/Presentable/IsCardinalFiltered.lean 8 5 ['github-actions', 'joelriou', 'robin-carlier'] robin-carlier
assignee:robin-carlier
1-2104
1 day ago
1-2985
1 day ago
10-69649
10 days
4
44284 xroblot
author:xroblot
feat(NumberTheory/RamificationInertia): splitting of a prime in the decomposition ring If `𝓟` is the prime of the decomposition ring below `P`, then `P` is the only prime above `𝓟`, `𝓟` has the same ramification index and inertia degree in `B` as `p`, and both are `1` over `A`. The ramification index and inertia degree of `P` over the decomposition ring are computed as well. The versions for the decomposition field are now deduced from these, and hold under weaker hypotheses than before. The mathematics and design are mine. Claude Code was used as a coding assistant and for the housekeeping around this PR. 🤖 --- - [x] depends on: #44283 t-number-theory 165/56 Mathlib/NumberTheory/RamificationInertia/Galois.lean,Mathlib/NumberTheory/RamificationInertia/HilbertTheory.lean 2 26 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'tb65536', 'xroblot'] tb65536
assignee:tb65536
1-2015
1 day ago
1-82986
1 day ago
24-52026
24 days
7
46265 gasparattila
author:gasparattila
chore(Analysis/Complex): make `UpperHalfPlane.I` protected Since there is a coercion from `ℍ` to `ℂ`, writing `I` can mean `↑UpperHalfPlane.I` instead of the intended `Complex.I`. This mistake occurs in multiple lemmas, which are fixed in this PR (including those that explicitly use `UpperHalfPlane.I` instead of `Complex.I`). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-number-theory t-analysis maintainer-merge 57/77 Mathlib/Analysis/Complex/UpperHalfPlane/Basic.lean,Mathlib/Analysis/Complex/UpperHalfPlane/FixedPoints.lean,Mathlib/Analysis/Complex/UpperHalfPlane/Manifold.lean,Mathlib/Analysis/Complex/UpperHalfPlane/MoebiusAction.lean,Mathlib/Analysis/Complex/UpperHalfPlane/ProperAction.lean,Mathlib/NumberTheory/Modular.lean,Mathlib/NumberTheory/ModularForms/Bounds.lean,Mathlib/NumberTheory/ModularForms/DedekindEta.lean,Mathlib/NumberTheory/ModularForms/Derivative.lean,Mathlib/NumberTheory/ModularForms/Discriminant.lean,Mathlib/NumberTheory/ModularForms/EisensteinSeries/E2/Defs.lean,Mathlib/NumberTheory/ModularForms/EisensteinSeries/E2/MDifferentiable.lean,Mathlib/NumberTheory/ModularForms/EisensteinSeries/E2/Summable.lean,Mathlib/NumberTheory/ModularForms/EisensteinSeries/E2/Transform.lean,Mathlib/NumberTheory/ModularForms/EisensteinSeries/QExpansion.lean,Mathlib/NumberTheory/ModularForms/LFunction.lean,Mathlib/NumberTheory/ModularForms/LevelOne/Basic.lean,Mathlib/NumberTheory/ModularForms/LevelOne/DimensionFormula.lean,Mathlib/NumberTheory/ModularForms/NormTrace.lean,Mathlib/NumberTheory/ModularForms/QExpansion.lean,Mathlib/NumberTheory/ModularForms/RamanujanFormula.lean 21 4 ['gasparattila', 'github-actions', 'mathlib-merge-conflicts', 'themathqueen'] nobody
0-85071
23 hours ago
2-8995
2 days ago
2-52431
2 days
0
46313 TheDarkLightX
author:TheDarkLightX
feat(ModelTheory): add definable functions of a theory Add `Theory.FunctionalFormula` for definable functions of a first-order theory. Its elements are semantic equivalence classes of formulas that define a unique output tuple for every input in every model of the theory. The API provides evaluation, extensionality, and composition. The expanded language adds a function symbol for each single-output definable function, with the output indexed by `Fin 1`. Every model of the original theory has a canonical expansion. Bounded formulas in the expanded language translate back to the original language with the same realization. Co-authored-by: Chris Hughes <[33847686+ChrisHughes24@users.noreply.github.com](mailto:33847686+ChrisHughes24@users.noreply.github.com)> Co-authored-by: Kenny Lau <[kc_kennylau@yahoo.com.hk](mailto:kc_kennylau@yahoo.com.hk)> --- This adopts #26398 and addresses the review comments on semantic equivalence and the single-output case. The Ax–Grothendieck refactor from #26399 compiled against this API. OpenAI ChatGPT adapted the original Lean code and proofs to current mathlib, revised the representation and documentation, and generated compatibility checks. Lean checked the module and downstream refactor. An independent lean4lean run checked all 100 declarations in the module and their dependencies, 5,832 declarations in total. ZenoADP, ZenoFCIS, ZAL, and Crucible supplied finite counterexample checks. t-logic LLM-generated new-contributor 582/0 Mathlib.lean,Mathlib/ModelTheory/FunctionalFormula.lean 2 3 ['TheDarkLightX', 'github-actions'] nobody
0-85041
23 hours ago
0-85523
23 hours ago
0-85468
23 hours
0
46045 omar826
author:omar826
feat(GroupTheory/FreeGroup): decidability of conjugacy We prove the conjugacy criterion for free groups: two elements are conjugate iff the cyclic reductions of their reduced words are rotations of each other (`FreeGroup.isConj_iff_isRotated`). We use it to show that `IsConj` is decidable in `FreeGroup α` when `α` has decidable equality. - `Mathlib/GroupTheory/FreeGroup/Conj.lean`: the criterion, a version for words that are not necessarily reduced (`FreeGroup.isConj_mk_iff`), supporting lemmas about cyclically reduced words, and the `DecidableRel IsConj` instance. - `Mathlib/GroupTheory/FreeGroup/CyclicallyReduced.lean`: `reduceCyclically` is redefined by structural recursion instead of `List.bidirectionalRec`. This lets `decide` evaluate the instance, e.g. `IsConj (of 0 * of 1 : FreeGroup (Fin 2)) (of 1 * of 0)`. Co-authored-by: Arjun Sheth <arjun.sheth_ug25@ashoka.edu.in> Co-authored-by: Vivek Rajesh Joshi <vivek.rajeshjoshi@students.iiserpune.ac.in> Co-authored-by: T V H Prathamesh <prathamesh.turaga@krea.edu.in> Co-authored-by: Rishi Vyas <rishi.vyas@krea.edu.in> --- *Use of AI.* original Lean formalization of this result were done by hand by the authors using our own definitions of reduced, cyclically reduced words, and our own cyclic reduction function. We then used Claude Code to use Mathlib's existing API (IsReduced, IsCyclicallyReduced, reduceCyclically) instead of our definitions, following the same overall strategy and fixing naming and style to Mathlib conventions. This work comes from a project with T V H Prathamesh's group at KREA University. t-group-theory new-contributor 298/13 Mathlib.lean,Mathlib/GroupTheory/FreeGroup/Conj.lean,Mathlib/GroupTheory/FreeGroup/CyclicallyReduced.lean 3 26 ['github-actions', 'mathlib-merge-conflicts', 'omar826', 'vihdzp', 'wwylele'] nobody
0-84673
23 hours ago
5-29064
5 days ago
6-80902
6 days
0
45709 YaelDillies
author:YaelDillies
chore(Algebra/Order): make `Nonneg` a structure The goal is to eventually make `NNRat` and `NNReal` `abbrev`s for `Nonneg Rat` and `Nonneg Real`, and deduplicate their API. This is currently not possible due to prohibitive slowdowns when making their definition in terms of `Subtype` visible to automation. Generated by Claude Sonnet in many rounds of review by myself. Assisted-by: Claude Sonnet 5.5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt t-order large-import LLM-generated
label:t-algebra$
766/354 Archive/Wiedijk100Theorems/AreaOfACircle.lean,Mathlib.lean,Mathlib/Algebra/Field/Rat.lean,Mathlib/Algebra/Order/Nonneg/Basic.lean,Mathlib/Algebra/Order/Nonneg/Defs.lean,Mathlib/Algebra/Order/Nonneg/Field.lean,Mathlib/Algebra/Order/Nonneg/Floor.lean,Mathlib/Algebra/Order/Nonneg/Interval.lean,Mathlib/Algebra/Order/Nonneg/Lattice.lean,Mathlib/Algebra/Order/Nonneg/Order.lean,Mathlib/Algebra/Order/Nonneg/Ring.lean,Mathlib/Analysis/Analytic/Composition.lean,Mathlib/Analysis/BoxIntegral/Integrability.lean,Mathlib/Analysis/CStarAlgebra/Basic.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Isometric.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Order.lean,Mathlib/Analysis/CStarAlgebra/GelfandDuality.lean,Mathlib/Analysis/CStarAlgebra/Hom.lean,Mathlib/Analysis/CStarAlgebra/Matrix.lean,Mathlib/Analysis/CStarAlgebra/Multiplier.lean,Mathlib/Analysis/CStarAlgebra/Unitization.lean,Mathlib/Analysis/Complex/Basic.lean,Mathlib/Analysis/Complex/CauchyIntegral.lean,Mathlib/Analysis/Complex/Norm.lean,Mathlib/Analysis/Complex/OperatorNorm.lean,Mathlib/Analysis/Complex/UpperHalfPlane/Measure.lean,Mathlib/Analysis/ConstantSpeed.lean,Mathlib/Analysis/Convex/Cone/Closure.lean,Mathlib/Analysis/Convex/Segment.lean,Mathlib/Analysis/Convex/SpecificFunctions/Pow.lean,Mathlib/Analysis/InnerProductSpace/Basic.lean,Mathlib/Analysis/LocallyConvex/Asymptotics.lean,Mathlib/Analysis/Matrix/Normed.lean,Mathlib/Analysis/MeanInequalities.lean,Mathlib/Analysis/Normed/Algebra/Spectrum.lean,Mathlib/Analysis/Normed/Algebra/UnitizationL1.lean,Mathlib/Analysis/Normed/Field/Basic.lean,Mathlib/Analysis/Normed/Group/Constructions.lean,Mathlib/Analysis/Normed/Group/Continuity.lean,Mathlib/Analysis/Normed/Group/Hom.lean,Mathlib/Analysis/Normed/Group/Uniform.lean,Mathlib/Analysis/Normed/Lp/lpHolder.lean,Mathlib/Analysis/Normed/Module/Basic.lean,Mathlib/Analysis/Normed/Operator/Basic.lean,Mathlib/Analysis/Normed/Operator/Mul.lean,Mathlib/Analysis/Normed/Operator/NNNorm.lean,Mathlib/Analysis/Normed/Operator/NormedSpace.lean,Mathlib/Analysis/Normed/Operator/Prod.lean,Mathlib/Analysis/ODE/PicardLindelof.lean,Mathlib/Analysis/Quaternion.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Basic/NNReal/Basic.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/Data/NNRat/Defs.lean,Mathlib/Data/Rat/Cast/Lemmas.lean,Mathlib/Data/Rat/Init.lean,Mathlib/FieldTheory/IntermediateField/Basic.lean,Mathlib/Geometry/Convex/Cone/Dual.lean,Mathlib/Geometry/Convex/Cone/Pointed.lean,Mathlib/MeasureTheory/Constructions/BorelSpace/Basic.lean,Mathlib/MeasureTheory/Function/ConditionalExpectation/Real.lean,Mathlib/MeasureTheory/Function/Jacobian.lean,Mathlib/MeasureTheory/Function/SimpleFuncDenseLp.lean,Mathlib/MeasureTheory/Function/SpecialFunctions/Basic.lean,Mathlib/MeasureTheory/Function/UniformIntegrable.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/MeasureTheory/Integral/SetToL1/L1.lean,Mathlib/MeasureTheory/MeasurableSpace/Constructions.lean,Mathlib/MeasureTheory/Measure/Prokhorov.lean,Mathlib/MeasureTheory/Measure/Stieltjes.lean,Mathlib/NumberTheory/Modular.lean,Mathlib/NumberTheory/NumberField/CanonicalEmbedding/Basic.lean,Mathlib/Probability/Moments/IntegrableExpMul.lean,Mathlib/Probability/Moments/Tilted.lean,Mathlib/RingTheory/RootsOfUnity/Complex.lean,Mathlib/RingTheory/Valuation/ValuationSubring.lean,Mathlib/Topology/Algebra/Field.lean,Mathlib/Topology/Algebra/MetricSpace/Lipschitz.lean,Mathlib/Topology/Algebra/Order/Module.lean,Mathlib/Topology/Algebra/Ring/Real.lean,Mathlib/Topology/Bornology/Real.lean,Mathlib/Topology/ContinuousMap/Bounded/Basic.lean,Mathlib/Topology/ContinuousMap/Bounded/Normed.lean,Mathlib/Topology/Instances/NNReal/Lemmas.lean,Mathlib/Topology/Instances/Rat.lean,Mathlib/Topology/MetricSpace/Basic.lean,Mathlib/Topology/MetricSpace/Cauchy.lean,Mathlib/Topology/MetricSpace/HausdorffDimension.lean,Mathlib/Topology/MetricSpace/Lipschitz.lean,Mathlib/Topology/MetricSpace/ProperSpace/Real.lean,Mathlib/Topology/MetricSpace/Pseudo/Constructions.lean,Mathlib/Topology/MetricSpace/Thickening.lean,Mathlib/Topology/Order/Nonneg.lean,Mathlib/Topology/UniformSpace/Real.lean 95 7 ['github-actions', 'mathlib-merge-conflicts'] nobody
0-83210
23 hours ago
0-85253
23 hours ago
12-38802
12 days
0
45861 grunweg
author:grunweg
chore: rename three lemmas involving the name some_eq_coe Reference the actual coercion being used. The ENNReal renames deserve a careful look. Found using the linter in #45229: among the cases of misnamed coercion lemmas using WithTop.some, these are some more interesting cases. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-order maintainer-merge 34/28 Mathlib/Algebra/Order/Monoid/Unbundled/WithTop.lean,Mathlib/Analysis/BoxIntegral/Partition/Additive.lean,Mathlib/Analysis/BoxIntegral/Partition/Basic.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Data/List/MinMax.lean,Mathlib/Order/WithBot.lean,Mathlib/Tactic/Echelon/Reflection.lean,Mathlib/Tactic/Inclusion/Extension/Interval/Basic.lean,Mathlib/Topology/Algebra/Ring/Real.lean,scripts/nolints_prime_decls.txt 11 11 ['YaelDillies', 'github-actions', 'grunweg', 'themathqueen'] nobody
0-80328
22 hours ago
11-84579
11 days ago
11-84743
11 days
0
46316 mathlib-splicebot
author:mathlib-splicebot
feat(Algebra/Algebra/NonUnitalHom): add `NonUnitalAlgHom.toLinearMap` --- This PR was automatically created from PR #46266 by @EtienneC30 via a [review comment](https://github.com/leanprover-community/mathlib4/pull/46266#discussion_r4653490663) by @themathqueen. maintainer-merge t-algebra
label:t-algebra$
12/0 Mathlib/Algebra/Algebra/NonUnitalHom.lean 1 3 ['github-actions', 'themathqueen'] nobody
0-79906
22 hours ago
0-82824
22 hours ago
0-82769
22 hours
0
43965 YaelDillies
author:YaelDillies
feat(NumberTheory): `decide`, `#eval` and `norm_num` for Carmichael numbers Provide both an efficient decidability instance and a `norm_num` extension to decide whether a given literal is a Carmichael number. This lets us prove that 561 is the smallest Carmichael number "in a computationally efficient manner". Deprecate the version of Korselt's criterion that was supposed to be used for this (but was less efficient than these new instance/extension). Generated by Claude Opus in several rounds of review to optimise various parts of the algorithms and make sure that the decidability instance works for both `#eval` and `decide`. I haven't made much of an effort to clean the proofs (existing proofs internal to `norm_num` read like garbage to me anyway). From FormalConjectures Assisted-by: Claude Opus 5.1 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-number-theory LLM-generated t-meta maintainer-merge 317/10 Mathlib/NumberTheory/CarmichaelNumber.lean,MathlibTest/NumberTheory/CarmichaelNumber.lean 2 39 ['Parcly-Taxel', 'SnirBroshi', 'Vierkantor', 'YaelDillies', 'github-actions', 'joneugster', 'leanprover-radar', 'mathlib-merge-conflicts', 'vihdzp', 'wwylele'] nobody
0-79864
22 hours ago
0-80247
22 hours ago
59-24372
59 days
1
45877 joelcanary
author:joelcanary
feat(NumberTheory/ArithmeticFunction/Moebius): `∑ n ≤ N, μ n * (N / n) = 1` This PR adds one lemma. It says that for `N ≠ 0` and for any ring `R`: ```lean ∑ n ∈ Ioc 0 N, (μ n : R) * (N / n : ℕ) = 1 ``` This is the same as `∑_{n ≤ N} μ(n)⌊N/n⌋ = 1`. The classical bound `|∑_{n ≤ N} μ(n)/n| ≤ 1` follows from this identity. PNT+ proves the identity again by hand inside `sum_mobius_div_self_le`; with this lemma, that part becomes one line. ------------ About the AI: I used an AI agent (Claude Code) to write the statement and the proof. I chose the target and I checked the result. t-number-theory LLM-generated new-contributor maintainer-merge 6/0 Mathlib/NumberTheory/ArithmeticFunction/Moebius.lean 1 10 ['GoldenPhysicsProject', 'MichaelStollBayreuth', 'github-actions', 'jcommelin', 'joelcanary'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
0-79069
21 hours ago
5-21141
5 days ago
11-54232
11 days
0
45249 YaelDillies
author:YaelDillies
feat(Order): transfer instances for complete lattices ... while preserving the existing bounded lattice structure. For coframes, this is neatly packaged using the `Coframe.MinimalAxioms` structure and the associated constructor `Coframe.ofMinimalAxioms`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 38/0 Mathlib/Order/CompleteBooleanAlgebra.lean,Mathlib/Order/CompleteLattice/Basic.lean,Mathlib/Order/ConditionallyCompleteLattice/Basic.lean 3 7 ['YaelDillies', 'github-actions', 'mathlib-merge-conflicts', 'tb65536'] Komyyy
assignee:Komyyy
0-79034
21 hours ago
17-19642
17 days ago
27-5240
27 days
1
45839 artie2000
author:artie2000
refactor(Topology/Algebra/Order): improve polynomial limit theorems * Improve statement of characterisation of polynomials with constant limit at infinity to be simpler and more usable * Prove that $$f(-X)=c$$ iff $$f(X)=c$$ --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-topology t-algebra t-order maintainer-merge
label:t-algebra$
46/13 Mathlib/Algebra/Polynomial/Degree/Lemmas.lean,Mathlib/Topology/Algebra/Order/Polynomial.lean 2 21 ['artie2000', 'github-actions', 'tb65536'] nobody
0-75784
21 hours ago
1-191
1 day ago
11-56685
11 days
0
44355 artie2000
author:artie2000
chore(Order): move Order/CompleteLattice/SetLike.lean to more descriptive location Order/CompleteLattice/SetLike.lean -> Order/CompleteSublattice/SetLike.lean Order/CompleteSublattice.lean -> Order/CompleteSublattice/Basic.lean This clears the file location for the material in #44253 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> file-removed t-order 5/5 Mathlib.lean,Mathlib/Order/CompleteSublattice/Basic.lean,Mathlib/Order/CompleteSublattice/SetLike.lean,Mathlib/RingTheory/SimpleModule/Isotypic.lean,Mathlib/SetTheory/Descriptive/Tree.lean 5 6 ['github-actions', 'mathlib-merge-conflicts'] nobody
0-75060
20 hours ago
11-55969
11 days ago
50-47902
50 days
1
44353 artie2000
author:artie2000
feat(Order/Lattice): generic membership lemmas under lattice operations * Add generic lemmas relating membership to lattice operations assuming `IsMemLE` * Tag these lemmas `membership`, and update a test --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #42342 t-order t-meta 78/4 Mathlib.lean,Mathlib/Basic/SetLike/Basic.lean,Mathlib/Order/Lattice/SetLike.lean,MathlibTest/SetLike.lean 4 4 ['artie2000', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
0-74438
20 hours ago
0-77498
21 hours ago
10-61529
10 days
1
42608 Deicyde
author:Deicyde
doc: add wikidata attributes This PR adds a batch of 7 `@[wikidata]` attributes. Claude helped generate the list of crossrefs (by scanning Wikidata + Mathlib). Comments are generated by [crossref-report](https://github.com/jcommelin/mathlib-crossref-report) and Wikilean. See https://wikilean.jackmccarthy.org/review?pr=42608 for reviewer UI. --- LLM-generated 14/2 Mathlib/Analysis/Convex/Segment.lean,Mathlib/Analysis/Convex/SimplicialComplex/Basic.lean,Mathlib/Combinatorics/SimpleGraph/Basic.lean,Mathlib/Combinatorics/SimpleGraph/Subgraph.lean,Mathlib/Data/Matrix/Diagonal.lean,Mathlib/RingTheory/MvPolynomial/Homogeneous.lean,Mathlib/Topology/Constructions.lean 7 21 ['Deicyde', 'SnirBroshi', 'github-actions', 'mathlib-merge-conflicts'] nobody
0-74421
20 hours ago
0-76488
21 hours ago
69-81931
69 days
0
46254 DanielJHorton
author:DanielJHorton
feat(Algebra/Group/Submonoid/Operations): port `fst` and `snd` from modules to monoids This PR is a generalization of `Submodule.fst` and `Submodule.snd` (along with some related API) to the `Submonoid` case. More precisely, this PR takes the results regarding submodules from lines 550-590 of `LinearAlgebra/Prod` and reformulates them in-terms of submonoids in the file `Algebra/Group/Submonoid/Operations`. The corollary `Submodule.isCompl_fst_snd` was not included in this PR because to prove it in the same file (in the way it is proved in the `Submodule` case) causes dependency issues. Specifically: `isCompl_fst_snd` and the lemma `isCompl_range_inl_inr` used in the proof are both true for monoids. Moreover, the proofs are basically identical to the ones that already exist for modules. The issue is that the proof of `isCompl_range_inl_inr` uses machinery from `Algebra/Group/Submonoid/Membership` which imports `Algebra/Group/Submonoid/Operations`, so these theorems can't go in that file with the rest of this PR. I'm happy to make another PR with monoid versions of those two theorems in some other file (perhaps `Algebra/Module/Submodule/Lattice`), but I thought it would be better to keep the scope of this PR small. It would probably also be a good idea to see if we can refactor (or at least relate) the module results to these generalizations. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
109/0 Mathlib/Algebra/Group/Subgroup/Basic.lean,Mathlib/Algebra/Group/Submonoid/Operations.lean 2 3 ['DanielJHorton', 'eric-wieser', 'github-actions'] nobody
0-73049
20 hours ago
2-73726
2 days ago
2-73671
2 days
0
46314 wrenna-robson
author:wrenna-robson
fix(GroupTheory/GroupAction/Hom): make `0 : A →+[M] A` the zero map, not the identity Since #34249, `to_additive` has translated `One (A →*[M] A)` (the identity map) to an instance `DistribMulActionHom.instZeroId : Zero (A →+[M] A)`, also the identity. This competes with the pointwise zero `DistriMulActionHom.instZero` on `A →ₑ+[φ] B`, and wins instance synthesis. (Note the lack of b!) As a result, on `master`: - `0 : A →+[M] A` is the identity map, and `One (A →+[M] A)` does not synthesise. - `DistribMulActionHom.coe_zero : ⇑(0 : A →+[M] A) = id` and `DistriMulActionHom.coe_zero : ⇑(0 : A →ₑ+[φ] B) = 0` are both `@[simp]`, and talk about different `0`s. This PR uses the approach of `Monoid.End`: 1. Add `to_additive_dont_translate` to `MulDistribMulActionHom`,. 2. Name the three generated declarations explicitly, as otherwise `to_additive` would still name them `instZeroId`, `coe_zero` and `zero_apply`. 3. Move the hand-written `DistriMulActionHom` instances and lemms to the `DistribMulActionHom` namespace (i.e. correct the typo). Note that `DistribMulActionHom.coe_zero` and `DistribMulActionHom.zero_apply` keep their names but change statement, from `⇑0 = id` and `0 a = a` to `⇑0 = 0` and `0 a = 0`. These are the statements they had before #34249, as are those of `coe_one` and `one_apply`. The old names cannot be deprecated, since they are reused - I feel this is fair dos as it's fixing a bug. The underlying issue: translating the identity map to `0` (and composition to `+`) is only safe when the raw type has no pointwise `+` or `0` of its own. `M ≃+ M` has none, so `AddAut` can do this; `A →+[M] A` does, so `DistribMulActionHom` needs `AddMonoid.End`'s convention instead. Unsure if there's a better way of ensuring this doesn't happen. --- ### Demonstration on `master` ```lean import Mathlib.GroupTheory.GroupAction.Hom variable {M A : Type*} [Monoid M] [AddMonoid A] [DistribMulAction M A] example (a : A) : (0 : A →+[M] A) a = 0 := by rw [DistriMulActionHom.zero_apply] -- error: Tactic `rewrite` failed: Did not find an occurrence of the pattern -- 0 ?a -- in the target expression -- 0 a = 0 theorem zero_ne_zero (a : A) (ha : a ≠ 0) : @OfNat.ofNat (A →+[M] A) (nat_lit 0) (@Zero.toOfNat0 _ DistriMulActionHom.instZero) ≠ 0 := fun h => ha (DFunLike.congr_fun h a).symm #check @zero_ne_zero -- @zero_ne_zero : ∀ {M A} … (a : A), a ≠ 0 → 0 ≠ 0 ``` 🤖 Generated with [Claude Code](https://claude.com/claude-code) LLM-generated t-group-theory maintainer-merge 12/7 Mathlib/GroupTheory/GroupAction/Hom.lean 1 10 ['github-actions', 'themathqueen', 'wrenna-robson'] nobody
0-71484
19 hours ago
0-84244
23 hours ago
0-84189
23 hours
0
45520 EzequielS2
author:EzequielS2
feat: add growth of finitely generated groups Add word-ball growth, domination, and independence of the generating set t-geometric-group-theory new-contributor 183/0 Mathlib.lean,Mathlib/Geometry/Group/Growth/Basic.lean 2 22 ['EzequielS2', 'github-actions', 'tb65536'] ADedecker
assignee:ADedecker
0-69711
19 hours ago
0-77207
21 hours ago
16-28578
16 days
3
45215 riccardobrasca
author:riccardobrasca
feat: add IsCyclotomicExtension.Rat.seven_pid We now have enough technology to prove this in one declaration. From flt-regular. - [x] depends on: #44548 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-number-theory maintainer-merge 67/31 Mathlib/NumberTheory/NumberField/ClassNumber.lean,Mathlib/NumberTheory/NumberField/Cyclotomic/PID.lean 2 42 ['DavidLedvinka', 'MichaelStollBayreuth', 'emlis42', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'ocfnash', 'raoxiaojia', 'riccardobrasca', 'tb65536', 'xroblot'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
0-69389
19 hours ago
0-69872
19 hours ago
4-67906
4 days
0
41975 fbarroero
author:fbarroero
feat(NumberTheory/NumberField/Ostrowski): prove nonarchimedean Ostrowski's theorem This PR proves the nonarchimedean case of Ostrowski’s theorem for number fields. The main declaration is ```lean theorem exists_heightOneSpectrum_equiv_adicAbv {f : AbsoluteValue K ℝ} (hf_nonarch : IsNonarchimedean f) (hf_nontriv : f.IsNontrivial) ∃! P : HeightOneSpectrum (𝓞 K), f ≈ adicAbv K P ``` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #40848 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-number-theory maintainer-merge 215/0 Mathlib.lean,Mathlib/Algebra/Module/Submodule/Defs.lean,Mathlib/NumberTheory/NumberField/Ostrowski.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Valuation.lean 4 20 ['MichaelStollBayreuth', 'fbarroero', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
0-67179
18 hours ago
1-50447
1 day ago
6-35103
6 days
0
44926 kedlaya
author:kedlaya
feat(FieldTheory): implement Artin-Schreier polynomials --- Implement Artin-Schreier polynomials in preparation for using them to describe cyclic degree-p extensions of fields of characteristic p. Split off from #43947. - [x] depends on: #44690 t-algebra new-contributor
label:t-algebra$
154/6 Mathlib.lean,Mathlib/Algebra/Polynomial/FieldDivision.lean,Mathlib/Algebra/Polynomial/Splits.lean,Mathlib/FieldTheory/ArtinSchreierExtension.lean 4 27 ['github-actions', 'kedlaya', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'plp127', 'tb65536'] nobody
0-66276
18 hours ago
0-66879
18 hours ago
2-61605
2 days
2
46322 Nicola9Falciola
author:Nicola9Falciola
feat(RingTheory/AdjointRoot): add iff lemma for when `AdjointRoot f` si reduced This PR add a small characterization lemma for `AdjointRoot f`: `IsReduced (AdjointRoot f) ↔ IsRadical f`. It also clean up `LinearAlgebra/SemiSimple` where this fact was deduced in line multiple times and remove a non neccesary import. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory 10/10 Mathlib/LinearAlgebra/Semisimple.lean,Mathlib/RingTheory/AdjoinRoot.lean 2 1 ['github-actions'] nobody
0-65649
18 hours ago
0-66254
18 hours ago
0-66199
18 hours
0
46307 estomagordo
author:estomagordo
refactor(LinearAlgebra/Basis): rename Basis.ext and Basis.ext' Rename `Basis.ext` to `Basis.ext_linearMap` and `Basis.ext'` to `Basis.ext_linearEquiv`, and deprecate the old names. `Basis.eq_of_apply_eq` stays as is. Renaming it to `Basis.ext` has to wait until the deprecation alias for `Basis.ext` is removed. Part of #46139. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor 107/92 Mathlib/Algebra/Azumaya/Matrix.lean,Mathlib/Algebra/Lie/CartanCriterion.lean,Mathlib/Algebra/Module/ZLattice/Basic.lean,Mathlib/Analysis/Complex/Isometry.lean,Mathlib/Analysis/InnerProductSpace/Adjoint.lean,Mathlib/Analysis/InnerProductSpace/Dual.lean,Mathlib/Analysis/InnerProductSpace/TwoDim.lean,Mathlib/Analysis/Matrix/Spectrum.lean,Mathlib/Analysis/Normed/Operator/LinearIsometry.lean,Mathlib/Geometry/Euclidean/Angle/Oriented/Rotation.lean,Mathlib/LinearAlgebra/Basis/Bilinear.lean,Mathlib/LinearAlgebra/Basis/Defs.lean,Mathlib/LinearAlgebra/Basis/SMul.lean,Mathlib/LinearAlgebra/Basis/Submodule.lean,Mathlib/LinearAlgebra/Basis/VectorSpace.lean,Mathlib/LinearAlgebra/BilinearForm/Hom.lean,Mathlib/LinearAlgebra/BilinearForm/Properties.lean,Mathlib/LinearAlgebra/Center.lean,Mathlib/LinearAlgebra/Coevaluation.lean,Mathlib/LinearAlgebra/Contraction.lean,Mathlib/LinearAlgebra/Determinant.lean,Mathlib/LinearAlgebra/Dimension/Constructions.lean,Mathlib/LinearAlgebra/Dual/Basis.lean,Mathlib/LinearAlgebra/Eigenspace/Zero.lean,Mathlib/LinearAlgebra/ExteriorPower/Basis.lean,Mathlib/LinearAlgebra/ExteriorPower/WedgePairing.lean,Mathlib/LinearAlgebra/Finsupp/VectorSpace.lean,Mathlib/LinearAlgebra/FreeModule/Norm.lean,Mathlib/LinearAlgebra/Matrix/Basis.lean,Mathlib/LinearAlgebra/Matrix/ToLin.lean,Mathlib/LinearAlgebra/PiTensorProduct/Dual.lean,Mathlib/LinearAlgebra/QuadraticForm/Basis.lean,Mathlib/LinearAlgebra/RootSystem/CartanMatrix.lean,Mathlib/LinearAlgebra/StdBasis.lean,Mathlib/LinearAlgebra/SymmetricAlgebra/Basis.lean,Mathlib/LinearAlgebra/TensorAlgebra/Basis.lean,Mathlib/LinearAlgebra/Trace.lean,Mathlib/LinearAlgebra/Transvection/Basic.lean,Mathlib/NumberTheory/NumberField/CanonicalEmbedding/Basic.lean,Mathlib/RepresentationTheory/Tannaka.lean,Mathlib/RingTheory/Extension/Cotangent/Basis.lean,Mathlib/RingTheory/Extension/Cotangent/LocalizationAway.lean,Mathlib/RingTheory/Flat/EquationalCriterion.lean,Mathlib/RingTheory/Ideal/Basis.lean,Mathlib/RingTheory/Ideal/Norm/AbsNorm.lean,Mathlib/RingTheory/Kaehler/JacobiZariski.lean,Mathlib/RingTheory/Localization/Module.lean,Mathlib/RingTheory/PowerBasis.lean,Mathlib/RingTheory/TensorProduct/Free.lean 49 2 ['github-actions'] nobody
0-64892
18 hours ago
1-17196
1 day ago
1-17141
1 day
0
46321 hzmsh
author:hzmsh
fix: add missing parentheses in `Repr` for `WithTop` and similar types - Before: the `Repr` instances for `WithBot`, `WithTop`, `WithOne`, `WithZero`, and `OnePoint` used `repr` on the inner value. For example, `-1` inside `WithBot ℤ` printed as `↑-1`, and `some 3` inside `WithTop (Option ℕ)` printed as `↑some 3`, which are not valid Lean syntax. - Change: replace `repr` with `reprArg` in all 5 instances, and add tests in `MathlibTest/WithTopRepr.lean`. - After: now those values print with parentheses as `↑(-1)` and `↑(some 3)` correctly. Fixes #45767. --- AI use: I used Claude (Opus 5.5 High) and Gemini (Carbon High) to locate the root cause and propose the solution. I have verified myself that the proposed solution is correct. LLM-generated new-contributor 30/5 Mathlib/Algebra/Group/WithOne/Defs.lean,Mathlib/Order/TypeTags.lean,Mathlib/Topology/Compactification/OnePoint/Basic.lean,MathlibTest/WithTopRepr.lean 4 3 ['github-actions', 'hzmsh'] nobody
0-63845
17 hours ago
0-66437
18 hours ago
0-66382
18 hours
0
46318 doge-th
author:doge-th
chore: rename rpow monotonicity lemmas Following #9095, #9235 and #18956, this renames the ambiguous rpow monotonicity lemma names in `Real`, `NNReal` and `ENNReal`, as requested in #13544 (the `rpow_le_rpow` part; @YaelDillies is working on the `zpow` one). The convention is the one established for `pow`/`zpow`: lemmas monotone in the base (the left argument of `^`) gain `_left`, lemmas monotone in the exponent gain `_right`, and iff-variants use the `_iff_left`/`_iff_right` infixes. Rename summary: - `rpow_le_rpow` → `rpow_le_rpow_left`, `rpow_lt_rpow` → `rpow_lt_rpow_left` (base varies) - `rpow_le_rpow_of_nonpos` → `rpow_le_rpow_left_of_nonpos`, `rpow_lt_rpow_of_neg` → `rpow_lt_rpow_left_of_neg` (antitone in base) - `rpow_le_rpow_iff` → `rpow_le_rpow_iff_left`, `rpow_lt_rpow_iff` → `rpow_lt_rpow_iff_left` (and the `_of_neg` variants likewise) - `rpow_le_rpow_of_exponent_le` → `rpow_le_rpow_right`, `rpow_lt_rpow_of_exponent_lt` → `rpow_lt_rpow_right` - `rpow_le_rpow_of_exponent_ge` → `rpow_le_rpow_right_of_le_one`, `rpow_lt_rpow_of_exponent_gt` → `rpow_lt_rpow_right_of_lt_one` (and the `'`/`of_imp` variants), matching `pow_le_pow_right_of_le_one'` and `pow_lt_pow_right_of_lt_one₀` - `rpow_le_rpow_left_iff` → `rpow_le_rpow_iff_right`, `rpow_lt_rpow_left_iff` → `rpow_lt_rpow_iff_right`, `rpow_le_rpow_left_iff_of_base_lt_one` → `rpow_le_rpow_iff_right_of_base_lt_one`, `rpow_lt_rpow_left_iff_of_base_lt_one` → `rpow_lt_rpow_iff_right_of_base_lt_one` — these varied the exponent, so keeping them under `_left_iff` would clash semantically with the new `_left` names All uses are updated (50 files, 225 occurrences) and `@[deprecated (since := "2026-11-22")] alias` entries are added for every old name in the three namespaces. Closes #13544 new-contributor 325/225 Mathlib/Algebra/Module/ZLattice/Summable.lean,Mathlib/Analysis/AbsoluteValue/Equivalence.lean,Mathlib/Analysis/Analytic/RadiusLiminf.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Order.lean,Mathlib/Analysis/CStarAlgebra/Multiplier.lean,Mathlib/Analysis/Complex/Hadamard.lean,Mathlib/Analysis/Complex/PhragmenLindelof.lean,Mathlib/Analysis/Distribution/SchwartzSpace/Basic.lean,Mathlib/Analysis/Distribution/TemperateGrowth.lean,Mathlib/Analysis/Fourier/PoissonSummation.lean,Mathlib/Analysis/FunctionalSpaces/SobolevInequality.lean,Mathlib/Analysis/Matrix/Normed.lean,Mathlib/Analysis/MeanInequalities.lean,Mathlib/Analysis/MeanInequalitiesPow.lean,Mathlib/Analysis/MellinTransform.lean,Mathlib/Analysis/Normed/Lp/lpSpace.lean,Mathlib/Analysis/Normed/Unbundled/SmoothingSeminorm.lean,Mathlib/Analysis/Normed/Unbundled/SpectralNorm.lean,Mathlib/Analysis/SpecialFunctions/ContinuousFunctionalCalculus/Rpow/Order.lean,Mathlib/Analysis/SpecialFunctions/ImproperIntegrals.lean,Mathlib/Analysis/SpecialFunctions/Integrability/Basic.lean,Mathlib/Analysis/SpecialFunctions/Log/Base.lean,Mathlib/Analysis/SpecialFunctions/Log/Monotone.lean,Mathlib/Analysis/SpecialFunctions/Pow/Asymptotics.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Analysis/SpecialFunctions/Pow/Real.lean,Mathlib/Analysis/SpecificLimits/FloorPow.lean,Mathlib/Combinatorics/Additive/AP/Three/Behrend.lean,Mathlib/Computability/AkraBazzi/GrowsPolynomially.lean,Mathlib/Computability/AkraBazzi/SumTransform.lean,Mathlib/MeasureTheory/Function/ConditionalExpectation/CondJensen.lean,Mathlib/MeasureTheory/Function/ContinuousMapDense.lean,Mathlib/MeasureTheory/Function/LpSeminorm/ChebyshevMarkov.lean,Mathlib/MeasureTheory/Function/LpSeminorm/Monotonicity.lean,Mathlib/MeasureTheory/Function/SimpleFuncDenseLp.lean,Mathlib/MeasureTheory/Function/UniformIntegrable.lean,Mathlib/MeasureTheory/Integral/IntegralEqImproper.lean,Mathlib/MeasureTheory/Measure/Hausdorff.lean,Mathlib/MeasureTheory/Measure/Lebesgue/VolumeOfBalls.lean,Mathlib/NumberTheory/Bertrand.lean,Mathlib/NumberTheory/Harmonic/EulerMascheroni.lean,Mathlib/NumberTheory/LSeries/PrimesInAP.lean,Mathlib/NumberTheory/ModularForms/EisensteinSeries/Summable.lean,Mathlib/NumberTheory/NumberField/CanonicalEmbedding/ConvexBody.lean,Mathlib/NumberTheory/NumberField/Discriminant/Basic.lean,Mathlib/NumberTheory/Ostrowski.lean,Mathlib/NumberTheory/SumPrimeReciprocals.lean,Mathlib/NumberTheory/Transcendental/Liouville/Measure.lean,Mathlib/RingTheory/Perfection.lean,Mathlib/Topology/MetricSpace/Snowflaking.lean 50 2 ['BoltonBailey', 'github-actions'] nobody
0-62716
17 hours ago
0-79483
22 hours ago
0-79428
22 hours
0
46179 eric-wieser
author:eric-wieser
feat(LinearAlgebra/Matrix/Nondegenerate): submatrix, conjTranspose, and op lemmas This adds `submatrix`, `conjTranspose`, and `map MulOpposite.op` lemmas for `SeparatingLeft`, `SeparatingRight`, and `Nondegenerate`. Many other lemmas are generalized in place from to `NonUnitalSemiring`. I claim the definition is nonsense in the non-associative case, so tighten it from `NonUnitalNonAssocSemiring` to `NonUnitalSemiring`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] --> - [x] depends on: #46184 t-algebra
label:t-algebra$
121/6 Mathlib/LinearAlgebra/Matrix/Nondegenerate.lean 1 7 ['eric-wieser', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'themathqueen'] nobody
0-61631
17 hours ago
2-77339
2 days ago
2-77284
2 days
0
45851 wrenna-robson
author:wrenna-robson
feat(GroupTheory): add the inner and outer automorphism groups Defines the inner automorphism group MulAut.inner G, the range of conjugation, and the outer automorphism group MulAut.Outer G, the quotient of the automorphism group by it. The basic API covers: - normality of the inner automorphisms; - the criteria for when the inner automorphisms are trivial (G commutative) and when they're everything (Out(G) trivial); - functoriality under group isomorphisms. Under this, `inner G` is the simp-normal form for `range conj`. We also add `ker_conj`, as a simp lemma, showing that the kernel is `center G`. it follows therefore that `inner G ≃* G/(center G)`. We don't give this explictly, however. A few general lemmas about conjugation and normal subgroups go in their natural upstream files. As part of this, Subgroup.Normal.conj_mem' is renamed to conj_inv_mem, and the old name is kept as a deprecated alias. 🤖 Written with the aid of [Claude Code](https://claude.com/claude-code) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated t-group-theory 200/10 Mathlib.lean,Mathlib/Algebra/Group/End.lean,Mathlib/Algebra/Group/Subgroup/Defs.lean,Mathlib/Algebra/Group/Subgroup/Lattice.lean,Mathlib/FieldTheory/Galois/Basic.lean,Mathlib/GroupTheory/GroupAction/Blocks.lean,Mathlib/GroupTheory/GroupAction/SubMulAction.lean,Mathlib/GroupTheory/InnerAutomorphism.lean,Mathlib/GroupTheory/OuterAutomorphism.lean,Mathlib/GroupTheory/Subgroup/Center.lean,Mathlib/RepresentationTheory/Homological/GroupCohomology/Functoriality.lean,Mathlib/RepresentationTheory/Invariants.lean,Mathlib/RingTheory/Invariant/Basic.lean,Mathlib/RingTheory/IsGaloisGroup/Basic.lean 14 33 ['github-actions', 'tb65536', 'vihdzp', 'wrenna-robson'] nobody
0-60946
16 hours ago
0-62491
17 hours ago
3-45651
3 days
0
46056 eric-wieser
author:eric-wieser
chore(Data/Matrix/Block): deprecate toSquareBlockProp and clean up nearby API Additionally this makes `toBlock` and `toSquareBlock` `abbrev`s, to avoid the need to duplicate the API for each one. One lemma about square blocks generalizes for free to `submatrix`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data maintainer-merge 89/63 Mathlib/Data/Matrix/Block.lean,Mathlib/LinearAlgebra/Matrix/Block.lean,Mathlib/LinearAlgebra/Matrix/Charpoly/Basic.lean,Mathlib/RingTheory/Norm/Transitivity.lean,Mathlib/Tactic/Hessenberg/Charpoly.lean 5 13 ['eric-wieser', 'github-actions', 'mathlib-merge-conflicts', 'themathqueen'] nobody
0-60611
16 hours ago
0-74849
20 hours ago
1-52066
1 day
1
46320 robertmaxton42
author:robertmaxton42
feat(Order/Hom/CompleteLattice): `CoframeHom`, as the `to_dual` of `FrameHom` Add `CoframeHom` as the `to_dual` of `FrameHom`; add `[to_dual]` related and derived `FrameHom` defs and lemmas. AI usage: Claude helped me find what needed to be `to_dual`ized to get the changes in `CompleteLattice.lean` to compile; in particular it wrote the changes to `Lattice.lean`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 61/17 Mathlib/Order/Hom/CompleteLattice.lean,Mathlib/Order/Hom/Lattice.lean 2 1 ['github-actions'] nobody
0-59906
16 hours ago
0-61560
17 hours ago
0-63332
17 hours
1
42667 gasparattila
author:gasparattila
chore: make `Set.inclusion` semireducible It is currently an abbrev, which confuses `fun_prop` due to dependent types in lemmas like `Topology.IsEmbedding.inclusion`. After this change, `fun_prop` will be able to prove goals like `IsEmbedding f → IsEmbedding (Set.inclusion h ∘ f)`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data increases-technical-debt 19/16 Mathlib/Algebra/Algebra/Subalgebra/Directed.lean,Mathlib/Combinatorics/Compactness.lean,Mathlib/Data/Set/Inclusion.lean,Mathlib/Data/Set/UnionLift.lean,Mathlib/Geometry/Manifold/Sheaf/Basic.lean,Mathlib/Logic/Equiv/Set.lean,Mathlib/ModelTheory/Fraisse.lean,Mathlib/ModelTheory/PartialEquiv.lean,Mathlib/ModelTheory/Substructures.lean,Mathlib/Order/CountableDenseLinearOrder.lean,Mathlib/Topology/Category/TopCat/Opens.lean,Mathlib/Topology/Covering/Basic.lean,Mathlib/Topology/UniformSpace/UniformEmbedding.lean 13 5 ['gasparattila', 'github-actions', 'mathlib-merge-conflicts', 'plp127'] nobody
0-58435
16 hours ago
0-60628
16 hours ago
99-61159
99 days
0
46008 SnirBroshi
author:SnirBroshi
feat(Order/CompactlyGenerated/Basic): `DirSupInacc (Ici a) ↔ IsCompactElement a` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 18/0 Mathlib/Order/CompactlyGenerated/Basic.lean 1 11 ['SnirBroshi', 'github-actions', 'mathlib-merge-conflicts', 'vihdzp'] nobody
0-55226
15 hours ago
1-2207
1 day ago
8-31736
8 days
0
45480 RFT-SIRM
author:RFT-SIRM
feat(Matrix): add ordered trace expansion for powers of sums ## Summary This PR adds a reusable ordered-word expansion for traces of powers of a sum of square matrices. - `Matrix.orderedWordExpansion A B p` lists products obtained by choosing either `A` or `B` at each of the `p` positions. - `Matrix.sum_orderedWordExpansion` proves that the list sums to `(A + B)^p`. - `Matrix.trace_orderedWordExpansion` gives the corresponding trace identity. The construction preserves the exact order of factors and retains repeated words with their full multiplicity. It does not assume that `A` and `B` commute or identify cyclically equivalent trace terms. ## Motivation For higher-moment trace identities, expanding `(A + B)^p` requires precise bookkeeping of ordered words before cyclic trace rotations and structural vanishing arguments can be applied. This generic expansion is useful for `p = 6` and for subsequent `p = 8, 10` developments without hard-coding a particular matrix model. This PR contains only general matrix-algebra lemmas. It does not include application-specific graph operators or claim to prove a particular moment recurrence. ## Verification The proofs use induction on `p`, right distributivity, and the existing `Matrix.trace_list_sum` theorem. Please run the full Mathlib build and style checks on this PR. t-algebra new-contributor LLM-generated
label:t-algebra$
40/0 Mathlib/LinearAlgebra/Matrix/Trace.lean 1 3 ['RFT-SIRM', 'github-actions'] nobody
0-54979
15 hours ago
23-65904
23 days ago
23-66757
23 days
0
46325 JoshuaR216
author:JoshuaR216
feat(Analysis/Calculus/LocalExtr/Polynomial): derivative of a real polynomial that splits also splits Add `Polynomial.Splits.derivative_of_real`: if `p : ℝ[X]` splits, then so does `p.derivative`. The proof is a counting argument from `Polynomial.card_roots_le_derivative` (Rolle's theorem), `Polynomial.card_roots'` and `Polynomial.natDegree_derivative_le`. --- Discussed on Zulip: [#Is there code for X? > derivative of a polynomial that splits over ℝ also splits @ 💬](https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/derivative.20of.20a.20polynomial.20that.20splits.20over.20.E2.84.9D.20also.20splits/near/642560961) As suggested there by Artie Khovanov, this is stated for ℝ for now; it can be generalised to real closed fields once the intermediate value theorem for them is in Mathlib. AI disclosure: The proof was written with help from Claude. I've checked that I understand each step, and it compiles with no `sorry`. t-analysis new-contributor LLM-generated 16/0 Mathlib/Analysis/Calculus/LocalExtr/Polynomial.lean 1 6 ['github-actions', 'vihdzp'] nobody
0-54657
15 hours ago
0-56844
15 hours ago
0-56789
15 hours
0
44145 Rida-Hamadani
author:Rida-Hamadani
feat(Analysis): translations preserve harmonicity also proves that translations preserves `C^n` regularity. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis 89/1 Mathlib/Analysis/Calculus/ContDiff/Operations.lean,Mathlib/Analysis/InnerProductSpace/Harmonic/Basic.lean,Mathlib/Analysis/InnerProductSpace/Laplacian.lean 3 9 ['Rida-Hamadani', 'github-actions', 'j-loreaux', 'mcdoll', 'themathqueen'] ADedecker
assignee:ADedecker
0-51257
14 hours ago
1-3525
1 day ago
57-11237
57 days
0
46208 JovanGerb
author:JovanGerb
chore(CategoryTheory/Limits/Shapes/Pullback): use `to_dual` This PR uses `to_dual` for `Pullback`. - This requires putting `(relevant_arg := _)` on `WidePullbackShape`, because it needs to be translated no matter what the argument `J` is (in this case it is `WalkingPair`). - `simps!` is removed from `pullback.congrHom` and written out manually instead to make it easier to use `to_dual`. - The definition of `pullback.congrHom`/`pushout.congrHom` is modified so that both projections can be generated by `simps`. - `hasPushouts_symmetry_of_hasPushoutsAlong` was misnamed (it has an `s` too many). Instead of replacing it with the correct name, I've deprecated it and its dual entirely, as they can be directly replaced by `hasPushout_symmetry`/`hasPullback_symmetry` respectively. I also added a `TODO` at `hasPullback_symmetry` to consider making it a global instance (it would be a loopy instance, but lean4 should handle this perfectly fine). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-category-theory 303/945 Mathlib/CategoryTheory/Limits/Shapes/Opposites/Pullbacks.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/Cospan.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/HasPullback.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/IsPullback/Basic.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/IsPullback/BicartesianSq.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/Pasting.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/PullbackCone.lean,Mathlib/CategoryTheory/Limits/Shapes/WidePullbacks.lean,Mathlib/CategoryTheory/MorphismProperty/Limits.lean,Mathlib/CategoryTheory/MorphismProperty/OverAdjunction.lean,Mathlib/CategoryTheory/SmallObject/Construction.lean 11 2 ['github-actions', 'mathlib-merge-conflicts'] robin-carlier
assignee:robin-carlier
0-51256
14 hours ago
1-39055
1 day ago
1-41641
1 day
0
46330 robertmaxton42
author:robertmaxton42
feat(CategoryTheory/LiftingProperties): notation and lifts along whiskered squares * Registers the suggestive infix notation `i ⧄ p` for `HasLiftingProperty i p`, as suggested [by nLab](https://ncatlab.org/nlab/show/separation+axioms+in+terms+of+lifting+properties). * Adds it to the permitted Unicode list. * Several convenience lemmas about moving/factoring isos through various arms of a `CommSq` * Several matching lemmas/defs for `HasLift` and `LiftStruct`s interacting with isos and other commutative squares/homs in `Arrow C` AI was used to assemble this PR from existing code. This PR otherwise contains no AI-generated code. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> 175/1 Mathlib/CategoryTheory/CommSq.lean,Mathlib/CategoryTheory/LiftingProperties/Basic.lean,Mathlib/Tactic/Linter/TextBased/UnicodeLinter.lean 3 2 ['github-actions'] nobody
0-51093
14 hours ago
0-52060
14 hours ago
0-52005
14 hours
0
46331 vihdzp
author:vihdzp
chore(Topology/Order/Cadlag): add missing `to_additive` attributes Due to a current limitation of the tactics, `to_additive (attr := to_dual)` does not link the order dualized theorems via `to_additive`. These attributes have to be added manually. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology t-order 9/1 Mathlib/Topology/Order/Cadlag.lean 1 1 ['github-actions'] nobody
0-50577
14 hours ago
0-51316
14 hours ago
0-51261
14 hours
0
44822 William7743
author:William7743
feat(Geometry/Euclidean/Inversion): affine limits and filter identities Adds filter-level limit and continuity lemmas for `EuclideanGeometry.inversion` in `Geometry/Euclidean/Inversion/Basic.lean`: * `not_continuousAt_inversion_center_of_neBot` — nonzero-radius inversion is discontinuous at a non-isolated center (`[NeBot (𝓝[≠] c)]`). * `continuousAt_inversion_iff` — inversion is continuous at `x` iff `x ≠ c ∨ R = 0`. * `tendsto_inversion_cobounded_nhds_center` / `tendsto_inversion_cobounded_nhdsNE_center` — as the argument tends to infinity, inversion tends to the center, resp. its punctured neighborhood for nonzero radius. * `map_inversion_cobounded` / `map_inversion_nhdsNE_center` — for nonzero radius, inversion pushes the cobounded filter exactly to `𝓝[≠] c` and back, via its involutivity. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-euclidean-geometry LLM-generated new-contributor 53/0 Mathlib/Geometry/Euclidean/Inversion/Basic.lean 1 6 ['SnirBroshi', 'William7743', 'github-actions'] nobody
0-50354
13 hours ago
22-33896
22 days ago
22-36506
22 days
0
45042 YaelDillies
author:YaelDillies
feat(Util/Notation3): don't try matching tactic blocks This means that `notation3` can e.g. be used to create a delaborator for concrete cycle notation `c[...]` whereas previously it would fail due to the `by decide` in the expansion. This is best effort, in the sense that eluding a proof in pretty-printing is necessarily a loss, unless we somehow run the tactic block while pretty-printing to determine whether the proof could have come from the tactic or had been hand-provided by the user. Remove the `(prettyPrint := false)` flag in concrete cycle notation and the application of `Cycle.nodup_coe_iff` in the default proof term: the decidability instance applies it automatically anyway. Generated by Claude Opus, hand-edited by myself afterwards. Assisted-by: Claude Opus 5.5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated t-meta 29/15 Mathlib/GroupTheory/Perm/Cycle/Concrete.lean,Mathlib/Util/Notation3.lean,MathlibTest/Util/Notation3.lean 3 3 ['JovanGerb', 'YaelDillies', 'github-actions'] nobody
0-50353
13 hours ago
34-1932
34 days ago
34-1877
34 days
0
46324 robertmaxton42
author:robertmaxton42
feat(CategoryTheory): add typeclasses and API for chosen (co)representing objects * Add the typeclasses `ChosenRepresentation` and `ChosenCorepresentation` following the similar chosen-limits design, carrying the data of a choice of (co)-representing objects and a natural choice of morphism for every element. * Add API paralleling `CategoryTheory.homOfElement` for convenient use of chosen (co)-representing objects to generate morphisms. * In particular, add API for the specific case of `ConcreteCategory` and its spellings of `(forget C).obj`, `(forget C).map`, etc. * Add the motivating example in `TopCat`. AI was used to help organize the PR once complete. The PR otherwise contains no AI-generated code. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated 257/2 Mathlib.lean,Mathlib/CategoryTheory/ChosenRepresentation.lean,Mathlib/CategoryTheory/ConcreteCategory/Representable.lean,Mathlib/Topology/Category/TopCat/Basic.lean 4 2 ['github-actions', 'joelriou', 'robertmaxton42'] nobody
0-44803
12 hours ago
0-53169
14 hours ago
0-54293
15 hours
1
46311 emlis42
author:emlis42
feat(Tactic/Inclusion): add div and inv support to the `dyadic_interval` tactic This PR adds div and inv extension for the `dyadic_interval` tactic. --- The interval part (`divBound`, `.*map_divBound.*`, `div`, `div_mem`) is adapted from David Ledvinka's branch [DavidLedvinka/mathlib4#inclusion-division](https://github.com/DavidLedvinka/mathlib4/tree/inclusion-division). t-meta 223/1 Mathlib.lean,Mathlib/Tactic.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Division.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Tactic.lean,MathlibTest/Tactic/Inclusion/Basic.lean 5 1 ['github-actions'] nobody
0-42827
11 hours ago
1-5978
1 day ago
1-5923
1 day
1
46332 vihdzp
author:vihdzp
chore(Algebra/Order/Group/Lattice): use `to_dual` Due to a current limitation of the tactics, `to_dual (attr := to_additive)` does not link the order dualized theorems via `to_dual`. These attributes have to be added manually. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
30/34 Mathlib/Algebra/Order/Group/Lattice.lean,Mathlib/Algebra/Order/Group/Unbundled/Abs.lean,Mathlib/Algebra/Order/Monoid/Unbundled/Pow.lean,Mathlib/RingTheory/UniqueFactorizationDomain/GCDMonoid.lean 4 1 ['github-actions'] nobody
0-39708
11 hours ago
0-42543
11 hours ago
0-43247
12 hours
0
45826 Parcly-Taxel
author:Parcly-Taxel
refactor: `Lex/Colex` as one-field structures Redefine ```lean structure Lex (α : Sort*) where /-- Equip a type with its lexicographic order. -/ toLex :: /-- The underlying element -/ ofLex : α ``` and similarly for `Colex`. Several rounds of Codex were used to repair some (but not all) of the proofs. t-order tech debt LLM-generated 1184/1076 Counterexamples/MapFloor.lean,Counterexamples/SeparableNotSecondCountable.lean,Counterexamples/ZeroDivisorsInAddMonoidAlgebras.lean,Mathlib/Algebra/CharP/Synonym.lean,Mathlib/Algebra/Field/Basic.lean,Mathlib/Algebra/MvPolynomial/SchwartzZippel.lean,Mathlib/Algebra/MvPolynomial/Variables.lean,Mathlib/Algebra/Order/Group/Action/Synonym.lean,Mathlib/Algebra/Order/Group/Equiv.lean,Mathlib/Algebra/Order/Group/PiLex.lean,Mathlib/Algebra/Order/Group/Synonym.lean,Mathlib/Algebra/Order/GroupWithZero/Action/Synonym.lean,Mathlib/Algebra/Order/GroupWithZero/Lex.lean,Mathlib/Algebra/Order/GroupWithZero/Synonym.lean,Mathlib/Algebra/Order/Module/Equiv.lean,Mathlib/Algebra/Order/Module/HahnEmbedding.lean,Mathlib/Algebra/Order/Module/Synonym.lean,Mathlib/Algebra/Order/Monoid/Lex.lean,Mathlib/Algebra/Order/Rearrangement.lean,Mathlib/Algebra/Order/Ring/Synonym.lean,Mathlib/Algebra/Vertex/HVertexOperator.lean,Mathlib/Analysis/Calculus/ContDiffHolder/Pointwise.lean,Mathlib/Combinatorics/Colex.lean,Mathlib/Combinatorics/SetFamily/KruskalKatona.lean,Mathlib/Data/DFinsupp/Lex.lean,Mathlib/Data/DFinsupp/WellFounded.lean,Mathlib/Data/Fin/Tuple/BubbleSortInduction.lean,Mathlib/Data/Fin/Tuple/Sort.lean,Mathlib/Data/Finsupp/Lex.lean,Mathlib/Data/Finsupp/MonomialOrder.lean,Mathlib/Data/Finsupp/MonomialOrder/DegLex.lean,Mathlib/Data/Finsupp/WellFounded.lean,Mathlib/Data/Fintype/Card.lean,Mathlib/Data/Fintype/Defs.lean,Mathlib/Data/Sum/Interval.lean,Mathlib/Order/CompleteLattice/PiLex.lean,Mathlib/Order/Extension/Well.lean,Mathlib/Order/Hom/Lex.lean,Mathlib/Order/Interval/Finset/Gaps.lean,Mathlib/Order/Interval/Lex.lean,Mathlib/Order/Lex.lean,Mathlib/Order/PSigma.lean,Mathlib/Order/PiLex.lean,Mathlib/Order/Prod/Lex/Basic.lean,Mathlib/Order/Prod/Lex/Hom.lean,Mathlib/Order/Sigma.lean,Mathlib/Order/Sum/Lattice.lean,Mathlib/Order/Sum/Order.lean,Mathlib/Order/WellFoundedSet.lean,Mathlib/RingTheory/HahnSeries/Basic.lean,Mathlib/RingTheory/HahnSeries/HahnEmbedding.lean,Mathlib/RingTheory/HahnSeries/Lex.lean,Mathlib/RingTheory/MvPolynomial/Symmetric/FundamentalTheorem.lean,Mathlib/RingTheory/MvPowerSeries/LexOrder.lean,Mathlib/RingTheory/Spectrum/Prime/ChevalleyComplexity.lean,Mathlib/SetTheory/Cardinal/Arithmetic.lean,Mathlib/SetTheory/Ordinal/Arithmetic.lean,Mathlib/SetTheory/Ordinal/Basic.lean,Mathlib/Topology/Order/Completion.lean,MathlibTest/NonemptyIntervalLex.lean 60 32 ['Parcly-Taxel', 'github-actions', 'mathlib-merge-conflicts', 'vihdzp'] nobody
0-39395
10 hours ago
4-12062
4 days ago
10-45604
10 days
0
46334 urkud
author:urkud
refactor(MeasureTheory): merge `finiteSpanningSetsInOpen` and `finiteSpanningSetsInOpen'` Merge `Measure.finiteSpanningSetsInOpen` (σ-compact spaces) and `Measure.finiteSpanningSetsInOpen'` (second countable spaces) into a single definition assuming `LindelofSpace`, whose sequence is monotone by construction (`Measure.monotone_finiteSpanningSetsInOpen`). The primed version is deprecated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability 38/59 Mathlib/MeasureTheory/Covering/Differentiation.lean,Mathlib/MeasureTheory/Measure/Regular.lean,Mathlib/MeasureTheory/Measure/Typeclasses/Finite.lean 3 1 ['github-actions'] nobody
0-38042
10 hours ago
0-38902
10 hours ago
0-38847
10 hours
4
41802 tb65536
author:tb65536
feat(Combinatorics/Design/Defs): definitions of Steiner systems This PR adds the definition of Steiner systems. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #41823 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics 78/0 Mathlib/Combinatorics/Design/Defs.lean,Mathlib/Data/Set/Card.lean 2 8 ['Parcly-Taxel', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'tb65536'] nobody
0-27562
7 hours ago
9-80138
9 days ago
9-80084
9 days
0
46051 xroblot
author:xroblot
feat(FieldTheory/LinearDisjoint): degrees of the compositum and intersection with a Galois extension If `A / F` is a finite Galois extension and `B` is an intermediate field, this PR shows that the relative degree of `A ⊔ B` over `A` is the degree of `B` over `A ⊓ B`. As a consequence, if `A / F` is Galois, the product of the degrees of `A ⊔ B` and `A ⊓ B` over `F` is the product of the degrees of `A` and `B` over `F`. In order to allow `B` to be infinite over `F` in this proof, the finiteness assumption on `B` is removed from `IntermediateField.LinearDisjoint.of_inf_eq_bot`, and the `finrank` versions of the degree formulas for linearly disjoint fields are proved without algebraicity assumptions. Some supporting API on `IntermediateField.extendScalars` and on the compositum is added along the way. The two instances `IsScalarTower F (K₁ ⊓ K₂) K₁` and `IsScalarTower F (K₁ ⊓ K₂) K₂` are also added. Without them, these towers can only be found through unfolding the `Algebra (K₁ ⊓ K₂) K₁` construction and thus they fail to synthesize unless `backward.isDefEq.respectTransparency` is set to `false`. :robot: This result is used in the proof of Stickelberger's theorem in #46022. It was extracted by Claude from the [SKW project](https://github.com/xroblot/SKW). t-algebra
label:t-algebra$
115/10 Mathlib/FieldTheory/IntermediateField/Adjoin/Basic.lean,Mathlib/FieldTheory/IntermediateField/Adjoin/Defs.lean,Mathlib/FieldTheory/IntermediateField/Basic.lean,Mathlib/FieldTheory/LinearDisjoint.lean 4 3 ['github-actions', 'leanprover-radar', 'xroblot'] nobody
0-25453
7 hours ago
0-26095
7 hours ago
5-15857
5 days
1
45423 kebekus
author:kebekus
feat(Analysis/Meromorphic): characterize meromorphic functions vanishing along `codiscreteWithin` This PR characterizes the meromorphic functions on `U` whose germ along `Filter.codiscreteWithin U` is zero, and adds a connectedness-free version of `MeromorphicOn.mul_inv_eventuallyEq`. These results are the ingredients needed to show that germs of meromorphic functions along `codiscreteWithin U` form a field when `U` is connected — the zero germ is exactly the class of functions of infinite order, and every other germ is invertible via the pointwise inverse. That construction will follow in a later PR. This material is used in [Project VD](https://github.com/kebekus/ProjectVD), formalizing Value Distribution Theory for meromorphic functions on the complex plane. Claude Code was used to create this PR. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis LLM-generated 54/10 Mathlib/Analysis/Meromorphic/IsolatedZeros.lean,Mathlib/Analysis/Meromorphic/Order.lean 2 1 ['github-actions'] nobody
0-22284
6 hours ago
24-33152
24 days ago
24-33097
24 days
0
43985 kebekus
author:kebekus
feat: API for working with canonical factors To prepare for upcoming work in Value Distribution Theory, add three elementary lemmas on canonical factors and their derivatives. This material is used in [Project VD](https://github.com/kebekus/ProjectVD), formalizing Value Distribution Theory for meromorphic functions on the complex plane. Claude Code was used to create this PR. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis LLM-generated 89/2 Mathlib/Analysis/Complex/CanonicalDecomposition.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
0-22255
6 hours ago
2-77477
2 days ago
62-85254
62 days
0
44629 kebekus
author:kebekus
feat: behavior of order in polymomial expressions of meromorphic functions Establish standard formulae for the behavior of order in finite sums and polynomial expressions of meromorphic functions. This material is used in [Project VD](https://github.com/kebekus/ProjectVD), formalizing Value Distribution Theory for meromorphic functions on the complex plane. Claude Code was used to create this PR. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis LLM-generated 223/0 Mathlib/Analysis/Meromorphic/Divisor.lean,Mathlib/Analysis/Meromorphic/Order.lean 2 1 ['github-actions'] nobody
0-22217
6 hours ago
2-77495
2 days ago
45-15832
45 days
0
44428 kebekus
author:kebekus
feat: behavior of zero/pole divisors of meromorphic functions under differentiation Relate the divisor of `deriv f` to the divisor of a meromorphic function `f`, and deduce the corresponding statements for the logarithmic counting functions of Value Distribution Theory. This material is used in [Project VD](https://github.com/kebekus/ProjectVD), formalizing Value Distribution Theory for meromorphic functions on the complex plane. Claude Code was used to create this PR. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis LLM-generated 152/0 Mathlib/Analysis/Complex/ValueDistribution/LogCounting/Truncated.lean,Mathlib/Analysis/Meromorphic/Divisor.lean,Mathlib/Analysis/Meromorphic/Order.lean 3 1 ['github-actions'] nobody
0-22201
6 hours ago
2-77487
2 days ago
49-65510
49 days
0
45841 GoldenPhysicsProject
author:GoldenPhysicsProject
feat: the adele ring of ℚ is ℝ × the finite adele ring This PR identifies the adele ring of `ℚ` with `ℝ × FiniteAdeleRing ℤ ℚ`, and adds a general `ContinuousAlgEquiv.prodCongr` to support it. In `Mathlib/Topology/Algebra/Algebra/Equiv.lean`: * `ContinuousAlgEquiv.prodCongr (e : A ≃A[R] B) (e' : C ≃A[R] D) : (A × C) ≃A[R] (B × D)`, the product of two continuous algebra equivalences, with the simp lemmas `prodCongr_toAlgEquiv`, `prodCongr_toHomeomorph`, `prodCongr_apply` and `prodCongr_symm`. In `Mathlib/NumberTheory/NumberField/AdeleRing.lean`: * `Rat.InfiniteAdeleRing.continuousAlgEquivReal : InfiniteAdeleRing ℚ ≃A[ℚ] ℝ` — `ℚ` has a single infinite place, and it is real, so the infinite adele ring is a one-factor product with factor `ℝ`; * `Rat.AdeleRing.continuousAlgEquivProd : AdeleRing ℤ ℚ ≃A[ℚ] ℝ × FiniteAdeleRing ℤ ℚ`, defined as `ContinuousAlgEquiv.prodCongr continuousAlgEquivReal (ContinuousAlgEquiv.refl _ _)`; * `Rat.AdeleRing.continuousAlgEquivProd_algebraMap`: the diagonal embedding `ℚ → 𝔸_ℚ` is `q ↦ (q, (q)_p)` under this identification. t-number-theory new-contributor LLM-generated 76/0 Mathlib/NumberTheory/NumberField/AdeleRing.lean,Mathlib/Topology/Algebra/Algebra/Equiv.lean 2 17 ['GoldenPhysicsProject', 'MichaelStollBayreuth', 'github-actions', 'tb65536', 'xroblot'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
0-17625
4 hours ago
0-17625
4 hours ago
9-86312
9 days
0
46043 EtienneC30
author:EtienneC30
refactor: make `WithTop` and `WithBot` inductive types Some points to notice: - The order on `WithZero` given by [WithZero.le](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/GroupWithZero/Canonical.html#WithZero.le) is defined through defeq with `WithBot`, which no longer holds. Thus this PR also makes `WithZero` an inductive type and transfers the order through an equivalence passing through `Option`. - In `Mathlib.Order.Hom.WithTopBot` file, I can't make the lemmas generated by `simps!` for `withTop'` and `withBot'` dual to each other, while they are currently. I don't really understand what is going on. Declarations deleted without deprecation: - [WithBot.some_eq_coe](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Order/WithBot.html#WithBot.some_eq_coe), [WithTop.some_eq_coe](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Order/WithBot.html#WithTop.some_eq_coe): those are now syntactic equalities. - [WithTop.mul_coe_eq_bind](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/Ring/WithTop.html#WithTop.mul_coe_eq_bind), [WithBot.mul_coe_eq_bind](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/Ring/WithTop.html#WithBot.mul_coe_eq_bind) - [WithTop.coe_mul_eq_bind](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/Ring/WithTop.html#WithTop.coe_mul_eq_bind), [WithBot.coe_mul_eq_bind](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/Ring/WithTop.html#WithBot.coe_mul_eq_bind) - [WithOne.instMonad](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Group/WithOne/Defs.html#WithOne.instMonad), [WithZero.instMonad](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Group/WithOne/Defs.html#WithZero.instMonad) Zulip thread: https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/Identity.20equivalence.20between.20WithTop.2FWithBot.20and.20Option/with/639616431 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> large-import tech debt t-order 1133/964 Archive/RiemannStieltjes.lean,Counterexamples/HomogeneousPrimeNotPrime.lean,Mathlib/Algebra/Group/WithOne/Basic.lean,Mathlib/Algebra/Group/WithOne/Defs.lean,Mathlib/Algebra/Group/WithOne/Map.lean,Mathlib/Algebra/GroupWithZero/Range.lean,Mathlib/Algebra/GroupWithZero/WithZero.lean,Mathlib/Algebra/Order/GroupWithZero/Canonical.lean,Mathlib/Algebra/Order/Interval/Basic.lean,Mathlib/Algebra/Order/Monoid/ToMulBot.lean,Mathlib/Algebra/Order/Monoid/Unbundled/WithTop.lean,Mathlib/Algebra/Order/Ring/WithTop.lean,Mathlib/Algebra/Polynomial/BigOperators.lean,Mathlib/Algebra/Polynomial/Degree/Defs.lean,Mathlib/Algebra/Polynomial/Degree/Operations.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Affine/Point.lean,Mathlib/Analysis/BoxIntegral/Box/Basic.lean,Mathlib/Analysis/BoxIntegral/Partition/Additive.lean,Mathlib/Analysis/BoxIntegral/Partition/Basic.lean,Mathlib/Analysis/BoxIntegral/Partition/Split.lean,Mathlib/Analysis/Convex/Combination.lean,Mathlib/Analysis/Convex/Jensen.lean,Mathlib/Analysis/Meromorphic/Order.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Basic/Countable/Basic.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/CategoryTheory/Presentable/CardinalDirectedPoset.lean,Mathlib/Combinatorics/SetFamily/AhlswedeZhang.lean,Mathlib/Data/ENat/Defs.lean,Mathlib/Data/ENat/Pow.lean,Mathlib/Data/Finset/Lattice/Fold.lean,Mathlib/Data/Finset/Lattice/Union.lean,Mathlib/Data/Finset/Max.lean,Mathlib/Data/Finset/NAry.lean,Mathlib/Data/Fintype/WithTopBot.lean,Mathlib/Data/Int/WithZero.lean,Mathlib/Data/List/MinMax.lean,Mathlib/Data/Ordmap/Invariants.lean,Mathlib/Data/Ordmap/Ordset.lean,Mathlib/GroupTheory/ArchimedeanDensely.lean,Mathlib/MeasureTheory/Constructions/BorelSpace/Real.lean,Mathlib/MeasureTheory/Constructions/BorelSpace/WithTop.lean,Mathlib/MeasureTheory/Group/Measure.lean,Mathlib/MeasureTheory/MeasurableSpace/Constructions.lean,Mathlib/Order/Category/BddLat.lean,Mathlib/Order/ConditionallyCompleteLattice/WithTop.lean,Mathlib/Order/Hom/WithTopBot.lean,Mathlib/Order/Interval/Basic.lean,Mathlib/Order/Interval/Finset/Defs.lean,Mathlib/Order/KrullDimension.lean,Mathlib/Order/Set.lean,Mathlib/Order/SuccPred/Basic.lean,Mathlib/Order/Sum/Order.lean,Mathlib/Order/TypeTags.lean,Mathlib/Order/WithBot.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Completion.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Valuation.lean,Mathlib/RingTheory/DiscreteValuationRing/Basic.lean,Mathlib/RingTheory/MvPowerSeries/LexOrder.lean,Mathlib/RingTheory/OrderOfVanishing/Basic.lean,Mathlib/RingTheory/OrderOfVanishing/Noetherian.lean,Mathlib/RingTheory/Polynomial/Resultant/Basic.lean,Mathlib/RingTheory/UniqueFactorizationDomain/FactorSet.lean,Mathlib/RingTheory/Valuation/Discrete/IsDiscreteValuationRing.lean,Mathlib/Tactic/Echelon/Reflection.lean,Mathlib/Tactic/Inclusion/Extension/Interval/Basic.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/BinarySplit.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Exp.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Log.lean,Mathlib/Tactic/Inclusion/Extension/IntervalInt/BinarySplit.lean,Mathlib/Topology/Algebra/Valued/WithVal.lean,Mathlib/Topology/Compactification/OnePoint/Basic.lean,Mathlib/Topology/EMetricSpace/Defs.lean,Mathlib/Topology/EMetricSpace/Weak.lean,Mathlib/Topology/Instances/ENNReal/Lemmas.lean,Mathlib/Topology/Order/Lattice.lean,MathlibTest/DifferentialGeometry/Notation/Basic.lean 77 13 ['EtienneC30', 'eric-wieser', 'github-actions', 'mathlib-merge-conflicts', 'plp127', 'vihdzp'] nobody
0-15329
4 hours ago
0-17091
4 hours ago
3-62283
3 days
0
42966 SnirBroshi
author:SnirBroshi
feat(Combinatorics/SimpleGraph/Hasse): smaller path graphs are contained in bigger ones --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics maintainer-merge 34/2 Mathlib/Combinatorics/SimpleGraph/Hasse.lean 1 14 ['SnirBroshi', 'YaelDillies', 'b-mehta', 'github-actions', 'mathlib-merge-conflicts'] nobody
0-10258
2 hours ago
1-80095
1 day ago
87-45460
87 days
0
38751 YaelDillies
author:YaelDillies
feat(Data/Finset/Density): more `NNRat.cast` lemmas From AddCombi --- - [x] depends on: #38716 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra large-import
label:t-algebra$
40/17 Mathlib/Data/Finset/Density.lean 1 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
0-8602
2 hours ago
0-9561
2 hours ago
26-80968
26 days
1
45896 YaelDillies
author:YaelDillies
feat(Tactic): `forallImpEq`, the dual simproc to `existsAndEq` It is useful to eliminate equalities under existential quantifiers but there is no finite set of simp lemmas that do it always, and instead the simproc `existsAndEq` does the job. Such a simproc was missing for the dual goal of eliminating equalities under binders. This PR adds it and uses it where possible. Assisted-by: Claude Opus 5.5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated t-meta maintainer-merge 246/52 Counterexamples/ZeroDivisorsInAddMonoidAlgebras.lean,Mathlib/Algebra/BigOperators/Associated.lean,Mathlib/Algebra/BigOperators/Group/Finset/Piecewise.lean,Mathlib/Algebra/MonoidAlgebra/Defs.lean,Mathlib/Algebra/MvPolynomial/Basic.lean,Mathlib/Algebra/Order/Monoid/Lex.lean,Mathlib/Analysis/Calculus/TangentCone/Defs.lean,Mathlib/Analysis/InnerProductSpace/Orthogonal.lean,Mathlib/Combinatorics/Additive/Convolution.lean,Mathlib/Combinatorics/Additive/Corner/Roth.lean,Mathlib/Data/Finset/NoncommProd.lean,Mathlib/Data/Finsupp/Basic.lean,Mathlib/Data/Finsupp/Weight.lean,Mathlib/Data/List/Basic.lean,Mathlib/Data/Matrix/Basis.lean,Mathlib/Data/Matrix/PEquiv.lean,Mathlib/Data/Multiset/Fintype.lean,Mathlib/Data/Sym/Sym2.lean,Mathlib/GroupTheory/OrderOfElement.lean,Mathlib/LinearAlgebra/Matrix/PosDef.lean,Mathlib/MeasureTheory/MeasurableSpace/Constructions.lean,Mathlib/NumberTheory/Chebyshev.lean,Mathlib/NumberTheory/Divisors.lean,Mathlib/NumberTheory/Harmonic/ZetaAsymp.lean,Mathlib/Order/Filter/Defs.lean,Mathlib/RingTheory/MvPolynomial/Groebner.lean,Mathlib/RingTheory/PowerSeries/Substitution.lean,Mathlib/RingTheory/Spectrum/Prime/ChevalleyComplexity.lean,Mathlib/SetTheory/ZFC/Class.lean,Mathlib/Tactic/Simproc/ExistsAndEq.lean,Mathlib/Topology/Algebra/IsOpenUnits.lean,Mathlib/Topology/CompactOpen.lean,Mathlib/Topology/Instances/Real/Lemmas.lean,Mathlib/Topology/MetricSpace/UniformConvergence.lean,MathlibTest/Simproc/ExistsAndEq.lean 35 10 ['SnirBroshi', 'YaelDillies', 'github-actions', 'joneugster', 'leanprover-radar', 'mathlib-merge-conflicts'] joneugster
assignee:joneugster
0-8298
2 hours ago
2-25960
2 days ago
9-35819
9 days
0
45422 YaelDillies
author:YaelDillies
feat(Algebra): characterise associatedness in `WithZero` --- - [x] depends on: #45245 t-algebra large-import
label:t-algebra$
30/8 Mathlib/Algebra/GroupWithZero/WithZero.lean 1 6 ['YaelDillies', 'github-actions', 'mathlib-dependent-issues', 'tb65536'] nobody
0-8150
2 hours ago
4-70749
4 days ago
4-73188
4 days
1
45677 fbarroero
author:fbarroero
feat(RingTheory/ClassGroup): when the class group is torsion ideals have some power that is principal Add `ClassGroup.exists_pow_eq_span_singleton`: if the class group of a Dedekind domain `R` is torsion, then every ideal `I` of `R` has a nonzero power `I ^ n` that is principal. Use it to shorten the proof of `IsDedekindDomain.exists_mul_algebraMap_eq_algebraMap` in `Mathlib/RingTheory/DedekindDomain/SInteger.lean`. --- Follow-up to #40848, as suggested by @xroblot in review. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory 26/9 Mathlib/RingTheory/ClassGroup/Basic.lean,Mathlib/RingTheory/DedekindDomain/SInteger.lean 2 6 ['github-actions', 'xroblot'] riccardobrasca
assignee:riccardobrasca
0-7171
1 hour ago
3-17922
3 days ago
17-52832
17 days
0
45250 YaelDillies
author:YaelDillies
refactor(Order): generalise the `CompleteLattice` instance on `WithTop` We used to have two conflicting instances of `CompleteLattice (WithTop <| WithBot α)` from `CompleteLattice α`: one going through `ConditionallyCompleteLattice α` and adding the top and bottom elements simultaneously, and another one adding them one by one by first going through `CompleteLattice (WithBot α)`. These didn't agree because `sSup ∅` on `WithTop α` would be defined as a junk value even if `α` already happened to have a bottom element. Changing `sSup ∅` on `WithTop α` to be a bottom element if one exists leads to a better solution: have an instance deducing `ConditionallyCompleteLattice (WithTop α)` from `ConditionallyCompleteLattice α`, and another one deducing `CompleteLattice (WithTop α)` from `ConditionallyCompleteLattice α` + `OrderBot α`, and similarly for `WithBot`. This is strictly more general than the previous instances, and avoids the diamond. Note that, since this PR was opened, the diamond was removed in #45406. --- - [x] depends on: #45406 t-order 98/73 Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Data/ENat/Lattice.lean,Mathlib/Dynamics/TopologicalEntropy/NetEntropy.lean,Mathlib/Order/ConditionallyCompleteLattice/WithTop.lean 4 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] Komyyy
assignee:Komyyy
0-6377
1 hour ago
4-3865
4 days ago
23-26654
23 days
1
45651 YaelDillies
author:YaelDillies
chore(Algebra/Polynomial): replace `Polynomial.sum` by `Finsupp.sum` Summing over a polynomial is not a mathematical concept. Generated by Claude Sonnet in several rounds of reviews by myself. Assisted-by: Claude Sonnet 5.5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra LLM-generated
label:t-algebra$
449/490 Archive/Wiedijk100Theorems/AbelRuffini.lean,Counterexamples/Cyclotomic105.lean,Counterexamples/MonicNonRegular.lean,Mathlib/Algebra/Lie/CartanExists.lean,Mathlib/Algebra/Polynomial/AlgebraMap.lean,Mathlib/Algebra/Polynomial/Basic.lean,Mathlib/Algebra/Polynomial/Bivariate.lean,Mathlib/Algebra/Polynomial/Coeff.lean,Mathlib/Algebra/Polynomial/CoeffMem.lean,Mathlib/Algebra/Polynomial/Degree/Lemmas.lean,Mathlib/Algebra/Polynomial/Degree/Operations.lean,Mathlib/Algebra/Polynomial/Degree/Support.lean,Mathlib/Algebra/Polynomial/Degree/TrailingDegree.lean,Mathlib/Algebra/Polynomial/Derivative.lean,Mathlib/Algebra/Polynomial/Div.lean,Mathlib/Algebra/Polynomial/EraseLead.lean,Mathlib/Algebra/Polynomial/Eval/Coeff.lean,Mathlib/Algebra/Polynomial/Eval/Defs.lean,Mathlib/Algebra/Polynomial/Eval/Degree.lean,Mathlib/Algebra/Polynomial/Eval/SMul.lean,Mathlib/Algebra/Polynomial/Expand.lean,Mathlib/Algebra/Polynomial/FieldDivision.lean,Mathlib/Algebra/Polynomial/HasseDeriv.lean,Mathlib/Algebra/Polynomial/Homogenize.lean,Mathlib/Algebra/Polynomial/Identities.lean,Mathlib/Algebra/Polynomial/Inductions.lean,Mathlib/Algebra/Polynomial/Mirror.lean,Mathlib/Algebra/Polynomial/Monic.lean,Mathlib/Algebra/Polynomial/OfFn.lean,Mathlib/Algebra/Polynomial/Smeval.lean,Mathlib/Algebra/Polynomial/Taylor.lean,Mathlib/Algebra/Polynomial/UnitTrinomial.lean,Mathlib/Analysis/Normed/Field/Approximation.lean,Mathlib/Analysis/Normed/Unbundled/SpectralNorm.lean,Mathlib/Analysis/Polynomial/MahlerMeasure.lean,Mathlib/Analysis/Real/Pi/Irrational.lean,Mathlib/Data/Nat/Choose/Lucas.lean,Mathlib/FieldTheory/KummerExtension.lean,Mathlib/FieldTheory/Minpoly/Basic.lean,Mathlib/FieldTheory/Minpoly/Field.lean,Mathlib/FieldTheory/RatFunc/Luroth.lean,Mathlib/LinearAlgebra/Matrix/Charpoly/Basic.lean,Mathlib/LinearAlgebra/Matrix/Charpoly/Coeff.lean,Mathlib/LinearAlgebra/SModEq/Basic.lean,Mathlib/LinearAlgebra/Vandermonde.lean,Mathlib/NumberTheory/BernoulliPolynomials.lean,Mathlib/RingTheory/Adjoin/Polynomial/Basic.lean,Mathlib/RingTheory/Adjoin/PowerBasis.lean,Mathlib/RingTheory/Algebraic/Basic.lean,Mathlib/RingTheory/FreeCommRing.lean,Mathlib/RingTheory/Henselian.lean,Mathlib/RingTheory/IntegralClosure/Algebra/Ideal.lean,Mathlib/RingTheory/IntegralClosure/IsIntegral/Basic.lean,Mathlib/RingTheory/IntegralClosure/IsIntegralClosure/Basic.lean,Mathlib/RingTheory/Localization/Integral.lean,Mathlib/RingTheory/MatrixPolynomialAlgebra.lean,Mathlib/RingTheory/MvPolynomial/Homogeneous.lean,Mathlib/RingTheory/Polynomial/Basic.lean,Mathlib/RingTheory/Polynomial/Content.lean,Mathlib/RingTheory/Polynomial/Cyclotomic/Roots.lean,Mathlib/RingTheory/Polynomial/DegreeLT.lean,Mathlib/RingTheory/Polynomial/Eisenstein/Criterion.lean,Mathlib/RingTheory/Polynomial/Hermite/Basic.lean,Mathlib/RingTheory/Polynomial/HilbertPoly.lean,Mathlib/RingTheory/Polynomial/Ideal.lean,Mathlib/RingTheory/Polynomial/IntegralNormalization.lean,Mathlib/RingTheory/Polynomial/IrreducibleRing.lean,Mathlib/RingTheory/Polynomial/IsIntegral.lean,Mathlib/RingTheory/Polynomial/Nilpotent.lean,Mathlib/RingTheory/Polynomial/Quotient.lean,Mathlib/RingTheory/Polynomial/Resultant/Basic.lean,Mathlib/RingTheory/Polynomial/ScaleRoots.lean,Mathlib/RingTheory/Polynomial/UniversalFactorizationRing.lean,Mathlib/RingTheory/PolynomialAlgebra.lean,Mathlib/RingTheory/PowerBasis.lean,Mathlib/RingTheory/PowerSeries/Trunc.lean,Mathlib/RingTheory/PowerSeries/WeierstrassPreparation.lean,Mathlib/RingTheory/ReesAlgebra.lean,Mathlib/RingTheory/Smooth/IntegralClosure.lean,Mathlib/RingTheory/Spectrum/Prime/Polynomial.lean,Mathlib/RingTheory/Trace/Basic.lean,Mathlib/RingTheory/ZariskisMainTheorem.lean,Mathlib/Tactic/ComputeDegree.lean,Mathlib/Topology/Algebra/Polynomial.lean,MathlibTest/ComputeDegree.lean 85 3 ['github-actions', 'mathlib-merge-conflicts'] nobody
0-6251
1 hour ago
0-7840
2 hours ago
8-31577
8 days
0
45253 YaelDillies
author:YaelDillies
chore(Order/CompleteLattice): use `@[to_dual]` more --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order 62/56 Mathlib/Order/CompleteLattice/Defs.lean,Mathlib/Order/ConditionallyCompleteLattice/Defs.lean,Mathlib/Order/ConditionallyCompleteLattice/WithTop.lean,Mathlib/Order/Heyting/Basic.lean 4 3 ['github-actions', 'mathlib-merge-conflicts', 'vihdzp'] nobody
0-5707
1 hour ago
4-6811
4 days ago
26-34079
26 days
1
46340 CocoSgt
author:CocoSgt
feat(Analysis/Matrix/Deriv): add Jacobi's formula for the derivative of the determinant New file `Mathlib/Analysis/Matrix/Deriv.lean` with **Jacobi's formula** for the derivative of the determinant along a path of matrices: * `Matrix.hasDerivAt_det`: if every entry of a path `G : 𝕜 → Matrix n n 𝔸` (with `𝔸` a normed commutative algebra over the normed field `𝕜`) is differentiable at `t` with derivative `G' i j`, then `s ↦ (G s).det` is differentiable at `t` with derivative `((G t).adjugate * G').trace`. * `Matrix.hasDerivAt_log_det_re`: if moreover `G t` is positive definite (for `𝔸 = 𝕜` an `RCLike` field, path parameter `ℝ`), then `s ↦ log ((G s).det).re` is differentiable at `t` with derivative `((G t)⁻¹ * G').trace.re`. Mathlib so far only has the formal derivative `Matrix.derivative_det_one_add_X_smul` (in `LinearAlgebra/Matrix/Charpoly/Coeff.lean`), which is the `1 + X • M` special case of the first statement. `Mathlib.lean` is updated via `lake exe mk_all`. Local check: `lake build --wfail Mathlib.Analysis.Matrix.Deriv` (with the Mathlib linters), `lake exe lint-style`, `lake exe mk_all --check` and a rebuild of the `Mathlib` root module all pass. ### Provenance The proofs are taken from **Levent Alpöge's** (with Claude) Lean formalization of the Riemann Hypothesis (and GRH for Dirichlet L-functions), released on 2026-11-20 at https://alpo.ge/. Original file: `ReciprocityTheory/GeometryOfNumbers/PluriharmonicAnalysis/LogDetSt.lean`, lines 8–77 (`trace_adjugate_mul_eq_sum_perm`, `hasDerivAt_det`, `hasDerivAt_log_det`); browsable in the mirror: https://github.com/CocoSgt/riemann-hypothesis-lean/blob/main/src/ReciprocityTheory/GeometryOfNumbers/PluriharmonicAnalysis/LogDetSt.lean The original statements are for paths `ℝ → Matrix (Fin r) (Fin r) ℂ`; here they are generalized to arbitrary finite index types, to matrices over any normed commutative `𝕜`-algebra (Jacobi) and to `RCLike` scalars (log det). The `first | … | …` version-compatibility alternatives of the original proof were fixed to the branch that applies to current Mathlib. The extraction, cleanup, port to current `master` and this PR were made by **GLM 5.4** (Z.ai) running in **DeepSeek Harness**; all mathematical credit belongs to Levent Alpöge and Claude, who is listed as the file author and as `Co-authored-by` in the commit. The extraction project is documented in https://github.com/CocoSgt/rh-mathlib-lemmas. Note on licensing: the original release does not state an explicit license file. Please make sure the author is OK with merging before doing so. t-analysis new-contributor 118/0 Mathlib.lean,Mathlib/Analysis/Matrix/Deriv.lean 2 2 ['github-actions'] nobody
0-3434
57 minutes ago
0-3882
1 hour ago
0-3827
1 hour
0
46339 CocoSgt
author:CocoSgt
feat(Analysis/Matrix/Order): add Minkowski, Fischer and Hadamard determinant inequalities Adds determinant inequalities for positive (semi)definite matrices over an `RCLike` field to `Mathlib/Analysis/Matrix/Order.lean` (the file where the Loewner order on matrices and `CFC.sqrt` on matrices are set up): * `Matrix.PosSemidef.det_one_add_eq_prod`: `det (1 + Q) = ∏ i, (1 + λ i)` for `Q` positive semidefinite with eigenvalues `λ i`. * `Matrix.PosDef.det_re_mono`: **Minkowski's determinant inequality** — if `G` is positive definite and `H - G` is positive semidefinite then `(G.det).re ≤ (H.det).re`, i.e. `det` is monotone on the positive definite cone. * `Matrix.PosDef.det_re_le_det_re_mul_det_re_fromBlocks`: **Fischer's inequality** `((fromBlocks A B C D).det).re ≤ (A.det).re * (D.det).re` for a positive definite block matrix (with `C = Bᴴ` derived from the hypothesis), plus the `Fin (a + b)` submatrix version. * `Matrix.PosDef.det_re_le_prod_diag_re`: **Hadamard's determinant inequality** `(D.det).re ≤ ∏ j, (D j j).re`, plus the block version. The statements use `RCLike.re`, in the style of `PosSemidef.re_dotProduct_nonneg` in `Mathlib/Analysis/Matrix/PosDef.lean`. Since the determinant of a Hermitian matrix is real, the `ComplexOrder`-style `G.det ≤ H.det` is a restatement away; happy to switch if reviewers prefer. Local check: `lake build --wfail Mathlib.Analysis.Matrix.Order` (with the Mathlib linters) and its only direct importer `Mathlib.Probability.Distributions.Gaussian.Multivariate` build cleanly; `lake exe lint-style` passes. ### Provenance The proofs are taken from **Levent Alpöge's** (with Claude) Lean formalization of the Riemann Hypothesis (and GRH for Dirichlet L-functions), released on 2026-11-20 at https://alpo.ge/. Original file: `ReciprocityTheory/GeometryOfNumbers/LatticeCovolumes/GramSt.lean`, lines 12–143 (`gramSt_det_one_add_eq`, `gramSt_det_re_le_of_sub`, `gramSt_fischer`, `gramSt_fin_blocks`, `gramSt_hadamard`, `det_re_le_mul_prod_diag`); browsable in the mirror: https://github.com/CocoSgt/riemann-hypothesis-lean/blob/main/src/ReciprocityTheory/GeometryOfNumbers/LatticeCovolumes/GramSt.lean The original statements are for `Matrix ι ι ℂ`; here they are generalized to `RCLike 𝕜`. Beyond renaming, docstrings and dropping two restatements of existing Mathlib lemmas, the changes are `Complex.*` → `RCLike.*` lemmas, `Finset.prod_le_prod₀` instead of `Finset.prod_le_prod`, and explicit `RCLike.re`. The extraction, cleanup, port to current `master` and this PR were made by **GLM 5.4** (Z.ai) running in **DeepSeek Harness**; all mathematical credit belongs to Levent Alpöge and Claude, who is listed as an author in the file header and as `Co-authored-by` in the commit. The extraction project (structure map of the 17.4M-line development, 52 further candidate lemmas) is documented in https://github.com/CocoSgt/rh-mathlib-lemmas. Note on licensing: the original release does not state an explicit license file. Please make sure the author is OK with merging before doing so. t-analysis new-contributor 152/1 Mathlib/Analysis/Matrix/Order.lean 1 2 ['github-actions'] nobody
0-3375
56 minutes ago
0-3887
1 hour ago
0-3832
1 hour
0
46341 CocoSgt
author:CocoSgt
feat(LinearAlgebra/Matrix/Determinant): add the Cauchy–Binet formula as a sum over functions Adds the **Cauchy–Binet formula** to `Mathlib/LinearAlgebra/Matrix/Determinant/Basic.lean`, right after `Matrix.det_mul`, as a sum over all functions between the index sets: ```lean theorem Matrix.det_mul_eq_sum_over_functions (A : Matrix m n R) (B : Matrix n m R) : (A * B).det = ∑ f : m → n, (∏ i, A i (f i)) * (B.submatrix f id).det ``` (Functions `f` that are not injective contribute `0`, since `B.submatrix f id` has a repeated row.) The proof is the natural one via `Matrix.detRowAlternating`: expanding `A * B` row-wise as a sum of multiples of the rows of `B` and applying `MultilinearMap.map_sum` / `MultilinearMap.map_smul_univ`. Local check: `lake build --wfail Mathlib.LinearAlgebra.Matrix.Determinant.Basic` (with the Mathlib linters) and `lake exe lint-style` pass. ### Provenance The proof is taken from **Levent Alpöge's** (with Claude) Lean formalization of the Riemann Hypothesis (and GRH for Dirichlet L-functions), released on 2026-11-20 at https://alpo.ge/. Original file: `Lemmata/GeneralBFact/Imports.lean`, line 8 (`Bl.general_b_fact.goal1`); browsable in the mirror: https://github.com/CocoSgt/riemann-hypothesis-lean/blob/main/src/Lemmata/GeneralBFact/Imports.lean The original statement is for `Fin`-indexed matrices; here it is generalized to arbitrary finite index types. The extraction, cleanup, port to current `master` and this PR were made by **GLM 5.4** (Z.ai) running in **DeepSeek Harness**; all mathematical credit belongs to Levent Alpöge and Claude, who is listed as an author in the file header and as `Co-authored-by` in the commit. The extraction project is documented in https://github.com/CocoSgt/rh-mathlib-lemmas. Note on licensing: the original release does not state an explicit license file. Please make sure the author is OK with merging before doing so. t-algebra new-contributor
label:t-algebra$
23/1 Mathlib/LinearAlgebra/Matrix/Determinant/Basic.lean 1 2 ['github-actions'] nobody
0-2908
48 minutes ago
0-3878
1 hour ago
0-3823
1 hour
0
46342 jkomyno
author:jkomyno
feat(Order/Submodular): define submodular, supermodular, and modular functions This PR adds the lattice-level vocabulary for submodularity: `Submodular`, `Supermodular` and `Modular` on a lattice, their restrictions to a subset, and the algebra that follows from the inequality alone. `Mathlib/Order/Submodular/Defs.lean` (145 lines): - `Submodular f` is `f (a ⊓ b) + f (a ⊔ b) ≤ f a + f b` for `[Lattice α] [Add β] [Preorder β]`. `Supermodular` is the reverse inequality and `Modular` is the equality. `Modular` asks only for `[Add β]`. - `SubmodularOn f s`, `SupermodularOn f s` and `ModularOn f s` restrict the pairs to a set `s`. - `modular_iff_submodular_and_supermodular`: over a partial order, modularity is submodularity plus supermodularity. The `*On` version is included. `Mathlib/Order/Submodular/Basic.lean` (262 lines): - constant functions, and `LinearOrder.modular` with its submodular and supermodular corollaries. - invariance under `OrderDual` (`submodular_comp_ofDual_iff`) and duality by negation (`submodular_neg_iff`). - closure of the submodular cone under `add`, `sub`, `smul` by a nonnegative scalar, `finset_sum` and `pi_sum`. - precomposition with a `LatticeHom` or an `OrderIso`. - `Submodular.inf_const` and `Supermodular.sup_const`: truncating a monotone function from above or below preserves the inequality. - `Submodular.sup_le_add_of_disjoint`: with `0 ≤ f ⊥`, a submodular function is subadditive on disjoint elements. Both files use the current module conventions (`module`, `public section`, `@[expose]` on the definitions). Zulip: I introduced myself and the project in [Alberto Schiabel / jkomyno / submodularity](https://leanprover.zulipchat.com/#narrow/channel/113489-new-members/topic/Alberto.20Schiabel.20.2F.20jkomyno.20.2F.20submodularity/near/642663285). Two questions are still open there, and I am happy to follow whatever comes out of it: `Submodular` versus `IsSubmodular` naming, and whether `Mathlib/Order/Submodular/` is the right home. Related: #43824 adds a single-file version of the same material in `Mathlib/Order/Submodular.lean`, with `IsSubmodular`-style names, `[LE β]` assumptions and a `Finset` diminishing-returns lemma. It has been awaiting author since 2026-10-16. This PR is meant to supersede it. I have no relationship with the original author. AI assistance: the Lean was written with LLM assistance, using `fable-5.2` and `gemini 4 neon` with Lean 4 agent skills for proof search and Mathlib API lookup. I reviewed every declaration by hand: the definitions, the typeclass assumptions and each proof, and I re-ran the build and the style linters after the fixes. I confirm that I can explain and defend each design decision here without a model. I'm also manually editing this PR description to make it as readable for you maintainers as possible. Verification, on the last commit of this branch: - `lake build Mathlib.Order.Submodular.Basic`, no warnings. - `lake exe lint-style` on both files, clean. - No `sorry` in either file. Planned follow-ups, each a separate future PR (if you'd appreciate having them): - `Finset` diminishing returns: `Submodular.add_insert_le`, the equivalences `submodular_iff_add_insert_le` and `submodular_iff_pair_insert_le`, complement duality, and cardinality as a modular set function. - Closure under `finset_sum` and adding a constant. - `k`-submodular functions in `Mathlib/Order/Submodular/KSubmodular/`: allocations `α → Option κ`, `kInter` and `kUnion`, orthant submodularity, pairwise monotonicity, and the `k = 1` case reducing to `Submodular`. - DR-submodularity on `ι → ℕ`: `CoordConcave`, `DRSubmodular ↔ Submodular ∧ CoordConcave`, and the unary-expansion reduction `DRSubmodularOn f (Icc 0 u) ↔ Submodular (f ∘ latticeProj u)`. - `Submodular M.eRk` for a matroid, phrased against the existing `Matroid.eRk_inter_add_eRk_union_le`. - Further out: concave-of-modular composition, the Lovász extension with submodular and base polyhedra, and greedy `(1 - 1/e)` guarantees. These are probably a better fit in a separate, submodularity-specific package that imports `mathlib4`, rather than in `mathlib4`'s own core. t-order LLM-generated new-contributor 409/0 Mathlib.lean,Mathlib/Order/Submodular/Basic.lean,Mathlib/Order/Submodular/Defs.lean 3 3 ['github-actions', 'jkomyno'] nobody
0-2381
39 minutes ago
0-3281
53 minutes ago
0-3226
53 minutes
0
36428 wrenna-robson
author:wrenna-robson
feat(Logic/Equiv/Fin): streamline equiv definitions using mkDivMod This PR redefines `finProdFinEquiv` using `Fin.mkDivMod` from Batteries, and adds its analogue `natProdFinEquiv : ℕ × Fin n ≃ ℕ`, whose inverse is now `Nat.divModEquiv`. Both are order isomorphisms for the lexicographic order. A new file, Order/Fin/Lex, adds these as `finProdFinOrderIso` and `natProdFinOrderIso`. A few downstream proofs are adjusted. The series expansions of arctan, sin and cos now reindex over even and odd terms directly, without going through `Nat.divModEquiv`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data 85/93 Mathlib.lean,Mathlib/Analysis/SpecialFunctions/Complex/Arctan.lean,Mathlib/Analysis/SpecialFunctions/Trigonometric/Series.lean,Mathlib/Logic/Equiv/Fin/Basic.lean,Mathlib/NumberTheory/Height/MvPolynomial.lean,Mathlib/Order/Fin/Lex.lean,Mathlib/Order/Partition/Equipartition.lean 7 22 ['JovanGerb', 'eric-wieser', 'github-actions', 'mathlib-merge-conflicts', 'wrenna-robson'] eric-wieser
assignee:eric-wieser
0-2209
36 minutes ago
1-54479
1 day ago
127-4663
127 days
0
46343 vihdzp
author:vihdzp
perf: remove bad `simp` attribute from `Real.ringHom_apply` See [Zulip](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Mathlib.27s.20morphism.20hierarchy/near/642638980). --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra
label:t-algebra$
1/1 Mathlib/Algebra/Order/Archimedean/Real/Hom.lean 1 3 ['github-actions', 'leanprover-radar', 'vihdzp'] nobody
0-1932
32 minutes ago
0-2648
43 minutes ago
0-2626
43 minutes
0
46304 vihdzp
author:vihdzp
chore: deprecate `(E)NNReal.bot_eq_zero` In favor of `bot_eq_zero` in the root namespace. We also golf a few proofs along the way. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data 36/49 Mathlib/Analysis/Asymptotics/TVS.lean,Mathlib/Analysis/Normed/Lp/PiLp.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/MeasureTheory/Group/FundamentalDomain.lean,Mathlib/MeasureTheory/Measure/SeparableMeasure.lean,Mathlib/Order/Filter/ENNReal.lean,Mathlib/Order/LiminfLimsup.lean,Mathlib/Probability/Moments/Basic.lean,Mathlib/Topology/MetricSpace/HolderNorm.lean 10 1 ['github-actions'] nobody
0-1868
31 minutes ago
1-47829
1 day ago
1-47774
1 day
0
46266 EtienneC30
author:EtienneC30
refactor: remove the coercion from `SemilinearMapClass` to `SemilinearMap` Deals with `SemilinearMapClass` in #31365. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #45954 t-algebra tech debt
label:t-algebra$
191/152 Mathlib/Algebra/Algebra/Bilinear.lean,Mathlib/Algebra/Algebra/Equiv.lean,Mathlib/Algebra/Algebra/Hom.lean,Mathlib/Algebra/Algebra/NonUnitalHom.lean,Mathlib/Algebra/Algebra/Subalgebra/Basic.lean,Mathlib/Algebra/Algebra/Subalgebra/Tower.lean,Mathlib/Algebra/Category/CoalgCat/Basic.lean,Mathlib/Algebra/Category/CoalgCat/ComonEquivalence.lean,Mathlib/Algebra/Module/Equiv/Defs.lean,Mathlib/Algebra/Module/LinearMap/Defs.lean,Mathlib/Algebra/Order/Module/PositiveLinearMap.lean,Mathlib/Algebra/Polynomial/Taylor.lean,Mathlib/Algebra/Star/LinearMap.lean,Mathlib/Algebra/Star/Subalgebra.lean,Mathlib/Analysis/CStarAlgebra/CStarMatrix.lean,Mathlib/Analysis/CStarAlgebra/CompletelyPositiveMap.lean,Mathlib/Analysis/CStarAlgebra/PositiveLinearMap.lean,Mathlib/Analysis/Convex/LinearIsometry.lean,Mathlib/Analysis/InnerProductSpace/Orthogonal.lean,Mathlib/Analysis/InnerProductSpace/Projection/Basic.lean,Mathlib/Analysis/Matrix/HermitianFunctionalCalculus.lean,Mathlib/Analysis/Normed/Algebra/Spectrum.lean,Mathlib/Analysis/Normed/Operator/Basic.lean,Mathlib/Analysis/Normed/Operator/LinearIsometry.lean,Mathlib/Analysis/SpecialFunctions/ContinuousFunctionalCalculus/PosPart/Basic.lean,Mathlib/Data/Matrix/Basic.lean,Mathlib/FieldTheory/Minpoly/Field.lean,Mathlib/FieldTheory/NormalizedTrace.lean,Mathlib/LinearAlgebra/LinearDisjoint.lean,Mathlib/LinearAlgebra/Matrix/Kronecker.lean,Mathlib/LinearAlgebra/SymmetricAlgebra/Basic.lean,Mathlib/LinearAlgebra/TensorProduct/Submodule.lean,Mathlib/LinearAlgebra/Trace.lean,Mathlib/NumberTheory/Modular.lean,Mathlib/RepresentationTheory/Coinvariants.lean,Mathlib/RepresentationTheory/Invariants.lean,Mathlib/RepresentationTheory/Rep/Res.lean,Mathlib/RingTheory/Adjoin/Basic.lean,Mathlib/RingTheory/Bialgebra/Basic.lean,Mathlib/RingTheory/Bialgebra/Hom.lean,Mathlib/RingTheory/Bialgebra/TensorProduct.lean,Mathlib/RingTheory/Coalgebra/Basic.lean,Mathlib/RingTheory/Coalgebra/Convolution.lean,Mathlib/RingTheory/Coalgebra/Equiv.lean,Mathlib/RingTheory/Coalgebra/Hom.lean,Mathlib/RingTheory/Coalgebra/TensorProduct.lean,Mathlib/RingTheory/DedekindDomain/LinearDisjoint.lean,Mathlib/RingTheory/Flat/Equalizer.lean,Mathlib/RingTheory/GradedAlgebra/AlgHom.lean,Mathlib/RingTheory/GradedAlgebra/TensorProduct.lean,Mathlib/RingTheory/LocalProperties/Exactness.lean,Mathlib/RingTheory/LocalRing/Quotient.lean,Mathlib/RingTheory/Localization/BaseChange.lean,Mathlib/RingTheory/Localization/Module.lean,Mathlib/RingTheory/TensorProduct/Basic.lean,Mathlib/RingTheory/TensorProduct/Maps.lean 56 11 ['EtienneC30', 'github-actions', 'mathlib-dependent-issues', 'mathlib-splicebot', 'themathqueen'] nobody
0-1833
30 minutes ago
0-8429
2 hours ago
0-34575
9 hours
0
46336 robin-carlier
author:robin-carlier
feat(Tactic/CategoryTheory): the `cat_nf` simp set and its term elaborator This PR adds a simp set called `cat_nf` that is intended to records the normal forms of categorical expressions (`dsimp`-normal form for objects, and normal forms for morphisms). It solves the following problem: in category theory, a lot of simp-based automation is used, and the normal forms usually right-normalize associativity, removes identities, and applies functoriality. This means that to perform the routine operation of "applying a functor to a diagram and then rewrite with it", the current pattern is to introduce the applied (e.g. using the `congr()` elaborator) diagram via a `have` statement and then run a combination of `dsimp` and `simp only` at this new local hypothesis to put it in good shape for rewriting. In some cases, the amount of lemmas in the `simp only` call can get big and clutter the proof visually. This type of problem arises not only when applying functors to diagram, but more generally when instantiating general categorical expressions with specific inputs that might enable more simplification. The previous `dsimp%` elaborator was partly addressing the problem, as it was at least introducing the dsimplified diagrams, but it was incapable of pushing functoriality through the expressions, as things like `Functor.map_comp` are not definitional equalities. The proposed solution here is to record these simplification in a dedicated simp set, which in practice should hold associativity, unitality, "basic" functoriality like lemmas, as well as the definitional unfolding for various functors. In addition to the simp set, a `cat_nf%` elaborator that runs `simp only [cat_nf]` at the term is provided. The goal is to enable use of things like `simp [cat_nf% congr(F.map $h)]` instead of the `have h := _; simp only at h; simp [h]` dance from before. Some initial (rather conservative) tagging is also done in this PR. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Initially, I wanted this elaborator to use `Sym.Simp` to make it as fast as possible (and to try out the API), but unfortunately it seems that the matching in `Sym.simp` is a bit more rigid compared to the one that happens in the regular `simp`, so that I could not get the `Sym` variant to be as powerful as the `simp`-based implementation (at least not without having to potentially rewrite many utilities). So instead I went with the easy route of making it `simp`-based. One thing that is not 100% clear to me is whether or not `cat_nf%` (and the `cat_nf` simp set) should include the `cancelIso` simproc. I did not try yet to make this work (and IMO this shouldn’t block having this first version of the elaborator). The reason I am not sure is that while it would be practical (i.e, `cat_nf% e.inv ≫= (h : e.hom ≫ … = …)` could be a way of "moving an isomorphism to the right of the equation"), these are equational lemmas akin to `NatTrans.naturality` that we could decide are out of scope for "normalization". Currently, there is no option to use local hypothesis in `cat_nf%` to further normalize, i.e, we can’t do `cat_nf% [h]`. It could be added (by doing something similar as what we did in `dsimp%`, but I’m also not sure it’s desirable: the intended goal of this elaborator is to normalize with respect to a fixed predictable set of lemma and not to become a hack to "apply simp only to a term". AI disclosure: I had some conversations with Claude when exploring the lean4 codebase around `Sym.simp` and the differences in its matching with the regular `simp`, but ultimately all the code in this PR is handwritten, so I’m skipping the LLM-generated tag. t-category-theory t-meta 145/11 Mathlib.lean,Mathlib/CategoryTheory/Category/Basic.lean,Mathlib/CategoryTheory/Functor/Basic.lean,Mathlib/CategoryTheory/Functor/Category.lean,Mathlib/CategoryTheory/Functor/Const.lean,Mathlib/Tactic.lean,Mathlib/Tactic/CategoryTheory/CatNF.lean,MathlibTest/CategoryTheory/CatNFAttr.lean 8 3 ['github-actions', 'leanprover-radar', 'robin-carlier'] nobody
0-1353
22 minutes ago
0-14061
3 hours ago
0-14117
3 hours
0
46337 EtienneC30
author:EtienneC30
refactor: remove the coercion from `CompletelyPositiveMapClass` Also fix some inconsistency in the definition: The docstring mentions `CStarMatrix.mapₗ` but the docstring actually refers to `CStarMatrix.map`, but still uses `toLinearMap` instead of `toFun`. Fix the docstring and replace `toLinearMap` with `toFun`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> I think `CompletelyPositiveMap` should be called `CompletelyPositiveLinearMap`. t-analysis maintainer-merge 6/10 Mathlib/Analysis/CStarAlgebra/CompletelyPositiveMap.lean 1 3 ['github-actions', 'themathqueen'] nobody
0-837
13 minutes ago
0-9787
2 hours ago
0-10099
2 hours
0
46344 EtienneC30
author:EtienneC30
refactor: rename `SemilinearEquivClass.semilinearEquiv` to `LinearEquiv.ofClass` The namespace is `LinearEquiv` to allow for anonymous dot notation. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt maintainer-merge
label:t-algebra$
10/6 Mathlib/Algebra/Module/Equiv/Defs.lean,Mathlib/NumberTheory/NumberField/Basic.lean,Mathlib/RingTheory/Coalgebra/Equiv.lean 3 3 ['github-actions', 'themathqueen'] nobody
0-477
7 minutes ago
0-2632
42 minutes ago
0-2577
42 minutes
0
46345 EtienneC30
author:EtienneC30
refactor: remove the coercion from `BialgEquivClass` Part of #31365 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-ring-theory 2/5 Mathlib/RingTheory/Bialgebra/Equiv.lean 1 1 ['github-actions', 'themathqueen'] nobody
0-430
7 minutes ago
0-1491
23 minutes ago
0-1436
23 minutes
0

New contributors' PRs on the review queue

Number Author Title Description Labels +/- Modified files (first 100) 📝 💬 All users who commented or reviewed Assignee(s) Updated Last status change total time in review blocks
36719 NoneMore
author:NoneMore
feat(ModelTheory): add `PartialType` for first-order theories This PR adds the definitions of partial types over theories and over parameter sets, and proves several equivalent characterizations. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #36667 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-logic new-contributor 432/17 Mathlib.lean,Mathlib/ModelTheory/PartialTypes.lean,Mathlib/ModelTheory/Semantics.lean 3 7 ['NoneMore', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'vihdzp'] nobody
129-48075
4 months ago
129-48596
129 days ago
137-31502
137 days
0
42590 AntoineduFresne
author:AntoineduFresne
feat(Order/UpperLower/Closure): the upper and lower closures of a maximal antichain cover the order I add `IsMaxAntichain.upperClosure_union_lowerClosure`. It says that the upper and lower closures of a maximal antichain cover the whole order. I put it right after `ordConnected_iff_upperClosure_inter_lowerClosure`, next to `upperClosure_inter_lowerClosure`, which seems the right spot. The lemma is about antichains, so `Mathlib/Order/Antichain.lean` would have looked like the natural file to modify, but `upperClosure` is defined in `Mathlib/Order/UpperLower/Closure.lean`, which imports `Mathlib.Order.Interval.Set.OrdConnected`, which imports `Mathlib.Order.Antichain`. So to avoid an import loop I put it in `Closure.lean`. I split this out of #40741, where a reviewer suggested it. Nothing in that PR uses the lemma. t-order new-contributor 13/0 Mathlib/Order/Antichain.lean,Mathlib/Order/UpperLower/Closure.lean 2 12 ['AntoineduFresne', 'Ruben-VandeVelde', 'SnirBroshi', 'github-actions', 'tdwag123'] nobody
82-23722
2 months ago
82-62182
82 days ago
98-19162
98 days
0
43672 javgomzar
author:javgomzar
chore(LinearAlgebra/Matrix): add push tags to transpose lemmas --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra new-contributor
label:t-algebra$
6/5 Mathlib/LinearAlgebra/Matrix/Defs.lean 1 3 ['github-actions'] nobody
73-1877
2 months ago
73-4411
73 days ago
73-4356
73 days
0
42424 lydia-schiff
author:lydia-schiff
feat(Order/Partition/Finpartition): transport a set partition along a type equivalence - Adds `Finpartition.congr` to transport a `Finpartition` along a type equivalence. - We can use `Finpartition.map` if we have an order-iso, and the equivalence induces one via the new `Finset.congrOrderIso` which is based on `Equiv.finsetCongr`. - Includes parts, card, refl, and round-trip lemmas. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - `Equiv.finsetCongr` already gives us an equivalence of Finsets, so the new `Finset.congrOrderIso` just adds that the power-set lattice structure is also preserved. - Includes lemmas showing that the parts are e-images of the old ones, card is preserved, and refl + round-trip for the equivalence. - The cardinality lemma was the original motivation from some work on Stirling numbers, but I thought that `Finpartition.congr` and `Finset.congrOrderIso` seemed reusable and hopefully useful in their own right, and thought it would make a good first contribution. - Zulip thread about naming and placement [here](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/.60Finpartition.2Econgr.60.20.E2.80.94.20naming.20.26.20placement) - I used Claude Opus 4.8 to help draft the proofs and explore the API. I have spent several weeks making sure I understand and can justify every line and I've learned a lot which is great. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-order LLM-generated new-contributor 61/0 Mathlib/Data/Finset/Image.lean,Mathlib/Order/Partition/Finpartition.lean 2 6 ['github-actions', 'lydia-schiff', 'mathlib-merge-conflicts'] nobody
72-71434
2 months ago
72-75891
72 days ago
99-60398
99 days
0
43780 SashaIr
author:SashaIr
feat: q-analogs An implementation of q-analogs, q-binomials, and counting results. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics 965/0 Mathlib.lean,Mathlib/Combinatorics/QAnalog/Basic.lean,Mathlib/Combinatorics/QAnalog/Binomial.lean,Mathlib/Combinatorics/QAnalog/Counting.lean,Mathlib/Combinatorics/QAnalog/Subspace.lean 5 7 ['SashaIr', 'SnirBroshi', 'b-mehta', 'github-actions'] nobody
62-68314
2 months ago
69-66284
69 days ago
69-66585
69 days
0
38334 8e7
author:8e7
feat(Combinatorics/SimpleGraph/TreeDecomp): define tree decompositions Add definition for tree decompositions on simple graphs. Define the tree width of a simple graph and prove basic statements and conversions. ```lean structure TreeDecomp (G : SimpleGraph V) (W : Type) where /-- The set of vertices in each bag. -/ bag : W → Finset V /-- The graph adjacency relation of bags. -/ tree : SimpleGraph W /-- T must be a tree. -/ isTree : IsTree tree /-- All vertices in G must appear in some bag. -/ vertexCover : ∀ v : V, ∃ w : W, v ∈ bag w /-- For any edge (u, v) in G, there is a bag containing both u and v. -/ edgeCover ⦃u v : V⦄ : G.Adj u v → ∃ w : W, u ∈ bag w ∧ v ∈ bag w /-- For any vertex v in G, the set of bags that contain v is preconnected. -/ connectedBags : ∀ v : V, (tree.induce ({w | v ∈ bag w})).Preconnected ``` AI Usage: Some proofs are written with the help of Claude Code, and everything has been manually reviewed. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #38027 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics LLM-generated 395/0 Mathlib.lean,Mathlib/Combinatorics/SimpleGraph/TreeDecomp.lean 2 42 ['8e7', 'SnirBroshi', 'YaelDillies', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
62-50355
2 months ago
119-38393
119 days ago
143-21673
143 days
1
43953 hasjack
author:hasjack
feat(Combinatorics/SimpleGraph/LapMatrix): bound Laplacian eigenvalues by `|V|` Prove that every Laplacian eigenvalue of a finite simple graph is at most the number of vertices, via comparison of the Rayleigh quotient with the complete graph. Also record the underlying quadratic-form bound `xᵀ L x ≤ |V| · ‖x‖²`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---` , otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) Adds `dotProduct_mulVec_lapMatrix_le_card` and `eigenvalues_lapMatrix_le_card` in `LapMatrix.lean` only. The claim is the uniform bound `λ ≤ |V|` for every indexed eigenvalue; it does not assert `|V| ∈ spectrum` for every graph. Searched existing LapMatrix API (PSD, `zero_mem_spectrum_lapMatrix`, `lapMatrix_top`) and did not find a card upper bound under another name. Happy to rename if a preferred lemma already exists. new-contributor t-combinatorics LLM-generated 37/1 Mathlib/Combinatorics/SimpleGraph/LapMatrix.lean,Mathlib/Data/Matrix/Mul.lean 2 61 ['Parcly-Taxel', 'SnirBroshi', 'github-actions', 'hasjack'] nobody
62-8267
2 months ago
62-55286
62 days ago
64-49367
64 days
0
44103 xiahongchi
author:xiahongchi
feat: equate derivatives of ordered functions at contact points This adds Fréchet-derivative and scalar-derivative lemmas saying that two everywhere-ordered real-valued functions have equal derivatives wherever they agree. The proof applies Fermat’s theorem to their nonnegative difference. This packages and generalizes the scalar envelope argument from Bryan Sanchez’s `NSBlwChain/Caveats/C2_Envelope.lean` at `Brsanch/ns-lean-proofs@b73f537d1646165fbdc0993c5b2e223355dc3469` (MIT). The new declarations elaborate under the released toolchain; compiling the current master file there reports only one pre-existing current-Lean field-notation incompatibility before the new code. Current-toolchain CI is authoritative. t-analysis new-contributor 20/0 Mathlib/Analysis/Calculus/LocalExtr/Basic.lean 1 2 ['github-actions'] nobody
60-49436
1 month ago
60-50695
60 days ago
60-50937
60 days
0
42955 mpacholski
author:mpacholski
feat(diffgeo): add Hom-bundle support and fix pullback base points in T% elaborator # Changes ## `Mathlib/Geometry/Manifold/Notation.lean` * **Add support for pullback bundles:** Replaced the hardcoded bound variable `x` with the dynamically extracted argument `arg`, which allows for using elaborator `T%` with pullback bundles, where the base point lies in a different manifold, e.g. `v : Π (m : M), E₁ (b m)`, where `b : M → B`. * **Add support for Hom-bundles:** The elaborator now supports sections of Hom-bundles (`ContinuousLinearMap` between two fiber bundles, e.g. `ϕ : ∀ x, (E₁ x →L[𝕜] E₂ x`). It also supports the case where the base point lies in a different manifold (e.g. `ϕ : ∀ x, (E₁ (b x) →L[𝕜] E₂ (b x))`) * **Support nested `TangentSpace`:** Modified `findModelFiber?` to natively intercept `TangentSpace` applications and extract the model fiber at index 2. This prevents typeclass synthesis failures when `TangentSpace` is used inside a Hom-bundle. ## `MathlibTest/DifferentialGeometry/Notation/Basic.lean` * **Added tests for all the new usecases** this includes pullback bundles, Hom-bundles, pullback Hom-bundles, and Hom-bundles where one of the fibers is a `TangentSpace`. ## `Mathlib/Geometry/Manifold/VectorBundle/Hom.lean` * **Refactor `Hom.lean`:** Replaced verbose `TotalSpace.mk'` boilerplate in with the newly supported `T%` syntax (e.g. `MDiffAt[s] T% ϕ x` instead of `MDiffAt[s] (fun m ↦ TotalSpace.mk' (F₁ →L[𝕜] F₂) (E := fun (x : B) ↦ (E₁ x →L[𝕜] E₂ x)) (b m) (ϕ m)) x)` # Use of AI The help of AI was used in writing the code in `Mathlib/Geometry/Manifold/Notation.lean`. It was hence manually edited to simplify the code as much as possible. While the author is not yet an expert in metaprogramming in Lean, he is willing to learn and receive feedback, and put all the effort to understand the presented code. The code was carefully tested with different parts of it changed and removed to make sure that every line serves a purpose to provide the expected functionality. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-differential-geometry new-contributor LLM-generated 127/36 Mathlib/Geometry/Manifold/Notation.lean,Mathlib/Geometry/Manifold/VectorBundle/Hom.lean,MathlibTest/DifferentialGeometry/Notation/Basic.lean 3 5 ['github-actions', 'grunweg', 'mpacholski'] nobody
58-50352
1 month ago
93-85964
93 days ago
93-85909
93 days
3
44222 SamuelSchlesinger
author:SamuelSchlesinger
feat(Analysis/SpecialFunctions/Stirling): asymptotics of the central binomial coefficient Upstreaming `n.centralBinom ~ 4 ^ n / √(π * n)` and its `4 ^ n`-normalised corollaries, needed for a Razborov–Smolensky `AC⁰[p]` lower bound in a circuit-complexity formalization, together with the Catalan asymptotic `catalan n ~ 4 ^ n / (√π * n ^ (3 / 2))` as a first application in Mathlib. Drafted with Claude Code from my existing proof of the same statement, then revised by me against Mathlib conventions. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis LLM-generated new-contributor 85/1 Mathlib.lean,Mathlib/Analysis/SpecialFunctions/Stirling.lean,Mathlib/Combinatorics/Enumerative/Catalan/Asymptotics.lean 3 4 ['SamuelSchlesinger', 'github-actions'] nobody
57-31026
1 month ago
57-31947
57 days ago
57-31892
57 days
0
44297 langston-barrett
author:langston-barrett
feat(Data/FinEnum): `Std.PRange.LawfulUpwardEnumerable` instance --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> I'm not sure how Mathlib feels about interfacing with std constructs, but I was looking for something along the lines of `succMany?` and found `Std.PRange.LawfulUpwardEnumerable`, so I figured I'd implement it and see what the appetite is. Even if we don't decide to use this particular typeclass, the underlying functionality still seems useful. This is my first ever Lean development, so I would greatly appreciate any tips and feedback on the style! I wrote all of this by hand, though I asked some questions about Lean to GPT 5.6 Luna along the way. A `LinearlyUpwardEnumerable` instance would be a good follow-up. t-data new-contributor 112/0 Mathlib/Data/FinEnum.lean 1 3 ['github-actions', 'langston-barrett'] nobody
53-65581
1 month ago
53-74874
53 days ago
53-82577
53 days
0
44437 FawadHa1der
author:FawadHa1der
perf(Analysis/Normed/Lp/SmoothApprox): manifold-free proof of smooth approximation in Lp Authored with AI help. Created after @mcdoll feedback on [leanprover-community/mathlib4#42451](https://github.com/leanprover-community/mathlib4/pull/42451) This is an alternate solution. This removes the manifold chain from the longest pole and even if the poisson summation is approved using denseRange_toLpCLM. We would still be saving roughly 5% in build time. There is only one new lemma but no change to existing lemmas/statements. t-analysis new-contributor 82/36 Mathlib/Analysis/Normed/Lp/SmoothApprox.lean 1 3 ['FawadHa1der', 'github-actions'] nobody
50-77086
1 month ago
50-77837
50 days ago
50-77782
50 days
0
44440 vincentqb
author:vincentqb
feat(Computability/TuringMachine): bound the output length of a TM2 run This PR bounds the output length of a TM2 run by the input length plus a machine constant times the step count. It deduces `TM2ComputableInPolyTime.length_le`, the polynomial output-length bound used in composition. It also adds step-count induction and defines `initList` and `haltList` using `Function.update`. --- Relates to #7172 #33132 #35366 The code, the testing, and this description were prepared with the help of an AI coding assistant (Codex). t-computability LLM-generated new-contributor 82/7 Mathlib/Computability/StateTransition.lean,Mathlib/Computability/TuringMachine/Computable.lean,Mathlib/Computability/TuringMachine/StackTuringMachine.lean 3 3 ['github-actions', 'vincentqb'] nobody
47-35853
1 month ago
50-59227
50 days ago
50-59172
50 days
1
44541 vincentqb
author:vincentqb
feat(Computability/Partrec): computability of list operations This PR adds `Computable.list_foldl`, `list_foldr`, `list_rec`, and `list_map`, with the same statements as their `Primrec` counterparts. --- The code, the testing, and this description were prepared with the help of an AI coding assistant. LLM-generated new-contributor t-computability 37/0 Mathlib/Computability/Partrec.lean 1 3 ['github-actions', 'vincentqb'] nobody
47-34539
1 month ago
47-34796
47 days ago
47-34741
47 days
0
44392 yhx-12243
author:yhx-12243
fix(Algebra/Polynomial/Roots): fix tendstoCofinite with normal generic universe Remove the extraneous accidentally {R : Type} [CommRing R] [IsDomain R] in the signature of `Polynomial.tendstoCofinite_of_natDegree_ne_zero`, make it generic. t-algebra new-contributor
label:t-algebra$
2/2 Mathlib/Algebra/Polynomial/Roots.lean 1 3 ['github-actions', 'plp127'] nobody
45-80059
1 month ago
51-86201
51 days ago
51-86146
51 days
0
44618 barni120400
author:barni120400
feat(RingTheory/MvPolynomial/Homogeneous): powers of linear forms span the homogeneous polynomials Prove that the `n`-th powers of linear forms span the homogeneous polynomials of degree `n` (`MvPolynomial.homogeneousSubmodule_eq_span_pow`). Along the way, add the identity `Finset.sum_powerset_neg_one_pow_card_mul_sum_sdiff_pow_card` used in the proof. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-data new-contributor LLM-generated 64/0 Mathlib/Data/Nat/Choose/Sum.lean,Mathlib/RingTheory/MvPolynomial/Homogeneous.lean 2 2 ['github-actions'] nobody
45-59282
1 month ago
45-62413
45 days ago
45-64573
45 days
0
44019 bally65
author:bally65
feat(Computability/Primrec): primality is primitive recursive Primrec.nat_prime : PrimrecPred Nat.Prime, via Nat.prime_def_lt' and the bounded quantifier PrimrecRel.forall_lt. Mathlib had no computability statement about Nat.Prime. AI disclosure: I used Claude and ChatGPT to discuss ideas, to adjust and optimize the approach, and to explore whether there was something worth taking on. They also proposed many of the problems, lines of thought, and decisions about direction. Almost all of the Lean code was written by Claude Code. I applied the reviewer's suggested changes myself. AI 使用聲明:我使用 Claude 和 ChatGPT 討論構思、調整與優化,也討論有沒有值得挑戰的方向。它們也提出了許多題目、思路和決策方向。Lean 程式碼幾乎全部由 Claude Code 撰寫。審稿人提供的修改建議由我自己套用。 Note: the English disclosure is a translation of my Chinese text, assisted by Claude. t-computability new-contributor LLM-generated 44/0 Mathlib.lean,Mathlib/Computability/Primrec/Prime.lean 2 6 ['bally65', 'github-actions', 'pepamontero'] nobody
44-84967
1 month ago
61-5318
61 days ago
62-39916
62 days
0
44261 javgomzar
author:javgomzar
feat(Algebra/Category/Grp): free functor preserves monomorphisms Refactored the proof for AddCommGrpCat, so that it also works in GrpCat. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra new-contributor
label:t-algebra$
18/5 Mathlib/Algebra/Category/Grp/Adjunctions.lean 1 15 ['JX-Mo', 'github-actions', 'javgomzar', 'mathlib-merge-conflicts'] nobody
43-79843
1 month ago
43-80538
43 days ago
55-53070
55 days
0
44681 Altabeh
author:Altabeh
feat(Analysis/ODE/Linearization): the derivative of a flow at a fixed… Add a new file `Mathlib/Analysis/ODE/Linearization.lean`. Let `ϕ : Flow ℝ E` on a real Banach space be generated by a vector field `f`, meaning `∀ x t, HasDerivAt (fun s ↦ ϕ s x) (f (ϕ t x)) t`. If `e` is a fixed point of `ϕ` and `f` has derivative `A` at `e`, then every time-`t` map has derivative `exp (t • A)` at `e`: * `Flow.hasFDerivAt_of_isFixedPt`: `HasFDerivAt (ϕ t) (exp (t • A)) e` for every `t : ℝ`. * `Flow.fderiv_eq_exp_of_isFixedPt`: the `fderiv` form. * `Flow.eventually_norm_sub_exp_le`: a uniform estimate on compact time intervals. For `0 ≤ T` and `0 < ε`, eventually for `x` near `e`, `‖ϕ t x - e - exp (t • A) (x - e)‖ ≤ ε * ‖x - e‖` for all `t ∈ [0, T]`. Only differentiability of `f` at `e` is needed; nothing is assumed about `f` elsewhere. The estimate comes from comparing `ϕ t x - e` with `exp (t • A) (x - e)` using Grönwall's inequality. Negative times are handled by applying the result to `ϕ.reverse`. --- This PR is independent of the `LipschitzWith.flow` PR. It applies to any `Flow ℝ E` with a generating vector field, which includes those flows. **Proof of `eventually_norm_sub_exp_le` is done by a combination of `Claude Opus 5.5` and `GPT-5.6 Sol`. Linting and comments were done by AI.*** new-contributor t-analysis LLM-generated 166/0 Mathlib.lean,Mathlib/Analysis/ODE/Linearization.lean 2 3 ['github-actions', 'grunweg'] nobody
43-66745
1 month ago
43-67348
43 days ago
43-69916
43 days
0
44680 Altabeh
author:Altabeh
feat(Analysis/ODE/LipschitzFlow): the flow of a globally Lipschitz ve… Add a new file `Mathlib/Analysis/ODE/LipschitzFlow.lean`. A globally Lipschitz vector field `v : E → E` on a real Banach space has a unique solution of `γ' = v ∘ γ` through every point, defined for all time, and these solutions form a continuous flow: * `LipschitzWith.exists_forall_hasDerivAt`: global existence of solutions. * `LipschitzWith.dist_le_of_forall_hasDerivAt`: two solutions satisfy `dist (γ t) (δ t) ≤ dist (γ 0) (δ 0) * exp (K * |t|)`. * `LipschitzWith.flow : Flow ℝ E`: the flow of `v`. * `LipschitzWith.hasDerivAt_flow`: the orbits of the flow solve `γ' = v ∘ γ`. * `LipschitzWith.flow_eq_of_hasDerivAt`: every global solution is an orbit of the flow. * `LipschitzWith.dist_flow_le`: `dist (flow t x) (flow t y) ≤ dist x y * exp (K * |t|)`. The field does not need to be bounded. For a bounded field, Picard–Lindelöf (`IsPicardLindelof`) gives solutions on each interval `(-(n + 1), n + 1)`, and uniqueness glues them into a global solution. A general field is reduced to this case by multiplying `v` by a Lipschitz cutoff that is `1` on `closedBall 0 R`. Grönwall's inequality, using `‖v y‖ ≤ ‖v 0‖ + K * ‖y‖`, shows that for large `R` the solution stays in that ball on the time interval, so the cutoff does not change it. --- Continuity of the flow jointly in `(t, x)` comes from `continuousOn_prod_of_continuousOn_lipschitzOnWith'`, using the exponential separation bound on bounded time intervals. **The proofs of`exists_forall_hasDerivAt_of_forall_Ioo`, `lipschitzWith_cutoff_smul`, `norm_le_gronwallBound` and part of `dist_le_of_forall_hasDerivAt` used a combo of `GPT-5.6 Sol` and `Claude Opus 5.5`. Linting and comments were done by AI as well.** t-analysis new-contributor LLM-generated 276/0 Mathlib.lean,Mathlib/Analysis/ODE/LipschitzFlow.lean 2 3 ['github-actions', 'grunweg'] nobody
43-66624
1 month ago
43-67253
43 days ago
43-70069
43 days
0
44740 user202729
author:user202729
chore(Algebra/Ring/CompTypeclasses): fix a typo and reformat slightly Change `σ₂₃` to `σ` in the header, this one is clearly a typo. Do some minor reformatting for the rest of the file, which I think make it nicer. --- t-algebra new-contributor
label:t-algebra$
7/11 Mathlib/Algebra/Ring/CompTypeclasses.lean 1 3 ['github-actions', 'user202729', 'vihdzp'] nobody
42-35533
1 month ago
42-39202
42 days ago
42-39147
42 days
0
44784 shunfeng8421
author:shunfeng8421
feat(Combinatorics): prove finitary Van der Waerden by compactness Proves the finitary version of Van der Waerden's theorem: ```lean theorem van_der_waerden (k : ℕ) {κ : Type*} [Finite κ] [Nonempty κ] : ∃ N : ℕ, ∀ C : Fin (N + 1) → κ, HasMonoAPWithin k N C ``` i.e. every finite coloring of a sufficiently large initial segment `[0, N]` contains a monochromatic arithmetic progression of length `k`. This resolves the TODO in `Mathlib/Combinatorics/HalesJewett.lean` asking for a finitary version of Van der Waerden's theorem. ## Proof sketch The proof goes by compactness (Rado's selection lemma), the route explicitly suggested in the TODO ("either by compactness or by modifying the current proof"): 1. Assume the theorem fails: every segment `[0, N]` admits a "bad" coloring with no monochromatic AP of length `k`. 2. For each finite set `s ⊆ ℕ`, pick the bad coloring of the covering interval `[0, s.sup id]` and extend it (arbitrarily) to all of `ℕ`. 3. **Rado's selection lemma** (`Finset.rado_selection`, from `Mathlib/Combinatorics/Compactness.lean`, itself proved via Tychonoff's theorem) stitches these local bad colorings into a global coloring `χ : ℕ → κ` that agrees with some local bad coloring on every finite set. 4. The **infinite** Van der Waerden theorem — `Combinatorics.exists_mono_homothetic_copy`, a corollary of Hales–Jewett — produces a monochromatic AP `(a * t + b)_{t < k}` in `χ`. 5. Viewed as a finite set, this AP lies inside the covering interval of some finite set `t` on which the bad coloring agrees with `χ`, so it is also monochromatic there — contradicting badness of that local coloring. No explicit bounds are produced; this is purely an existence proof, which is exactly what the compactness route buys. ## New definitions - `Combinatorics.HasMonoAPWithin k N C`: the coloring `C : Fin (N+1) → κ` of the initial segment `[0, N]` contains a monochromatic AP of length `k`. ## Changes - `Mathlib/Combinatorics/HalesJewett.lean`: removed the completed TODO item ("Prove a finitary version of Van der Waerden's theorem ... by compactness"), added a pointer to the new theorem in the "Main results" list. - `Mathlib/Combinatorics/VanDerWaerden.lean`: new file. ## Notes for the reviewer - The file header still contains the `[Author]` placeholder: fill in your name before committing. ------- **AI disclosure**: AI-assisted tools were used to draft the proof outline and Lean code, and to debug type/simplifier issues; all contributions were reviewed and verified by the author, who takes full responsibility for the correctness of the mathematics and code. t-combinatorics new-contributor LLM-generated 100/3 Mathlib.lean,Mathlib/Combinatorics/HalesJewett.lean,Mathlib/Combinatorics/VanDerWaerden.lean 3 5 ['github-actions', 'grunweg', 'shunfeng8421'] nobody
40-60742
1 month ago
40-60742
40 days ago
40-69043
40 days
0
44831 scottdhughes
author:scottdhughes
feat(Analysis/MeanInequalitiesPow): add a real power difference bound Add `Real.abs_rpow_sub_rpow_le` in `Mathlib/Analysis/MeanInequalitiesPow.lean`: for nonnegative real bases and `0 ≤ p ≤ 1`, ```lean |a ^ p - b ^ p| ≤ |a - b| ^ p ``` Provide a direct scalar API for downstream fractional-power regularity estimates. Derive the bound from the neighboring `Real.rpow_add_le_add_rpow`, then handle the two input orders. Include both exponent endpoints. Add one lemma and its docstring, with no new imports. --- Local validation on Lean/Mathlib 4.35.0: - `lake build Mathlib.Analysis.MeanInequalitiesPow` - `lake exe lint-style Mathlib.Analysis.MeanInequalitiesPow` - Fresh source elaboration, exported-type and axiom checks, plus all 15 default declaration linters for the new lemma. The axiom check reports only `propext`, `Classical.choice` and `Quot.sound`. AI assistance: Codex adapted an existing downstream proof, searched Mathlib and relevant open PRs, drafted this description, and ran the local checks. t-analysis new-contributor LLM-generated 19/0 Mathlib/Analysis/MeanInequalitiesPow.lean 1 3 ['copilot-pull-request-reviewer', 'github-actions', 'scottdhughes'] nobody
38-75870
1 month ago
39-79034
39 days ago
39-78979
39 days
0
44537 vincentqb
author:vincentqb
feat(Analysis/Convex/Cone): prove that open sets have open hulls This PR proves `ConvexCone.isOpen_hull`: if addition and multiplication by each fixed scalar are continuous, the convex cone hull of an open set is open. It defines `ConvexCone.interior`, with coercion, membership, and equality lemmas parallel to the closure API. The hull theorem then follows from cone minimality. The original hypotheses do not suffice, see #44689 for a counterexample. --- AI-assisted contribution. t-analysis LLM-generated new-contributor file-removed 57/24 Mathlib.lean,Mathlib/Analysis/Convex/Cone/Basic.lean,Mathlib/Analysis/Convex/Cone/Interior.lean,Wanted.lean,Wanted/Analysis/Convex/Cone/Basic.lean 5 15 ['github-actions', 'pepamontero', 'vincentqb'] nobody
38-56905
1 month ago
43-44105
43 days ago
46-57325
46 days
0
44941 CollinYuanjieRen
author:CollinYuanjieRen
feat(Data/Finset/Sort): add filtering and greatest insertion lemmas Prove that filtering commutes with `Finset.sort`, and that inserting a new greatest element appends it to the sorted list. Both lemmas work for general total, transitive, antisymmetric relations. Continues the sorting portion of #9605 by @davikrehalt. Codex (GPT-6 Astra) assisted with the Lean proofs. t-data LLM-generated new-contributor 13/0 Mathlib/Data/Finset/Sort.lean 1 3 ['CollinYuanjieRen', 'github-actions'] nobody
37-6689
1 month ago
37-8291
37 days ago
37-8236
37 days
0
44893 unknown8575
author:unknown8575
chore(Topology/MetricSpace/Polish): generalize `IsClopenable.iUnion` to countable index types The proof only used ℕ to get `t' ≤ t` through index 0, but `exists_polishSpace_forall_le` already gives this directly. So the lemma now works for any countable index type, and the TODO is removed. I used an LLM to find this TODO and draft the change. I've checked it, built it locally, and understand every line. t-topology new-contributor 18/15 Mathlib/Topology/MetricSpace/Polish.lean 1 5 ['github-actions', 'plp127', 'unknown8575', 'vihdzp'] nobody
36-81927
1 month ago
38-14608
38 days ago
38-14553
38 days
0
44945 CollinYuanjieRen
author:CollinYuanjieRen
chore(Algebra/Lie): generalize subalgebra map membership Generalize `LieSubalgebra.mem_map_submodule` to arbitrary Lie algebra morphisms. Add `mem_map_equiv` and update the three skew-adjoint equivalence proofs. Continues Eric Rodriguez Boidi's #7994, marked `please-adopt`. --- Checked the five affected modules with Lean 4.36.0-rc1 and a zero-morphism client regression. AI-assisted: Codex prepared the Lean changes; GPT-6 Astra assisted with proof checks. t-algebra LLM-generated new-contributor
label:t-algebra$
9/6 Mathlib/Algebra/Lie/SkewAdjoint.lean,Mathlib/Algebra/Lie/Subalgebra.lean 2 3 ['CollinYuanjieRen', 'github-actions'] nobody
36-63857
1 month ago
36-64624
36 days ago
36-64569
36 days
0
29713 jessealama
author:jessealama
feat(Algebra/Homology): add Euler–Poincaré formula This PR builds on the generalized Euler characteristic framework from #31121 to prove the Euler-Poincaré formula for chain complexes. PR #31121 defines the Euler characteristic for general homological complexes. This PR specializes those definitions to ℤ-indexed chain complexes and proves the main Euler-Poincaré theorem. ### Main result (in `EulerPoincare.lean`) * `ChainComplex.eulerChar_eq_homologyEulerChar`: For ℤ-indexed bounded chain complexes of finite-dimensional modules over a division ring, the alternating sum of chain dimensions equals the alternating sum of homology dimensions. ### Supporting lemmas The file also provides dimension lemmas generalized to arbitrary `HomologicalComplex (ModuleCat k) c` (not just ℤ-indexed chain complexes): * `HomologicalComplex.dFrom_zero_range` / `dTo_zero_range`: zero range when the target/source object is zero * `HomologicalComplex.dFrom_range_finrank_eq_d` / `dTo_range_finrank_eq_d`: range of `dFrom`/`dTo` has the same dimension as the underlying differential * `HomologicalComplex.range_dTo_le_ker_dFrom`: range of `dTo` is contained in the kernel of `dFrom` t-algebra new-contributor
label:t-algebra$
264/0 Mathlib.lean,Mathlib/Algebra/Homology/EulerPoincare.lean 2 26 ['github-actions', 'jessealama', 'joelriou', 'kim-em', 'mathlib-merge-conflicts', 'mathlib4-merge-conflict-bot'] nobody
35-63152
1 month ago
35-63361
35 days ago
71-22706
71 days
0
44982 sw1sh
author:sw1sh
feat(Data/List): define Lyndon words This PR adds `Mathlib/Data/List/Lyndon.lean` with the definition of Lyndon words and their two basic properties. * `List.IsLyndon w`: the list `w` is nonempty and strictly smaller, in the lexicographic order, than each of its proper nonempty suffixes. * `List.IsLyndon.not_hasPeriod`: a Lyndon word has no period `p` with `0 < p < w.length`; that is, it is unbordered. It is stated with `List.HasPeriod` from `Mathlib/Data/List/PeriodicityLemma.lean`. * `List.IsLyndon.append`: if `u` and `v` are Lyndon words and `u < v`, then `u ++ v` is a Lyndon word. Two general lemmas on the lexicographic order of lists are added along the way: * `List.Lex.append_of_not_isPrefix`: if `Lex r u s` holds and `u` is not a prefix of `s`, then `Lex r (u ++ v) (s ++ w)` holds. * `List.lt_append_of_ne_nil`: a list is smaller than each of its proper extensions. A planned follow-up uses these to prove the Ehrenfeucht–Silberger theorem for infinite words: over a finite ordered alphabet, an infinite word whose sufficiently long factors are all bordered is eventually periodic. The proof cuts off longest Lyndon prefixes, which gives a non-increasing sequence of short Lyndon words. --- AI disclosure: this code was written with Claude Code (Anthropic, model Opus 5.5) as part of a project that formalizes equivalent forms of Wolfram's Rule 30 Problem 1 (https://github.com/WolframInstitute/Rule30PrizeKit). 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-data new-contributor LLM-generated 120/0 Mathlib.lean,Mathlib/Data/List/Lyndon.lean 2 3 ['github-actions'] nobody
35-18221
1 month ago
35-68653
35 days ago
35-68598
35 days
0
44958 dkaysin
author:dkaysin
feat(Combinatorics/SimpleGraph/Cayley): reachability and connectedness of Cayley graphs This PR adds reachability and connectedness results for Cayley Simple graphs. --- Implements connectedness results requested [here](https://github.com/leanprover-community/mathlib4/pull/44853#discussion_r4296323074). Implementation details: * One-directional reachability results can also be proven for semigroups and monoids. I chose to implement one such result for monoids: `reachable_mulCayley_mul_of_mem_submonoidClosure`. * Machinery with values of darts can be useful for further proofs when working with Cayley graphs in geometric group theory. Edit: made private for now as per reviewer's comment. Use of AI: I used Claude Opus 5.5 for the following tasks: * To brainstorm and compare API design ideas and naming conventions * To propose simplifications to proofs * To check docstrings for consistency All AI-generated content was reviewed and edited by me. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor t-combinatorics large-import 106/1 Mathlib/Combinatorics/SimpleGraph/Cayley.lean 1 11 ['SnirBroshi', 'dkaysin', 'github-actions'] nobody
32-81403
1 month ago
32-81633
32 days ago
32-84050
32 days
0
44864 user202729
author:user202729
feat(Order/Bounds): notation for sSup and sInf Also fix a typo (add a full stop) and change some call sites to use the new notation. --- As discussed on Zulip: https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Adding.20notation.20for.20sSup.2FsInf.3F t-topology new-contributor 14/3 Mathlib/Order/Bounds/Defs.lean,Mathlib/Order/SetNotation.lean,Mathlib/Topology/Sets/Closeds.lean,Mathlib/Topology/Sets/Opens.lean 4 5 ['Multramate', 'github-actions', 'user202729'] nobody
32-19472
1 month ago
37-79151
37 days ago
37-82857
37 days
0
45111 will1491
author:will1491
feat(Topology/ContinuousMap): define normal families Define `IsNormalFamily` for families of continuous maps into `OnePoint Y` as compactness of their closure in the compact-open topology. The one-point compactification is chosen for applications in complex dynamics. See the [Zulip discussion](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Geometry.20and.20complex.20dynamics.20formalization/with/615696635) for the definition and design discussion. Co-authored-by: Lasse Rempe <lasse.rempe@manchester.ac.uk> Co-authored-by: Filip Moruś <filip.morus@postgrad.manchester.ac.uk> --- t-topology new-contributor 30/0 Mathlib.lean,Mathlib/Topology/ContinuousMap/NormalFamily.lean 2 3 ['JX-Mo', 'github-actions'] nobody
32-10902
1 month ago
32-45601
32 days ago
32-45546
32 days
0
45135 rmcrkd
author:rmcrkd
feat(Analysis/Calculus/Deriv/Inverse): add HasDerivWithinAt.of_local_left_inverse Add lemma `HasDerivWithinAt.of_local_left_inverse`, following the existing pattern via `HasDerivWithinAt.hasFDerivWithinAt_equiv`. Assisted by Claude (found the gap, helped with learning and examples, linting and building). --- [#mathlib4 > HasDerivWithinAt.of_local_left_inverse](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/HasDerivWithinAt.2Eof_local_left_inverse/with/633245785) t-analysis new-contributor 18/0 Mathlib/Analysis/Calculus/Deriv/Inverse.lean 1 9 ['github-actions', 'grunweg', 'rmcrkd'] nobody
31-65233
1 month ago
31-65233
31 days ago
31-66213
31 days
0
45176 marcelolynch
author:marcelolynch
ci: shake Archive and Counterexamples in the weekly shake job This PR adds `Archive` and `Counterexamples` to the weekly `lake shake` job. The job fetches their oleans with `lake exe cache get Archive.lean Counterexamples.lean` and builds them before it runs `lake shake`. Five files get `shake: keep` annotations. `lake shake` does not see the uses inside `example` declarations or the `deriving Fintype` handler. Without the annotations, its edits break these files. With the annotations, the 76 shake edits to `Archive` and `Counterexamples` build. A fork PR runs the workflow file from `master`, so this PR cannot test the workflow change in CI. 🤖 new-contributor 10/10 .github/workflows/shake.yaml,Archive/Examples/Eisenstein.lean,Archive/Imo/Imo1988Q6.lean,Archive/Wiedijk100Theorems/Konigsberg.lean,Counterexamples/OrderedCancelAddCommMonoidWithBounds.lean,Counterexamples/ZeroDivisorsInAddMonoidAlgebras.lean 6 2 ['github-actions'] nobody
30-83269
30 days ago
30-83269
30 days ago
30-83214
30 days
0
44810 zixiaowang17
author:zixiaowang17
feat(Combinatorics): add abstract graphical Markov properties Introduce the global, local, and pairwise Markov properties for undirected graphs, and prove the forward implications global → local → pairwise under the semigraphoid axioms. The implementation is a single module importing `Mathlib.Combinatorics.SimpleGraph.Walk.Basic`. The current framework allows arbitrary vertex types, including infinite and uncountable types. Reference: David Montague and Bala Rajaratnam, *Graphical Markov models for infinitely many variables*, *Transactions of the American Mathematical Society* **370** (2018), no. 11, 7557–7603. [doi:10.1090/tran/7048](https://doi.org/10.1090/tran/7048). --- I want to introduce “a graphical framework in which we can analyze the Markov properties from a purely set theoretic perspective which is independent of probability theory,” as described in [Section 4](https://arxiv.org/pdf/1501.07878#page=8). Motivation: I was trying to provide a common foundation connecting graphical models in statistics, random fields, and percolation on lattices. Along the way, I found that most of the materials I read assumed finite vertex sets. However, I want to understand better what drives the equivalence of the Markov properties, so that we can talk about theorems with more flexibility. I then found this paper, which, in Section 4, takes a purely set-theoretic approach to independence and graphical Markov properties, separately from its treatment of measure-theoretic conditional independence in probabilistic models. If this PR meets the requirements and is in the right direction, I plan to finish proving the equivalence of the pairwise, local, and global Markov properties for ternary relations under suitable intersection assumptions. In the long term, I plan to connect conditional independence in probability with graphical models, including DAGs. AI assistance: OpenAI Codex assisted with the Lean definitions and proofs. I checked every line of the code. t-combinatorics LLM-generated new-contributor 231/0 Mathlib.lean,Mathlib/Combinatorics/SimpleGraph/Markov.lean,docs/references.bib 3 4 ['github-actions', 'zixiaowang17'] nobody
27-79624
27 days ago
40-55074
40 days ago
40-55019
40 days
0
44978 ArtificialZeng
author:ArtificialZeng
feat(Analysis/Normed/Module): uniform bounds for compact injective families A continuous family of injective continuous linear maps, with finite-dimensional source over a complete nontrivially normed field, has a uniform positive lower bound on a compact parameter set. A second lemma gives a uniform operator-norm perturbation radius preserving injectivity; the perturbing family need not be continuous. These estimates support compact-family derivative perturbation arguments. The proof uses `LinearMap.exists_antilipschitzWith` and `IsCompact.induction_on`, adds no imports, and does not require the target to be finite-dimensional or complete. --- Local validation on base `4c71e7e7e5f99e938e520c4242aaf2522a594953`, Lean 4.36.0-rc1: - `lake build Mathlib.Analysis.Normed.Module.FiniteDimension` passed after refreshing the base's dependency cache. - Standard Mathlib source linters and examples covering a nonconstant compact family, empty sets, and a zero-dimensional source passed. - A separate fresh compilation and axiom queries passed; both lemmas use only `propext`, `Classical.choice`, and `Quot.sound`. - The same new proofs and a downstream derivative-estimate consumer also compiled against the pinned Lean 4.35.0 baseline. AI disclosure: OpenAI Codex generated and adapted the proofs and performed automated source review and local checks. This draft is pending human review of the mathematics and API choices. Automated checks and AI review do not replace that review. Full upstream CI is still required. t-analysis LLM-generated new-contributor 57/0 Mathlib/Analysis/Normed/Module/FiniteDimension.lean 1 3 ['ArtificialZeng', 'github-actions'] nobody
27-79408
27 days ago
35-78299
35 days ago
35-78244
35 days
0
41053 hawkrobe
author:hawkrobe
refactor(RingTheory): bialgebra and Hopf algebra structures on RingCon quotients --- Since #40451, SymmetricAlgebra R M is (symRingCon R M).Quotient, which the ideal quotients of #39790 don't cover. This PR adds the congruence-level constructions, so SymmetricAlgebra's bialgebra and Hopf algebra structures can descend from TensorAlgebra as suggested in #39579, once #31898 lands. - [x] depends on: #41052 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory new-contributor 154/41 Mathlib/RingTheory/Bialgebra/Quotient.lean,Mathlib/RingTheory/HopfAlgebra/Quotient.lean 2 6 ['github-actions', 'hawkrobe', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
27-61574
27 days ago
34-61252
34 days ago
34-66621
34 days
0
45136 raja-19
author:raja-19
chore(RingTheory/MvPolynomial/Homogeneous): add lemmas These lemmas are used in the proof that the Motzkin polynomial is not expressible as a polynomial sum of squares: #45138. t-ring-theory new-contributor 52/0 Mathlib/RingTheory/MvPolynomial/Homogeneous.lean 1 9 ['github-actions', 'raja-19', 'vihdzp', 'wwylele'] nobody
27-16123
27 days ago
31-82690
31 days ago
31-82635
31 days
1
45137 raja-19
author:raja-19
chore(Algebra/Polynomial/BigOperators): add `natDegree_sum_pow_eq_of_even` This lemma is used in the proof that the Motzkin polynomial is not expressible as a polynomial sum of squares: #45138 . t-algebra new-contributor
label:t-algebra$
125/0 Mathlib/Algebra/Polynomial/BigOperators.lean,Mathlib/Algebra/Polynomial/Degree/Operations.lean,Mathlib/Order/WithBot.lean 3 20 ['SnirBroshi', 'github-actions', 'raja-19', 'wwylele'] nobody
27-14108
27 days ago
30-69426
30 days ago
31-62027
31 days
1
42189 cameronfreer
author:cameronfreer
feat(ModelTheory/Basic): add characterization of languages with countably many symbols Add the instance `Countable.countable_relations`, the counterpart of `Countable.countable_functions`, and relate `Countable L.Symbols` and `L.card ≤ ℵ₀` to the separate countability of function and relation symbols, which is how model-theoretic statements usually assume a countable language: * `countable_symbols_iff : Countable L.Symbols ↔ Countable (Σ l, L.Functions l) ∧ Countable (Σ l, L.Relations l)` * `card_le_aleph0_iff_countable : L.card ≤ ℵ₀ ↔ Countable (Σ l, L.Functions l) ∧ Countable (Σ l, L.Relations l)` Also add a general instance `Countable.countable_sum` for `L.sum L'`, move the `constantsOn` instance from `Encoding.lean` to `LanguageMap.lean` as `Countable.countable_constantsOn`, and replace the `withConstants` instance in `Encoding.lean` with `Countable.countable_withConstants` in `LanguageMap.lean`, derived from the sum instance. --- For example, [`Descriptive/Polish.lean#L46`](https://github.com/cameronfreer/infinitary-logic/blob/1a478e80794080a536931c029281bb65266b3171/InfinitaryLogic/Descriptive/Polish.lean#L46) in cameronfreer/infinitary-logic assumes only that the relation symbols are countable. Thanks to @NoneMore for suggesting the `Encoding.lean` cleanup. 🤖 These proofs were written with the assistance of Claude Opus 5 high and reviewed by GPT Sol 5.6 xhigh. t-logic new-contributor LLM-generated 33/12 Mathlib/ModelTheory/Basic.lean,Mathlib/ModelTheory/Encoding.lean,Mathlib/ModelTheory/LanguageMap.lean 3 5 ['NoneMore', 'cameronfreer', 'github-actions'] nobody
25-68356
25 days ago
116-26935
116 days ago
116-30088
116 days
0
42758 cameronfreer
author:cameronfreer
feat(ModelTheory): add syntax and semantics for infinitary logic Add syntax and semantics for the infinitary logics L∞ω and Lω₁ω. In `BoundedFormulaInf L ι α n`, the `iSup`/`iInf` constructors are indexed by a single type `ι`, which is used for every infinitary conjunction and disjunction in a formula. The specialization ```lean abbrev BoundedFormulaω (α : Type u') (n : ℕ) := L.BoundedFormulaInf ℕ α n ``` lives in the same universe as the finitary `BoundedFormula`, as suggested by @plp127 in [#mathlib4 > ModelTheory: API for infinitary formulas of L_{∞,ω} @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/ModelTheory.3A.20API.20for.20infinitary.20formulas.20of.20L_.7B.E2.88.9E.2C.CF.89.7D/near/613390601). Also add derived connectives with `alls`/`exs`, `Realize` with `simp` lemmas for each constructor and derived connective, and the embedding `BoundedFormula.toInf` with `realize_toInf`. --- I developed this with extensive assistance from several Claude and GPT models along with [lean4-skills](https://github.com/cameronfreer/lean4-skills) and [lean-lsp-mcp](https://github.com/oOo0oOo/lean-lsp-mcp) as part of the ongoing project [cameronfreer/infinitary-logic](https://github.com/cameronfreer/infinitary-logic/). t-logic LLM-generated new-contributor 446/0 Mathlib.lean,Mathlib/ModelTheory/Infinitary/Semantics.lean,Mathlib/ModelTheory/Infinitary/Syntax.lean,MathlibTest/InfinitarySyntax.lean 4 4 ['cameronfreer', 'github-actions'] nobody
25-68346
25 days ago
100-49426
100 days ago
100-49371
100 days
0
45404 davidiach
author:davidiach
feat(InformationTheory/KullbackLeibler): add restriction lemmas Restricting two finite measures to the same set decreases their KL divergence. This PR adds the integral identity that explains why, and the inequality that follows from it. Neither lemma requires the set to be measurable. Both concern restrictions without normalization and build on the existing `klFun` API. Verified against current mathlib on Lean 4.36.0-rc2, including builds, linters, and axiom checks. AI assistance: Astra Pro identified the contribution; Codex extracted and refined the proofs, checked for duplicates, and ran verification. t-measure-probability LLM-generated new-contributor 32/0 Mathlib/InformationTheory/KullbackLeibler/Basic.lean 1 3 ['davidiach', 'github-actions'] nobody
25-22520
25 days ago
25-23015
25 days ago
25-22960
25 days
0
45409 JackFeliks
author:JackFeliks
feat(Analysis/SpecificLimits): bound alternating series error from convergence Our change allows the same error bound to be used in more cases, for example when calculating π/4 using the Leibniz series. Existing uses continue to work. --- I came up with this contribution while testing my own experimental stack of algorithms. Codex prepared the code and tests, and Argon reviewed the proposal. t-analysis LLM-generated new-contributor 81/27 Mathlib/Analysis/Real/Pi/Leibniz.lean,Mathlib/Analysis/SpecificLimits/Normed.lean,MathlibTest/AlternatingSeries.lean 3 3 ['JackFeliks', 'github-actions'] nobody
25-9964
25 days ago
25-13517
25 days ago
25-13462
25 days
0
45441 janbernloehr
author:janbernloehr
feat(Analysis/Normed/Operator/Compact): preserve compact remainders under one-sided inverses Add `IsCompactOperator.sub_id_of_rightInverse` and `IsCompactOperator.sub_id_of_leftInverse`: if `f - id` is compact and `g` is a continuous linear right or left inverse of `f`, then `g - id` is compact. Work over an arbitrary ring and a module whose underlying additive group is a topological group. The proofs use compactness under composition and negation, through the identities `(f - id) ∘L g = id - g` and `g ∘L (f - id) = id - g`. These lemmas are used in my thesis formalization to show that compact derivative remainders are preserved under inverse coordinate changes. They package an elementary consequence of compactness being preserved under composition with continuous linear maps and negation. --- Local validation passed with Lean `v4.36.0-rc2`: the affected-module build, style lint, axiom checks, standalone usage examples, and `git diff --check`. There are no PR dependencies. AI assistance: OpenAI Codex was used when writing the Lean proofs. Related background: #35048 (the existing Fredholm alternative), #39274 (broader Fredholm infrastructure), and #43906 (a closed, unmerged compact-perturbation development). t-analysis new-contributor LLM-generated 37/0 Mathlib/Analysis/Normed/Operator/Compact/Basic.lean 1 2 ['github-actions'] nobody
24-58306
24 days ago
24-61681
24 days ago
24-61626
24 days
0
45444 janbernloehr
author:janbernloehr
feat(Analysis): characterize weighted summability by geometric tails Add `ENNReal.tsum_rpow_mul_lt_top_iff_geometric_tails`: for $f:I\to[0,\infty]$, a size map $\nu:I\to\mathbb N$, a real base $b>1$, a positive integer cutoff $M$, and real $t>0$, set $$ \begin{aligned} S&:=\sum_i f_i, & W_t&:=\sum_i(1+\nu(i))^t f_i,\\ T_k&:=\sum_{\nu(i)\ge b^kM}f_i, & G_t&:=\sum_{k=0}^{\infty}b^{kt}T_k. \end{aligned} $$ Prove the quantitative ENNReal estimates $$ W_t\le(1+bM)^t(S+G_t), \qquad G_t\le\frac{b^t}{b^t-1}\,W_t, $$ and hence the equivalence $$ W_t<\infty \quad\Longleftrightarrow\quad S<\infty\;\land\;G_t<\infty. $$ The estimates allow infinite coefficients and divergent sums; the first also holds at order zero. Use nonnegative double-sum interchange and finite geometric-series estimates, then derive the real-valued summability criteria as corollaries. No monotonicity of the coefficients or finiteness of the size-map fibers is required. This criterion is used in the formalisation of my dissertation, in a weighted-regularity argument. --- Local validation passed with Lean `v4.36.0-rc2`: the affected-module build, style lint, 15 linters, axiom checks, standalone usage examples (including the nonintegral base $b=3/2$ and natural-base specialisations), and `git diff --check`. There are no PR dependencies. AI assistance: OpenAI Codex was used to adapt and generalize the proofs for the ENNReal formulation. t-analysis new-contributor LLM-generated 274/0 Mathlib.lean,Mathlib/Analysis/SummableGeometricTails.lean 2 2 ['github-actions'] nobody
24-58301
24 days ago
24-59349
24 days ago
24-59294
24 days
0
45445 janbernloehr
author:janbernloehr
feat(Analysis/Normed/Lp): detect PiLp norms by conjugate pairings Add norm-attaining conjugate test vectors for finite real or complex `PiLp` spaces, and deduce a criterion for bounding the norm from all conjugate-unit-ball pairings. Include the corresponding Hölder bound, both endpoint pairs `(1, ∞)` and `(∞, 1)`, and empty index types. Use the bilinear pairing `∑ i, a i * b i`, with conjugation incorporated into the test vector, so the results support holomorphic interpolation. Reuse `NNReal.isGreatest_Lp` for finite exponents and handle the endpoints explicitly. These lemmas are used in the formalization of my dissertation to recover ℓp norm bounds from finite test-pairing estimates in the discrete Hilbert-transform argument. --- ## Dependencies and merge order No prerequisite PRs. Merge this before #45447, which is stacked on this change. The coordinate-restriction contribution is independent. ## Validation Checked using Lean `v4.36.0-rc2`: - Module build, style linter and declaration linters. - Real/complex examples, p=2, both conjugate endpoint pairs and an empty index type. - Generated import and diff/whitespace checks. - Axiom inspection: only `propext`, `Classical.choice`, `Quot.sound`. ## AI assistance OpenAI Codex has been used in the writing of the Lean implementation. t-analysis LLM-generated new-contributor 167/0 Mathlib.lean,Mathlib/Analysis/Normed/Lp/PiLpDual.lean 2 2 ['github-actions'] nobody
24-58296
24 days ago
24-59010
24 days ago
24-58955
24 days
1
41466 EzequielS2
author:EzequielS2
feat(Algebra/Order): stronger sublist product inequality via diff ## Summary Add `Sublist.prod_le_prod'_of_mem_diff` and `Sublist.sum_le_sum_of_mem_diff`. ## Test plan - [x] `lake build` and `lake exe runLinter` on `Mathlib.Algebra.Order.BigOperators.Group.List` t-algebra new-contributor
label:t-algebra$
12/4 Mathlib/Algebra/Order/BigOperators/Group/List.lean 1 8 ['EzequielS2', 'github-actions', 'mathlib-merge-conflicts', 'themathqueen', 'wwylele'] nobody
24-41932
24 days ago
24-42836
24 days ago
65-59744
65 days
0
41449 EzequielS2
author:EzequielS2
feat(Topology/ContinuousMap): domMulAct action on C(X, Y) ## Summary - Define the action of `Mᵈᵐᵃ` on `C(α, β)` when `M` acts continuously on `α`. - Add `SMul`, `MulAction`, `SMulCommClass`, and `ContinuousSMul` instances. - Closes #5379. ## Test plan - [x] `lake build Mathlib.Topology.ContinuousMap.DomAct` - [x] `lake exe runLinter Mathlib.Topology.ContinuousMap.DomAct` t-topology new-contributor 105/0 Mathlib.lean,Mathlib/Topology/ContinuousMap/DomAct.lean 2 7 ['EzequielS2', 'github-actions', 'j-loreaux'] nobody
24-39726
24 days ago
24-40534
24 days ago
45-71663
45 days
1
45482 chenle02
author:chenle02
feat(Analysis/Distribution/SchwartzSpace): the Schwartz space on a finite-dimensional space is separable ## What is proved In `Mathlib/Analysis/Distribution/SchwartzSpace/Separable.lean`: ```lean instance SchwartzMap.instSecondCountableTopology {E F : Type*} [NormedAddCommGroup E] [NormedSpace ℝ E] [NormedAddCommGroup F] [NormedSpace ℝ F] [FiniteDimensional ℝ E] [SecondCountableTopology F] : SecondCountableTopology 𝓢(E, F) ``` so `SeparableSpace 𝓢(E, F)` is found by instance search, for example for `𝓢(EuclideanSpace ℝ (Fin d), ℂ)`, and in particular for `𝓢(ℝ, ℝ)`. There are two supporting instances, both stated in general form: ```lean -- Mathlib/Topology/Compactification/OnePoint/Basic.lean instance OnePoint.instSecondCountableTopology [WeaklyLocallyCompactSpace X] [R1Space X] [SecondCountableTopology X] : SecondCountableTopology (OnePoint X) -- Mathlib/Analysis/Distribution/SchwartzSpace/Separable.lean instance ContinuousMultilinearMap.instSecondCountableTopologyFin [FiniteDimensional 𝕜 E] [SecondCountableTopology F] (n : ℕ) : SecondCountableTopology (E [×n]→L[𝕜] F) ``` ## Proof idea * For `f : 𝓢(E, F)`, the function `x ↦ ‖x‖ ^ k • iteratedFDeriv ℝ n f x` tends to `0` along `cocompact E`, because it is bounded by `‖x‖⁻¹ * seminorm (k + 1) n f`. It therefore extends by `0` to a continuous function on `OnePoint E`, and the sup norm of that extension is exactly `SchwartzMap.seminorm ℝ k n f`. * The resulting map `𝓢(E, F) →L[ℝ] Π (k, n), C(OnePoint E, E [×n]→L[ℝ] F)` is inducing, because each Schwartz seminorm is the norm of one coordinate. * Its target is second countable. `OnePoint E` is compact and second countable (new instance), `E [×n]→L[ℝ] F` is second countable (new instance, proved by induction via currying from the existing `E →L[𝕜] F` instance), and `ContinuousMap.instSecondCountableTopology` gives the rest. ## History of this PR The first version of this PR proved only the case `E = ℝ`, by bounding each Schwartz seminorm by the `L¹` norm of a derivative (`norm_le_integral_norm_deriv`, `derivCLM_pow_apply`). The general argument above covers `E = ℝ`, so that `L¹` proof and its two auxiliary lemmas have been removed. The file now depends only on `SchwartzSpace.Basic`, not on `SchwartzSpace.Deriv` and the integration library. ## Follow-ups * `ContinuousMultilinearMap.instSecondCountableTopologyFin` could be moved next to the `E →L[𝕜] F` instance in `Mathlib/Analysis/Normed/Module/FiniteDimension.lean`, possibly in a more general form (a `Fintype` index with finite-dimensional factors). It sits in this file for now so that the PR does not trigger a rebuild of most of the analysis library. * Consequences that need separability, for example for tempered distributions. AI tools (Claude and Codex) were used to port and adapt this proof to Mathlib; the author reviewed it. t-analysis new-contributor LLM-generated 177/0 Mathlib.lean,Mathlib/Analysis/Distribution/SchwartzSpace/Separable.lean,Mathlib/Topology/Compactification/OnePoint/Basic.lean 3 3 ['github-actions', 'lua-vr'] nobody
23-57201
23 days ago
23-64389
23 days ago
23-64334
23 days
0
44906 yudukikun5120
author:yudukikun5120
feat(Archive): formalize negation in vector logic This adds a formalization of negation in Mizraji's two-valued vector logic to `Archive/VectorLogic.lean`, using mathlib's matrix and real-number APIs. For two orthonormal real vectors `s` and `n` in an arbitrary finite-dimensional coordinate space, define `N = nsᵀ + snᵀ` and the logical identity `I₂ = ssᵀ + nnᵀ`. Prove that negation exchanges the truth vectors, exchanges the coefficients of their linear combinations, and satisfies `N * N = I₂`. Double negation fixes every linear combination of the truth vectors. The formalization also shows that negation annihilates vectors orthogonal to both, so it does not assert that `N²` is the ambient identity in higher dimension. The definitions follow Eduardo Mizraji's *Vector logics: The matrix-vector representation of logical calculus* (1992), as reproduced in §4.2, equations (15)–(16), of his 2016 paper: https://doi.org/10.1387/theoria.13959. --- This is a draft for feedback on whether this paper-specific formalization is suitable for `Archive`; its placement has not been agreed with maintainers. Validation on macOS arm64 with Lean 4.35.0: - `lake build Archive.VectorLogic` - `lake exe lint-style Archive.VectorLogic` - `lake exe mk_all --lib Archive --check` - Separate local checks with a three-dimensional truth pair, including a counterexample to the ambient identity assertion. AI disclosure: OpenAI Codex generated the implementation, proofs, and this PR description, and ran the local validation. The changes are marked as LLM-generated. This description does not claim completion of independent human review. LLM-generated new-contributor t-data 102/0 Archive.lean,Archive/VectorLogic.lean 2 3 ['github-actions', 'yudukikun5120'] nobody
23-51714
23 days ago
38-1103
38 days ago
38-1048
38 days
0
45470 benpigchu
author:benpigchu
feat(Data): theorem about `List.splitBy` of `List.append` when `getLast` of the first list and `head` of the second list are related This PR add a theorem describing the behaviour of `List.splitBy` of `List.append` when the `ha` assumption in `List.splitBy_append` does not hold. --- This theorem came from https://github.com/dwrensha/compfiles/blob/1745e6ced3e671bd74417548494b034eb2c87da8/Compfiles/Imo2022P1.lean#L148 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data new-contributor 59/0 Mathlib/Data/List/SplitBy.lean 1 2 ['github-actions'] nobody
23-44087
23 days ago
23-85267
23 days ago
23-85212
23 days
0
45494 chenle02
author:chenle02
feat(MeasureTheory): the cylinder σ-algebra on the weak dual This PR adds `Mathlib/MeasureTheory/Constructions/WeakDual.lean`, which defines the cylinder σ-algebra on `WeakDual 𝕜 E` (the σ-algebra generated by the evaluations `T ↦ T x`) and proves that a finite measure for it is determined by its finite-dimensional marginals. ## Statements The setting is the general one of `WeakDual`: `𝕜` a commutative topological semiring with `[MeasurableSpace 𝕜]`, and `E` a topological `𝕜`-module. * `WeakDual.cylinderMeasurableSpace 𝕜 E : MeasurableSpace (WeakDual 𝕜 E)`, defined as `MeasurableSpace.comap (fun T x ↦ T x) MeasurableSpace.pi`. This mirrors the definition of the weak-* topology as an induced topology. * `cylinderMeasurableSpace_eq_iSup`: it equals `⨆ x, MeasurableSpace.comap (fun T ↦ T x) ‹_›`. * `measurable_cylinder_iff`: a map `f : α → WeakDual 𝕜 E` is measurable iff `fun a ↦ f a x` is measurable for every `x`. Also `measurable_eval_cylinder` and `measurable_coeFn_cylinder`. * `cylinderMeasurableSpace_le_borel` (needs `[BorelSpace 𝕜]`): it is contained in `borel (WeakDual 𝕜 E)`. `cylinderMeasurableSpace_le` gives the same for any `OpensMeasurableSpace` structure. * `ext_of_forall_finset_map_eq`: two measures `μ ν`, with `μ` finite, are equal if `μ.map (fun T (x : I) ↦ T x) = ν.map (fun T (x : I) ↦ T x)` for every `I : Finset E`. * `map_eq_iff_forall_finset_map_eq`: two a.e.-measurable random elements `X : Ω → WeakDual 𝕜 E` and `Y : Ω' → WeakDual 𝕜 E` (under a finite `P` and `P'`) have the same law iff they have the same finite-dimensional laws. This is the analogue of `ProbabilityTheory.map_eq_iff_forall_finset_map_restrict_eq` for processes. * `cylinderMeasurableSpace_eq_comap_of_denseRange` (needs `[FrechetUrysohnSpace E] [PseudoMetrizableSpace 𝕜] [BorelSpace 𝕜]`): for any `d : ι → E` with `DenseRange d`, the σ-algebra is `comap (fun T i ↦ T (d i)) pi`. * `ext_of_forall_finset_map_eq_of_denseRange`: under the same hypotheses, it is enough to compare finite-dimensional marginals along `d`. * `countablyGenerated_cylinderMeasurableSpace`: if in addition `E` is separable and `𝕜` is countably generated, then the cylinder σ-algebra is countably generated. ## Design: a `def`, not an instance The measurable structure of a topological type in Mathlib is normally its Borel σ-algebra, and lemmas such as `Continuous.measurable` rely on `OpensMeasurableSpace`. On `WeakDual 𝕜 E` the cylinder σ-algebra is contained in the Borel σ-algebra, but the two are different in general. Equality needs extra hypotheses, for instance E separable Fréchet/nuclear, and that is not proved here. A global instance would therefore close off the Borel choice for every user of `WeakDual`. So the σ-algebra is a `def` marked `@[instance_reducible]`, in the same way as `borel` and `cylinderEvents`, and users enable it with `attribute [local instance] WeakDual.cylinderMeasurableSpace`. This adds no global instance and creates no diamond. `WeakDual` is a non-reducible `def`, so the norm-Borel instance `ContinuousLinearMap.instMeasurableSpace` on `E →L[𝕜] F` (for normed `E`) does not apply to it. I checked that `MeasurableSpace (WeakDual ℝ ℝ)` still fails to synthesize after importing that file. A downstream project that wants an instance can set `instance : MeasurableSpace (WeakDual 𝕜 E) := WeakDual.cylinderMeasurableSpace 𝕜 E` on its own type synonym. Projects that do this all get the same σ-algebra. ## Proof idea The coercion `F : T ↦ (x ↦ T x)` generates the σ-algebra by definition. Hence `μ.map F` and `ν.map F` are both projective limits of the same family of finite-dimensional laws, and `IsProjectiveLimit.unique` makes them equal. Every measurable set has the form `F ⁻¹' t`, so `μ = ν` follows. For the dense-range version, `T x` is the limit of `T (d (j n))` along a sequence (Fréchet–Urysohn, and each `T` is continuous), so `measurable_of_tendsto_metrizable` shows that the evaluations along `d` already generate the σ-algebra. ## Prior art * Two projects outside Mathlib already define this σ-algebra, each as a global instance: * mrdouglasny/gaussian-field defines `instMeasurableSpaceConfiguration` on `Configuration E := WeakDual ℝ E` as `comap (fun ω f ↦ ω f) pi`. It proves `configuration_measurable_of_eval_measurable` and, for Gaussian measures, `pushforward_eq_of_eval_eq`. * mrdouglasny/bochner (`Minlos/NuclearSpace.lean`) defines an instance on `WeakDual ℝ E` as `⨆ f, (borel ℝ).comap (· f)`. These two definitions are not defeq, so importing both projects fails to synthesize instances; gaussian-field's notes record this. A shared definition in Mathlib avoids that diamond. No code was taken from either project. * Mathlib has `cylinderEvents` and `measurableCylinders` on product types, and `ProbabilityTheory.map_eq_iff_forall_finset_map_restrict_eq` for processes. Neither covers `WeakDual`, and Mathlib has no `MeasurableSpace` on `WeakDual`, `WeakBilin` or `WeakSpace`. * Open PRs: a search for WeakDual measurable, cylinder, Minlos, nuclear, "random distribution" and "measure on dual" found no overlapping PR. #42278 (nuclear spaces) touches no measurable structure on duals, but it would be a natural input to a later Minlos theorem. #44909 (Kolmogorov extension) covers existence on product spaces, so it complements the uniqueness result here. * Zulip could only be searched through the public web archive, which showed no prior thread. ## Follow-ups * The Bochner–Minlos theorem on duals of nuclear spaces, stated for this σ-algebra. * Borel = cylinder on `WeakDual 𝕜 E` under suitable separability hypotheses (e.g. separable Fréchet `E`). This would allow a `BorelSpace` statement for the cylinder σ-algebra. * Tempered distributions: once the `SeparableSpace 𝓢(ℝ, ℝ)` instance (#45482) lands, `countablyGenerated_cylinderMeasurableSpace` and `ext_of_forall_finset_map_eq_of_denseRange` apply directly to `WeakDual ℝ 𝓢(ℝ, ℝ)`. `SchwartzMap` is already first-countable on master. AI tools (Claude and Codex) were used to port and adapt this proof to Mathlib; the author reviewed it. t-measure-probability new-contributor LLM-generated 245/0 Mathlib.lean,Mathlib/MeasureTheory/Constructions/WeakDual.lean 2 2 ['github-actions'] nobody
23-9423
23 days ago
23-59420
23 days ago
23-59365
23 days
0
45487 chenle02
author:chenle02
feat(Probability/Distributions/Poisson): higher moments of the Poisson distribution This PR adds a new file `Mathlib/Probability/Distributions/Poisson/Moments.lean` with the moments of the Poisson distribution `poissonMeasure r`, `r : ℝ≥0`. Main statements (namespace `ProbabilityTheory`): * `hasSum_mul_descFactorial_poissonMeasure` and `integral_descFactorial_poissonMeasure`: the factorial moments, `∫ n, (n.descFactorial k : ℝ) ∂Po(r) = r ^ k`. * `integrable_exp_mul_map_cast_poissonMeasure`, `integrableExpSet_id_map_cast_poissonMeasure`: `x ↦ exp (t * x)` is integrable for every `t`, so `integrableExpSet id Po(ℝ, r) = univ`. * `memLp_id_map_cast_poissonMeasure (p : ℝ≥0) : MemLp id p Po(ℝ, r)` and `integrable_pow_map_cast_poissonMeasure : Integrable (fun x ↦ x ^ k) Po(ℝ, r)`. * `hasSum_mul_pow_poissonMeasure` and `integral_pow_map_cast_poissonMeasure`: the raw moments are the Touchard polynomials, `∫ x, x ^ k ∂Po(ℝ, r) = ∑ j ∈ range (k + 1), S(k, j) * r ^ j` with `S(k, j) = Nat.stirlingSecond k j`. * `integral_id_map_cast_poissonMeasure : ∫ x, x ∂Po(ℝ, r) = r` * `integral_pow_two_map_cast_poissonMeasure : ∫ x, x ^ 2 ∂Po(ℝ, r) = r ^ 2 + r` * `integral_pow_three_map_cast_poissonMeasure : ∫ x, x ^ 3 ∂Po(ℝ, r) = r ^ 3 + 3 * r ^ 2 + r` * `integral_pow_four_map_cast_poissonMeasure : ∫ x, x ^ 4 ∂Po(ℝ, r) = r ^ 4 + 6 * r ^ 3 + 7 * r ^ 2 + r` * `variance_id_map_cast_poissonMeasure : Var[id; Po(ℝ, r)] = r` * `centralMoment_three_map_cast_poissonMeasure : centralMoment id 3 Po(ℝ, r) = r` * `centralMoment_four_map_cast_poissonMeasure : centralMoment id 4 Po(ℝ, r) = 3 * r ^ 2 + r` Proof idea: the factorial moment sum is reindexed by `n ↦ n + k` (the first `k` terms vanish) and becomes `r ^ k` times the total mass of `Po(r)`. Writing `n ^ k` in terms of falling factorials with `Nat.pow_eq_sum_stirlingSecond_mul_descFactorial` gives the general raw moment; the moments of order 1 to 4 are its special cases. The central moments follow by expanding `(x - r) ^ j` into raw moments, adding the corresponding `HasSum` statements and `ring`. Integrability comes from finiteness of the moment generating function via `memLp_of_mem_interior_integrableExpSet`. --- Relation to #33688: that PR adds `HasSum`/`tsum` expectation lemmas for the old `poissonPMF` / `poissonPMFReal` API in `Mathlib/Probability/Distributions/Poisson.lean`. Those declarations and that file are no longer on master (the distribution is now `poissonMeasure` in `Poisson/Basic.lean`), and #33688 is labelled `merge-conflict` / `awaiting-author`. This PR states the mean at the level of `poissonMeasure` in the same style as `integral_id_binomial` and `integral_id_gaussianReal`; it does not depend on #33688 and touches different files. AI tools (Claude and Codex) were used to port and adapt this proof to Mathlib; the author reviewed it. t-measure-probability new-contributor LLM-generated 187/0 Mathlib.lean,Mathlib/Probability/Distributions/Poisson/Moments.lean 2 2 ['github-actions'] nobody
23-9415
23 days ago
23-60425
23 days ago
23-60370
23 days
0
44613 keithadler
author:keithadler
feat(RepresentationTheory): irreducible representations are bounded by conjugacy classes For a finite group `G` and an algebraically closed field `k` in which `|G|` is invertible, `Representation.char_orthonormal` gives orthogonality of irreducible characters. This PR adds the consequence that is used in practice: * `Representation.classFunction ρ : ConjClasses G → k`, the character as a class function; * `Representation.linearIndependent_classFunction`: the class functions of a family of pairwise non-isomorphic irreducible representations are linearly independent; * `Representation.card_le_card_conjClasses`: such a family has at most `Nat.card (ConjClasses G)` members. This is the upper-bound half of "the number of irreducible representations equals the number of conjugacy classes" (the other half, that characters span the class functions, is not yet in Mathlib). The bound is exactly what is needed to show that an explicit list of `Nat.card (ConjClasses G)` pairwise non-isomorphic irreducibles is complete; e.g. with the companion PR on conjugacy classes of `Perm α`, that the Specht modules exhaust the irreducible representations of `S_n` (used downstream in https://github.com/keithadler/saxl-lean). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- t-algebra new-contributor LLM-generated
label:t-algebra$
118/0 Mathlib.lean,Mathlib/RepresentationTheory/CharacterCount.lean 2 3 ['artie2000', 'github-actions'] nobody
22-77993
22 days ago
45-69670
45 days ago
45-69615
45 days
0
45420 PSchwahn
author:PSchwahn
feat(Algebra): define sets of finite products in a magma This PR adds a file `Algebra/Products.lean` containing declarations about products of tuples of elements in a magma, together with some basic API. We plan to expand on this later. Ultimately we plan to use these to prove results about [Leibniz algebras](https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Leibniz.20algebras/with/598438796). We note that `Fin.prod` (from `Batteries.Data.Fin.Basic`) provides a similar functionality as our declaration `OrderedLeftProduct`. However `Fin.prod` requires a multiplicative unit on the magma and it associates the products to the right, whereas `OrderedLeftProduct` is associated to the left and works for any magma. This will become important because we work with non-associative operations and in the future would like to align with the literature (e.g. on Leibniz algebras). Co-authored by: Viviana del Barco, Gustavo Infanti, Artem Lopatin, Exequiel Rivas --- t-algebra new-contributor
label:t-algebra$
162/0 Mathlib.lean,Mathlib/Algebra/Products.lean 2 2 ['github-actions'] nobody
22-68493
22 days ago
24-71606
24 days ago
24-72147
24 days
0
45514 PSchwahn
author:PSchwahn
feat(Logic/Equiv/Fin/Basic): extension/deletion operations on permutations on `Fin n` Add basic operations on permutations on `Fin n`: - `Fin.Perm.castSucc`: extend a permutation on `Fin n` to one on `Fin (n + 1)` in the obvious way. - `Fin.Perm.removeNth`: removes a given position in a permutation on `Fin (n + 1)`, and collapses the domain and range to `Fin n`. Useful in conjunction with `Fin.succAbove`. Along this, add some API theorems: - `removeNth_of_castSucc_lt₁`, `removeNth_of_castSucc_lt₂`, `removeNth_of_le_castSucc₁` and `removeNth_of_le_castSucc₂` are analogous to [Fin.succAbove_of_castSucc_lt](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/Fin/SuccPred.html#Fin.succAbove_of_castSucc_lt) resp. [Fin.succAbove_of_le_castSucc](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/Fin/SuccPred.html#Fin.succAbove_of_le_castSucc). - `succAbove_removeNth` shows how `Fin.Perm.removeNth` interacts with [Fin.succAbove](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/Fin/SuccPred.html#Fin.succAbove). - `castSucc_zero` and `castSucc_succ` are simp lemmas for `Fin.Perm.castSucc`. --- new-contributor t-logic 130/0 Mathlib/Logic/Equiv/Fin/Basic.lean 1 3 ['github-actions'] nobody
22-62482
22 days ago
22-65216
22 days ago
22-65161
22 days
0
44955 user202729
author:user202729
chore: change all occurrences of equational lemma to equation lemma Change all occurrences of "equational lemma" to "equation lemma". Also add a missing apostrophe. --- As far as I can tell, both are grammatical: the "equation" in "equation lemma" is a noun adjunct, while "equational" is an adjective. It feels like noun adjunct is "more advanced English" though. Before this pull request: ("equation lemma" is more popular than "equational lemma") ``` [mathlib4]$ rg 'equational lemma'|wc -l 10 [mathlib4]$ rg 'equation lemma'|wc -l 31 [mathlib4]$ rg 'equational theorem'|wc -l 6 [mathlib4]$ rg 'equation theorem'|wc -l 2 ``` and in Lean: (same, but only slightly) ``` [lean4]$ rg 'equational lemma'|wc -l 16 [lean4]$ rg 'equation lemma'|wc -l 20 [lean4]$ rg 'equational theorem'|wc -l 85 [lean4]$ rg 'equation theorem'|wc -l 38 ``` Not sure if it's worth unifying the theorem case (probably yes. But in this case, apparently "equational theorem" is more popular than "equation theorem".), and/or unify lemma and theorem (probably not, mathlib distinguishes lemmas and theorems). new-contributor 10/10 Mathlib/Algebra/Homology/HomotopyCategory/HomComplex.lean,Mathlib/Algebra/Homology/HomotopyCategory/MappingCone.lean,Mathlib/CategoryTheory/Limits/Final.lean,Mathlib/CategoryTheory/Sites/CoversTop/Basic.lean,Mathlib/CategoryTheory/Sites/Hypercover/One.lean,Mathlib/Data/Nat/Fib/Zeckendorf.lean,Mathlib/Tactic/Eqns.lean,Mathlib/Tactic/Translate/ToAdditive.lean,docs/Conv/Guide.lean 9 4 ['SnirBroshi', 'github-actions', 'mathlib-merge-conflicts'] nobody
22-15715
22 days ago
22-19078
22 days ago
31-67217
31 days
0
43280 idontgetoutmuch
author:idontgetoutmuch
feat(Topology/VectorBundle): coordinate lemmas for the bundle of bilinear forms Coordinate lemmas for bundles of continuous linear maps. Bundle.Trivialization.continuousLinearMap_symm_apply, hom_trivializationAt_symm_apply: the inverse of the trivialization of the bundle fun x ↦ E₁ x →SL[σ] E₂ x sends a model map L to v ↦ e₂⁻¹ (L (e₁ v)). inCoordinates_apply_eq₂_of_trivial: inCoordinates_apply_eq₂ when the target bundle is trivial. trivializationAt_symm_apply_bilin: the same for bilinear maps into a fixed space, deduced from hom_trivializationAt_symm_apply. Motivation: in #33714 (existence of a Riemannian metric), the local metric is defined as the inverse trivialization applied to the inner product on the model fibre, and trivializationAt_symm_apply_bilin rewrites it as ⟪e u, e v⟫, from which symmetry and positivity follow. This PR is the first piece split out of #33714, which will be rebased on it. t-topology new-contributor 68/20 Mathlib/Topology/VectorBundle/Hom.lean,Mathlib/Topology/VectorBundle/Riemannian.lean 2 29 ['github-actions', 'grunweg', 'idontgetoutmuch'] grunweg
assignee:grunweg
21-17622
21 days ago
21-17766
21 days ago
78-40735
78 days
0
45583 ouboub
author:ouboub
feat(Analysis/ODE): Grönwall's inequality with a variable coefficient Title: feat(Analysis/ODE): Grönwall's inequality with a variable coefficient- #45583 Description: I believe I have successfully implemented and tested the differential form of Grönwall's inequality with variable coefficients. Details can be found in https://leanprover.zulipchat.com/#narrow/channel/144837-PR-reviews/topic/Gronwall.27s.20inequality.3A.20differential.20form.2C.20variable.20coeff/with/636639527 which includes two PDFs with a more detailed description. - Here is a short description: Add Grönwall's inequality in differential form with a variable coefficient `K` and a variable inhomogeneous term `ε`, both continuous and of arbitrary sign, for a function with right derivatives: if `f` is continuous on `[a, b]`, `f' t ≤ K t * f t + ε t` on `[a, b)` and `f a ≤ δ`, then on `[a, b]` `f t ≤ (δ + ∫ s in a..t, ε s / exp (∫ r in a..s, K r)) * exp (∫ s in a..t, K s)`. This addresses (for differentiable `f`) the TODO in `Mathlib/Analysis/ODE/Gronwall.lean` asking for a variable coefficient `K x` of any sign. The main results found in the new file `Mathlib/Analysis/ODE/GronwallVariableCoeff.lean` are * `gronwallBoundVar`: the bound above; * `le_gronwallBoundVar_of_deriv_right_le`: the inequality; * `gronwallBoundVar_const`: for constant `K` and `ε`, `gronwallBoundVar` agrees with the existing `gronwallBound`; * `le_mul_exp_integral_of_deriv_right_le_mul`: the homogeneous case `ε = 0`. The proof uses the integrating factor `exp (∫ s in a..t, K s)` and the comparison lemma `image_le_of_deriv_right_le_deriv_boundary`. - Some open problems: 1. The two auxiliary lemmas `continuousOn_primitive_of_continuousOn` and `hasDerivWithinAt_Ici_primitive` (one-sided FTC) are stated here; I did not find them in Mathlib. Should they move to `Mathlib/MeasureTheory/Integral/IntervalIntegral/`, or into the `intervalIntegral` namespace? 2. I did not dare to put my results into `Mathlib/Analysis/ODE/Gronwall.lean` itself, 3. There might be another TODO in the module docstring: the energy form of Bahouri–Chemin–Danchin, Lemma 3.3. At some point, I asked Claude for advice on the main lemma, but I didn't include syntax I don't understand or haven't tested. The code might be clumsy. regards Uwe Brauer t-analysis new-contributor 270/0 Mathlib.lean,Mathlib/Analysis/ODE/GronwallVariableCoeff.lean 2 4 ['github-actions', 'ouboub'] nobody
20-4014
20 days ago
20-15593
20 days ago
20-15606
20 days
0
45282 3y3y3y-huaiji
author:3y3y3y-huaiji
feat(Topology/Order): add zero-crossing for odd maps on antipodal paths Add `exists_zero_of_antipodal_path`: a continuous odd map (`f (τ x) = -f x`) along a path connecting antipodal points (`γ b = τ (γ a)`) must have a zero. This provides a direct path-lifting bridge over `intermediate_value_Icc` for spaces with domain involutions. * `exists_zero_of_antipodal_path`: main existence theorem. * `IsOddMap`: anti-invariance predicate `f (τ x) = -f x`. --- > [!NOTE] > **LLM Disclosure / AI Use**: This PR was prepared with the assistance of an LLM (`LLM-generated`). All proofs and statements have been formally verified by Lean 4 and checked with linters. t-topology LLM-generated new-contributor 71/0 Mathlib.lean,Mathlib/Topology/Order/Antipodal.lean 2 5 ['3y3y3y-huaiji', 'github-actions', 'leanprover-radar'] nobody
19-74074
19 days ago
19-74606
19 days ago
27-39904
27 days
0
42995 jacob-greenfield
author:jacob-greenfield
feat: add `List.Pairwise.orderedInsert'`, `List.sortedLE_orderedInsert_lt`, and `List.sortedGE_orderedInsert_gt` Introduce a generalized `Pairwise.orderedInsert'` lemma to prove that `Pairwise r l` is maintained after performing an `orderedInsert` using a relation stronger than `r` under certain conditions. Prove `sortedLE_orderedInsert_lt`, showing that `l.orderedInsert (· < ·) a` preserves `SortedLE` for decidable total preorders (analogously for `sortedGE_orderedInsert_gt`). This is useful for inserting an element into a sorted list *behind* any other elements which compare equal. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> I was hoping to avoid `omit`, but that would require moving all of `Pairwise.orderedInsert'`, `Pairwise.orderedInsert`, `pairwise_insertionSort`, `sublist_insertionSort'`, `pair_sublist_insertionSort'`, and `mergeSort_eq_insertionSort` after `end sort` on line 365 and reintroducing all the section variables. I also considered moving `Pairwise.orderedInsert'` somewhere _before_ `variable {α β : Type*} (r : α → α → Prop) (s : β → β → Prop)` on line 30, but that would place it before `orderedInsert` is defined. "Omit" seemed like the least invasive approach. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data new-contributor 27/11 Mathlib/Data/List/Sort.lean 1 8 ['github-actions', 'jacob-greenfield', 'theebayuser'] TwoFX
assignee:TwoFX
19-51247
19 days ago
93-41617
93 days ago
93-41562
93 days
0
45540 arsmagic
author:arsmagic
feat(RingTheory/ZMod): odd-unit square criterion in ZMod (2^n) For an odd integer a, a is a square in ZMod (2^n) iff a ≡ 1 (mod 2^min(n,3)): case forms isSquare_two_pow_iff_of_odd_three_le (n≥3, mod 8) and isSquare_two_pow_iff_of_odd_le_three (n≤3, mod 2^n), plus the uniform form. Discussed on Zulip (#Is there code for X? > Squares in ZMod (2^n) for odd units). (https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/Squares.20in.20ZMod.20.282.5En.29.20for.20odd.20units) (Xavier Roblot confirmed #45509 will not cover squares; split into two case forms per Snir Broshi's suggestion.) Adds the characterization of squares among odd (unit) residues modulo a power of two. For an odd integer a: ZMod.isSquare_two_pow_iff_of_odd_three_le — for 3 ≤ n, IsSquare (a : ZMod (2^n)) ↔ a ≡ 1 [ZMOD 8]. ZMod.isSquare_two_pow_iff_of_odd_le_three — for n ≤ 3, ↔ a ≡ 1 [ZMOD 2^n]. ZMod.isSquare_two_pow_iff_of_odd — uniform form via min n 3. Sufficiency is derived from `ZMod.isComplement'_zpowers_unitFive_neg_one` (#45509), and the custom Hensel lifting has been removed. AI-tools used during preparation. LLM-generated t-data new-contributor 128/0 Mathlib.lean,Mathlib/RingTheory/ZMod/IsSquare.lean 2 21 ['SnirBroshi', 'arsmagic', 'felixpernegger', 'github-actions', 'wwylele'] nobody
19-1342
19 days ago
21-76271
21 days ago
21-76994
21 days
0
40050 ReemMelamed
author:ReemMelamed
feat(Algebra/Group/GreensRelations): add definitions for Green's relations This PR introduces the foundational definitions for Green's relations (L, R, H, D, and J) on semigroups. This is the first in a series of PRs aimed at formalizing Green's relations for semigroups. [Zulip](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Formalization.20of.20Green.27s.20Relations.20for.20semigroups/with/598557876) --- - [x] depends on: #40843 t-algebra new-contributor
label:t-algebra$
505/0 Mathlib.lean,Mathlib/Algebra/Group/GreensRelations/Basic.lean 2 33 ['ReemMelamed', 'YaelDillies', 'YanYablonovskiy', 'github-actions', 'mathlib-bors', 'mathlib-dependent-issues'] mattrobball
assignee:mattrobball
17-51257
17 days ago
72-15200
72 days ago
92-6295
92 days
1
42226 espottesmith
author:espottesmith
feat(Combinatorics/Hypergraph): add restriction `x ≠ y` to hypergraph vertex and edge adjacency --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> This introduces a small change to the definitions of adjacency and edge-adjacency for undirected hypergraphs, based on a conversation with @Jun2M and @b-mehta in [#28613](https://github.com/leanprover-community/mathlib4/pull/28613). Previously, any two vertices (edges) `x` and `y` could be adjacent, provided that there was an edge in the edge set containing both of them (there was a vertex contained in both of them). Now, we add the restriction that `x` is not equal to `y`. This should allow `SimpleGraph` to be a clean specialization of `Hypergraph` and to ease the eventual implementation of walks. This PR has no dependencies, but see also [42164](https://github.com/leanprover-community/mathlib4/pull/42162), @Jun2M's implementation of `HyperGraphLike` and formalization that `Hypergraph`s are `HyperGraphLike`, which includes this restriction on `Adj`. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics new-contributor 4/4 Mathlib/Combinatorics/Hypergraph/Basic.lean 1 3 ['github-actions'] b-mehta
assignee:b-mehta
17-51255
17 days ago
116-24066
116 days ago
116-24011
116 days
0
42820 tolgadgrmnc27
author:tolgadgrmnc27
feat(Data/Nat/Choose): elementary Chernoff bound for tail sums of binomial coefficients Adds an elementary, purely combinatorial Chernoff-type bound on tail sums of binomial coefficients: ```lean theorem Nat.sum_Ico_choose_le_div (n m : ℕ) {x : α} (hx : 1 ≤ x) : ∑ j ∈ Ico m (n + 1), (n.choose j : α) ≤ (1 + x) ^ n / x ^ m ``` together with the specialization at `x = 2`: ```lean theorem Nat.sum_Ico_choose_le_three_pow_div (n m : ℕ) : ∑ j ∈ Ico m (n + 1), (n.choose j : α) ≤ 3 ^ n / 2 ^ m ``` The proof is the classical exponential moment trick done combinatorially: for `m ≤ j` and `1 ≤ x` we have `x ^ m ≤ x ^ j`, so the tail sum is bounded by `x ^ (-m) * ∑ j, n.choose j * x ^ j = x ^ (-m) * (1 + x) ^ n` by the binomial theorem. A helper `Nat.sum_range_choose_mul_pow` states the binomial theorem in the convenient form `∑ j ≤ n, n.choose j * x ^ j = (1 + x) ^ n`. ### Why this is not already in Mathlib * `Nat.sum_range_choose` gives the *total* sum `∑ j ≤ n, n.choose j = 2 ^ n`. * `Mathlib/Data/Nat/Choose/Bounds.lean` bounds a *single* coefficient (`choose_le_pow`, `choose_le_two_pow`, `choose_le_pow_div`, …). * `Mathlib/Probability/Moments/SubGaussian.lean` has Chernoff/Hoeffding, but measure-theoretically: using it for a counting argument requires setting up a probability space with independent Bernoulli variables and translating back to cardinalities. I could not find a statement bounding a *partial* sum of binomial coefficients. The version here needs no probability space and applies directly to counting arguments (its original use was bounding the number of `n < 2 ^ k` whose first `k` binary digits contain at least `m` ones). ### Notes * Stated over a general `[Semifield α] [LinearOrder α] [IsStrictOrderedRing α]`, matching the typeclass style of `Mathlib/Data/Nat/Choose/Bounds.lean`. * `Ico m (n + 1)` rather than a `filter (m ≤ ·)` form, as is idiomatic in Mathlib; the two are equal by `Finset.filter_le_eq_Ico`-style reasoning. * Names are of course open to bikeshedding. --- - [x] depends on: nothing t-data new-contributor 84/0 Mathlib.lean,Mathlib/Data/Nat/Choose/Tail.lean 2 3 ['github-actions'] eric-wieser
assignee:eric-wieser
17-51254
17 days ago
98-12230
98 days ago
98-12175
98 days
0
45598 JunkaiWang-TheoPhy
author:JunkaiWang-TheoPhy
feat(Analysis/Fourier): translate frequency under character modulation ## Summary This PR adds the frequency-shift identity dual to the existing translation-to-phase identity for Fourier integrals. Modulating a function by an additive character translates its Fourier transform in frequency. ## Changes - Add the general `VectorFourier.fourierIntegral_smul_addChar` identity. - Add the scalar `Fourier.fourierIntegral_smul_addChar` specialization. - Add the real inner-product-space theorem `Real.fourier_smul_fourierChar`. - Add the corresponding inverse-transform identity `Real.fourierInv_smul_fourierChar`. The general theorem is proved by pointwise equality of the integration kernels. It does not require integrability, continuity, Haar invariance, finite dimensionality, or a nondegenerate pairing beyond the assumptions already present in the Fourier integral definition. With the convention `𝓕 f w = ∫ e (-L v w) • f v`, the forward shift is `w - w₀`; the inverse-transform identity consequently uses `w + w₀`. The change is confined to `Mathlib/Analysis/Fourier/FourierTransform.lean`. It adds no definitions, imports, instances, simp attributes, or dependencies. ## Validation - `lake build Mathlib.Analysis.Fourier.FourierTransform Mathlib.Analysis.SpecialFunctions.Gaussian.FourierTransform Mathlib.Analysis.Fourier.FourierTransformDeriv` — passed (`Build completed successfully (6312 jobs)`). - `lake exe batteries/runLinter --no-build Mathlib.Analysis.Fourier.FourierTransform` — passed. - Standalone local examples covering zero modulation, degenerate pairings, non-Haar measures, non-integrable total-function cases, the inverse sign, and a modulated Gaussian derivation — passed with the repository Lean options. - `#print axioms` for the four new declarations reports only `propext`, `Classical.choice`, and `Quot.sound`. - Full `MathlibTest` and hosted CI have not been run locally; hosted CI should provide the final repository-level check. ## AI disclosure Codex (gpt-6.1-sol) assisted with candidate discovery, Lean implementation, and local verification. I have reviewed the declarations and proofs, and I am responsible for understanding and explaining the mathematical design and sign conventions. t-analysis new-contributor LLM-generated 35/2 Mathlib/Analysis/Fourier/FourierTransform.lean 1 3 ['JunkaiWang-TheoPhy', 'github-actions'] nobody
17-9821
17 days ago
19-69509
19 days ago
19-69454
19 days
0
45566 PeaBrane
author:PeaBrane
feat(Analysis/Convex): limits and sums of convex functions Add pointwise-limit and summation lemmas for convex and concave functions. * `convexOn_of_frequently_convexOn_of_tendsto`, `concaveOn_of_frequently_concaveOn_of_tendsto`: if `F i` is frequently convex (concave) on `s` along a filter and `F i x → f x` for every `x ∈ s`, then `f` is convex (concave) on `s`. * `convexOn_finsetSum`, `concaveOn_finsetSum`: a finite sum of convex (concave) functions is convex (concave). * `convexOn_tsum`, `concaveOn_tsum`: a pointwise summable series of convex (concave) functions is convex (concave). These complement `isClosed_setOfPred_convexOn` from #37352. Closedness of the set of convex functions covers limits in the product topology, which needs convergence at every point of the domain. The new limit lemmas need convergence only on `s`, and only frequently along the filter, following `monotoneOn_of_frequently_monotoneOn_of_tendsto`. Finite sums and series of convex functions were not stated before; only `ConvexOn.add` existed. I needed the series version to show that a periodic kernel defined by an image sum is convex. `FunctionTopology.lean` now imports `Mathlib.Topology.Algebra.InfiniteSum.Defs` for `tsum`. AI disclosure: the statements, the proofs, and a draft of this description were written with Claude Code. I checked them against existing Mathlib conventions and built the changed files locally. --- t-analysis LLM-generated new-contributor 69/1 Mathlib/Analysis/Convex/Function.lean,Mathlib/Analysis/Convex/FunctionTopology.lean 2 6 ['PeaBrane', 'github-actions', 'wwylele'] nobody
16-82206
16 days ago
17-72351
17 days ago
20-67721
20 days
0
42095 DrDMT-VR
author:DrDMT-VR
feat(Analysis/CStarAlgebra): the non-unital CFC maps into closed two-sided ideals ## What For a non-unital C*-algebra `A`, a closed two-sided ideal `I`, an element `a ∈ I`, and any `f : ℝ → ℝ`, this proves `cfcₙ f a ∈ I`. No hypotheses on `f` are needed: whenever `cfcₙ` would take its junk value (`f` not continuous on the quasispectrum, `f 0 ≠ 0`, or `a` not selfadjoint) that value is `0 ∈ I`. New declarations (namespace `TwoSidedIdeal`): - `smul_mem_of_isClosed` — a closed two-sided ideal in a non-unital C*-algebra is closed under the scalar action (proved via the canonical approximate unit `CStarAlgebra.approximateUnit`). - `cfcₙHom_mem_of_isClosed` — for selfadjoint `a ∈ I`, every value of the underlying homomorphism `cfcₙHom` lies in `I` (Weierstrass induction on `C(σₙ ℝ a, ℝ)₀`). - `cfcₙ_mem_of_isClosed` — the main result. ## Why Closed two-sided ideals of a C*-algebra are hereditary under the continuous functional calculus; this is a basic tool for spectral-projection and ideal-membership arguments, and complements the existing "cfc commutes with *-homomorphisms" results. `smul_mem_of_isClosed` is of independent interest (a closed two-sided ideal is a submodule). ## Notes This is my second contribution (see #42093). I checked the referenced cfc / approximate-unit API against current master at the source level; CI is the first full build and I will fix anything it flags. Suggested location `Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Ideal.lean`; happy to relocate if preferred. Parts of this contribution were developed with AI assistance (Claude). All statements are machine-checked by the Lean kernel; `#print axioms` on the new declarations reports only `[propext, Classical.choice, Quot.sound]`. t-analysis new-contributor LLM-generated 92/0 Mathlib.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Ideal.lean 2 5 ['DrDMT-VR', 'github-actions', 'grunweg'] nobody
16-59813
16 days ago
25-65013
25 days ago
27-26350
27 days
1
42363 ghseeli
author:ghseeli
feat(Combinatorics): card_le_card_biUnion_of_card_le_card This PR contributes a lemma to combinatorics, `card_le_card_biUnion_of_card_le_card`. this is a set theoretic corollary of a double counting result proved for bipartite graphs (`Finset.sum_card_bipartiteAbove_eq_sum_card_bipartiteBelow`). This result was needed for our Latin Square PR https://github.com/leanprover-community/mathlib4/pull/36698. This result was proved in less general terms in that PR, but is independent of Latin Square considerations and so we have generalized and moved it into this file. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-combinatorics new-contributor 38/0 Mathlib/Combinatorics/Enumerative/DoubleCounting.lean 1 16 ['cjrl', 'github-actions', 'vlad902', 'wwylele'] b-mehta
assignee:b-mehta
16-51253
16 days ago
99-50953
99 days ago
112-42416
112 days
1
43087 JX-Mo
author:JX-Mo
feat(RepresentationTheory): add Hecke/Basic.lean This file defines `HeckeModule` of a representation `ρ` as `Hom_G(k[G ⧸ H], ρ)` and identifies it with the space of `H`-invariants. We deliberately choose the intertwining model over the invariant model as the main API, for it has good defeq property when we define the mixed level Hecke action of Hecke operators which is just the composition of intertwining maps. This has significant technical advantage because it avoids proving associativity and compatibility combinarically which is nasty using the invariant model. It is an `abbrev` for maximally reusing API from `ofMulAction` and `IntertwiningMap`. We remark that the abstract boundary will be cut out at `HeckeAlgera` which will be a `def` instead and we will provide an instance `Module HeckeAlgebra HeckeModule`. Before that, we need to develop representation theoretic lemmas about `HeckeModule` and `HeckeBimodule` first so `HeckeModule` should stay transparent. new-contributor t-algebra
label:t-algebra$
84/0 Mathlib.lean,Mathlib/RepresentationTheory/Hecke/Basic.lean 2 8 ['JX-Mo', 'Whysoserioushah', 'github-actions'] riccardobrasca
assignee:riccardobrasca
16-51247
16 days ago
31-40254
31 days ago
90-3762
90 days
1
43886 gabriel-turinici
author:gabriel-turinici
feat(Analysis/Asymptotics): add Filter.Tendsto.weighted_cesaro_smul Adds `Filter.Tendsto.weighted_cesaro_smul`, a weighted (Toeplitz-type) generalization of `Filter.Tendsto.cesaro_smul`: if `S k → L` and `w k ≥ 0` has divergent partial sums, the weighted running average of `S` w.r.t. `w` also tends to `L`. Recovers `cesaro_smul` as the `w ≡ 1` case. Also adds `weighted_cesaro`, the real-valued convenience wrapper mirroring `cesaro`. This is a small building block toward a planned follow-up PR formalizing Kronecker's lemma, at its turn needed in some stochastic analysis setting. --- **AI disclosure**: this proof was developed using formatting assistance, library search and code corrections from Claude Code (Claude Sonnet 5) and a personal LLM automation. Alternative, shorter, proofs can be obtained with `IsLittleO`-style but that style seems too recent for me now. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis new-contributor LLM-generated 81/0 Mathlib/Analysis/Asymptotics/SpecificAsymptotics.lean 1 2 ['github-actions'] nobody
15-50352
15 days ago
66-61632
66 days ago
66-61577
66 days
0
45785 JonasReif
author:JonasReif
chore(Order/BooleanAlgebra/Set): derive `disjoint_sdiff_inter` from the Boolean algebra lemma `Set.disjoint_sdiff_inter` carried a TODO asking for a proof via a Boolean algebra lemma. The general lemma `disjoint_inf_sdiff` already exists, so the set version is now its `symm`. The statement is unchanged. --- Created with Claude Opus 5.5 in Claude Code. t-order new-contributor 1/3 Mathlib/Order/BooleanAlgebra/Set.lean 1 2 ['github-actions'] nobody
14-58359
14 days ago
14-62189
14 days ago
14-62134
14 days
0
42046 LegaSage
author:LegaSage
feat(Polynomial): add Wronskian linear dependence lemmas This extends the polynomial Wronskian API of Baek and Lee from the existing coprime case to arbitrary polynomials over a characteristic-zero field. It adds: * an explicit nontrivial scalar relation for any pair with zero Wronskian, including zero-polynomial edge cases; * scalar-multiple corollaries when either polynomial is nonzero; * the weighted derivative corollary that solutions of `a * f' - n * a' * f = 0` are scalar multiples of `a ^ n` when `a ≠ 0`. The proof factors out the polynomial gcd and applies the existing `IsCoprime.wronskian_eq_zero_iff` theorem. This PR makes no novelty claim; it packages standard consequences of the existing Baek–Lee coprime Wronskian API. ------- The implementation was prepared with assistance from OpenAI Codex and reviewed and submitted by LegaSage. t-ring-theory new-contributor large-import LLM-generated 96/1 Mathlib/RingTheory/Polynomial/Wronskian.lean 1 2 ['github-actions'] alreadydone
assignee:alreadydone
14-51253
14 days ago
121-49040
121 days ago
121-48985
121 days
0
45550 user202729
author:user202729
refactor(AlgebraicGeometry/EllipticCurve): make baseChange transparent notation - Make `baseChange` an `abbrev`, so the user doesn't need to explicitly unfold `baseChange`. - Explicitly document that `W⁄A` is equivalent to `W.map <| algebraMap R A`, so users seeing a `map` lemma applied on `W⁄S` at a use site can see why. - Rename `S` to `A` for consistency. --- As discussed in https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Expose.20public.20section.20bad.3F/with/635418753 , `W⁄A` is meant to be transparent, so I think this change is appropriate. This explicitly changes the meaning of `baseChange`, making code that previously name `baseChange` explicitly backwards incompatible, but I think this is fine. The affected proofs are fixed. I think the impact is rather minimal. The four copies of the notation in fact return the same thing, but for example `Affine R` is defined to be an `abbrev` of `WeierstrassCurve R`, so if one writes `(W⁄S).map`, the method `map` is looked up in namespace `Affine`. Without the notation in namespace `Affine`, it would implicitly convert `W` to `WeierstrassCurve`, then lookup the method `map` in namespace `WeierstrassCurve`. The `name` is added to the notation that needs linking from `baseChangeAux` to make the link in the HTML page works. (Similar to https://github.com/leanprover-community/mathlib4/pull/45129) t-algebraic-geometry new-contributor 29/41 Mathlib/AlgebraicGeometry/EllipticCurve/Affine/Basic.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Jacobian/Basic.lean,Mathlib/AlgebraicGeometry/EllipticCurve/LFunction.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Projective/Basic.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Reduction.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Weierstrass.lean 6 7 ['JX-Mo', 'github-actions', 'user202729'] kim-em
assignee:kim-em
14-51241
14 days ago
21-39075
21 days ago
21-39020
21 days
0
44853 dkaysin
author:dkaysin
feat(Geometry/Group): relate the word metric to the Cayley graph distance This PR constructs the Cayley graph (realized as a `SimpleGraph`) for a group `G` with respect to a generating family `P : Group.Generators G ι`, implements the link between walks in the Cayley graph and words, and establishes equivalence of the word metric and the distance on the Cayley graph. --- Resolves TODO from [#43118](https://github.com/leanprover-community/mathlib4/pull/43118). Implementation details: * `SimpleGraph` was chosen vs `Quiver/Schreier` because it has a more comprehensive API at the moment. More context: [Zulip thread](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Relate.20the.20word.20metric.20to.20the.20distance.20in.20the.20Cayley.20graph/with/631376709). * To accommodate possible future implementation for `Quiver/Schreier`, I've included "Simple" in the names of definitions and theorems (e.g., `cayleySimpleGraph`). * Because simple graph has no loops, in several places we have to check that a letter/generator is not trivial. Use of AI: I used Claude Opus 5.5 to help me with gathering context, designing API and implementation of several proofs. * I used AI to brainstorm and compare API design ideas based on the context from previous Zulip threads and existing repo code. * I used AI for suggesting parts of the proofs for `exists_walk_of_word` and `exists_word_of_walk` lemmas. * I used AI for checking docstrings for consistency. All AI-generated content was reviewed and edited by me. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #45359 [additivization of dependencies] t-geometric-group-theory new-contributor LLM-generated 161/3 Mathlib.lean,Mathlib/Geometry/Group/CayleySimpleGraph.lean,Mathlib/Geometry/Group/README.md,Mathlib/Geometry/Group/WordMetric.lean 4 16 ['dkaysin', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'tb65536', 'vlad902'] nobody
14-50356
14 days ago
24-73184
24 days ago
38-11503
38 days
0
45786 matt-w-horn
author:matt-w-horn
feat(Probability/Distributions): head and tail mass of the geometric distribution For `p ≠ 0` the geometric distribution gives `Iio m` mass `1 - (1 - p) ^ m` and `Ici m` mass `(1 - p) ^ m`. Split out of #42381. --- Assisted-by: Claude Fable 5.1 (code), Gemini Argon (review); used in https://github.com/matt-w-horn/overload t-measure-probability LLM-generated new-contributor 23/0 Mathlib/Probability/Distributions/Geometric.lean 1 3 ['github-actions', 'matt-w-horn'] nobody
14-45941
14 days ago
14-46004
14 days ago
14-45949
14 days
1
42487 bocowgill
author:bocowgill
feat(Algebra/BigOperators/Group/Finset/Powerset): add nested powersetCard identities This PR adds product and sum identities for nested collections of fixed-cardinality subsets. For `r ≤ k`, each `r`-element subset of a finite set `s` is contained in exactly `Nat.choose (s.card - r) (k - r)` of the `k`-element subsets of `s`. Thus, a sum over the `r`-element subsets of every `k`-element subset reduces to this multiplicity, times a single sum over `s.powersetCard r`. The product version is the analogous power identity. The proof exchanges the order of the two big operators using `Finset.prod_comm'`. It then counts each fiber with `Finset.card_filter_powersetCard_subset`. The additive identities are generated with `to_additive`. The PR also provides the useful elementwise specialization `r = 1`. **Motivation**: These results provide reusable weighted double-counting tools for finite combinatorics. They are useful in arguments about uniform set systems, incidence relations, and sums or products over fixed-cardinality subsets. --- ### LLM disclosure For theorem planning and Lean implementation, I used OpenAI Codex substantially. I also used Codex to search Mathlib and open PRs for related results, suggest naming and documentation, iterate on the proofs, audit import dependencies, and validate the commits locally. I personally reviewed the mathematical statements and Lean code line-by-line, including the naming and API choices. I also confirmed that I can explain each step of the proofs. For the current revision, I ran a targeted build of `Mathlib.Algebra.BigOperators.Group.Finset.Powerset`, the style and environment linters, and `git diff --check`. I also inspected the generated additive declarations and axiom dependencies, and tested an alternative proof using explicit incidence finsets. The complete GitHub CI suite passes. This is one of my earliest Mathlib contributions. I welcome corrections and suggestions, and I am prepared to revise the PR and learn from the review. t-algebra new-contributor LLM-generated
label:t-algebra$
27/0 Mathlib/Algebra/BigOperators/Group/Finset/Powerset.lean 1 17 ['bocowgill', 'github-actions', 'pepamontero'] alreadydone
assignee:alreadydone
13-51255
13 days ago
69-43487
69 days ago
107-71789
107 days
0
45443 janbernloehr
author:janbernloehr
feat(Analysis/ODE): add variable-coefficient integral Grönwall Add `le_mul_exp_integral_of_le_const_add_integral`, the integral Grönwall inequality with a continuous nonnegative variable coefficient. If `f t ≤ c + ∫ s in a..t, β s * f s` on `[a, b]`, conclude `f t ≤ c * exp (∫ s in a..t, β s)`. Require continuity only on the interval, with no sign assumptions on `f` or `c`. Use interval FTC and derivative monotonicity on the dominating primitive times its integrating factor. Put the theorem in a separate integral module so existing importers of differential Grönwall do not acquire FTC dependencies. This lemma is used in the formalization of my dissertation for Volterra inverse bounds and stability estimates; one concrete use is the [Volterra inverse bound](https://github.com/janbernloehr/diss-lean/blob/2091dba5870425e38372f9e0a9106c4214a1dfbe/NLS/ZakharovShabat/ClassicalVolterraL2Bound.lean#L41). Keeping the coefficient's integral in the exponential matters when integral norms are controlled but pointwise bounds are not uniform. For another contribution arising from the same dissertation formalization, see [#45441](https://github.com/leanprover-community/mathlib4/pull/45441), on compact remainders under one-sided inverses. --- ## Related work The same integral statement was previously proposed in [#37287](https://github.com/leanprover-community/mathlib4/pull/37287), which was withdrawn and not merged. The stronger variable-forcing proposal [#38829](https://github.com/leanprover-community/mathlib4/pull/38829) is also closed unmerged. Open [#39871](https://github.com/leanprover-community/mathlib4/pull/39871) concerns uniform Grönwall; its internal exponential comparison is a potential consumer of this lemma. No PR dependencies. ## Validation Checked using Lean `v4.36.0-rc2`: - Affected-module build and direct source check with warnings treated as errors. - `mk_all --lib Mathlib --check` and `lint-style`. - Default semantic linters and documentation linters. - Axiom inspection: only `propext`, `Classical.choice`, `Quot.sound`. - Clean merge simulation, diff/whitespace checks, and separate Volterra-use examples. ## AI assistance OpenAI Codex was used to write the Lean implementation. The proof design was informed by downstream proofs and the earlier proposals linked above. t-analysis LLM-generated new-contributor 70/0 Mathlib.lean,Mathlib/Analysis/ODE/GronwallIntegral.lean 2 3 ['NousVolition', 'github-actions'] nobody
13-15462
13 days ago
24-59869
24 days ago
24-59814
24 days
0
45069 korbonits
author:korbonits
feat(Geometry/Manifold): the Riemann curvature of a covariant derivative Define the Riemann curvature `R(X, Y) Z = ∇_X ∇_Y Z - ∇_Y ∇_X Z - ∇_[X,Y] Z` of a covariant derivative on the tangent bundle, as an operator on vector fields, in a new file `CovariantDerivative/Curvature.lean` (alongside `Torsion.lean`). Main results: - `CovariantDerivative.curvature_swap`: antisymmetry in the first two arguments. - `curvature_smul_left/snd`, `curvature_add_left/snd`: function-linearity in the first two arguments, with explicit differentiability hypotheses. - `tensorialAt_curvature_fst/snd`: for a `C¹` covariant derivative and a `C²` field `Z`, the curvature is `TensorialAt` in each of its first two arguments. - `CovariantDerivative.mdifferentiableAt_apply`: for a `C¹` covariant derivative, `∇_X σ` is differentiable at `x` when `σ` is `C²` and `X` is differentiable at `x`. Most of the code I'm planning to upstream into mathlib4 is already proved in https://github.com/korbonits/ricci-flow-blueprint --- AI disclosure - level: Level 5 / Level 6 in [the link shared](https://www.visidata.org/blog/2026/ai/#self-assessed-ai-level-for-contributions) I feel confident about the math but I am still learning Lean itself - code: most of the Lean in this PR was drafted by Claude Code (statements, proofs, docstrings). - direction and review: I chose the contribution, made the decisions, reviewed every line, and wrote all GitHub/Zulip comments. new-contributor t-differential-geometry LLM-generated 167/0 Mathlib.lean,Mathlib/Geometry/Manifold/VectorBundle/CovariantDerivative/Curvature.lean 2 3 ['github-actions', 'korbonits'] ocfnash
assignee:ocfnash
12-28617
12 days ago
33-37447
33 days ago
33-37392
33 days
0
45858 pelicanhere
author:pelicanhere
feat(EReal): continuity of addition by real-valued functions Add continuity lemmas for addition of real-valued functions to `EReal`-valued functions. t-topology new-contributor 13/0 Mathlib/Topology/Instances/EReal/Lemmas.lean 1 2 ['github-actions'] nobody
12-8965
12 days ago
12-21929
12 days ago
12-21874
12 days
0
45857 wobniW
author:wobniW
feat(Computability/Primrec): add Primcodable instance for empty types Add a low-priority `Primcodable` instance for any type with `[IsEmpty α]`. ### Motivation `IsEmpty.toEncodable` already gives a blanket `Encodable` instance for `[IsEmpty α]`, and `Empty` already has a `Primcodable` instance. Any empty type should have a `Primcodable` instance too. Right now, users have to build the instance by hand, via `Primcodable.ofEquiv` or by writing the instance fields manually. ### Design notes - `ofEquiv` is still the right tool when an explicit equivalence is available and definitional transparency matters. However, instance synthesis can't pick it up on its own. This blanket instance fills a gap where `[IsEmpty α]` already exists. t-computability new-contributor 3/0 Mathlib/Computability/Primrec/Basic.lean 1 4 ['github-actions', 'grunweg', 'wobniW'] nobody
12-501
12 days ago
12-501
12 days ago
12-20402
12 days
0
45868 pelicanhere
author:pelicanhere
feat(Geometry/Convex): add subgradients Define proper functions and subgradients along bilinear pairings. Prove addition and linear pullback rules, convexity of subdifferentials, and Fermat's rule. --- t-convex-geometry new-contributor 336/0 Mathlib.lean,Mathlib/Geometry/Convex/Fun/Proper.lean,Mathlib/Geometry/Convex/Fun/Subgradient/Basic.lean 3 2 ['github-actions'] nobody
11-77896
11 days ago
11-78771
11 days ago
11-78716
11 days
0
45263 huntse
author:huntse
feat(Order/Filter/Cofinite): add `Filter.countable_sets_cofinite` My first attempt at a PR for mathlib so I apologize if I'm doing it wrong. I picked up a lemma in FLT that was marked as TODO to upstream into mathlib (there it is Filter.cofinite.sets.countable in FLT/Mathlib/Order/Filter/Cofinite.lean) and upstreamed it. - I used a name which seemed more in keeping with mathlib convention but please lmk if I should rename it. Both `countable_sets_cofinite` and `cofinite_sets_countable` seemed somewhat defensible. - I changed it to a theorem since the neighbouring code seems to all be theorems. - The actual lean proof is due to kbuzzard. I just copied it upstream and made the following tweaks: - `(ι : Type*)` was not needed as that's mentioned higher in the file in a `variable` line - I removed namespacing on Filter.cofinite as we're in that namespace here already - I didn't use AI to generate this PR or description but since it's my first PR to mathlib and I'm a bit nervous I did use AI to review the PR and give me suggestions. It suggested the name change and the removal of the redundant namespacing and type info. - FLT also has a Countable instance for ↥(cofinite).sets which I left there. Co-authored-by: kbuzzard t-order FLT new-contributor 5/0 Mathlib/Order/Filter/Cofinite.lean 1 5 ['github-actions', 'huntse', 'vihdzp'] nobody
11-10824
11 days ago
28-51354
28 days ago
28-51299
28 days
0
45898 WaterKing201030
author:WaterKing201030
feat(Data/List/Chain): exists nodup isChain of relationReflTransGen The existing theorem `List.exists_isChain_cons_of_relationReflTransGen` gives chain from ReflTransGen, but do not guarantee that its elements are distinct. Chains with no duplicates are useful in many settings. For example, `SimpleGraph.Walk.bypass` removes repeated elements while preserving its endpoints. But, the adjacency relations must be symmetric and irreflexive. Add the following three theorems for arbitrary relations: 1. `List.exists_isChain_cons_nodup_sublist_of_isChain` 2. `List.exists_isChain_cons_nodup_of_relationReflTransGen` 3. `List.exists_isChain_ne_nil_nodup_of_relationReflTransGen` --- Use of AI: I asked ChatGPT to check whether these theorems duplicate existing ones. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data new-contributor 43/0 Mathlib/Data/List/Chain.lean 1 2 ['github-actions'] nobody
11-10749
11 days ago
11-20661
11 days ago
11-20606
11 days
0
41935 martinamaggio
author:martinamaggio
feat(Probability/Independence): grouping an independent family by pairwise disjoint index sets If `m : ι → MeasurableSpace Ω` is an independent family of σ-algebras and `G : ι' → Set ι` is a pairwise disjoint family of index sets, then the family of grouped σ-algebras `fun i' ↦ ⨆ j ∈ G i', m j` is again independent. This is the indexed-family version of the existing two-group lemma `indep_iSup_of_disjoint`, from which it follows by induction on the finite subfamily, peeling off one group at a time against the union of the remaining ones. As usual it is proven for the kernel notion of independence (`Kernel.iIndep_iSup_of_disjoint`) and specialized to independence w.r.t. a measure (`iIndep_iSup_of_disjoint`) and to conditional independence (`iCondIndep_iSup_of_disjoint`). The lemma is the natural bridge from an independent family to block/grouping arguments — e.g. Markov-style properties of recursions driven by disjoint sets of randomness sources. It was developed for a formalization of end-to-end latency distributions of periodic task chains, where it establishes that successive chain states, being measurable w.r.t. σ-algebras of disjoint groups of an independent family, form an independent family themselves. t-measure-probability new-contributor 56/0 Mathlib/Probability/Independence/Basic.lean,Mathlib/Probability/Independence/Conditional.lean,Mathlib/Probability/Independence/Kernel/Indep.lean 3 6 ['bocowgill', 'github-actions', 'martinamaggio'] nobody
11-7167
11 days ago
11-51408
11 days ago
35-25494
35 days
0
42718 justinhalford
author:justinhalford
feat(Combinatorics/SetFamily): the linear algebra method and the Oddtown theorem Adds the basic form of the **linear algebra method** for set families (Babai–Frankl) together with its standard first application, the **Oddtown theorem** (Berlekamp, 1969). ### What's here - `linearIndependent_of_dotProduct_eq_ite` — a family of vectors whose pairwise dot products form the identity matrix is linearly independent. Stated over an arbitrary field, so it does not rely on positivity; this is the engine of the method. - `Finset.charVec` — the characteristic vector of a finset, valued in a semiring, with `charVec_apply`. - `Finset.charVec_dotProduct_charVec` — the dot product of two characteristic vectors is the cardinality of the intersection. - `Finset.card_le_card_of_odd_card_of_even_card_inter` — **Oddtown**: a family of finsets of odd cardinality, any two of which meet in an even number of elements, has at most `Fintype.card α` members. ### Why I could not find the linear algebra method anywhere in Mathlib. Searching for `Oddtown`, `Eventown`, Fisher's inequality, `RayChaudhuri` and `FranklWilson` returns nothing, and exactly one file under `Mathlib/Combinatorics/` uses `finrank`/`LinearIndependent` (`SimpleGraph/LapMatrix.lean`, for spectral graph theory). Since the technique underlies a large family of extremal results, the general lemma is stated separately from Oddtown so that Eventown, Fisher's inequality and Ray-Chaudhuri–Wilson can be added on top later. If this does already exist under a formulation I did not think to search for, I would be glad to be pointed at it. ### Verification Compiles against `master` (Lean 4.34.0-rc1) with no errors or warnings. `#print axioms` on each of the three results reports only `[propext, Classical.choice, Quot.sound]`. No `sorry`, no new axioms, no `set_option` overrides. ### Disclosure This file was written with AI assistance (Claude Opus 5) and then checked against the Lean kernel; that is noted in the module docstring as well. Every statement, proof and docstring has been read through by me before submission. Happy to adjust naming, generality or placement to whatever the maintainers prefer. ### Process note I am a first-time contributor and I am aware the usual convention is to raise a new file on Zulip before opening a PR. Apologies for going in the other order — I am glad to move the discussion to `#mathlib4` if that is preferred, or to close this if the material is not wanted. --- [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/leanprover-community/mathlib4) t-combinatorics new-contributor 144/0 Mathlib.lean,Mathlib/Combinatorics/SetFamily/Oddtown.lean 2 3 ['D-Thomine', 'github-actions'] b-mehta
assignee:b-mehta
10-51248
10 days ago
101-18505
101 days ago
101-18450
101 days
0
41728 vaca22
author:vaca22
feat(GroupTheory): prove uniqueness of ℤᵐ⁰ automorphisms Prove that every order-preserving multiplicative automorphism of ℤᵐ⁰ is the identity. This also gives a Unique instance for its automorphism type and a Subsingleton instance for order-preserving multiplicative normalizations from G to ℤᵐ⁰. The proof transports an automorphism through WithZero.exp and WithZero.log to an additive automorphism of ℤ, then excludes negation by monotonicity. ------------ **AI disclosure**: this PR is primarily LLM-generated (Claude Code). t-group-theory new-contributor LLM-generated 58/0 Mathlib/GroupTheory/ArchimedeanDensely.lean 1 16 ['github-actions', 'grunweg', 'tb65536', 'vaca22', 'wwylele'] nobody
10-50356
10 days ago
77-85649
77 days ago
92-43736
92 days
0
42815 korbonits
author:korbonits
feat(Analysis/Calculus/VectorField): the Lie bracket acts as a derivation on functions Add `VectorField.lieBracket_apply_fun`: for a function `f` with derivative `f'` and vector fields `V`, `W`, D(f' W) V - D(f' V) W = f' [V, W] i.e. the familiar `[V, W] f = V (W f) - W (V f)`. The two second-derivative terms cancel by symmetry of the second derivative, leaving exactly the bracket. Placed beside the existing `lieBracket_smul_*` product rules. Needs no new import: `FDeriv.Symmetric` is already imported for `second_derivative_symmetric`, which supplies the symmetry and is the source of the `IsRCLikeNormedField` hypothesis. --- AI disclosure - level: Level 5 / Level 6 in [the link shared](https://www.visidata.org/blog/2026/ai/#self-assessed-ai-level-for-contributions) I feel confident about the math but I am still learning Lean itself - code: most of the Lean in this PR was drafted by Claude Code (statements, proofs, docstrings). - direction and review: I chose the contribution, made the decisions, reviewed every line, and wrote all GitHub/Zulip comments. t-analysis new-contributor LLM-generated t-differential-geometry 17/0 Mathlib/Analysis/Calculus/VectorField.lean 1 12 ['github-actions', 'korbonits', 'themathqueen'] nobody
10-37068
10 days ago
57-83532
57 days ago
98-28189
98 days
0
45947 alainchmt
author:alainchmt
feat(FieldTheory/Finite): add Rabin's polynomial irreducibility test This PR adds Rabin's irreducibility test: a polynomial `f` of degree `n > 0` over a finite field of cardinality `q` is irreducible if and only if `f` divides `X ^ q ^ n - X` and `f` is coprime to `X ^ q ^ (n / p) - X` for every prime `p` dividing `n`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra new-contributor
label:t-algebra$
15/0 Mathlib/FieldTheory/Finite/Extension.lean 1 2 ['github-actions'] nobody
9-81242
9 days ago
9-85472
9 days ago
9-85417
9 days
0
45971 WaterKing201030
author:WaterKing201030
feat(GroupTheory/Perm/Cycle/Basic): add some lemmas for Perm.SameCycle Add following lemmas: - `sameCycle_apply_left/right_self`: Inspired by `EqvGen.rel` - `SameCycle.map(_of_apply)`: Inspired by and generalized `SameCycle.conj` - `SameCycle.eq_of_invariant`: A function invariant under a permutation is constant on each cycle of permutation. - `sameCycle_iff_eqvGen`: `SameCycle` is equivalent to the equivalence closure of relation generated by the permutation. These simple lemmas appeared many times in proofs generated with AI assistance during my formalization work. I believe they are worth turning into an API. Therefore, I manually wrote the definitions and proofs for these lemmas. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-group-theory new-contributor 62/0 Mathlib/GroupTheory/Perm/Cycle/Basic.lean 1 2 ['github-actions'] nobody
9-22594
9 days ago
9-24562
9 days ago
9-24507
9 days
0
42353 sankalpsthakur
author:sankalpsthakur
feat(RingTheory): add nilpotence lemmas for zero sums In a semiring, adds: - `sq_eq_sq_of_add_eq_zero`: if `x + y = 0` then `x^2 = y^2` - `IsNilpotent.of_add_eq_zero_left`: if `x + y = 0` and `y` is nilpotent, so is `x` - `isNilpotent_iff_of_add_eq_zero`: under `x + y = 0`, `x` is nilpotent iff `y` is Motivated by #10539. --- ### Validation Built locally: `lake build Mathlib.RingTheory.Nilpotent.Basic` succeeds. ### AI/LLM disclosure AI coding tools were used to help draft this change and PR description. I reviewed the complete change, understand the reasoning, and verified the build locally before submitting. t-ring-theory new-contributor LLM-generated 51/0 Mathlib/RingTheory/Nilpotent/Basic.lean 1 33 ['artie2000', 'github-actions', 'sankalpsthakur', 'tb65536'] mattrobball
assignee:mattrobball
8-62937
8 days ago
8-64214
8 days ago
94-21215
94 days
0
42165 bocowgill
author:bocowgill
feat(Probability/HasCondDistrib): characterize independence using conditional distributions This PR uses conditional distributions to characterize independence of two random variables. It adds eight public declarations to `Mathlib/Probability/HasCondDistrib.lean`, which is the only file modified: - `indepFun_iff_hasCondDistrib_const_of_hasLaw`: characterizes independence using a constant conditional-distribution kernel when the laws are specified. - `indepFun_iff_hasCondDistrib_const`: specializes this characterization to the marginal laws `P.map X` and `P.map Y`. - `IndepFun.hasCondDistrib_const`: the forward implication of the preceding equivalence. - `HasCondDistrib.indepFun_of_const`: the reverse implication. - `hasCondDistrib_condDistrib`: shows that the regular conditional distribution `condDistrib Y X P` satisfies `HasCondDistrib`. - `hasCondDistrib_iff_condDistrib_ae_eq`: characterizes finite kernels satisfying `HasCondDistrib` by almost-everywhere equality with `condDistrib`. - `indepFun_iff_condDistrib_ae_eq_const_of_hasLaw`: characterizes independence by almost-everywhere equality of `condDistrib` with the constant kernel at the specified law. - `indepFun_iff_condDistrib_ae_eq_const`: specializes this characterization to the marginal laws. The PR adds no new file and makes no change to the root `Mathlib.lean` imports. --- ### Motivation These results provide a basic building block for formalizing randomized experiments and causal identification. The main result provides a starting point for later ignorability and conditional-independence results in causal inference. ### LLM disclosure For theorem planning and Lean implementation, I substantially used Codex by OpenAI. I also used it for suggestions around naming and documentation, for iterating on the proofs, and for validating my commits locally. I manually searched for the best locations and earlier results to build upon. I personally reviewed both the mathematical statements and Lean code (line-by-line), as well as the suggestions around naming and API choices. I also reviewed and confirmed that I can explain each step of the results (both Mathematics and Lean syntax). To validate the change, I directly compiled the modified file and ran a targeted build. I also ran the style linter, and completed a full `lake build` and a full `lake test`. Please note: This is one of my first mathlib contributions. I welcome corrections or suggestions about all aspects of this PR. I'm prepared to revise it as necessary, and to learn from the review. t-measure-probability LLM-generated new-contributor large-import 63/3 Mathlib/Probability/HasCondDistrib.lean 1 43 ['CoolRmal', 'EtienneC30', 'bocowgill', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] RemyDegenne
assignee:RemyDegenne
8-51255
8 days ago
11-71932
11 days ago
85-18707
85 days
0
44269 ROTARTSI82
author:ROTARTSI82
feat(Dynamics): periodic orbits must jump up and down If x is a periodic point and not a fixed point, there exists some b in its periodic orbit such that b < f b, and some b' such that f b' < b'. --- This change was motivated by the following proof, a special case of Sharkovskii's theorem: ```lean theorem exists_isFixedPt_of_continuous_of_mem_periodicPts' {α : Type*} [ConditionallyCompleteLinearOrder α] [TopologicalSpace α] [OrderTopology α] [DenselyOrdered α] {f : α → α} {x₀ : α} (hx₀ : x₀ ∈ periodicPts f) (hf : Continuous f) : ∃(c : α), IsFixedPt f c := by by_cases hfixed : IsFixedPt f x₀ · exact ⟨x₀, hfixed⟩ obtain ⟨a, _, ha⟩ := exists_lt_map_of_mem_periodicPts hx₀ hfixed obtain ⟨b, _, hb⟩ := exists_map_lt_of_mem_periodicPts hx₀ hfixed obtain ⟨c, _, hc⟩ := exists_mem_uIcc_isFixedPt hf.continuousOn ha.le hb.le exact ⟨c, hc⟩ ``` Would this theorem itself or something similar be wanted in mathlib? <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor t-dynamics 39/0 Mathlib/Dynamics/PeriodicPts/Lemmas.lean,Mathlib/Order/Monotone/Basic.lean 2 7 ['ROTARTSI82', 'github-actions', 'sgouezel'] sgouezel
assignee:sgouezel
8-44845
8 days ago
8-44845
8 days ago
55-661
55 days
0
45076 vdelbarc
author:vdelbarc
feat(Algebra/Lie/SemiDirect): add natural ideal and subalgebra; add equivalences Define the left ideal and right subalgebra of a semidirect product of Lie algebras. Give characterizations through natural inclusion/projection maps. Co-authored-by: Gustavo Infanti <g246337@dac.unicamp.br> Co-authored-by: Exequiel Rivas <exequiel.rivas@taltech.ee> Co-authored-by: Paul Schwahn <pschwahn@uni-muenster.de> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor t-algebra
label:t-algebra$
88/0 Mathlib/Algebra/Lie/SemiDirect.lean 1 2 ['github-actions'] nobody
8-24932
8 days ago
33-17369
33 days ago
33-17976
33 days
0
45608 vdelbarc
author:vdelbarc
feat(Algebra/Algebra): add ideals and quotients for non-unital non-associative algebras Introduce `NonUnitalNonAssocAlgebra.TwoSidedIdeal R A` as an `R`-submodule closed under multiplication by arbitrary elements of `A` on either side. This provides scalar-closed ideals for quotient constructions in non-unital, non-associative algebras. Add basic lemmas, together with a forgetful map to the existing ring-theoretic `TwoSidedIdeal A`. Construct the quotient `A ⧸ I` using the underlying submodule quotient. Equip it with non-unital, non-associative ring and module structures, and provide the quotient map as a non-unital algebra homomorphism, computation lemmas, and an induction principle. Show that `SMulCommClass R A A` and `IsScalarTower R A A`, when available, descend to the quotient. Co-authored-by: Gustavo Infanti <g246337@dac.unicamp.br> Co-authored-by: Exequiel Rivas <exequiel.rivas@taltech.ee> Co-authored-by: Paul Schwahn <pschwahn@uni-muenster.de> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra new-contributor
label:t-algebra$
262/0 Mathlib.lean,Mathlib/Algebra/Algebra/NonUnitalIdeal.lean 2 2 ['github-actions'] nobody
8-24892
8 days ago
19-15975
19 days ago
19-17247
19 days
0
45610 vdelbarc
author:vdelbarc
feat(Algebra/Algebra/Leibniz): introduce Leibniz rings and algebras Introduce the basic theory of right Leibniz rings and algebras. Define `IsLeibniz` by the identity `(x * y) * z = (x * z) * y + x * (y * z)`, and establish its basic consequences. Design choices were briefly discussed in https://leanprover.zulipchat.com/#narrow/channel/116395-maths/topic/Leibniz.20algebras/near/611073252 Define `IsSkew` for multiplication satisfying `x * x = 0`. Construct Lie ring and Lie algebra structures on Leibniz rings and algebras satisfying this condition. Conversely, show that every Lie ring satisfies the right Leibniz identity when its bracket is used as multiplication. More on two-sided ideals and quotients of Leibniz algebras to come after PR#45608 is merged, from which this PR is independent now. Co-authored-by: Gustavo Infanti <g246337@dac.unicamp.br> Co-authored-by: Exequiel Rivas <exequiel.rivas@taltech.ee> Co-authored-by: Paul Schwahn <pschwahn@uni-muenster.de> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra new-contributor
label:t-algebra$
218/0 Mathlib.lean,Mathlib/Algebra/Algebra/Leibniz/Basic.lean 2 7 ['Julian-Kuelshammer', 'github-actions'] nobody
8-24263
8 days ago
19-15447
19 days ago
19-15392
19 days
0
45944 rytjy
author:rytjy
feat(Probability): wilson score interval Adds the Wilson score interval for a binomial proportion: centre, half-width, endpoints, and the facts that the centre lies in [0, 1] and that the sample proportion always lies inside the interval. This is a small, self-contained start on a gap noted while using the interval: mathlib4 has no confidence-interval / Wilson-score notion. Main results: `wilsonCenter_mem_Icc`, `wilsonLo_le_wilsonHi`, `wilsonHi_nonneg`, `wilsonLo_le_one`, `wilson_contains`. Opened as a draft: happy to reshape the statement, add one-sided bounds, or move it under a different namespace after review. t-measure-probability new-contributor 245/0 Mathlib.lean,Mathlib/Probability/WilsonInterval.lean 2 4 ['github-actions', 'rytjy'] nobody
8-20699
8 days ago
9-12587
9 days ago
9-12532
9 days
0
37279 imalinowskip
author:imalinowskip
feat(Probability): multivariate CLT --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> <!-- [ ] depends on: #40345 --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-measure-probability tech debt 210/18 Mathlib/MeasureTheory/Function/ConvergenceInDistribution.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/AEStronglyMeasurable.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/Basic.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/MeasureTheory/Measure/LevyConvergence.lean,Mathlib/MeasureTheory/Measure/ProbabilityMeasure.lean,Mathlib/Probability/CentralLimitTheorem.lean,Mathlib/Probability/CramerWold.lean,Mathlib/Probability/Distributions/Gaussian/Multivariate.lean,Mathlib/Probability/Moments/Variance.lean 10 66 ['EtienneC30', 'RemyDegenne', 'github-actions', 'imalinowskip', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] EtienneC30
assignee:EtienneC30
7-73413
7 days ago
11-70880
11 days ago
57-25019
57 days
0
43104 elazarg
author:elazarg
feat(InformationTheory/KullbackLeibler): finite Kullback-Leibler divergence Add finite-sum formulas for `InformationTheory.klDiv` on finite measurable spaces, including equal-mass and probability-measure specializations and formulas for sums of weighted Dirac measures. Provide both `ℝ≥0∞`-valued and `toReal` versions. Supporting API includes a formula for the Radon–Nikodym derivative at points of nonzero reference-measure mass, a finite-sum formula for the integral of the log-likelihood ratio, and singleton-mass and absolute-continuity lemmas for sums of weighted Dirac measures. --- Continuing #42584, another part of https://github.com/elazarg/kraft. Following review, this uses the existing `klDiv` instead of introducing `klDivFin`. The `toReal` formulas connect it to real-valued sums in downstream code. For measures of unequal mass, the formulas retain the correction term `ν.real univ - μ.real univ`. The KL formulas are in `KullbackLeibler/Basic.lean`; the supporting lemmas are in the corresponding measure-theory modules. [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-measure-probability new-contributor LLM-generated 103/1 Mathlib/InformationTheory/KullbackLeibler/Basic.lean,Mathlib/MeasureTheory/Measure/Decomposition/RadonNikodym.lean,Mathlib/MeasureTheory/Measure/Dirac/Basic.lean,Mathlib/MeasureTheory/Measure/LogLikelihoodRatio.lean 4 13 ['DavidLedvinka', 'EtienneC30', 'elazarg', 'github-actions', 'vlad902'] urkud
assignee:urkud
7-64599
7 days ago
7-64631
7 days ago
77-39911
77 days
0
39347 Sfgangloff
author:Sfgangloff
feat(SymbolicDynamics): refactor of Pattern and shift-invariance of shape languages for subshifts ## Summary This PR refactors Pattern.mulShift in Mathlib/Dynamics/SymbolicDynamics/Basic.lean and uses the cleaner definition to prove shift-invariance of the language of a subshift on a finite shape. ## Changes Pattern.mulShift now returns a Pattern instead of a configuration (more natural). - Old type: Pattern.mulShift : Pattern A G → G → (G → A) - New type: Pattern.mulShift : Pattern A G → G → Pattern A G - The result carries its support (p.support.image (v * ·)) and the default-outside-support proof, so callers don't have to re-derive them. The [IsLeftCancelMul G] hypothesis is moved to the lemmas that actually use it. - The definition Pattern.mulShift itself no longer needs left-cancellation (it only chooses a preimage noncomputably). - The hypothesis is now stated on mulShift_config_apply_mul_left_of_mem and mulOccursInAt_eq_cylinder directly, instead of being a section-level variable. Renames following the type change. - mulShift_apply_mul_left_of_mem → mulShift_config_apply_mul_left_of_mem (because we now write (p.mulShift v).config instead of p.mulShift v). New @[simp] and @[ext] lemmas for Pattern. - Pattern.ext: two patterns are equal iff their supports agree and their configurations agree on the support. - Pattern.mulShift_support: the support of p.mulShift v is p.support.image (v * ·). - Pattern.fromConfig_support: the support of fromConfig x U is U. - Pattern.fromConfig_config_of_mem: on its support, fromConfig x U agrees with x. New lemma Pattern.fromConfig_mulShift. For a left inverse g' * g = 1, shifting the pattern fromConfig x U by g equals fromConfig (mulShift g' x) (U.image (g * ·)). New theorem MulSubshift.languageOn_image_mulShift. For a subshift Y and elements g, g' with g * g' = 1 and g' * g = 1: (fun p => p.mulShift g) '' Y.languageOn U = Y.languageOn (U.image (g * ·)) i.e. the language on the translated shape is exactly the image of the language on U under the pattern-shift map. This gives a bijection between Y.languageOn U and Y.languageOn (U.image (g * ·)), with inverse p ↦ p.mulShift g'. Stated for left-cancellative monoids with an invertible element. Updated docstrings for Pattern.mulShift and the renamed lemma to reflect the bundled-Pattern return type and clarify which results need [IsLeftCancelMul G]. t-dynamics new-contributor 144/47 Mathlib/Dynamics/SymbolicDynamics/Basic.lean 1 13 ['Sfgangloff', 'github-actions', 'mathlib-merge-conflicts', 'sgouezel'] ADedecker
assignee:ADedecker
7-51257
7 days ago
39-27994
39 days ago
99-65460
99 days
0
45968 Ruizsolveall
author:Ruizsolveall
feat(Analysis/Convex): convex bodies are determined up to homeomorphism by their dimension This PR shows that a convex body in a finite-dimensional real normed space is determined up to homeomorphism by the dimension of its affine span (`ConvexBody.nonempty_homeomorph`). The closed-ball versions follow as special cases. --- I looked at both `Mathlib/Analysis/Convex` and `Mathlib/Geometry/Convex/ConvexSpace` before deciding where to put this. I went with `Analysis/Convex`, since the proof uses radial rescaling (`gaugeRescale`), which needs an ambient vector space. A few notes: * `Convex.nonempty_homeomorph_closedBall` is close to `exists_homeomorph_image_interior_closure_frontier_eq_unitBall`. I kept it since it's the form people usually look for, but I can drop it. * Only one direction is proved; the converse needs invariance of dimension. I'd like this to be a step towards Brouwer's fixed point theorem: once Brouwer is known for a ball or a simplex, this transfers it to any convex body, including lower-dimensional ones like a triangle in ℝ³. I used AI (Claude Code) to explore the API, try out code quickly, and split up the argument. I understand the work and can explain it. Thanks to the Xena community for helping me get up to speed on the math and the design choices. new-contributor t-analysis 126/0 Mathlib.lean,Mathlib/Analysis/Convex/HomeomorphClosedBall.lean 2 3 ['github-actions', 'wwylele'] nobody
7-44547
7 days ago
9-45356
9 days ago
9-45301
9 days
0
42786 rshlyakh
author:rshlyakh
feat(Data/Finsupp/NatCard): count finsupps of bounded degree Adds the formula that the number of finitely-supported functions `α →₀ ℕ` with degree less than or equal to `n` is equal to `Nat.choose (Nat.card α + n) n`. The proof is by establishing an equivalence `Sym (Option α) n ≃ {f : α →₀ ℕ // f.degree ≤ n}` and using the stars-and-bars formula `Sym.equivNatSum.` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data new-contributor 69/0 Mathlib.lean,Mathlib/Data/Finsupp/NatCard.lean 2 4 ['eric-wieser', 'github-actions'] eric-wieser
assignee:eric-wieser
7-35691
7 days ago
7-36104
7 days ago
91-33809
91 days
0
45946 GoldenPhysicsProject
author:GoldenPhysicsProject
feat(Analysis/Analytic): add Pringsheim's theorem **Disclosure (per Mathlib's AI policy):** this is a resubmission of #44790, which was closed in October because the original submission, prepared and sent by Claude, an AI assistant working in my project (the Golden Physics Project), did not disclose the AI involvement. This version is submitted by me, Daniel Toupin, the account holder, with the disclosure stated here: the code was AI-generated under my direction and review, in my library GPPVerify (https://github.com/GoldenPhysicsProject/GPPVerify), where it is Lean-checked with zero sorry and only the standard axioms. I stand behind the content and will make any changes you ask for. --- Add Pringsheim's theorem (Vivanti–Pringsheim): a power series `∑ aₙ zⁿ` with nonnegative real coefficients whose sum continues analytically to a neighbourhood of the positive point `R` of its circle of convergence in fact converges beyond `R`. Equivalently, such a series is singular at the positive point of its circle of convergence. Main result: `Pringsheim.exists_gt_summable_mul_pow_of_analyticAt`. The proof re-expands the series at `t = R − e/4`, identifies the re-expanded coefficients with the Cauchy power series of the continuation by uniqueness of power series, and transfers summability back to the original series by a rearrangement in `ℝ≥0∞` that needs no convergence hypotheses. The auxiliary lemmas are `private`. --- Contributed by Daniel Toupin (Golden Physics Project), with AI assistance from Claude (Anthropic) in writing the formalization. It was first developed and machine-checked in the Golden Physics Project's verification library against Mathlib v4.33.1. It was then ported to the module system and rebuilt cleanly against current `master` (48192e0, Lean v4.35.0-rc4), with zero warnings under Mathlib's linters and axioms only `propext`, `Classical.choice` and `Quot.sound`. Happy to rename or restructure to fit Mathlib's API (for example, stating it in terms of `FormalMultilinearSeries.ofScalars` and `radius`) if reviewers prefer. t-analysis new-contributor LLM-generated 279/0 Mathlib.lean,Mathlib/Analysis/Analytic/Pringsheim.lean 2 2 ['github-actions'] nobody
7-19631
7 days ago
9-86078
9 days ago
9-86023
9 days
0
45825 GoldenPhysicsProject
author:GoldenPhysicsProject
feat: explicit orthogonal projection onto the span of two vectors This adds a short file, `Mathlib/Analysis/InnerProductSpace/Projection/SpanPair.lean`, with explicit formulas for the orthogonal projection onto the span of two vectors in a real inner product space. Main results: * `InnerProductSpace.starProjection_span_pair`: the projection of `x` onto `span ℝ {u, v}`, evaluated by Cramer's rule for the two-by-two Gram matrix. The coefficients are the entries of the inverse Gram matrix applied to `(⟪u, x⟫, ⟪v, x⟫)`, under the single hypothesis that the Gram determinant is nonzero. * `InnerProductSpace.norm_sub_starProjection_span_pair_sq`: the squared distance from `x` to the span, as `‖x‖ ^ 2` minus the quadratic form of the inverse Gram matrix evaluated at `(⟪u, x⟫, ⟪v, x⟫)`. The file is self-contained: it depends only on `Mathlib.Analysis.InnerProductSpace.Projection.Basic` and proves both results from the existing `Submodule.starProjection` API. The `HasOrthogonalProjection` instance for the pair span is taken as an instance argument; in practice it is discharged from `FiniteDimensional.span_of_finite` together with `FiniteDimensional.completeSpace`. Provenance: the file comes from the GPPVerify library (GoldenPhysicsProject/GPPVerify, Apache-2.0), where it is staged in `GppVerify/Upstream/`, and is contributed here under the same license and copyright (Daniel Toupin) t-analysis new-contributor LLM-generated 113/0 Mathlib.lean,Mathlib/Analysis/InnerProductSpace/Projection/SpanPair.lean 2 5 ['GoldenPhysicsProject', 'github-actions', 'grunweg'] nobody
7-19562
7 days ago
7-19562
7 days ago
7-20042
7 days
0
42494 JadAbouHawili
author:JadAbouHawili
feat(Combinatorics/SimpleGraph/Connectivity): add edge reachability and connectivity numbers Define edge reachability and connectivity numbers with some basic API Partially solves #34961 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics 81/2 Mathlib/Combinatorics/SimpleGraph/Connectivity/EdgeConnectivity.lean,Mathlib/Order/CompleteLattice/Lemmas.lean 2 169 ['JadAbouHawili', 'SnirBroshi', 'github-actions', 'grunweg', 'mathlib-merge-conflicts'] nobody
6-50356
6 days ago
28-34761
28 days ago
78-51492
78 days
0
43216 JadAbouHawili
author:JadAbouHawili
feat(Combinatorics/SimpleGraph/Clique): independence number is zero iff the graph has no vertices --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics 62/11 Mathlib/Combinatorics/SimpleGraph/Clique.lean 1 66 ['JadAbouHawili', 'SnirBroshi', 'github-actions', 'mathlib-merge-conflicts'] nobody
6-50354
6 days ago
28-32737
28 days ago
73-65447
73 days
0
44885 3y3y3y-huaiji
author:3y3y3y-huaiji
feat(Combinatorics/Quiver/Monotone): define Monotone and StrictMono Define `Quiver.Monotone` and `Quiver.StrictMono` for functions from the vertices of a quiver into a preorder, and deduce that `Quiver.Reachable` is a partial order when a strictly monotone function exists. --- > [!NOTE] > **LLM Disclosure / AI Use**: This PR was prepared with the assistance of an LLM (`LLM-generated`). All proofs and statements have been formally verified by Lean 4 and checked with linters. t-combinatorics LLM-generated new-contributor 69/0 Mathlib.lean,Mathlib/Combinatorics/Quiver/Monotone.lean 2 15 ['3y3y3y-huaiji', 'github-actions', 'joelriou', 'leanprover-radar', 'vihdzp'] nobody
6-32694
6 days ago
6-32997
6 days ago
26-73588
26 days
0
46050 YijunYuan
author:YijunYuan
feat(NumberTheorey/Padics/Complex): prove the p-adic algebraic closure is not complete The ultimate goal of this PR is to show that the algebraic closure `PadicAlgCl p` of the field `ℚ_[p]` of p-adic rational numbers is not complete with respect to the p-adic norm. To do so, I prove the following results: 1. Let K be a complete non-trivially normed ultrametric field. If a normed extension E of K is perfect and is a Baire space, then E must be finite-dimensional over K 2. As a result of the above result, the algebraic closure of K is a Baire space w.r.t. the spectral norm if and only if it is of finite dimension over K. 3. As a corollary, the algebraic closure of K is a complete space w.r.t. the spectral norm if and only if it is of finite dimension over K. 4. `PadicAlgCl p` is of infinite dimension over `ℚ_[p]`. 5. By the above results, `PadicAlgCl p` is not a Baire space and is not complete w.r.t. the p-adic norm. Several reusable helper results are also supplied. new-contributor t-number-theory 252/1 Mathlib.lean,Mathlib/Analysis/Normed/Field/Baire.lean,Mathlib/FieldTheory/Minpoly/Bounds.lean,Mathlib/NumberTheory/Padics/Complex.lean 4 15 ['YijunYuan', 'github-actions', 'vihdzp', 'wwylele'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
6-2421
6 days ago
6-85317
6 days ago
7-1606
7 days
0
41957 YijunYuan
author:YijunYuan
feat(NumberTheory/Padics/Complex): add densely normed field and separable space instances Equip the field `ℂ_[p]` of `p`-adic complex numbers and its dense subfield `PadicAlgCl p` (the algebraic closure of `ℚ_[p]`) with two further standard typeclass instances. Main additions: * `DenselyNormedField (PadicAlgCl p)`: the norm takes values dense in the positive reals. The witness between two given bounds `a < b` is built from an `n`-th root `z` of `p` (which exists since `PadicAlgCl p` is algebraically closed): choosing `n` so that `(a / b) ^ n < ‖p‖` gives `a / b < ‖z‖ < 1`, and some integer power `z ^ m` then has norm strictly between `a` and `b`. * `SeparableSpace (PadicAlgCl p)`: the elements algebraic over `ℚ` form a countable dense subset. Density follows from continuity of roots — `α` is a root of its minimal polynomial `f` over `ℚ_[p]`, and approximating the coefficients of `f` by a polynomial `g` over the dense subfield `ℚ` yields a root `β` of `g` (hence algebraic over `ℚ`) arbitrarily close to `α`. * The corresponding instances `DenselyNormedField ℂ_[p]` and `SeparableSpace ℂ_[p]` are then inferred, `ℂ_[p]` being the completion of `PadicAlgCl p`. Supporting general instance: * `DenselyNormedField (UniformSpace.Completion A)` for a densely normed field `A` with `CompletableTopField A`, since the norm on the completion extends the norm on `A`. The existing `NontriviallyNormedField` instances on `PadicAlgCl p` and `ℂ_[p]` are simplified to `inferInstance`, as they now follow from the new `DenselyNormedField` instances. new-contributor t-number-theory t-algebra large-import
label:t-algebra$
196/12 Mathlib.lean,Mathlib/Analysis/Normed/Field/Separable.lean,Mathlib/Analysis/Normed/Module/Completion.lean,Mathlib/Analysis/Normed/Unbundled/SpectralNorm.lean,Mathlib/NumberTheory/Padics/Complex.lean,Mathlib/NumberTheory/Padics/PadicNumbers.lean,Mathlib/Topology/Algebra/Field.lean 7 23 ['YijunYuan', 'github-actions', 'jjdishere', 'mathlib-merge-conflicts', 'pechersky', 'riccardobrasca'] jjdishere
assignee:jjdishere
6-2282
6 days ago
6-2282
6 days ago
112-72970
112 days
0
44762 Julian-Kuelshammer
author:Julian-Kuelshammer
feat(Combinatorics/Enumerative/Catalan/BracketingFunction): adds Huang-Tamari's bracketing functions This PR defines bracketing functions, an elementary description of the Tamari lattice. This PR is intentially kept short and just adds the definition and a bit of basic API. There are potential follow-ups proving that these are counted by the Catalan numbers and giving the lattice instance, for a preview see https://github.com/Julian-Kuelshammer/ExtensionClosedSubcategoriesOfAn/blob/main/ExtensionClosedSubcategoriesOfAn/BracketingFunctions.lean A first version of the file was created with the help of Aristotle and Claude. In this PR a large percentage of proofs has been rewritten afterwards. The docstring is entirely human-written except for the ASCII art. --- new-contributor t-combinatorics LLM-generated 102/0 Mathlib.lean,Mathlib/Combinatorics/Enumerative/Catalan/BracketingFunction.lean 2 4 ['Julian-Kuelshammer', 'github-actions'] nobody
5-85708
5 days ago
42-6586
42 days ago
42-6925
42 days
0
43852 ZRTMRH
author:ZRTMRH
feat(Combinatorics/Quiver/Schreier): add Schreier Cayley basics Defined Cayley graph as a coset Schreier graph. Proved connectivity and vertex-transitivity on Cayley graphs, as promised in #38310. Follow-up to #38310, this is the 3rd split pr from #35467. This PR was written with AI assistance (Claude). The code has been reviewed by the author. P.S. cayley_subsingleton_weaklyConnectedComponent's proof is generic and I can extract it to Quiver/ConnectedComponent.lean as a weak-connectivity lemma, if it is wanted. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-combinatorics large-import LLM-generated 278/7 Mathlib/Combinatorics/Quiver/Schreier.lean 1 10 ['SnirBroshi', 'ZRTMRH', 'github-actions', 'mathlib-merge-conflicts', 'vlad902'] nobody
5-84788
5 days ago
55-4194
55 days ago
67-53354
67 days
0
46004 danderson70-UNL
author:danderson70-UNL
feat(Data/List/Destutter): add lemmas about `List.destutter.head` and `List.destutter.getLast` These proofs have a version for `List.destutter'` as well as for `List.destutter`. The `getLast` proofs don't apply in general, such as for `[5, 6, 2].destutter (<) = [5, 6]`, and I don't believe that there is a clean way to maintain the generality without adding complex hypotheses. The documentation for [`List.destutter`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/List/Defs.html#List.destutter) suggests that `List.destutter` is usually used with the `≠` relation, so I think that the lemmas I created may still have general use. I wasn't sure whether to mark these lemmas with `@[simp]`. I think it could be useful to include them, but I didn't know how to check for infinite loops and other issues that could arise from adding the `@[simp]` tag. (I also forgot to include them in my commits.) --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-data new-contributor 36/0 Mathlib/Data/List/Destutter.lean 1 2 ['github-actions'] nobody
5-74027
5 days ago
8-58610
8 days ago
8-58555
8 days
0
41729 vaca22
author:vaca22
feat(RingTheory/DedekindDomain): add divisor group core Add the divisor group of a Dedekind domain as a formal-sum model, together with the additive equivalence to the multiplicative group of nonzero fractional ideals. **Relation to what Mathlib already has.** As pointed out on Zulip, Mathlib already knows that fractional ideals factor: `FractionalIdeal.count` gives the exponent of a height-one prime, and `ClassGroup` is built from fractional ideals directly. This PR does not re-prove any of that — it reuses `count` and `finite_factors` verbatim. What it adds is the *additive* packaging: * `IsDedekindDomain.Divisor R := HeightOneSpectrum R →₀ ℤ`, so a divisor is a finitely supported integer-valued function and one can write `D₁ + D₂`, `-D`, `D v`, and use the whole `Finsupp` API (`support`, `sum`, induction on the support); * `FractionalIdeal.divisorEquiv`, an `AddEquiv` from `(FractionalIdeal R⁰ K)ˣ` to `Divisor R`, turning ideal multiplication into divisor addition. The multiplicative view is the right one for the class group; the additive one is what divisor-theoretic arguments are written in, where one constantly forms `D - D'`, compares coefficients prime by prime, and does induction over `D.support`. Having both, related by a single `AddEquiv`, means neither side has to be re-derived. **Downstream use.** This is the bottom layer of a formalization of Riemann–Roch for algebraic function fields (announced in `#AI authored projects > Riemann–Roch for function fields`): `L(D)`, `deg D`, and the statement `ℓ(D) = deg D + 1 - g + ℓ(W - D)` are all phrased in terms of additive divisors, and the degree map is defined by summing coefficients over `D.support`. Happy to reshape the API — in particular whether `Divisor` should be an `abbrev` or a structure, and whether this belongs next to `Factorization` rather than in its own file. AI usage: LLM-generated, disclosed per the AI policy. t-ring-theory new-contributor LLM-generated 100/0 Mathlib.lean,Mathlib/RingTheory/DedekindDomain/Divisor.lean 2 4 ['github-actions', 'grunweg', 'vaca22'] nobody
5-50356
5 days ago
128-61223
128 days ago
130-58371
130 days
0
42775 hawkrobe
author:hawkrobe
feat(RingTheory/HopfAlgebra): construct Hopf algebras from primitive generators Upgrade a bialgebra generated by primitive elements to a Hopf algebra (`HopfAlgebra.ofPrimitives`), given an anti-algebra hom `S : A →ₐ[R] Aᵐᵒᵖ` negating each generator, and show that such an `S` is the antipode (`HopfAlgebra.eq_antipodeAlgHomOp_of_primitives`). Both build on `HopfAlgebra.ofAntipodeOfAdjoin` from #41828, which superseded the generators construction this PR originally carried. Split out of #39841. Claude Code was used to prepare this revision. t-ring-theory new-contributor 31/4 Mathlib/RingTheory/HopfAlgebra/Primitive.lean 1 3 ['github-actions'] nobody
5-50355
5 days ago
26-78768
26 days ago
97-47345
97 days
1
42895 cameronfreer
author:cameronfreer
feat(SetTheory/Ordinal): add lift_sSup and lift_iSup Show that an initial segment embedding between conditionally complete linear orders with bottom preserves bounded suprema (`InitialSeg.map_csSup`, `InitialSeg.map_ciSup`). Specializing to `Ordinal.liftInitialSeg` gives `Ordinal.lift_sSup` and `Ordinal.lift_iSup`. `Ordinal.lift_sSup` assumes `[Small.{u} s]`, while `Ordinal.lift_iSup` assumes `BddAbove (Set.range f)` rather than a small index type. --- 🤖 This PR was developed with assistance from Claude and GPT models, using [lean4-skills](https://github.com/cameronfreer/lean4-skills) and [lean-lsp-mcp](https://github.com/oOo0oOo/lean-lsp-mcp). t-set-theory new-contributor LLM-generated 27/1 Mathlib/Order/IsNormal.lean,Mathlib/SetTheory/Cardinal/Cofinality/Ordinal.lean,Mathlib/SetTheory/Ordinal/Family.lean 3 34 ['bryangingechen', 'cameronfreer', 'github-actions', 'jjdishere', 'leanprover-radar', 'plp127', 'vihdzp'] jjdishere
assignee:jjdishere
5-47981
5 days ago
7-54976
7 days ago
84-33476
84 days
0
45014 GoldenPhysicsProject
author:GoldenPhysicsProject
feat(Analysis/SpecialFunctions/Trigonometric): infinite product formula for sinh Transfers the absolutely convergent Euler product for sine (`euler_sineTerm_tprod`) to the hyperbolic sine, in `Mathlib/Analysis/SpecialFunctions/Trigonometric/Cotangent.lean` next to the sine statement: * `multipliable_one_add_sq_div`: `Multipliable fun n : ℕ ↦ 1 + x ^ 2 / (n + 1) ^ 2` for every `x : ℂ`. * `euler_sinh_tprod`: for `x * I ∈ ℂ_ℤ`, `∏' n : ℕ, (1 + x ^ 2 / (n + 1) ^ 2) = Complex.sinh (π * x) / (π * x)`. This follows a review comment by @wwylele on the first version of this PR, which was a separate file with the conditionally convergent `Tendsto` form. I searched master and the open PRs for an existing hyperbolic-sine product and found none. ----- AI-assistance disclosure: this PR was written and submitted by Claude Code (Anthropic) at the request of the account owner. The account owner has not reviewed the code line by line. The file builds against current master, `lake exe lint-style` is clean, and `#print axioms` shows only `propext`, `Classical.choice` and `Quot.sound`. Please review it as AI-generated. t-analysis new-contributor LLM-generated 19/0 Mathlib/Analysis/SpecialFunctions/Trigonometric/Cotangent.lean 1 11 ['GoldenPhysicsProject', 'github-actions', 'themathqueen', 'wwylele'] nobody
5-19779
5 days ago
33-66605
33 days ago
33-80108
33 days
0
46135 Lxsoftroxs
author:Lxsoftroxs
feat(Data/{Nat,Int}/ModEq): solvability criterion for two congruences Add the solvability criterion for a pair of congruences, over `ℕ` and `ℤ`: * `Nat.modEq_gcd_of_modEq_of_modEq`, `Int.modEq_gcd_of_modEq_of_modEq`: if `k ≡ a [MOD n]` and `k ≡ b [MOD m]`, then `a ≡ b [MOD gcd n m]`; * `Nat.exists_modEq_and_modEq_iff`, `Int.exists_modEq_and_modEq_iff`: `(∃ k, k ≡ a [MOD n] ∧ k ≡ b [MOD m]) ↔ a ≡ b [MOD gcd n m]`. No assumptions are made on the moduli (zero moduli, and negative moduli over `ℤ`, are allowed). `Nat.chineseRemainder'` already constructs a solution under `a ≡ b [MOD gcd n m]`. Mathlib does not yet state that this condition is also necessary, or the resulting `iff`. Over `ℤ` there is currently no existence statement for two moduli: users go through `Ideal.exists_forall_sub_mem_ideal`, which needs pairwise coprime ideals, or through `ZMod`. The `ℤ` existence proof uses Bézout directly: if `b - a = gcd n m * q`, then `b - m * q * gcdB n m` is a solution. --- **AI disclosure.** These lemmas were found and first proved with an automated pipeline. It used a local LLM prover (BFS-Prover-V2-7B), retrieval over Mathlib and a symbolic certificate search. Each machine proof was checked with `lake env lean`, and the statements with `comparator`. The proofs in this PR were then rewritten in Mathlib style, with Claude's help, and re-checked the same way. I have read and understood the code and will respond to review. The duplicate search, done before opening this PR, found no equivalent: - `exact?` closes none of the statements. - Loogle finds no declaration mentioning both `Nat.ModEq, Nat.gcd, Exists` or `Int.ModEq, Int.gcd, Exists`. - No open or merged PR adds them. #13306, #7532 and #29761 are the ideal-level and `ZMod` versions. - Related Zulip thread (#new-members, "How to use chinese remainder theorem for mutliple modulos"): CRT is noted to be available only for `ℕ`. Checked locally against `master` (`883bd4c`): - both modules build; - `runLinter` and `lint-style` pass; - the 13 direct importers rebuild. Possible conflict: #28631 also edits `Mathlib/Data/Nat/ModEq.lean`. Naming is open to suggestions: e.g. `ModEq.modEq_gcd` for dot notation on the necessity lemma. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01LX9nkpL1i1ovEWvsCPWZZM t-data new-contributor 30/0 Mathlib/Data/Int/ModEq.lean,Mathlib/Data/Nat/ModEq.lean 2 2 ['github-actions'] nobody
4-62040
4 days ago
4-64718
4 days ago
4-64663
4 days
0
45963 marco-david
author:marco-david
feat(Algebra/Homology/AInfinity): define A-infinity categories Co-authored-by: Zhan Shi <lennox08@tutanota.com> Co-authored-by: Annie Yao <annie.z.yao@gmail.com> Co-authored-by: Justin Mu <justinmu2007@gmail.com> Co-authored-by: Jasper van de Kreeke <jasper.kreeke@berkeley.edu> --- We add the definition of an A∞ category, and introduce a general `Grading` typeclass for its morphism spaces that generalizes Z-gradings and bi- or multigradings. This is a minimal self-contained piece that shows the full stack of new definitions, carved out from the larger development at [marco-david/ainfinity-lean](https://github.com/marco-david/ainfinity-lean), following @joelriou's feedback on #40984, which this PR now supersedes. In order to keep its size reasonable, this PR does not include any examples of the new definition, but in [marco-david/ainfinity-lean](https://github.com/marco-david/ainfinity-lean) we show that our definition is non-vacuous. We show that every dg-category (defined via `EnrichedCategory`) is an A∞-category and that every linear category, concentrated in degree 0, is also an example. Follow-up PRs can add a variety of things to this library: We expect the examples cited above to be useful, so we plan to add them to Mathlib. For our custom type `Grading` we have also developed additional API that allows users to construct product grading types such as ℤ × ℤ, ℤ × ℤ/2ℤ to match their grading conventions. Finally, we have also developed A∞ functors, and are working on A∞ natural transformations and the categorical homotopy transfer theorem. Among the primary producers and consumers of these categories are symplectic geometers, but they also arise in algebraic topology and representation theory. This development will be useful to many formalization efforts in those field. **N.B.:** We are not sure if the file `GradedMultilinearMap` should be placed into the new `AInfinity` folder, or elsewhere, and would appreciate your advice. We are also open to feedback on the new namespace `AInfinity`. **AI Disclosure:** These files were developed throughout many in-person human-to-human meetings and conversations, with LLM feedback and input on many design decisions. Every addition in our separate repository was reviewed by at least one human who wasn't the original author, and these internal reviews, too, were assisted by LLMs. We have further used LLMs to draft initial sketches, help with refactoring, write mechanical proofs, and carve out this minimal set of files and declarations for the first Mathlib PR. (Tools used: GitHub Copilot, Codex Sol / Astra and Claude Opus / Fable, among them primarily Claude Code. I would say "LLM-edited" is a more accurate label than "LLM-generated".) Discussion on [this Zulip thread](https://leanprover.zulipchat.com/#narrow/channel/144837-PR-reviews/topic/Towards.20A.E2.88.9E.20categories.20.28.2340984.29/with/608915845). t-algebra new-contributor LLM-generated
label:t-algebra$
1022/0 Mathlib.lean,Mathlib/Algebra/Homology/AInfinity/AInfinityCategory.lean,Mathlib/Algebra/Homology/AInfinity/AInfinityCategoryStruct.lean,Mathlib/Algebra/Homology/AInfinity/GradedLinearQuiver.lean,Mathlib/Algebra/Homology/AInfinity/GradedMultilinearMap.lean,Mathlib/Algebra/Homology/AInfinity/Grading.lean,Mathlib/Algebra/Homology/AInfinity/Stasheff.lean,Mathlib/Algebra/Homology/AInfinity/StasheffIndex.lean,docs/references.bib 9 2 ['github-actions'] nobody
4-57541
4 days ago
9-59495
9 days ago
9-59440
9 days
0
38223 Deicyde
author:Deicyde
feat(Geometry/Manifold): add `MfldCat`, the category of `C^n` manifolds Defines `MfldCat 𝕜 n`: the category of `C^n` manifolds over a field `𝕜`, in which the model with corners is allowed to vary between objects. An object bundles a model vector space `E`, a model space `H`, a model with corners `I : ModelWithCorners 𝕜 E H` and a term of `ModelWithCorners.MfldCat I n`--see #41109. This includes manifolds with boundary / corners. For more discussion see this Zulip thread: [#PR reviews > #38223 The Category of C^n Manifolds](https://leanprover.zulipchat.com/#narrow/channel/144837-PR-reviews/topic/.2338223.20The.20Category.20of.20C.5En.20Manifolds/with/587038032) Also added: `ContMDiffMap.id_apply`, `.coe_id` and `.coe_comp` which are comparable to `ContinuousMap` API. ### Future work - ✅ Define a Monoidal structure via product manifolds, analogous to `Manifold.Topology.Category.TopCat.Monoidal` #38560 - ✅ Define the tangent functor: `M ↦ TM`, `F ↦ F.tangentMap` from `MfldCat (n+1) 𝕜` to `MfldCat n 𝕜` #38270 - Functor `FGModuleCat 𝕜 ⥤ MfldCat 𝕜 n` sending a finite-dimensional `𝕜`-vector space to the manifold modeled on itself. Left as `TODO`. - Define `FGModuleCat 𝕜` as an enriched category over `MfldCat n 𝕜`. Then _smooth functors_ can be realized as endofunctors on the enriched category. This is the main motivation for this construction. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #41109 [The category of `C^n` manifolds on a fixed model] [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-differential-geometry new-contributor t-category-theory 210/0 Mathlib.lean,Mathlib/Geometry/Manifold/Category/MfldCat/Basic.lean,Mathlib/Geometry/Manifold/ContMDiffMap.lean 3 63 ['Deicyde', 'chrisflav', 'dagurtomas', 'github-actions', 'idontgetoutmuch', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'peabrainiac'] mattrobball
assignee:mattrobball
4-51254
4 days ago
73-12351
73 days ago
132-52535
132 days
2
42113 LAC1213
author:LAC1213
feat(RingTheory/Noetherian): injective modules over a Noetherian ring… … surject onto localizations by powers of an element. [Hartshorne III.3.3] Disclaimer: I used Claude to help me find the names of useful lemmas and definitions and explain lean errors to me. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-ring-theory new-contributor LLM-generated 114/0 Mathlib.lean,Mathlib/Algebra/Module/Torsion/Basic.lean,Mathlib/RingTheory/Noetherian/InjectiveModule.lean 3 46 ['LAC1213', 'NoahW314', 'github-actions', 'robin-carlier', 'tb65536'] alreadydone
assignee:alreadydone
4-51251
4 days ago
118-4416
118 days ago
118-29089
118 days
0
45437 zblore
author:zblore
feat(Analysis/Normed/Module): projective space is Hausdorff and compact This shows `ℙ K V` is Hausdorff when continuous linear forms separate the points of `V`. Here `K` is Hausdorff with continuous multiplication and each unit of `K` acts continuously on `V`. It also shows `ℙ K V` is compact when `V` is a finite-dimensional topological vector space over a locally compact nontrivially normed field like ℝ, ℂ or the p-adics. Hausdorff uses the open quotient map from #44117. Two nonzero vectors span the same line exactly when `f v * g w = f w * g v` for all continuous linear forms `f` and `g`. The same-line relation is an intersection of closed sets. Compactness goes through the compact shell in a proper normed space and then a basis. It also adds an instance that continuous linear forms separate points in a finite-dimensional Hausdorff topological vector space over a complete nontrivially normed field. Mathlib's existing instances need ℝ or ℂ. With it `ℙ K V` is compact and Hausdorff for every finite-dimensional Hausdorff topological vector space `V` over a complete locally compact nontrivially normed field. The Hausdorff part is adapted from the Tau Ceti project's [projective space file](https://github.com/TauCetiProject/TauCeti/blob/06c598245d42977f79bf09aafd3154dd215c23cd/TauCeti/Topology/Algebra/Projectivization.lean). The compactness proof and the separating dual instance are new. This covers the compactness and Hausdorff instances for real projective space in #25999 but not its main result. This is the next step towards the Fubini-Study metric and measure. I asked on Zulip whether this file is in the right place: https://leanprover.zulipchat.com/#narrow/id/634983707 --- I used Claude to draft the Lean against the existing Mathlib API. I used Codex and Claude to review it. I've reworked and checked every line myself and can explain all of it. t-topology t-analysis LLM-generated new-contributor 151/0 Mathlib.lean,Mathlib/Analysis/Normed/Module/Projectivization.lean 2 3 ['github-actions', 'zblore'] nobody
4-50343
4 days ago
24-68231
24 days ago
24-68176
24 days
0
42093 DrDMT-VR
author:DrDMT-VR
feat(Topology/Algebra/Ring): topological closure of a two-sided ideal Defines `TwoSidedIdeal.closure`, the topological closure of a two-sided ideal in a topological ring, together with its basic API. This mirrors the existing one-sided `Ideal.closure` (`Mathlib/Topology/Algebra/Ring/Ideal.lean`), but is stated in the generality of non-unital non-associative topological rings (`IsTopologicalRing` over `NonUnitalNonAssocRing`), where one-sided ideals are unavailable. New declarations (namespace `TwoSidedIdeal`): `closure`, `coe_closure`, `mem_closure_iff`, `le_closure`, `closure_mono`, `closure_minimal`, `isClosed_closure`, `closure_eq_of_isClosed`, `closure_closure`, `closure_top`, and `closure_ne_top` (in a unital ring whose units are open, e.g. a Banach algebra via `Units.isOpen`, the closure of a proper two-sided ideal is proper). Mathlib has no topological-closure API for `TwoSidedIdeal`. Closed two-sided ideals are the basic objects of C*-algebra ideal theory, and `closure_ne_top` is the standard first step toward "maximal two-sided ideals are closed". ------ - should the definition be called `topologicalClosure` instead? (The current name matches `Ideal.closure`.) - Claude was utilized throughout the project. It helped with coding, syntax and running repetitive testing. t-topology new-contributor LLM-generated 127/0 Mathlib.lean,Mathlib/Topology/Algebra/Ring/TwoSidedIdeal.lean 2 16 ['DrDMT-VR', 'FractalDevTeam', 'github-actions', 'grunweg', 'j-loreaux'] nobody
4-50339
4 days ago
25-64488
25 days ago
63-56564
63 days
0
43539 abhijitaj1997
author:abhijitaj1997
feat(CategoryTheory/Monoidal/Cartesian/Endomorphism): add ring and semiring structures Given two monoidal object in a nice enough category, this show that the monoidal morphisms between then forms an additive group. This additive group is part of a larger semiring structure. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-category-theory 133/0 Mathlib.lean,Mathlib/CategoryTheory/Monoidal/Cartesian/Endomorphism.lean 2 41 ['Multramate', 'abhijitaj1997', 'alreadydone', 'github-actions', 'joelriou', 'robin-carlier'] nobody
4-50337
4 days ago
25-69080
25 days ago
74-28218
74 days
0
41882 theebayuser
author:theebayuser
feat(Data/List): decidability of HasPeriod and periods of repeated lists Hello, this PR extends `Mathlib/Data/List/PeriodicityLemma.lean` with: * a `Decidable (List.HasPeriod w p)` instance (it is a prefix test), and * two directions that relate periods to repetition: * `hasPeriod_flatten_replicate` — `(replicate n l).flatten` has period `l.length` * `eq_flatten_replicate_of_hasPeriod` — a word with period `p` and length `r * p` is the `r`-fold repetition of its length-`p` prefix. This characterizes `r`-th powers of words by a period plus a length constraint, which a future follow-up PR that I plan to work on will use. AI disclosure: This code was mostly generated by Claude Fable 5 and Opus 4.8 as part of my larger project on combinatorics on words, which I then reviewed and revised to contribute to mathlib. t-data LLM-generated new-contributor 56/1 Mathlib/Data/List/PeriodicityLemma.lean 1 8 ['SnirBroshi', 'github-actions', 'theebayuser'] nobody
4-50335
4 days ago
43-36253
43 days ago
127-27950
127 days
0
43871 manman4
author:manman4
feat(PowerSeries): add Lagrange inversion formula ## What this PR adds This PR formalizes the Lagrange inversion formula for formal power series over commutative rings without additive torsion (`HasUniqueDiv R`), together with divided versions over characteristic-zero fields. For formal power series `P`, `Y`, and `H` over such a ring, suppose `Y = X * P.subst Y`. Then, for every natural number `n`, the Lagrange–Bürmann formula states: ``` (n + 1)[X^{n + 1}]H(Y) = [X^n](H' P^{n + 1}). ``` The brackets denote coefficient extraction, and `H'` denotes the formal derivative of `H`. Over a characteristic-zero field, dividing by `n + 1` gives the usual coefficient formula. ## Proof and scope The proof follows the inductive argument of Surya and Warnke. The torsion-free assumption is used to cancel multiplication by positive natural numbers. Following the review suggestions, this PR is restricted to the torsion-free version. ## Motivation Lagrange inversion is a classical tool in enumerative combinatorics, treated for example in Section 5.4 of Richard P. Stanley’s *Enumerative Combinatorics*, Volume 2. It gives coefficient formulas for implicitly defined generating functions, with applications to counting rooted trees and other recursively defined combinatorial structures. My motivation was to make this tool, which is also used in competitive programming, available in Mathlib. ## LLM We (Julian and I) used Aristotle and Codex for code generation and ChatGPT and Claude for cleanup. t-ring-theory new-contributor LLM-generated 212/0 Mathlib.lean,Mathlib/RingTheory/PowerSeries/Basic.lean,Mathlib/RingTheory/PowerSeries/Derivative.lean,Mathlib/RingTheory/PowerSeries/LagrangeInversion.lean,Mathlib/RingTheory/PowerSeries/Substitution.lean,docs/references.bib 6 126 ['JX-Mo', 'Julian-Kuelshammer', 'github-actions', 'manman4', 'wwylele'] nobody
4-14224
4 days ago
22-14354
22 days ago
67-2860
67 days
0
44591 r-irbe
author:r-irbe
feat(Analysis/SpecificLimits/Cesaro): cesaro means of geometrically dominated sequences in normed spaces Adding this because the Cesaro-mean step appears inside ergodic and mixing arguments constantly + mathlib's `SpecificLimits` files do not carry it. It proves that a sequence has convergent Cesaro means with an explicit rate via the following four lemmas: - `norm_sum_range_smul_le_of_norm_le_geometric`: `‖a k‖ ≤ C * r ^ k → ‖n⁻¹ • ∑ a k‖ ≤ (C / (1 - r)) * n⁻¹` in any normed space; - `tendsto_sum_range_smul_nhds_zero_of_norm_le_geometric`: the means tend to zero, via `squeeze_zero_norm'`; The real-valued forms are worked out as full examples in `MathlibTest/Cesaro.lean`, alongside further usage examples including the orbit-average case and serve as documentation for users :) Disclaimer: I used AI for proof golfing. Every proof is kernel-checked and I take full responsibility for the mathematics. t-analysis new-contributor 176/0 Mathlib.lean,Mathlib/Analysis/SpecificLimits/Cesaro.lean,MathlibTest/Cesaro.lean 3 3 ['github-actions'] nobody
4-2637
4 days ago
4-3292
4 days ago
4-3237
4 days
0
45513 PSchwahn
author:PSchwahn
feat(Data/Fin/Tuple): add Fin.cons_cons_swap `Fin.cons_cons_swap` shows that composing `cons x (cons y q)` with the transposition swapping 0 and 1 yields `cons y (cons x q)`. --- t-data new-contributor 13/0 Mathlib/Data/Fin/Tuple/Basic.lean 1 7 ['PSchwahn', 'github-actions', 'themathqueen'] nobody
3-79524
3 days ago
22-68299
22 days ago
22-68244
22 days
0
45498 ShirinShafaie
author:ShirinShafaie
feat(LinearAlgebra): identify Sp₂(R) with SL₂(R) This PR resolves the TODO in `Mathlib.LinearAlgebra.SymplecticGroup`: > For `n = 1` the symplectic group coincides with the special linear group. I formalised this as an explicit group isomorphism between the two-dimensional symplectic group and `SL₂(R)`, over any commutative ring. The proof is developed in five steps: 1. **Determinant formula.** I first established the two-by-two determinant formula for matrices indexed by `ι ⊕ m`, with a chosen index in each of the two subsingleton types. This gives the reusable public theorem `Matrix.det_subsingleton_sum_subsingleton`. 2. **Symplectic characterisation.** Using this formula and the existing block-matrix characterisation of symplectic matrices, I proved that a matrix indexed by `ι ⊕ ι` for a subsingleton `ι` is symplectic if and only if its determinant is one. This gives `SymplecticGroup.mem_subsingleton_iff_det_eq_one`. 3. **Group equivalence.** The determinant-one characterisation then gives `subsingletonEquivSpecialLinear`, a group equivalence between the symplectic group and the special linear group on `m ⊕ m` for any finite subsingleton `m`, without changing the underlying matrices. 4. **Reindexing to `Fin 2`.** The symplectic matrices are indexed by `Fin 1 ⊕ Fin 1`, while the usual `SL₂(R)` is indexed by `Fin 2`. I initially implemented the required general reindexing equivalence for special linear groups in [PR 45495](https://github.com/leanprover-community/mathlib4/pull/45495). It was then pointed out that [PR 44094](https://github.com/leanprover-community/mathlib4/pull/44094) was already developing a more general `Matrix.SpecialLinearGroup.reindex` API, so PR 45495 was closed in favour of that work. Now that PR 44094 has merged, this PR uses the resulting `SpecialLinearGroup.reindex` equivalence directly. Composing it with `subsingletonEquivSpecialLinear R (Fin 1)` gives `finOneEquivSL2`, closing the original TODO. 5. **Supporting lemmas and integration.** I added simp lemmas describing the forward and inverse equivalences, replaced the original TODO with a pointer to the new result, and included the new module in `Mathlib.lean`. I came across this TODO while taking the Shared Graduate Course, *Elements of Mathematical Formalization and Auto-Formalization with Lean*, at the Fields Institute. I started working on it as a project alongside the course exercises, and discussed an earlier version in a private review. That feedback led me to investigate several alternatives, including the generalisation to singleton index types. Throughout the project, I worked with OpenAI Codex and GPT-6 to explore proof approaches, work through Lean implementation details and test alternative formulations. I evaluated these against the mathematics and the existing mathlib definitions, made the final choices about the theorem statements, proof structure and supporting lemmas, and personally ran the builds and verification in VS Code. I take responsibility for the final formalisation and the code submitted here. **Checks:** `lake build Mathlib.LinearAlgebra.SymplecticGroup.SpecialLinearGroup`, `lake exe mk_all --check`, and `lake exe lint-style` all passed. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #44094 LLM-generated t-algebra new-contributor
label:t-algebra$
129/2 Mathlib.lean,Mathlib/LinearAlgebra/Matrix/Determinant/Basic.lean,Mathlib/LinearAlgebra/SymplecticGroup.lean,Mathlib/LinearAlgebra/SymplecticGroup/SpecialLinearGroup.lean 4 20 ['ShirinShafaie', 'github-actions', 'mathlib-dependent-issues', 'themathqueen'] nobody
3-66979
3 days ago
3-67734
3 days ago
19-21789
19 days
0
45791 JonasReif
author:JonasReif
chore: remove obsolete proof workarounds Several proofs still carried workarounds marked by TODOs, porting notes, an adaptation note, or `erw`, for problems that have since been fixed: the missing lemmas now exist, or Lean no longer needs the hint. This PR removes those workarounds. Only proofs change; every statement stays the same. - `PullbackCone.isLimitOfFactors`: use `t.condition_assoc h` instead of the manual reassoc workaround - `Scheme.basicOpen_add_le`: use `Opens.mem_sup` (resolves the TODO) - `Cardinal.toNat_congr`: use `mk_congr_lift`, dropping the universe hint - `LieIdeal.map_of_image`: replace `erw [h]` with `exact h.subset` - `isPullback_inl_inl_coprodMap`: plain `simp` works now that `Scheme.Hom.mem_opensRange` exists (resolves the TODO) - `Proj.fromOfGlobalSections_preimage_basicOpen`: use `Scheme.Hom.mem_preimage` (resolves the TODO) - `Tuple.graph.card`: one-line injectivity proof - `StarModule.decomposeProdAdjoint`: drop the `erw` and its outdated note - `skyscraperPresheaf_isSheaf`: the universe annotation is no longer needed --- Created with Claude Opus 5.5 in Claude Code. 🤖 Generated with [Claude Code](https://claude.com/claude-code) tech debt new-contributor 11/29 Mathlib/Algebra/Lie/Ideal.lean,Mathlib/Algebra/Star/Module.lean,Mathlib/AlgebraicGeometry/Limits.lean,Mathlib/AlgebraicGeometry/ProjectiveSpectrum/Basic.lean,Mathlib/AlgebraicGeometry/Scheme.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/Mono.lean,Mathlib/Data/Fin/Tuple/Sort.lean,Mathlib/SetTheory/Cardinal/ToNat.lean,Mathlib/Topology/Sheaves/Skyscraper.lean 9 9 ['JonasReif', 'Parcly-Taxel', 'github-actions', 'grunweg'] nobody
3-57803
3 days ago
3-60552
3 days ago
4-8480
4 days
0
42630 will1491
author:will1491
feat(Analysis/Complex): define Wirtinger derivatives Define the Wirtinger derivatives `Complex.wirtingerDeriv` and `Complex.wirtingerDerivBar` from `fderiv ℝ`, and prove: the Cauchy-Riemann characterization of complex differentiability (pointwise and on open sets), agreement of `wirtingerDeriv` with `deriv` for holomorphic functions, additivity, Leibniz product rules, conjugation identities, both Wirtinger chain rules, and the Wirtinger decomposition of a real-linear map `ℂ →L[ℝ] ℂ`. Extracted from https://github.com/will1491/RiemannDynamics, where it underlies the Beltrami-equation and Cauchy/Beurling-transform theory used in the proof of the measurable Riemann mapping theorem. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis new-contributor 253/0 Mathlib.lean,Mathlib/Analysis/Complex/Wirtinger.lean 2 6 ['Maldooor', 'github-actions', 'mathlib-merge-conflicts', 'will1491'] j-loreaux
assignee:j-loreaux
3-51257
3 days ago
72-65340
72 days ago
103-40926
103 days
0
42912 justin-palumbo
author:justin-palumbo
feat(Topology/GDelta): a completely metrizable subspace of a T6 space is Gδ Adds TopologicalSpace.IsCompletelyMetrizableSpace.isGδ: a completely metrizable subspace of a T6 space is Gδ This is one direction of a foundational fact in descriptive set theory --- the Polish subspaces of a Polish space are exactly the Gδ subsets. The proof here is modeled on the exposition in Anush Tserunyan's descriptive set theory notes https://www.math.mcgill.ca/atserunyan/Teaching_notes/dst_lectures.pdf, with one adjustment; to make the formalization easier and avoid having multiple distance metrics instantiated at the same time, instead of directly defining open `U_n` with `s = ⋂ n, U` define them such that `s = closure s ∩ ⋂ n, U n` and then appeal to the fact closed sets are Gδ in a perfectly normal space. --- - [x] depends on: #42896 [which fixes buggy naming present in Topology/Metrizable/CompletelyMetrizable] This can be viewed as a companion to #42693, which - under the stronger assumption of the ambient space being Polish - establishes the other direction --- a Gδ subspace of a Polish space is itself Polish. Together, these give Alexandrov's theorem, characterizing the Polish subspaces of an ambient Polish space as exactly the Gδ ones, and (via `Metric.PiNatEmbed.exists_embedding_to_hilbert_cube`) Polish spaces as exactly the Gδ subsets of the Hilbert cube. If and when both these PRs are committed, I anticipate adding these consequences to Topology/MetricSpace/Polish.lean LLM usage: I wrote the initial version myself, while using Google's free "AI mode" to help me find relevant lemma names in the codebase, and afterward used helped Claude Opus to review, which led to simplifying some of the arguments. I take full responsibility for the code here t-topology new-contributor 91/0 Mathlib.lean,Mathlib/Topology/GDelta/CompletelyMetrizable.lean 2 8 ['github-actions', 'justin-palumbo', 'mathlib-dependent-issues', 'plp127'] j-loreaux
assignee:j-loreaux
3-51255
3 days ago
95-8038
95 days ago
95-8280
95 days
0
42142 philipp-svinger
author:philipp-svinger
feat(Analysis/ODE): peano existence theorem, Tonelli approximation 1 Add Tonelli approximation method for ODEs. Implement the structure IsPeano similar to IsPicardLindelof. Construct a sequence of approximations using Tonelli technique. First step towards Peano existence Co-authored-by: Florian Grube <fgrube@math.uni-bielefeld.de> Co-authored-by: Paul Niessner <pniessner@math.uni-bielefeld.de> Co-authored-by: Julian Rolfes <jrolfes@math.uni-bielefeld.de> Co-authored-by: Luke Schleef <lschleef@math.uni-bielefeld.de> Co-authored-by: Philipp Svinger <psvinger@math.uni-bielefeld.de> --- We want to add the proof of the Peano existence theorem for ODEs, using Tonelli approximations. This will be a series of PRs working towards this goal. In this first PR, we implement the structure IsPeano similar to IsPicardLindelof and construct a sequence of approximations using Tonelli technique. See our further PRs for more information, last: #42148 --- The statements, definitions and proofs were written without AI. AI was used afterwards to help us to adapt our code to the style and naming conventions. We also used it in the process of writing a documentation. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis new-contributor 207/0 Mathlib.lean,Mathlib/Analysis/ODE/Peano.lean 2 24 ['github-actions', 'mcdoll', 'philipp-svinger', 'sgouezel'] nobody
3-50352
3 days ago
57-69688
57 days ago
114-32670
114 days
5
46202 gloges
author:gloges
feat(Analysis/InnerProductSpace): inner products for `PiTensorProduct` Following up on #45819, adds inner products for pi tensor products `⨂[𝕜] i : ι, E i` of 𝕜-inner product spaces `E i`. This follows [Mathlib.Analysis.InnerProductSpace.TensorProduct](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Analysis/InnerProductSpace/TensorProduct.html) fairly closely. - The inner product is defined by lifting the product of the component inner products, so that `⟪⨂ₜ[𝕜] i, x i, ⨂ₜ[𝕜] i, y i⟫ = ∏ i, ⟪x i, y i⟫`. - `exists_finite_submodule_of_setFinite` (which itself depends on `range_map_mono` and `range_mapIncl_mono`) is required for `InnerProductSpace.Core`, following the proof strategy used for [TensorProduct.instNormedAddCommGroup](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Analysis/InnerProductSpace/TensorProduct.html#TensorProduct.instNormedAddCommGroup) in which `inner_self` relies on having finite orthonormal bases. - Includes linear isometry (equivelence) versions of `PiTensorProduct.map`, `PiTensorProduct.congr`, `PiTensorProduct.mapIncl`, `PiTensorProduct.reindex`, `PiTensorProduct.isEmptyEquiv`, `PiTensorProduct.subsingletonEquiv`, and their basic properties. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor 344/0 Mathlib.lean,Mathlib/Analysis/InnerProductSpace/PiTensorProduct.lean,Mathlib/LinearAlgebra/PiTensorProduct/Basic.lean,Mathlib/LinearAlgebra/PiTensorProduct/Finite.lean 4 3 ['github-actions', 'gloges'] nobody
3-48589
3 days ago
3-49081
3 days ago
3-49026
3 days
0
45950 kac3pro
author:kac3pro
feat: defining the Gauss map and gauss measure This PR defines the Gauss map and the Gauss measure on [0,1). This is the beginning of the work on connecting the theory of continued fractions to dynamics. LLM usage: LLMs were used primarily as a way to quickly search for relevant lemmas/techniques in the mathlib. All the code is human written. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-dynamics new-contributor 124/0 Mathlib.lean,Mathlib/Dynamics/Ergodic/GaussMap.lean 2 4 ['EtienneC30', 'github-actions', 'lua-vr'] mcdoll
assignee:mcdoll
3-45390
3 days ago
9-83272
9 days ago
9-83217
9 days
0
45727 pleich
author:pleich
feat(Order/WellFoundedSet): PWO iff well-founded with finite antichains Add `Set.partiallyWellOrderedOn_iff_wellFoundedOn_and_finite_antichains`: For preorder `r`, a set is partially well-ordered iff the strict part of `r` is well-founded on it and all antichains are finite. This removes the open TODO in the module docstring. Additionally, prove theorem `IsAntichain.finite_of_partiallyWellOrderedOn` by reusing the analog theorem (`IsAntichain.finite_of_wellQuasiOrdered `) for well-quasi orders and remove the corresponding TODO. This commit has been assisted by Claude Code with Opus 5.5. --- This is my first PR to the mathlib project, and I am welcome for any feedback. If these TODOs are already assigned to others, feel free to close the PR. Claude has been used to create this PR, in particular to help me understand the relevant definitions, make the proofs more concise, adhering to the mathlib style and to review my proposed changes afterwards. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-order new-contributor 19/6 Mathlib/Order/WellFoundedSet.lean 1 5 ['SnirBroshi', 'github-actions', 'mathlib-merge-conflicts', 'pleich'] nobody
2-86352
2 days ago
3-2171
3 days ago
16-10558
16 days
0
44214 ZRTMRH
author:ZRTMRH
feat(Analysis/SpecialFunctions): taylor series bounds for sin and cos Adds `Mathlib/Analysis/SpecialFunctions/Trigonometric/SeriesBounds.lean` with three groups of results: 1. Remainder bounds on the unit disc at every order: `Complex.sin_series_bound`, `Complex.cos_series_bound` and their real forms. Ported from #29355, taken over with the author's agreement. This PR supersedes #29355, which can be closed when this lands. 2. `Real.sum_lt_sin_of_pos`, `Real.sin_lt_sum_of_pos`, `Real.sum_lt_cos_of_pos`, and `Real.cos_lt_sum_of_pos`: `sin x` and `cos x` lie between consecutive partial sums of their Taylor series. Yury posted on Zulip in October 2025 with a request that someone open a PR for it ([Upper and Lower Bounds of Cosine](https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/Upper.20and.20Lower.20Bounds.20of.20Cosine/near/546287708)), it had not been opened. 4. Six low-order corollaries, as completion to `one_sub_sq_div_two_lt_cos` and `sin_gt_sub_cube` which Mathlib already has: `cos_lt/le_one_sub_sq_div_two_add_pow_four`, `sin_lt/le_sub_cube_add_pow_five`, and `sub_cube_add_pow_five_lt/le_sin` for negative arguments. The 6 low-order corollaries and the docstrings were written with AI assistance (Claude). The code has been reviewed by the author. Co-authored-by: Geoffrey Irving <irving@naml.us> Co-authored-by: Yury G. Kudryashov <urkud@urkud.name> --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> LLM-generated new-contributor t-analysis 288/0 Mathlib.lean,Mathlib/Algebra/BigOperators/Ring/Finset.lean,Mathlib/Analysis/SpecialFunctions/Trigonometric/SeriesBounds.lean 3 63 ['SnirBroshi', 'ZRTMRH', 'github-actions', 'luigi-massacci', 'wwylele'] nobody
2-83831
2 days ago
2-83831
2 days ago
50-74572
50 days
0
46121 ldiedering
author:ldiedering
feat(MeasureTheory): add more API for `NoAtoms` Main additions: - `NoAtoms` implies `NullSingletonClass` under mild assumptions, which however cannot be dropped (`instNullSingletonClass`, `instNullSingletonClass_of_sfinite`). - The restriction of a nonatomic measure is again nonatomic under mild assumptions (`restrict`, `Measure.restrict.instNoAtoms`). - API for the interaction of `IsAtom` and `NoAtoms` with `MeasurableEquiv`. This PR builds directly on the new definition of `NoAtoms` introduced in #45666. --- Use of AI: A first version of the new API was written manually as part of the Carleson project. Claude Code was then used to create a plan for upstreaming, suggest additional lemmas, golf proofs and write documentation. <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability new-contributor LLM-generated 136/3 Mathlib/MeasureTheory/Measure/Typeclasses/NoAtoms.lean 1 12 ['felixpernegger', 'github-actions', 'ldiedering', 'lua-vr', 'wwylele'] nobody
2-82477
2 days ago
3-84176
3 days ago
4-10013
4 days
0
46261 SHW715
author:SHW715
feat(MeasureTheory/Function/Holder): add `ContinuousLinearMap.norm_lpPairing_le` Add `ContinuousLinearMap.norm_lpPairing_le`: `‖B.lpPairing μ p q‖ ≤ ‖B‖`. This is the analogue for `lpPairing` of `ContinuousLinearMap.norm_holderL_le` earlier in this file. --- I need this inequality for showing that `B.lpPairing` is an isometry when `B` is an isometry (under certain conditions). This is the straightforward direction of that result. The proof was written with the help of AI (Claude), which helped me find the relevant lemmas. t-measure-probability new-contributor 7/0 Mathlib/MeasureTheory/Function/Holder.lean 1 2 ['github-actions'] nobody
2-66775
2 days ago
2-67342
2 days ago
2-67287
2 days
0
45794 ambrose-tang
author:ambrose-tang
feat(LinearAlgebra/Matrix/Cartan/Basic): submatrices and bonds of finite Cartan matrices This PR adds basic API for `Matrix.IsFiniteCartan`: * relabellings of finite Cartan matrices are finite Cartan matrices (`IsFiniteCartan.reindex`, `IsFiniteCartan.submatrix_equiv_iff`); * `IsFiniteCartan.mul_lt_four`: `Mᵢⱼ Mⱼᵢ < 4` for `i ≠ j`; * `CartanMatrix.bonds` (the five possible pairs `(Mᵢⱼ, Mⱼᵢ)` of non-zero off-diagonal entries), the predicate `CartanMatrix.IsBond` with the characterisation `CartanMatrix.isBond_iff`, and `IsFiniteCartan.apply_cases`; * `CartanMatrix.IsBond` and `IsFiniteCartan.apply_cases`: the five possible pairs `(Mᵢⱼ, Mⱼᵢ)` of non-zero off-diagonal entries; * the symmetries `CartanMatrix.A_submatrix_revPerm` and `CartanMatrix.D_submatrix_swap`. This is part 1 of 7 of the classification of finite Cartan matrices (`Matrix.IsFiniteCartan.exists_A_or_B_or_C_or_D_or_E_or_F_or_G`, see `Wanted/LinearAlgebra/Matrix/Cartan/Basic.lean`). t-algebra new-contributor
label:t-algebra$
100/1 Mathlib/LinearAlgebra/Matrix/Cartan/Basic.lean 1 19 ['ambrose-tang', 'github-actions', 'mathlib-merge-conflicts', 'vihdzp', 'wwylele'] nobody
2-25504
2 days ago
2-27267
2 days ago
10-67530
10 days
6
45828 aliquis11
author:aliquis11
feat(Analysis/InnerProductSpace/LinearPMap): characterise the adjoint domain Add a characterisation of the adjoint domain of a densely defined operator. The existing mem_adjoint_domain_of_exists gives one implication. The new result states that domain membership is equivalent to the existence of a vector satisfying the inner product identity. This standard characterisation from functional analysis is useful in constructing the Friedrichs extension. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-analysis new-contributor 33/0 Mathlib/Analysis/InnerProductSpace/LinearPMap.lean,Mathlib/Topology/Algebra/Module/ContinuousLinearMap/Restrict.lean 2 19 ['aliquis11', 'github-actions', 'j-loreaux', 'lyw-ops', 'mcdoll'] nobody
2-20954
2 days ago
2-22824
2 days ago
8-70734
8 days
0
41915 theebayuser
author:theebayuser
feat(Data/List): infixes, the enumerator of contiguous factors This PR adds `List.infixes`, which is the list of all infixes of a list. --- AI disclosure: This code was mostly generated by Claude Fable 5 and Opus 4.8 as part of my larger project on combinatorics on words, which I then reviewed and revised to contribute to mathlib. t-data LLM-generated new-contributor 37/2 Mathlib/Data/List/Infix.lean 1 7 ['YaelDillies', 'github-actions', 'mathlib-merge-conflicts', 'theebayuser'] YaelDillies
assignee:YaelDillies
2-17407
2 days ago
3-22470
3 days ago
109-38672
109 days
0
41069 ymonbru
author:ymonbru
feat: adds the definition of the pushforward of a Ksheaf For f: X to Y a proper map between T2 spaces and Y being locally comapct, this files adds the pushforward of KSheaves: in particular one gets a functor from Ksheaf A X to Ksheaf A Y. In order to prove this lemma, we add the fact that the base changes of compact neighbourhoods of K to f^-1(K) is an initial functor. This require to know that if f is closed then kernImage f (the adjoint of the preimage) is Open. (Note that if f is open then kernImage f is closed, we thus add this lemma even though we do not use it there). We also add the ddefinition of the pushforward of a bicartesian square in order to define the pushforward. Maybe the `properPreimage`in l.101 of BasechngeNhds should go elsewhere but find_home told me to let it there. --- - [x] depends on: #40953 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-topology t-category-theory 99/2 Mathlib/Order/CompleteLattice/MulticoequalizerDiagram.lean,Mathlib/Topology/Sets/BaseChangeNhds.lean,Mathlib/Topology/Sheaves/KSheaf.lean 3 45 ['Multramate', 'github-actions', 'joelriou', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'ymonbru'] nobody
2-4095
2 days ago
2-4467
2 days ago
3-37904
3 days
0
46148 kirill-kondrashov
author:kirill-kondrashov
feat(LinearAlgebra/ExteriorPower): hodgeStar isometry Prove that, for any bijective bilinear form `B`, the Hodge star preserves the induced bilinear form on exterior powers up to a scalar: ``` Δ * B.exteriorPower l (hodgeStar B hB vol hkl x) (hodgeStar B hB vol hkl y) = B.exteriorPower k x y ``` where `Δ := B.exteriorPower (finrank R M) (vol.symm 1) (vol.symm 1)`. This removes the corresponding item from the `TODO` in `Mathlib/LinearAlgebra/ExteriorPower/HodgeStar.lean`. The proof was assisted by Claude Sonnet 5.5 Max in a multi-prompt session with manual adjustments and human review. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra LLM-generated new-contributor
label:t-algebra$
58/8 Mathlib/LinearAlgebra/ExteriorPower/BilinForm.lean,Mathlib/LinearAlgebra/ExteriorPower/HodgeStar.lean 2 6 ['github-actions', 'kirill-kondrashov', 'ocfnash'] nobody
2-188
2 days ago
2-680
2 days ago
2-85631
2 days
0
43884 joelcanary
author:joelcanary
feat(NumberTheory/ArithmeticFunction): the gcd matrix and Smith's determinant This PR adds the GCD matrix `Matrix.gcdMatrix n f` (entry `f (gcd (i + 1) (j + 1))`) and proves **Smith's determinant** (1875): if `f m = ∑ d ∈ m.divisors, g d` for every `m ≥ 1` (i.e. `f = g * ζ` as arithmetic functions), then `det (gcdMatrix n f) = ∏ i, g (i + 1)`, over any commutative ring (`Matrix.det_gcdMatrix`). The classical case `det [gcd (i, j)] = φ 1 * φ 2 * ⋯ * φ n` is `Matrix.det_gcdMatrix_id`, from `Nat.sum_totient`. Proof: the factorisation `gcdMatrix n f = Zᵀ * (D * Z)` (`Matrix.gcdMatrix_eq_transpose_mul_mul`) with `Z = zetaMatrix R n` from #43758 and `D = diagonal (g (i + 1))`; entry-wise this is `∑ k, [k + 1 ∣ i + 1] [k + 1 ∣ j + 1] g (k + 1) = ∑ d ∣ gcd (i + 1) (j + 1), g d`, obtained from the reindexing lemma of #43880 with `a = 1` and `Nat.dvd_gcd_iff` (`Nat.sum_fin_dvd_dvd_eq_sum_divisors_gcd`). Then `det Z = 1` (`Matrix.det_zetaMatrix`) and `det_diagonal`. New file `Mathlib/NumberTheory/ArithmeticFunction/Smith.lean`, importing `Data.Nat.Totient` and `NumberTheory.ArithmeticFunction.ZetaMatrixInv`; `docs/references.bib` gets `smith1875`. The divisor-function instances are included as one-line corollaries: `Matrix.det_gcdMatrix_sigma` (`det [σ k (gcd i j)] = ∏ (i + 1) ^ k`, so `n!` for `k = 1`) and `Matrix.det_gcdMatrix_card_divisors` (`det [τ (gcd i j)] = 1`). The LCM matrix is left for a follow-up. AI use: the Lean code and this description were written with an AI agent (Claude) under my direction, from a proof in my own project; I reviewed every declaration, and the branch was checked locally with `lake build`, `lake exe lint-style`, `lake exe runLinter` and `scripts/lint-bib.sh` before pushing. - [x] depends on: #43880 t-number-theory LLM-generated new-contributor 531/0 Mathlib.lean,Mathlib/NumberTheory/ArithmeticFunction/Moebius.lean,Mathlib/NumberTheory/ArithmeticFunction/Redheffer.lean,Mathlib/NumberTheory/ArithmeticFunction/Smith.lean,Mathlib/NumberTheory/ArithmeticFunction/ZetaMatrixInv.lean,docs/references.bib 6 6 ['github-actions', 'joelcanary', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-83474
1 day ago
1-83477
1 day ago
1-84390
1 day
0
45072 HugLycan
author:HugLycan
refactor(Tactic/Positivity): add a cache This PR adds caching to `positivity`, following the implementation in `FunProp`. It is the first step towards #45305 . This does not speed up mathlib but is crucial for `positivity_lemma` attribute. The two test example in the newly created file `Positivity/Cache.lean` took 359 heartbeats and 641 heartbeats respectively before the PR, and 172 heartbeats and 568 heartbeats afterwards. We had to change many positivity extensions for two reasons: - The type of `PositvityExt` has changed from `MetaM` to `PositivityM`. - We have to return `.none` instead of failing to preserve the cache. Most of the positivity extensions will soon be replaced by the `positivity_lemma` attribute. --- <!-- Your PR title will become the first line of the commit messag In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor t-meta file-removed 526/343 Mathlib/Algebra/Order/Algebra.lean,Mathlib/Algebra/Order/BigOperators/Ring/Finset.lean,Mathlib/Algebra/Order/Floor/Extended.lean,Mathlib/Algebra/Order/Floor/Ring.lean,Mathlib/Algebra/Order/Interval/Basic.lean,Mathlib/Analysis/Complex/Exponential.lean,Mathlib/Analysis/Complex/Trigonometric.lean,Mathlib/Analysis/Complex/UpperHalfPlane/Basic.lean,Mathlib/Analysis/Normed/Algebra/GelfandRadius.lean,Mathlib/Analysis/Normed/Group/Basic.lean,Mathlib/Analysis/Real/Sqrt.lean,Mathlib/Analysis/SpecialFunctions/Gamma/Basic.lean,Mathlib/Analysis/SpecialFunctions/Log/Basic.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Analysis/SpecialFunctions/Pow/Real.lean,Mathlib/Analysis/SpecialFunctions/Trigonometric/Basic.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Basic/ENNReal/Real.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/Combinatorics/Enumerative/DyckWord.lean,Mathlib/Combinatorics/SimpleGraph/Regularity/Bound.lean,Mathlib/Combinatorics/SimpleGraph/Triangle/Removal.lean,Mathlib/Data/EReal/Basic.lean,Mathlib/Data/EReal/Inv.lean,Mathlib/Data/EReal/Operations.lean,Mathlib/Data/Nat/Choose/Multinomial.lean,Mathlib/Data/Nat/Totient.lean,Mathlib/Geometry/Convex/ConvexSpace/Defs.lean,Mathlib/Geometry/Euclidean/Altitude.lean,Mathlib/Geometry/Euclidean/Volume/Basic.lean,Mathlib/MeasureTheory/Covering/Besicovitch.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/NumberTheory/ArithmeticFunction/VonMangoldt.lean,Mathlib/NumberTheory/Chebyshev.lean,Mathlib/NumberTheory/Height/Basic.lean,Mathlib/NumberTheory/Height/NumberField.lean,Mathlib/NumberTheory/Height/Projectivization.lean,Mathlib/NumberTheory/LucasLehmer.lean,Mathlib/NumberTheory/SelbergSieve.lean,Mathlib/RingTheory/Radical/NatInt.lean,Mathlib/Tactic/LinearCombination.lean,Mathlib/Tactic/Positivity/Basic.lean,Mathlib/Tactic/Positivity/Core.lean,Mathlib/Tactic/Positivity/Finset.lean,Mathlib/Topology/Algebra/InfiniteSum/Order.lean,Mathlib/Topology/MetricSpace/Bounded.lean,Mathlib/Topology/MetricSpace/Pseudo/Defs.lean,MathlibTest/Tactic/Positivity/Basic.lean,MathlibTest/Tactic/Positivity/Cache.lean 49 15 ['HugLycan', 'JovanGerb', 'fpvandoorn', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] JovanGerb and fpvandoorn
assignee:fpvandoorn assignee:JovanGerb
1-82321
1 day ago
8-20678
8 days ago
13-30500
13 days
2
45670 user202729
author:user202729
chore(AlgebraicGeometry/EllipticCurve/Projective): remove `erw` in `Formula.lean` Reducing tech debt. The main reason why `erw` was needed in this file instead of `rw` is the following. - Background: Each point is represented by a function `P : Fin 3 → R`, and there's local notation `x` being `(0 : Fin 3)`, similar for `y` and `z`. So `P x` is the first coordinate of `P`. For a curve `W'` and a point `P`, `W'.dblXYZ P` is another point, its double i.e. `2 • P`. - There are functions to compute various operations on elliptic curves, for example, `W.dblY P` computes the `Y`-coordinate of `2 • P`. Of course, this can be equivalently written as `W.dblXYZ P y`. - The two forms `W.dblY P` and `W.dblXYZ P y` are not definitionally equal at the default transparency level. Depends on which lemma we want to apply, we need to convert the goal to use one form or the other. --- Personally, I think it's a better idea to normalize on the `W.dblXYZ P y` form, and keep the `W.dblY P` form as strictly an implementation detail if needed. In this case, the `XYZ` suffix wouldn't be needed either, and the main definitions would be: ``` * `WeierstrassCurve.Projective.neg`: The negation `-P` of a point `P`. * `WeierstrassCurve.Projective.dbl`: The double `2 • P` of a point `P`. * `WeierstrassCurve.Projective.negDbl`: The negated double `-(2 • P)` of a point `P`. ``` etc. Thoughts? Note that `W.dbl P y` is only 1 character longer than `W.dblY P`. Most lemmas that we want to apply are already stated in term of the point (except that many use `W.negY P` instead of `W.neg P y`, though currently `W.neg` doesn't exist). Also, there are (very) long `rw` chains. ([#mathlib4 > Is long &#96;rw&#96; chain bad?](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Is.20long.20.60rw.60.20chain.20bad.3F/with/637217759)) Ideas? Another idea: have a `array_index` tactic that evaluates `![a, b, c, d] 2` to `c` when the index is a known constant, for example. Currently there is `simp only [fin3_def_ext]` which obviously only works on length-3 arrays. new-contributor t-algebraic-geometry tech debt 59/24 Mathlib/AlgebraicGeometry/EllipticCurve/Projective/Formula.lean 1 5 ['Multramate', 'github-actions', 'tb65536'] nobody
1-79313
1 day ago
17-79115
17 days ago
17-79060
17 days
0
45053 tomaz1502
author:tomaz1502
feat(Analysis/Polynomial): the jump of a real rational function and the Cauchy index This PR defines `Polynomial.jumpVal p q x : ℤ`, the jump of the rational function `q / p` at a point `x`: `1` if it goes from `-∞` to `+∞`, `-1` if it goes from `+∞` to `-∞`, and `0` otherwise. The definition is algebraic: `q / p` changes sign at `x` exactly when `rootMultiplicity x p - rootMultiplicity x q` is odd, and the direction of the jump is then `signRight x (p * q)`. It develops the API of `jumpVal` needed for the Sturm–Tarski theorem: * `jumpVal_of_eval_ne_zero`, `jumpVal_of_rootMultiplicity_le`: there is no jump where `q / p` has no pole; * `jumpVal_mul_mul`: a common factor of `p` and `q` does not change the jump; * `jumpVal_mod`: `q` can be replaced by `q % p`; * `jumpVal_C_mul`: scaling `q` by `c` scales the jump by `sign c`; * `jumpVal_of_isCoprime`, `jumpVal_mul_one`: jumps of products of coprime polynomials; * `jumpVal_derivative_mul`: at a root `x` of `p`, the jump of `derivative p * q / p` is `sign (q.eval x)`. This is what links the Cauchy index to the signs of `q` at the roots of `p`. It also defines `Polynomial.rootsInInterval p a b`, the distinct roots of `p` in `(a, b)`, and the Cauchy index `Polynomial.cauchyIndex p q a b`, the sum of `jumpVal p q x` over those roots, with a few basic lemmas (`cauchyIndex_zero_left`, `cauchyIndex_zero_right`, `cauchyIndex_C`, `cauchyIndex_mul_mul`, `cauchyIndex_mod`, `cauchyIndex_C_mul`), which follow directly from the corresponding `jumpVal` lemmas. The main results about the Cauchy index (its relation to sign changes and to Tarski queries) will follow in the next PR of the series. One small addition to existing files: * `Polynomial.rootMultiplicity_C_mul` in `RingDivision.lean`: multiplying by a nonzero constant does not change root multiplicities; This is the fourth PR of a series formalising the Sturm-Tarski theorem, following #43783 (`List.signVariations`), #43954 (`Polynomial.sturmSeq`) and #44248 (`Polynomial.signRight`). Co-authored-by: Pedro Saccomani <psaccomani15@gmail.com> Co-authored-by: Sarah Pereira <sarahcomh@proton.me> --- The definitions and the original proofs, ported from Wenda Li's Isabelle/AFP entry, were written by hand. We used Claude to review the code, suggest improvements and help in the preparation of the PR. new-contributor t-analysis 248/0 Mathlib.lean,Mathlib/Analysis/Polynomial/CauchyIndex.lean 2 16 ['github-actions', 'mathlib-splicebot', 'ocfnash', 'tomaz1502', 'vihdzp'] ocfnash
assignee:ocfnash
1-67430
1 day ago
1-67736
1 day ago
11-25160
11 days
0
44679 Altabeh
author:Altabeh
feat(LinearAlgebra/FiniteDimensional/Lemmas): dimension counts - `Function.Exact.finrank_range_add_finrank_range`: For an exact sequence `A → B → C` with maps `f` and `g`, proves that `finrank (range f) + finrank (range g) = finrank B`, assuming `B` is finite and the relevant ranges are free. - `Function.Exact.linearEquivQuotientRangeProdKer`: For an exact sequence `A → B → C → D → E` with maps `f`, `g`, `h`, and `j`, constructs a linear equivalence `C ≃ₗ[R] (B ⧸ range f) × ker j`, assuming `ker j` is projective. This generalizes the splitting of exact sequences. - `Function.Exact.finrank_eq_finrank_quotient_range_add_finrank_ker`: Establishes the corresponding dimension formula `finrank C = finrank (B ⧸ range f) + finrank (ker j)`, assuming `C` is finite and the quotient and kernel are free. These results apply in particular to finite-dimensional vector spaces and extend the existing API for working with exact sequences, linear maps, and dimension identities in Mathlib. **These are basic results that have been written by myself. The only use of AI was to write the comments and test.** t-algebra new-contributor
label:t-algebra$
57/0 Mathlib/LinearAlgebra/FiniteDimensional/Lemmas.lean 1 20 ['Altabeh', 'Nicola9Falciola', 'artie2000', 'github-actions', 'grunweg'] nobody
1-65780
1 day ago
1-66834
1 day ago
43-69635
43 days
0
46174 ldiedering
author:ldiedering
feat(MeasureTheory): add `of_innerRegularCompactLTTop` to get `NoAtoms` from `NullSingletonClass` `of_innerRegularCompactLTTop` is planned to be used as the main way to upgrade instances of `NullSingletonClass` to `NoAtoms`, applicable to most of the instances currently in mathlib. It complements the reverse direction added in #46121, which holds under much weaker assumptions. --- Use of AI: Based on a partial proof strategy, Claude Code was used to write write statements and proofs. Intermediate statements were then extracted manually, with proofs again supplied by AI <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability new-contributor LLM-generated 96/1 Mathlib.lean,Mathlib/MeasureTheory/Measure/Regular.lean,Mathlib/MeasureTheory/Measure/Typeclasses/NoAtoms.lean,Mathlib/MeasureTheory/Measure/Typeclasses/NoAtoms/Regular.lean 4 7 ['github-actions', 'lua-vr'] nobody
1-63939
1 day ago
3-83565
3 days ago
3-83510
3 days
0
36896 PieterCuijpers
author:PieterCuijpers
feat (Algebra/Order/Quantale): isMulLeftsided, isMulRightsided, isMulTwosided and strict versions * Adding definitions of quantale elements being leftsided, rightsided, and twosided, and strict versions The reason for adding those is because, like for example with IsIdempotent elements in a group or semigroup, or prime elements or compact elements, the leftsided and rightsided elements have a special status in Quantale theory. They don't really occur anywhere else, a.f.a.i.k., hence I think a definition in Quantale.lean makes sense. The central theorem on two-sided elements that should imo be in the library is that any frame is a quantale with only two-sided idempotent elements, and vice versa any quantale with only two-sided idempotent elements is a frame. This establishes quantales as a generalization of point-free topology. This PR prepares for that theorem and others. I'm not sure whether it would already make sense to start a separate Quantale directory and put these definitions in a separate file there. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra new-contributor
label:t-algebra$
102/13 Mathlib/Algebra/Order/Quantale.lean 1 8 ['NoahW314', 'PieterCuijpers', 'chrisflav', 'copilot-pull-request-reviewer', 'github-actions', 'mathlib-merge-conflicts'] mariainesdff
assignee:mariainesdff
1-63907
1 day ago
1-64716
1 day ago
40-82883
40 days
0
41111 erdkocak
author:erdkocak
feat(ModelTheory): add cardinal-generated substructure API This is the first PR in a sequence splitting #40561. It adds a `CardinalLTGenerated` predicate for substructures, basic closure and map lemmas, and the finitely generated specialization. Co-authored-by: Yağız Kaan Aydoğdu <y.kaan.aydogdu@gmail.com> Co-authored-by: Yusuf Demir <yusufdemir12610@gmail.com> Advised-by: Ayhan Günaydın <ayhan.gunaydin@bogazici.edu.tr> Advised-by: Metin Ersin Arıcan <metin.arican@bogazici.edu.tr> Please note that we utilized agentic AI tools (Claude Opus, ChatGPT Codex) during the development of this PR. Most of the proofs of the major theorems are direct translations from human-language source material (see the diff in `references.bib`) into Lean proofs using the mentioned AI tools. However, all design and formalization decisions were made by us. t-logic new-contributor LLM-generated 38/0 Mathlib/ModelTheory/FinitelyGenerated.lean,Mathlib/ModelTheory/Substructures.lean 2 23 ['NoahW314', 'erdkocak', 'felixpernegger', 'github-actions', 'iosephusferrum', 'mathlib-merge-conflicts', 'staroperator'] nobody
1-62165
1 day ago
18-30239
18 days ago
121-37027
121 days
5
45771 darkhipo
author:darkhipo
feat(MeasureTheory): bochner product integral over Measure.infinitePi # PR — Bochner product integral over `Measure.infinitePi` The proof is a single new file, `Mathlib/MeasureTheory/Integral/InfinitePiProduct.lean`, carrying the Mathlib module header (`module` / `public import` / `public section`), the Apache 2.0 licence line with `Copyright (c) 2026 darkhipo`, and `namespace MeasureTheory`. --- ## Proposed title `feat(MeasureTheory): Bochner product integral over Measure.infinitePi` ## Proposed file placement `Mathlib/MeasureTheory/Integral/InfinitePiProduct.lean` Imports (verified sufficient — the module compiles with exactly these, under `set_option autoImplicit false`, in the modern `module`/`public import` form): ```lean public import Mathlib.Analysis.SpecialFunctions.Log.Summable public import Mathlib.MeasureTheory.Integral.DominatedConvergence public import Mathlib.MeasureTheory.Integral.Lebesgue.Map public import Mathlib.MeasureTheory.Integral.Pi public import Mathlib.Probability.ProductMeasure ``` Rationale for placement: it is the infinite-index companion of `MeasureTheory.integral_fintype_prod_eq_prod` (`Mathlib/MeasureTheory/Integral/Pi.lean`), and it integrates over `Measure.infinitePi` (`Mathlib/Probability/ProductMeasure.lean`). ## Main results ```lean theorem MeasureTheory.integral_finset_prod_infinitePi (hf : ∀ i, AEStronglyMeasurable (f i) (μ i)) (s : Finset ι) : ∫ x, ∏ i ∈ s, f i (x i) ∂(Measure.infinitePi μ) = ∏ i ∈ s, ∫ x, f i x ∂(μ i) theorem MeasureTheory.ae_summable_norm_sub_one_infinitePi (hf : ∀ i, AEStronglyMeasurable (f i) (μ i)) (hsum : ∑' i, ∫⁻ x, (‖f i x - 1‖₊ : ℝ≥0∞) ∂(μ i) ≠ ∞) : ∀ᵐ x ∂(Measure.infinitePi μ), Summable fun i => ‖f i (x i) - 1‖ -- the general form: a norm bound family instead of a flat 1 theorem MeasureTheory.hasProd_integral_tprod_infinitePi_of_norm_le (hf : ∀ i, AEStronglyMeasurable (f i) (μ i)) (hC0 : ∀ i, 0 ≤ C i) (hb : ∀ i, ∀ᵐ x ∂(μ i), ‖f i x‖ ≤ C i) (hC : Summable fun i => ‖C i - 1‖) (hsum : ∑' i, ∫⁻ x, (‖f i x - 1‖₊ : ℝ≥0∞) ∂(μ i) ≠ ∞) : HasProd (fun i => ∫ x, f i x ∂(μ i)) (∫ x, ∏' i, f i (x i) ∂(Measure.infinitePi μ)) -- the ≤ 1 case, kept as a corollary (this is the form the campaign consumes) theorem MeasureTheory.hasProd_integral_tprod_infinitePi (hf) (hb : ∀ i, ∀ᵐ x ∂(μ i), ‖f i x‖ ≤ 1) (hsum) : HasProd … theorem MeasureTheory.integral_tprod_infinitePi (hf) (hb) (hsum) : ∫ x, ∏' i, f i (x i) ∂(Measure.infinitePi μ) = ∏' i, ∫ x, f i x ∂(μ i) ``` (`ι` countable, `[∀ i, MeasurableSpace (X i)]`, `μ : (i : ι) → Measure (X i)` with `[∀ i, IsProbabilityMeasure (μ i)]`, `f : (i : ι) → X i → ℂ`, `C : ι → ℝ`.) ## Why it is not already there * finite index, product-measure form: `MeasureTheory.integral_fintype_prod_eq_prod`; * finite index, independence form: `ProbabilityTheory.iIndepFun.integral_prod_eq_prod_integral` (and the more general `iIndepFun.integral_fun_prod_comp` for functions of independent random variables), in `Mathlib/Probability/Independence/Integration.lean` — this is the closest existing relative of the present file, and it already contains the reduction of independence to the pi product measure (`iIndepFun.map_fun_eq_pi_map`) that the infinite-index statement takes as its starting point; * nonnegative integrands, infinite index: derivable from `lintegral_tsum` (monotone convergence); * Bochner/`ℂ` integrands, infinite index: **absent** — and monotone convergence does not apply, because the products are not nonnegative. The proof needs an honest convergence argument. ## Relation to `iIndepFun.integral_prod_eq_prod_integral` That theorem and its neighbors state the **finite-index** identity `μ[∏ i, X i] = ∏ i, μ[X i]` for a family of **mutually independent random variables** `X : (i : ι) → Ω → 𝓧 i` on a common probability space (`[Fintype ι]`, `iIndepFun X μ`, measurability only — at finite index no convergence content is even statable). The present file is the **countable-index, infinite-product, bare-product-measure** analogue, and the delta is exactly what finiteness hid: * **index**: `[Fintype ι]` there vs `[Countable ι]` with genuinely infinite `∏'` here — the conclusion is a `HasProd` convergence statement, so a.e. summability of `∑ i, ‖f i (x i) - 1‖` (Tonelli) and `multipliable_one_add_of_summable` enter, neither of which has a finite-index counterpart; * **framing**: there, hypotheses on a common probability space plus `iIndepFun`; here, no random-variable layer at all — the statement is directly about `Measure.infinitePi μ`, the product-measure form their `iIndepFun.map_fun_eq_pi_map` reduces independence to; * **bounds**: there, none needed; here, the `‖f i x‖ ≤ C i` bound family with `∑ i, ‖C i - 1‖` summable is what makes dominated convergence along `Finset ι` work ("Why the bound family is `∑ ‖C i - 1‖`" below). Conversely, neither statement subsumes the other: the independence file cannot state an infinite product, and this file does not require (or produce) the `iIndepFun` common-space packaging. ## Proof sketch (for the review) 1. **Finite subsets.** `(Measure.infinitePi μ).map (Finset.restrict s) = Measure.pi (μ|_s)` (`Measure.infinitePi_map_restrict`), then `integral_fintype_prod_eq_prod` and `measurePreserving_eval_infinitePi` for the single coordinates. 2. **A.e. summability of the deviations.** Tonelli: `∫⁻ x, ∑' i, ‖f i (x i) - 1‖` equals `∑' i, ∫⁻ x, ‖f i x - 1‖` (`lintegral_tsum` + `lintegral_map'`), finite by hypothesis, hence `∑ i, ‖f i (x i) - 1‖` is summable for a.e. `x`. 3. **A.e. multipliability.** `multipliable_one_add_of_summable` applied to `f i (x i) - 1`. 4. **Domination.** `‖∏ i ∈ s, f i (x i)‖ = ∏ i ∈ s, ‖f i (x i)‖ ≤ ∏ i ∈ s, C i`, and `C i ≤ exp (C i - 1)` for `C i ≥ 0` gives `∏ i ∈ s, C i ≤ exp (∑ i ∈ s, (C i - 1)) ≤ exp (∑' i, ‖C i - 1‖)` — a constant independent of `s`. 5. **Limit.** `tendsto_integral_filter_of_dominated_convergence` along `atTop : Filter (Finset ι)`, dominated by that constant, pointwise convergence from step 3; the finite-subset integrals are rewritten by step 1. `HasProd.tprod_eq` turns the convergence form into the equation form. ## Why the bound family is `∑ ‖C i - 1‖` and not `∑ C i` A product of bounds is not additive in them: a factor `C i < 1` scales the bound *down*, a factor `> 1` scales it *up*, so summability of `C` alone does not bound `∏ i ∈ s, C i` uniformly. The log-scale hypothesis `Summable fun i => ‖C i - 1‖` is exactly the statement that the family `C` is multipliable, made explicit; `exp (∑' i, ‖C i - 1‖)` is then the dominator. The flat case is `C ≡ 1` (where `∑ ‖C i - 1‖ = 0` and the dominator is `1`), which is the corollary above. ## Review-risk notes (honest) * The `𝕜`-generalization (any `RCLike 𝕜` / `NormedField` instead of `ℂ`) is **open**; `ℂ` is what the use case needs. The proofs use only the normed-field structure plus completeness of `ℂ`, so the generalization is plausible but not attempted here. * The summability hypothesis `∑' i, ∫⁻ x, ‖f i x - 1‖₊ ≠ ∞` is chosen because `multipliable_one_add_of_summable` consumes the real-valued `Summable fun i => ‖f i (x i) - 1‖` and `ENNReal.tsum_coe_ne_top_iff_summable` converts between them. A reviewer may prefer a hypothesis phrased through `Summable` on `ℝ≥0`-norms directly; the two are equivalent. * The bound family is not required to be *sharp* or to converge to `1`; `C i` may be any nonnegative family with `∑ ‖C i - 1‖` summable, including `C i < 1` for every `i`. * No `sorry`, no `native_decide`, no new axioms: every declaration reports `[propext, Classical.choice, Quot.sound]`, including the generalized theorem (receipt: `receipt/axcheck_infinitepiproduct.txt`, regenerated by `receipt/axcheck_infinitepiproduct.lean`). ## AI usage disclosure (Mathlib requires one) This contribution was produced by an AI agent (a large language model driven by the `opencode` harness) inside a human-directed formalization campaign; the human, darkhipo, reviewed and is submitting it. Every statement was checked by the Lean kernel; the proofs are machine-generated and human-readable but not human-written. The docstrings and this description were written by the agent. ## Checklist (Mathlib's) - [x] depends on no new axioms / `sorry`-free (kernel-verified, `#print axioms` receipt attached for all five declarations) - [x] builds with the narrowest import set that works (five `public import`s, each exercised) - [x] `set_option autoImplicit false` clean - [x] no linter warnings in this file (rebuilt clean: `lake build Pg182D2` reports no warning or error for `Pg182D2/InfinitePiProduct.lean`) - [x] docstrings on every declaration, module docstring present, `## Main results` section - [x] naming matches Mathlib conventions (`integral_*_prod_*`, `ae_*`, `hasProd_*`, `_of_norm_le`) - [x] Mathlib module form (`module`, `public import`, `public section`) - [x] licence header complete: `Copyright (c) 2026 darkhipo. All rights reserved.`, Apache 2.0, `Authors: darkhipo` - [ ] reviewed by a human Lean expert — **not done**. Nothing in this file has been read by a human with Lean expertise; the human submitting it has reviewed the *statement* and the campaign's use of it, not the proof scripts. - [ ] argued as `Mathlib`-worthy by a maintainer — that is the reviewers' call, not ours. ## Verification against upstream `master` at PR time Copied into `Mathlib/MeasureTheory/Integral/InfinitePiProduct.lean` on branch `infinite-pi-product`, based on `master` @ `71441a1480` (`chore: update Mathlib dependencies 2026-11-07`), toolchain `leanprover/lean4:v4.36.0-rc2`. * `lake exe cache get` + `lake build Mathlib.MeasureTheory.Integral.InfinitePiProduct` → `Build completed successfully`, **no warnings** (the build runs Mathlib's standard linter set, including `linter.style.longLine`, the header linter and `unusedSectionVars`). * `lake exe lint-style Mathlib.MeasureTheory.Integral.InfinitePiProduct` → exit code 0. * `lake exe mk_all` → the generated `Mathlib.lean` import line is byte-identical to the committed one. * `#print axioms` on the upstream copy: all five declarations depend only on `[propext, Classical.choice, Quot.sound]`, i.e. no `sorry` and no new axioms. Adaptations required by upstream `master` (the proof itself is unchanged from the version that compiled against the pin used during the campaign): 1. removed `set_option autoImplicit false` — `autoImplicit` is `false` globally in `lakefile.lean`; 2. `AEMeasurable.nnnorm` → `AEMeasurable.nnNorm` (two sites) and `coe_nnnorm` → `coe_nnNorm`, which are deprecated at `master`; 3. two lines reflowed to satisfy the 100-character `linter.style.longLine`; 4. added the import to `Mathlib.lean`. t-measure-probability new-contributor 224/0 Mathlib.lean,Mathlib/MeasureTheory/Integral/InfinitePiProduct.lean 2 3 ['github-actions'] nobody
1-58868
1 day ago
14-80665
14 days ago
14-80610
14 days
0
45906 darkhipo
author:darkhipo
feat(Analysis/Fourier): exactness of the periodic trapezoidal rule on characters ### The periodic trapezoidal rule is exact on characters New file `Mathlib/Analysis/Fourier/TrapezoidalRulePeriodic.lean` (also registered in `Mathlib.lean`). **What this adds.** The `n`-point periodic trapezoidal rule — the average of `F` over the `n` equally spaced nodes `2 * π * j / n` — reproduces the circle mean of every character `x ↦ e^{i m x}` *exactly*, except at the aliased nonzero frequencies `m ≠ 0, n ∣ m`, where the error is exactly `-1` (`PeriodicTrapezoidal.error_char`). The mechanism is algebraic: * `char_sum`: `∑_{j < n} e^{2 * π i m j / n} = n` if `n ∣ m`, else `0`; * `integral_char` / `circleMean_char`: `(1 / (2 * π)) ∫_0^{2 * π} e^{i m x} dx = 1` if `m = 0`, else `0`. Because the error functional `Eₙ = circleMean - mean` is additive and `ℂ`-homogeneous, these two facts give a **geometric convergence theorem** from a Fourier-decay hypothesis (`error_le_of_decay`): if `F` is uniformly `ε`-close on `[0, 2 * π]` to a partial character sum whose nonzero coefficients satisfy `‖cₖ‖ ≤ M * q ^ {|k|}` for some `q < 1`, then the `n`-point error is at most `M * q ^ n * (2 * K + 1) + 2 * ε`. **What is classical.** The trapezoidal rule, character orthogonality and the geometric-sum identity are all classical; the exponential accuracy of the periodic trapezoidal rule for periodic analytic integrands is the subject of Trefethen & Weideman, *The Exponentially Convergent Trapezoidal Rule*, SIAM Rev. 56 (2014). Nothing here is mathematically new; the contribution is the missing statement in Mathlib. **Relationship to existing API.** `intervalIntegral.trapezoidal_error_le` and `trapezoidal_error_le_of_c2` bound the error through derivative moduli and give rates polynomial in `N`, for any smooth integrand on an interval. This PR is the complementary regime: periodic integrands, coefficients instead of derivatives, geometric rate. Neither subsumes the other. The `2 * K + 1` factor is a deliberately crude cardinality bound on the frequencies that can alias (it counts the terms of the partial sum); a sharper tail could replace it at the cost of a stronger hypothesis on `K`. **The decay hypothesis is deliberately left abstract.** `error_le_of_decay` takes the coefficient decay as a hypothesis. It is classically supplied by analyticity of `F` in a strip around the real axis (the coefficients then decay like `e ^ (- a * |k|)`); we plan to contribute that contour-shift ingredient separately so the two compose into the fully classical statement. **Motivation from a use case (not a claim about Mathlib).** Consider a periodic integral that needs a `1.3 · 10⁻⁶` enclosure. The derivative-bound route, instantiated with realistic constants, needs `n ≥ 7.7 · 10¹⁷` panels there; the same integrand's Fourier tail under strip analyticity gives exponential accuracy at modest `n` — roughly 15 orders of magnitude apart at the node counts that matter. Mathlib's existing theorems are correct for their hypotheses; the gap is that the spectral mechanism, which is the standard reason one uses the periodic rule at all, had no statement to build on. new-contributor t-analysis 435/0 Mathlib.lean,Mathlib/Analysis/Fourier/TrapezoidalRulePeriodic.lean 2 3 ['darkhipo', 'github-actions'] nobody
1-58840
1 day ago
1-59325
1 day ago
1-61000
1 day
0
45909 darkhipo
author:darkhipo
feat(Analysis/Fourier): geometric decay of Fourier coefficients from strip analyticity ### What Adds the classical **strip decay of Fourier coefficients**: if `g : ℂ → ℂ` is holomorphic on the horizontal strip `{z | |z.im| < a}`, `T`-periodic there, and bounded there by `M`, and `f : AddCircle T → ℂ` agrees with `g` on the real axis, then ```lean theorem norm_fourierCoeff_le_of_strip ... (k : ℤ) : ‖fourierCoeff f k‖ ≤ M * Real.exp (-(2 * π * a / T) * |(k : ℝ)|) ``` For `T = 2 * π` this is the familiar `‖ĉ_k‖ ≤ M * exp (- a * |k|)`. ### Why this belongs in Mathlib `Analysis/Fourier/` has the `L²` theory (Parseval, inversion, `RiemannLebesgueLemma`) — i.e. *qualitative* decay — but no quantitative geometric coefficient bound, which is the entry point for spectral/quadrature accuracy results. This result is textbook classical (Cauchy estimates for Fourier/Laurent coefficients; Katznelson, *An Introduction to Harmonic Analysis*; Kahane, *Some Random Series of Functions*, 2nd ed., 1985; Trefethen & Weideman, SIAM Rev. 56 (2014), for the numerical corollary), so the contribution here is the formalization and the proof route, not the mathematics. ### The proof route Elementary, and deliberately so — it avoids annulus/Laurent machinery entirely: 1. `integral_eq_shift_of_periodic_of_differentiableOn` — the reusable piece: the period integral of a holomorphic `T`-periodic function is invariant under vertical shifts whose closed rectangle stays in the domain (on `Complex.integral_boundary_rect_eq_zero_of_differentiableOn`'s rectangle, the two vertical sides cancel by periodicity). 2. `norm_fourierCoeff_le_of_shift` — applying this to `z ↦ exp (2 * π * I * (-k) * z / T) * g z` scales the `k`-th coefficient by a factor of modulus `exp (2 * π * k * s / T)` at any height `|s| < a`. 3. The optimization over `|s| < a` is an **endpoint limit** (`le_of_tendsto_of_tendsto`), not a substitution: `e ^ (k * s)` is not bounded by its value at the strip edge at any interior `s`. ### Notes - A follow-up PR is planned for `trap_error_char` — the exactness of the `n`-point trapezoid rule on characters (the aliasing identity `Σ_{j<n} e^{2πimj/n} = n` when `n ∣ m`, else `0`) — which consumes this decay bound and gives the exponential-accuracy version of the periodic trapezoid rule. - Verified locally at current master (`2e9cd83`, toolchain `v4.36.0-rc2`): `lake build Mathlib` clean, the Batteries linter passes on this file, the module compiles twice from scratch with byte-identical `.olean`s, and `#print axioms` on all three declarations shows exactly `{propext, Classical.choice, Quot.sound}`. t-analysis new-contributor 272/0 Mathlib.lean,Mathlib/Analysis/Fourier/StripDecay.lean 2 2 ['github-actions'] nobody
1-58744
1 day ago
1-59314
1 day ago
1-60985
1 day
0
45210 dongxuelian2
author:dongxuelian2
feat(LinearAlgebra/Matrix/Charpoly): finite determination of matrix power sequences Add finite-determination criteria for matrix sequences `C * A ^ k * B`, allowing the two square matrices to have different index types. `Matrix.mul_pow_mul_eq_of_aeval_eq_zero` uses a common monic annihilating polynomial: agreement below its degree implies agreement at every natural exponent. `Matrix.mul_pow_mul_eq_of_lt_card_add` applies this to the product of the characteristic polynomials, giving the bound `Fintype.card ι + Fintype.card κ`. The statements work over commutative rings and allow empty state index types. The proof reduces `X ^ k` modulo the common polynomial and uses `Polynomial.sum_modByMonic_coeff`, which handles degree zero without a separate dimension case split. This adds two theorems to the existing matrix-power reduction API without introducing imports or definitions. The proof is adapted from [LeanForControl's finite-determination result](https://github.com/dongxuelian2/LeanForControl/blob/kalman-structural-completion/LeanForControl/LinearSystems/Realization/FiniteDetermination.lean). --- ### Validation Checked locally with Lean v4.36.0-rc1 against mathlib master `3d14fd9a313ac35ed4b5c653ed5d99157c9e29f6`: - `lake build Mathlib.LinearAlgebra.Matrix.Charpoly.Coeff` - `lake exe batteries/runLinter --no-build Mathlib.LinearAlgebra.Matrix.Charpoly.Coeff` - Direct invocation of the upstream text linters and module-name checks. - Separate local examples for the requested field/`Fin` statement, either or both dimensions zero, degree-zero and degree-one common annihilators, and matching nonzero sequences in dimensions 1 and 2. - `#print axioms` for both theorems reports only `propext`, `Classical.choice`, and `Quot.sound`. - `git diff --check`. The standalone `lint-style` launcher failed while loading Lake's workspace on Windows; its text linters passed when invoked directly. A clean full `lake shake` run was not obtained: the initial run needed uncached modules outside the targeted dependencies, and the forced run reported suggestions throughout the existing dependency closure. Imports are unchanged from upstream. No full-library build is claimed. ### AI use OpenAI Codex was used to audit nearby APIs and possible duplicates, extract and generalize the LeanForControl proof, write the Lean code and local examples, run validation, and prepare this PR description. t-algebra LLM-generated new-contributor
label:t-algebra$
44/0 Mathlib/LinearAlgebra/Matrix/Charpoly/Coeff.lean 1 4 ['dongxuelian2', 'github-actions', 'mathlib-merge-conflicts'] nobody
1-45337
1 day ago
1-46114
1 day ago
20-457
20 days
0
44836 cmhsu2012
author:cmhsu2012
feat(NumberTheory/Legendre/Basic): the legendre symbol for p-adics Co-authored-by: María Inés de Frutos-Fernández 88536493+mariainesdff@users.noreply.github.com and Nirvana Coppola 58878663+NirvanaC93@users.noreply.github.com In the ongoing formalization of the Hasse-Minkowski Theorem on quadratic forms, we need the Legendre symbol for the p-adics. The following declarations were added to the basic.lean file: ```def compMonoidHom``` an auxiliary definition: the composition between multiplicative characters and a local homomorphism ```def legendreSym``` the definition of the Legendre symbol for Z_p: composition of the reduction from Z_p to Z mod p and the usual Legendre symbol ```def hom``` The Legendre symbol is a homomorphism The remaining lemmas are the API: ```lemma intCast``` ```theorem eq_pow``` ```theorem eq_on_or_neg_one``` ```eq_neg_one_iff_not_one``` ```theorem eq_zero_iff``` ```theorem sq_one``` ```theorem sq_one'``` ```theorem eq_one_iff``` ```theorem eq_neg_one_iff``` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-number-theory new-contributor 179/2 Mathlib.lean,Mathlib/Algebra/Ring/Int/Units.lean,Mathlib/NumberTheory/MulChar/Basic.lean,Mathlib/RingTheory/LocalRing/LegendreSymbol.lean 4 67 ['JX-Mo', 'NirvanaC93', 'cmhsu2012', 'github-actions', 'loefflerd', 'mariainesdff', 'tb65536'] loefflerd
assignee:loefflerd
1-40332
1 day ago
1-42572
1 day ago
17-34429
17 days
0
46313 TheDarkLightX
author:TheDarkLightX
feat(ModelTheory): add definable functions of a theory Add `Theory.FunctionalFormula` for definable functions of a first-order theory. Its elements are semantic equivalence classes of formulas that define a unique output tuple for every input in every model of the theory. The API provides evaluation, extensionality, and composition. The expanded language adds a function symbol for each single-output definable function, with the output indexed by `Fin 1`. Every model of the original theory has a canonical expansion. Bounded formulas in the expanded language translate back to the original language with the same realization. Co-authored-by: Chris Hughes <[33847686+ChrisHughes24@users.noreply.github.com](mailto:33847686+ChrisHughes24@users.noreply.github.com)> Co-authored-by: Kenny Lau <[kc_kennylau@yahoo.com.hk](mailto:kc_kennylau@yahoo.com.hk)> --- This adopts #26398 and addresses the review comments on semantic equivalence and the single-output case. The Ax–Grothendieck refactor from #26399 compiled against this API. OpenAI ChatGPT adapted the original Lean code and proofs to current mathlib, revised the representation and documentation, and generated compatibility checks. Lean checked the module and downstream refactor. An independent lean4lean run checked all 100 declarations in the module and their dependencies, 5,832 declarations in total. ZenoADP, ZenoFCIS, ZAL, and Crucible supplied finite counterexample checks. t-logic LLM-generated new-contributor 582/0 Mathlib.lean,Mathlib/ModelTheory/FunctionalFormula.lean 2 3 ['TheDarkLightX', 'github-actions'] nobody
0-85041
23 hours ago
0-85523
23 hours ago
0-85468
23 hours
0
46045 omar826
author:omar826
feat(GroupTheory/FreeGroup): decidability of conjugacy We prove the conjugacy criterion for free groups: two elements are conjugate iff the cyclic reductions of their reduced words are rotations of each other (`FreeGroup.isConj_iff_isRotated`). We use it to show that `IsConj` is decidable in `FreeGroup α` when `α` has decidable equality. - `Mathlib/GroupTheory/FreeGroup/Conj.lean`: the criterion, a version for words that are not necessarily reduced (`FreeGroup.isConj_mk_iff`), supporting lemmas about cyclically reduced words, and the `DecidableRel IsConj` instance. - `Mathlib/GroupTheory/FreeGroup/CyclicallyReduced.lean`: `reduceCyclically` is redefined by structural recursion instead of `List.bidirectionalRec`. This lets `decide` evaluate the instance, e.g. `IsConj (of 0 * of 1 : FreeGroup (Fin 2)) (of 1 * of 0)`. Co-authored-by: Arjun Sheth <arjun.sheth_ug25@ashoka.edu.in> Co-authored-by: Vivek Rajesh Joshi <vivek.rajeshjoshi@students.iiserpune.ac.in> Co-authored-by: T V H Prathamesh <prathamesh.turaga@krea.edu.in> Co-authored-by: Rishi Vyas <rishi.vyas@krea.edu.in> --- *Use of AI.* original Lean formalization of this result were done by hand by the authors using our own definitions of reduced, cyclically reduced words, and our own cyclic reduction function. We then used Claude Code to use Mathlib's existing API (IsReduced, IsCyclicallyReduced, reduceCyclically) instead of our definitions, following the same overall strategy and fixing naming and style to Mathlib conventions. This work comes from a project with T V H Prathamesh's group at KREA University. t-group-theory new-contributor 298/13 Mathlib.lean,Mathlib/GroupTheory/FreeGroup/Conj.lean,Mathlib/GroupTheory/FreeGroup/CyclicallyReduced.lean 3 26 ['github-actions', 'mathlib-merge-conflicts', 'omar826', 'vihdzp', 'wwylele'] nobody
0-84673
23 hours ago
5-29064
5 days ago
6-80902
6 days
0
45877 joelcanary
author:joelcanary
feat(NumberTheory/ArithmeticFunction/Moebius): `∑ n ≤ N, μ n * (N / n) = 1` This PR adds one lemma. It says that for `N ≠ 0` and for any ring `R`: ```lean ∑ n ∈ Ioc 0 N, (μ n : R) * (N / n : ℕ) = 1 ``` This is the same as `∑_{n ≤ N} μ(n)⌊N/n⌋ = 1`. The classical bound `|∑_{n ≤ N} μ(n)/n| ≤ 1` follows from this identity. PNT+ proves the identity again by hand inside `sum_mobius_div_self_le`; with this lemma, that part becomes one line. ------------ About the AI: I used an AI agent (Claude Code) to write the statement and the proof. I chose the target and I checked the result. t-number-theory LLM-generated new-contributor maintainer-merge 6/0 Mathlib/NumberTheory/ArithmeticFunction/Moebius.lean 1 10 ['GoldenPhysicsProject', 'MichaelStollBayreuth', 'github-actions', 'jcommelin', 'joelcanary'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
0-79069
21 hours ago
5-21141
5 days ago
11-54232
11 days
0
45520 EzequielS2
author:EzequielS2
feat: add growth of finitely generated groups Add word-ball growth, domination, and independence of the generating set t-geometric-group-theory new-contributor 183/0 Mathlib.lean,Mathlib/Geometry/Group/Growth/Basic.lean 2 22 ['EzequielS2', 'github-actions', 'tb65536'] ADedecker
assignee:ADedecker
0-69711
19 hours ago
0-77207
21 hours ago
16-28578
16 days
3
44926 kedlaya
author:kedlaya
feat(FieldTheory): implement Artin-Schreier polynomials --- Implement Artin-Schreier polynomials in preparation for using them to describe cyclic degree-p extensions of fields of characteristic p. Split off from #43947. - [x] depends on: #44690 t-algebra new-contributor
label:t-algebra$
154/6 Mathlib.lean,Mathlib/Algebra/Polynomial/FieldDivision.lean,Mathlib/Algebra/Polynomial/Splits.lean,Mathlib/FieldTheory/ArtinSchreierExtension.lean 4 27 ['github-actions', 'kedlaya', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'plp127', 'tb65536'] nobody
0-66276
18 hours ago
0-66879
18 hours ago
2-61605
2 days
2
46307 estomagordo
author:estomagordo
refactor(LinearAlgebra/Basis): rename Basis.ext and Basis.ext' Rename `Basis.ext` to `Basis.ext_linearMap` and `Basis.ext'` to `Basis.ext_linearEquiv`, and deprecate the old names. `Basis.eq_of_apply_eq` stays as is. Renaming it to `Basis.ext` has to wait until the deprecation alias for `Basis.ext` is removed. Part of #46139. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> new-contributor 107/92 Mathlib/Algebra/Azumaya/Matrix.lean,Mathlib/Algebra/Lie/CartanCriterion.lean,Mathlib/Algebra/Module/ZLattice/Basic.lean,Mathlib/Analysis/Complex/Isometry.lean,Mathlib/Analysis/InnerProductSpace/Adjoint.lean,Mathlib/Analysis/InnerProductSpace/Dual.lean,Mathlib/Analysis/InnerProductSpace/TwoDim.lean,Mathlib/Analysis/Matrix/Spectrum.lean,Mathlib/Analysis/Normed/Operator/LinearIsometry.lean,Mathlib/Geometry/Euclidean/Angle/Oriented/Rotation.lean,Mathlib/LinearAlgebra/Basis/Bilinear.lean,Mathlib/LinearAlgebra/Basis/Defs.lean,Mathlib/LinearAlgebra/Basis/SMul.lean,Mathlib/LinearAlgebra/Basis/Submodule.lean,Mathlib/LinearAlgebra/Basis/VectorSpace.lean,Mathlib/LinearAlgebra/BilinearForm/Hom.lean,Mathlib/LinearAlgebra/BilinearForm/Properties.lean,Mathlib/LinearAlgebra/Center.lean,Mathlib/LinearAlgebra/Coevaluation.lean,Mathlib/LinearAlgebra/Contraction.lean,Mathlib/LinearAlgebra/Determinant.lean,Mathlib/LinearAlgebra/Dimension/Constructions.lean,Mathlib/LinearAlgebra/Dual/Basis.lean,Mathlib/LinearAlgebra/Eigenspace/Zero.lean,Mathlib/LinearAlgebra/ExteriorPower/Basis.lean,Mathlib/LinearAlgebra/ExteriorPower/WedgePairing.lean,Mathlib/LinearAlgebra/Finsupp/VectorSpace.lean,Mathlib/LinearAlgebra/FreeModule/Norm.lean,Mathlib/LinearAlgebra/Matrix/Basis.lean,Mathlib/LinearAlgebra/Matrix/ToLin.lean,Mathlib/LinearAlgebra/PiTensorProduct/Dual.lean,Mathlib/LinearAlgebra/QuadraticForm/Basis.lean,Mathlib/LinearAlgebra/RootSystem/CartanMatrix.lean,Mathlib/LinearAlgebra/StdBasis.lean,Mathlib/LinearAlgebra/SymmetricAlgebra/Basis.lean,Mathlib/LinearAlgebra/TensorAlgebra/Basis.lean,Mathlib/LinearAlgebra/Trace.lean,Mathlib/LinearAlgebra/Transvection/Basic.lean,Mathlib/NumberTheory/NumberField/CanonicalEmbedding/Basic.lean,Mathlib/RepresentationTheory/Tannaka.lean,Mathlib/RingTheory/Extension/Cotangent/Basis.lean,Mathlib/RingTheory/Extension/Cotangent/LocalizationAway.lean,Mathlib/RingTheory/Flat/EquationalCriterion.lean,Mathlib/RingTheory/Ideal/Basis.lean,Mathlib/RingTheory/Ideal/Norm/AbsNorm.lean,Mathlib/RingTheory/Kaehler/JacobiZariski.lean,Mathlib/RingTheory/Localization/Module.lean,Mathlib/RingTheory/PowerBasis.lean,Mathlib/RingTheory/TensorProduct/Free.lean 49 2 ['github-actions'] nobody
0-64892
18 hours ago
1-17196
1 day ago
1-17141
1 day
0
46321 hzmsh
author:hzmsh
fix: add missing parentheses in `Repr` for `WithTop` and similar types - Before: the `Repr` instances for `WithBot`, `WithTop`, `WithOne`, `WithZero`, and `OnePoint` used `repr` on the inner value. For example, `-1` inside `WithBot ℤ` printed as `↑-1`, and `some 3` inside `WithTop (Option ℕ)` printed as `↑some 3`, which are not valid Lean syntax. - Change: replace `repr` with `reprArg` in all 5 instances, and add tests in `MathlibTest/WithTopRepr.lean`. - After: now those values print with parentheses as `↑(-1)` and `↑(some 3)` correctly. Fixes #45767. --- AI use: I used Claude (Opus 5.5 High) and Gemini (Carbon High) to locate the root cause and propose the solution. I have verified myself that the proposed solution is correct. LLM-generated new-contributor 30/5 Mathlib/Algebra/Group/WithOne/Defs.lean,Mathlib/Order/TypeTags.lean,Mathlib/Topology/Compactification/OnePoint/Basic.lean,MathlibTest/WithTopRepr.lean 4 3 ['github-actions', 'hzmsh'] nobody
0-63845
17 hours ago
0-66437
18 hours ago
0-66382
18 hours
0
46318 doge-th
author:doge-th
chore: rename rpow monotonicity lemmas Following #9095, #9235 and #18956, this renames the ambiguous rpow monotonicity lemma names in `Real`, `NNReal` and `ENNReal`, as requested in #13544 (the `rpow_le_rpow` part; @YaelDillies is working on the `zpow` one). The convention is the one established for `pow`/`zpow`: lemmas monotone in the base (the left argument of `^`) gain `_left`, lemmas monotone in the exponent gain `_right`, and iff-variants use the `_iff_left`/`_iff_right` infixes. Rename summary: - `rpow_le_rpow` → `rpow_le_rpow_left`, `rpow_lt_rpow` → `rpow_lt_rpow_left` (base varies) - `rpow_le_rpow_of_nonpos` → `rpow_le_rpow_left_of_nonpos`, `rpow_lt_rpow_of_neg` → `rpow_lt_rpow_left_of_neg` (antitone in base) - `rpow_le_rpow_iff` → `rpow_le_rpow_iff_left`, `rpow_lt_rpow_iff` → `rpow_lt_rpow_iff_left` (and the `_of_neg` variants likewise) - `rpow_le_rpow_of_exponent_le` → `rpow_le_rpow_right`, `rpow_lt_rpow_of_exponent_lt` → `rpow_lt_rpow_right` - `rpow_le_rpow_of_exponent_ge` → `rpow_le_rpow_right_of_le_one`, `rpow_lt_rpow_of_exponent_gt` → `rpow_lt_rpow_right_of_lt_one` (and the `'`/`of_imp` variants), matching `pow_le_pow_right_of_le_one'` and `pow_lt_pow_right_of_lt_one₀` - `rpow_le_rpow_left_iff` → `rpow_le_rpow_iff_right`, `rpow_lt_rpow_left_iff` → `rpow_lt_rpow_iff_right`, `rpow_le_rpow_left_iff_of_base_lt_one` → `rpow_le_rpow_iff_right_of_base_lt_one`, `rpow_lt_rpow_left_iff_of_base_lt_one` → `rpow_lt_rpow_iff_right_of_base_lt_one` — these varied the exponent, so keeping them under `_left_iff` would clash semantically with the new `_left` names All uses are updated (50 files, 225 occurrences) and `@[deprecated (since := "2026-11-22")] alias` entries are added for every old name in the three namespaces. Closes #13544 new-contributor 325/225 Mathlib/Algebra/Module/ZLattice/Summable.lean,Mathlib/Analysis/AbsoluteValue/Equivalence.lean,Mathlib/Analysis/Analytic/RadiusLiminf.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Order.lean,Mathlib/Analysis/CStarAlgebra/Multiplier.lean,Mathlib/Analysis/Complex/Hadamard.lean,Mathlib/Analysis/Complex/PhragmenLindelof.lean,Mathlib/Analysis/Distribution/SchwartzSpace/Basic.lean,Mathlib/Analysis/Distribution/TemperateGrowth.lean,Mathlib/Analysis/Fourier/PoissonSummation.lean,Mathlib/Analysis/FunctionalSpaces/SobolevInequality.lean,Mathlib/Analysis/Matrix/Normed.lean,Mathlib/Analysis/MeanInequalities.lean,Mathlib/Analysis/MeanInequalitiesPow.lean,Mathlib/Analysis/MellinTransform.lean,Mathlib/Analysis/Normed/Lp/lpSpace.lean,Mathlib/Analysis/Normed/Unbundled/SmoothingSeminorm.lean,Mathlib/Analysis/Normed/Unbundled/SpectralNorm.lean,Mathlib/Analysis/SpecialFunctions/ContinuousFunctionalCalculus/Rpow/Order.lean,Mathlib/Analysis/SpecialFunctions/ImproperIntegrals.lean,Mathlib/Analysis/SpecialFunctions/Integrability/Basic.lean,Mathlib/Analysis/SpecialFunctions/Log/Base.lean,Mathlib/Analysis/SpecialFunctions/Log/Monotone.lean,Mathlib/Analysis/SpecialFunctions/Pow/Asymptotics.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Analysis/SpecialFunctions/Pow/Real.lean,Mathlib/Analysis/SpecificLimits/FloorPow.lean,Mathlib/Combinatorics/Additive/AP/Three/Behrend.lean,Mathlib/Computability/AkraBazzi/GrowsPolynomially.lean,Mathlib/Computability/AkraBazzi/SumTransform.lean,Mathlib/MeasureTheory/Function/ConditionalExpectation/CondJensen.lean,Mathlib/MeasureTheory/Function/ContinuousMapDense.lean,Mathlib/MeasureTheory/Function/LpSeminorm/ChebyshevMarkov.lean,Mathlib/MeasureTheory/Function/LpSeminorm/Monotonicity.lean,Mathlib/MeasureTheory/Function/SimpleFuncDenseLp.lean,Mathlib/MeasureTheory/Function/UniformIntegrable.lean,Mathlib/MeasureTheory/Integral/IntegralEqImproper.lean,Mathlib/MeasureTheory/Measure/Hausdorff.lean,Mathlib/MeasureTheory/Measure/Lebesgue/VolumeOfBalls.lean,Mathlib/NumberTheory/Bertrand.lean,Mathlib/NumberTheory/Harmonic/EulerMascheroni.lean,Mathlib/NumberTheory/LSeries/PrimesInAP.lean,Mathlib/NumberTheory/ModularForms/EisensteinSeries/Summable.lean,Mathlib/NumberTheory/NumberField/CanonicalEmbedding/ConvexBody.lean,Mathlib/NumberTheory/NumberField/Discriminant/Basic.lean,Mathlib/NumberTheory/Ostrowski.lean,Mathlib/NumberTheory/SumPrimeReciprocals.lean,Mathlib/NumberTheory/Transcendental/Liouville/Measure.lean,Mathlib/RingTheory/Perfection.lean,Mathlib/Topology/MetricSpace/Snowflaking.lean 50 2 ['BoltonBailey', 'github-actions'] nobody
0-62716
17 hours ago
0-79483
22 hours ago
0-79428
22 hours
0
45480 RFT-SIRM
author:RFT-SIRM
feat(Matrix): add ordered trace expansion for powers of sums ## Summary This PR adds a reusable ordered-word expansion for traces of powers of a sum of square matrices. - `Matrix.orderedWordExpansion A B p` lists products obtained by choosing either `A` or `B` at each of the `p` positions. - `Matrix.sum_orderedWordExpansion` proves that the list sums to `(A + B)^p`. - `Matrix.trace_orderedWordExpansion` gives the corresponding trace identity. The construction preserves the exact order of factors and retains repeated words with their full multiplicity. It does not assume that `A` and `B` commute or identify cyclically equivalent trace terms. ## Motivation For higher-moment trace identities, expanding `(A + B)^p` requires precise bookkeeping of ordered words before cyclic trace rotations and structural vanishing arguments can be applied. This generic expansion is useful for `p = 6` and for subsequent `p = 8, 10` developments without hard-coding a particular matrix model. This PR contains only general matrix-algebra lemmas. It does not include application-specific graph operators or claim to prove a particular moment recurrence. ## Verification The proofs use induction on `p`, right distributivity, and the existing `Matrix.trace_list_sum` theorem. Please run the full Mathlib build and style checks on this PR. t-algebra new-contributor LLM-generated
label:t-algebra$
40/0 Mathlib/LinearAlgebra/Matrix/Trace.lean 1 3 ['RFT-SIRM', 'github-actions'] nobody
0-54979
15 hours ago
23-65904
23 days ago
23-66757
23 days
0
46325 JoshuaR216
author:JoshuaR216
feat(Analysis/Calculus/LocalExtr/Polynomial): derivative of a real polynomial that splits also splits Add `Polynomial.Splits.derivative_of_real`: if `p : ℝ[X]` splits, then so does `p.derivative`. The proof is a counting argument from `Polynomial.card_roots_le_derivative` (Rolle's theorem), `Polynomial.card_roots'` and `Polynomial.natDegree_derivative_le`. --- Discussed on Zulip: [#Is there code for X? > derivative of a polynomial that splits over ℝ also splits @ 💬](https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/derivative.20of.20a.20polynomial.20that.20splits.20over.20.E2.84.9D.20also.20splits/near/642560961) As suggested there by Artie Khovanov, this is stated for ℝ for now; it can be generalised to real closed fields once the intermediate value theorem for them is in Mathlib. AI disclosure: The proof was written with help from Claude. I've checked that I understand each step, and it compiles with no `sorry`. t-analysis new-contributor LLM-generated 16/0 Mathlib/Analysis/Calculus/LocalExtr/Polynomial.lean 1 6 ['github-actions', 'vihdzp'] nobody
0-54657
15 hours ago
0-56844
15 hours ago
0-56789
15 hours
0
44822 William7743
author:William7743
feat(Geometry/Euclidean/Inversion): affine limits and filter identities Adds filter-level limit and continuity lemmas for `EuclideanGeometry.inversion` in `Geometry/Euclidean/Inversion/Basic.lean`: * `not_continuousAt_inversion_center_of_neBot` — nonzero-radius inversion is discontinuous at a non-isolated center (`[NeBot (𝓝[≠] c)]`). * `continuousAt_inversion_iff` — inversion is continuous at `x` iff `x ≠ c ∨ R = 0`. * `tendsto_inversion_cobounded_nhds_center` / `tendsto_inversion_cobounded_nhdsNE_center` — as the argument tends to infinity, inversion tends to the center, resp. its punctured neighborhood for nonzero radius. * `map_inversion_cobounded` / `map_inversion_nhdsNE_center` — for nonzero radius, inversion pushes the cobounded filter exactly to `𝓝[≠] c` and back, via its involutivity. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-euclidean-geometry LLM-generated new-contributor 53/0 Mathlib/Geometry/Euclidean/Inversion/Basic.lean 1 6 ['SnirBroshi', 'William7743', 'github-actions'] nobody
0-50354
13 hours ago
22-33896
22 days ago
22-36506
22 days
0
45841 GoldenPhysicsProject
author:GoldenPhysicsProject
feat: the adele ring of ℚ is ℝ × the finite adele ring This PR identifies the adele ring of `ℚ` with `ℝ × FiniteAdeleRing ℤ ℚ`, and adds a general `ContinuousAlgEquiv.prodCongr` to support it. In `Mathlib/Topology/Algebra/Algebra/Equiv.lean`: * `ContinuousAlgEquiv.prodCongr (e : A ≃A[R] B) (e' : C ≃A[R] D) : (A × C) ≃A[R] (B × D)`, the product of two continuous algebra equivalences, with the simp lemmas `prodCongr_toAlgEquiv`, `prodCongr_toHomeomorph`, `prodCongr_apply` and `prodCongr_symm`. In `Mathlib/NumberTheory/NumberField/AdeleRing.lean`: * `Rat.InfiniteAdeleRing.continuousAlgEquivReal : InfiniteAdeleRing ℚ ≃A[ℚ] ℝ` — `ℚ` has a single infinite place, and it is real, so the infinite adele ring is a one-factor product with factor `ℝ`; * `Rat.AdeleRing.continuousAlgEquivProd : AdeleRing ℤ ℚ ≃A[ℚ] ℝ × FiniteAdeleRing ℤ ℚ`, defined as `ContinuousAlgEquiv.prodCongr continuousAlgEquivReal (ContinuousAlgEquiv.refl _ _)`; * `Rat.AdeleRing.continuousAlgEquivProd_algebraMap`: the diagonal embedding `ℚ → 𝔸_ℚ` is `q ↦ (q, (q)_p)` under this identification. t-number-theory new-contributor LLM-generated 76/0 Mathlib/NumberTheory/NumberField/AdeleRing.lean,Mathlib/Topology/Algebra/Algebra/Equiv.lean 2 17 ['GoldenPhysicsProject', 'MichaelStollBayreuth', 'github-actions', 'tb65536', 'xroblot'] MichaelStollBayreuth
assignee:MichaelStollBayreuth
0-17625
4 hours ago
0-17625
4 hours ago
9-86312
9 days
0
46340 CocoSgt
author:CocoSgt
feat(Analysis/Matrix/Deriv): add Jacobi's formula for the derivative of the determinant New file `Mathlib/Analysis/Matrix/Deriv.lean` with **Jacobi's formula** for the derivative of the determinant along a path of matrices: * `Matrix.hasDerivAt_det`: if every entry of a path `G : 𝕜 → Matrix n n 𝔸` (with `𝔸` a normed commutative algebra over the normed field `𝕜`) is differentiable at `t` with derivative `G' i j`, then `s ↦ (G s).det` is differentiable at `t` with derivative `((G t).adjugate * G').trace`. * `Matrix.hasDerivAt_log_det_re`: if moreover `G t` is positive definite (for `𝔸 = 𝕜` an `RCLike` field, path parameter `ℝ`), then `s ↦ log ((G s).det).re` is differentiable at `t` with derivative `((G t)⁻¹ * G').trace.re`. Mathlib so far only has the formal derivative `Matrix.derivative_det_one_add_X_smul` (in `LinearAlgebra/Matrix/Charpoly/Coeff.lean`), which is the `1 + X • M` special case of the first statement. `Mathlib.lean` is updated via `lake exe mk_all`. Local check: `lake build --wfail Mathlib.Analysis.Matrix.Deriv` (with the Mathlib linters), `lake exe lint-style`, `lake exe mk_all --check` and a rebuild of the `Mathlib` root module all pass. ### Provenance The proofs are taken from **Levent Alpöge's** (with Claude) Lean formalization of the Riemann Hypothesis (and GRH for Dirichlet L-functions), released on 2026-11-20 at https://alpo.ge/. Original file: `ReciprocityTheory/GeometryOfNumbers/PluriharmonicAnalysis/LogDetSt.lean`, lines 8–77 (`trace_adjugate_mul_eq_sum_perm`, `hasDerivAt_det`, `hasDerivAt_log_det`); browsable in the mirror: https://github.com/CocoSgt/riemann-hypothesis-lean/blob/main/src/ReciprocityTheory/GeometryOfNumbers/PluriharmonicAnalysis/LogDetSt.lean The original statements are for paths `ℝ → Matrix (Fin r) (Fin r) ℂ`; here they are generalized to arbitrary finite index types, to matrices over any normed commutative `𝕜`-algebra (Jacobi) and to `RCLike` scalars (log det). The `first | … | …` version-compatibility alternatives of the original proof were fixed to the branch that applies to current Mathlib. The extraction, cleanup, port to current `master` and this PR were made by **GLM 5.4** (Z.ai) running in **DeepSeek Harness**; all mathematical credit belongs to Levent Alpöge and Claude, who is listed as the file author and as `Co-authored-by` in the commit. The extraction project is documented in https://github.com/CocoSgt/rh-mathlib-lemmas. Note on licensing: the original release does not state an explicit license file. Please make sure the author is OK with merging before doing so. t-analysis new-contributor 118/0 Mathlib.lean,Mathlib/Analysis/Matrix/Deriv.lean 2 2 ['github-actions'] nobody
0-3434
57 minutes ago
0-3882
1 hour ago
0-3827
1 hour
0
46339 CocoSgt
author:CocoSgt
feat(Analysis/Matrix/Order): add Minkowski, Fischer and Hadamard determinant inequalities Adds determinant inequalities for positive (semi)definite matrices over an `RCLike` field to `Mathlib/Analysis/Matrix/Order.lean` (the file where the Loewner order on matrices and `CFC.sqrt` on matrices are set up): * `Matrix.PosSemidef.det_one_add_eq_prod`: `det (1 + Q) = ∏ i, (1 + λ i)` for `Q` positive semidefinite with eigenvalues `λ i`. * `Matrix.PosDef.det_re_mono`: **Minkowski's determinant inequality** — if `G` is positive definite and `H - G` is positive semidefinite then `(G.det).re ≤ (H.det).re`, i.e. `det` is monotone on the positive definite cone. * `Matrix.PosDef.det_re_le_det_re_mul_det_re_fromBlocks`: **Fischer's inequality** `((fromBlocks A B C D).det).re ≤ (A.det).re * (D.det).re` for a positive definite block matrix (with `C = Bᴴ` derived from the hypothesis), plus the `Fin (a + b)` submatrix version. * `Matrix.PosDef.det_re_le_prod_diag_re`: **Hadamard's determinant inequality** `(D.det).re ≤ ∏ j, (D j j).re`, plus the block version. The statements use `RCLike.re`, in the style of `PosSemidef.re_dotProduct_nonneg` in `Mathlib/Analysis/Matrix/PosDef.lean`. Since the determinant of a Hermitian matrix is real, the `ComplexOrder`-style `G.det ≤ H.det` is a restatement away; happy to switch if reviewers prefer. Local check: `lake build --wfail Mathlib.Analysis.Matrix.Order` (with the Mathlib linters) and its only direct importer `Mathlib.Probability.Distributions.Gaussian.Multivariate` build cleanly; `lake exe lint-style` passes. ### Provenance The proofs are taken from **Levent Alpöge's** (with Claude) Lean formalization of the Riemann Hypothesis (and GRH for Dirichlet L-functions), released on 2026-11-20 at https://alpo.ge/. Original file: `ReciprocityTheory/GeometryOfNumbers/LatticeCovolumes/GramSt.lean`, lines 12–143 (`gramSt_det_one_add_eq`, `gramSt_det_re_le_of_sub`, `gramSt_fischer`, `gramSt_fin_blocks`, `gramSt_hadamard`, `det_re_le_mul_prod_diag`); browsable in the mirror: https://github.com/CocoSgt/riemann-hypothesis-lean/blob/main/src/ReciprocityTheory/GeometryOfNumbers/LatticeCovolumes/GramSt.lean The original statements are for `Matrix ι ι ℂ`; here they are generalized to `RCLike 𝕜`. Beyond renaming, docstrings and dropping two restatements of existing Mathlib lemmas, the changes are `Complex.*` → `RCLike.*` lemmas, `Finset.prod_le_prod₀` instead of `Finset.prod_le_prod`, and explicit `RCLike.re`. The extraction, cleanup, port to current `master` and this PR were made by **GLM 5.4** (Z.ai) running in **DeepSeek Harness**; all mathematical credit belongs to Levent Alpöge and Claude, who is listed as an author in the file header and as `Co-authored-by` in the commit. The extraction project (structure map of the 17.4M-line development, 52 further candidate lemmas) is documented in https://github.com/CocoSgt/rh-mathlib-lemmas. Note on licensing: the original release does not state an explicit license file. Please make sure the author is OK with merging before doing so. t-analysis new-contributor 152/1 Mathlib/Analysis/Matrix/Order.lean 1 2 ['github-actions'] nobody
0-3375
56 minutes ago
0-3887
1 hour ago
0-3832
1 hour
0
46341 CocoSgt
author:CocoSgt
feat(LinearAlgebra/Matrix/Determinant): add the Cauchy–Binet formula as a sum over functions Adds the **Cauchy–Binet formula** to `Mathlib/LinearAlgebra/Matrix/Determinant/Basic.lean`, right after `Matrix.det_mul`, as a sum over all functions between the index sets: ```lean theorem Matrix.det_mul_eq_sum_over_functions (A : Matrix m n R) (B : Matrix n m R) : (A * B).det = ∑ f : m → n, (∏ i, A i (f i)) * (B.submatrix f id).det ``` (Functions `f` that are not injective contribute `0`, since `B.submatrix f id` has a repeated row.) The proof is the natural one via `Matrix.detRowAlternating`: expanding `A * B` row-wise as a sum of multiples of the rows of `B` and applying `MultilinearMap.map_sum` / `MultilinearMap.map_smul_univ`. Local check: `lake build --wfail Mathlib.LinearAlgebra.Matrix.Determinant.Basic` (with the Mathlib linters) and `lake exe lint-style` pass. ### Provenance The proof is taken from **Levent Alpöge's** (with Claude) Lean formalization of the Riemann Hypothesis (and GRH for Dirichlet L-functions), released on 2026-11-20 at https://alpo.ge/. Original file: `Lemmata/GeneralBFact/Imports.lean`, line 8 (`Bl.general_b_fact.goal1`); browsable in the mirror: https://github.com/CocoSgt/riemann-hypothesis-lean/blob/main/src/Lemmata/GeneralBFact/Imports.lean The original statement is for `Fin`-indexed matrices; here it is generalized to arbitrary finite index types. The extraction, cleanup, port to current `master` and this PR were made by **GLM 5.4** (Z.ai) running in **DeepSeek Harness**; all mathematical credit belongs to Levent Alpöge and Claude, who is listed as an author in the file header and as `Co-authored-by` in the commit. The extraction project is documented in https://github.com/CocoSgt/rh-mathlib-lemmas. Note on licensing: the original release does not state an explicit license file. Please make sure the author is OK with merging before doing so. t-algebra new-contributor
label:t-algebra$
23/1 Mathlib/LinearAlgebra/Matrix/Determinant/Basic.lean 1 2 ['github-actions'] nobody
0-2908
48 minutes ago
0-3878
1 hour ago
0-3823
1 hour
0
46342 jkomyno
author:jkomyno
feat(Order/Submodular): define submodular, supermodular, and modular functions This PR adds the lattice-level vocabulary for submodularity: `Submodular`, `Supermodular` and `Modular` on a lattice, their restrictions to a subset, and the algebra that follows from the inequality alone. `Mathlib/Order/Submodular/Defs.lean` (145 lines): - `Submodular f` is `f (a ⊓ b) + f (a ⊔ b) ≤ f a + f b` for `[Lattice α] [Add β] [Preorder β]`. `Supermodular` is the reverse inequality and `Modular` is the equality. `Modular` asks only for `[Add β]`. - `SubmodularOn f s`, `SupermodularOn f s` and `ModularOn f s` restrict the pairs to a set `s`. - `modular_iff_submodular_and_supermodular`: over a partial order, modularity is submodularity plus supermodularity. The `*On` version is included. `Mathlib/Order/Submodular/Basic.lean` (262 lines): - constant functions, and `LinearOrder.modular` with its submodular and supermodular corollaries. - invariance under `OrderDual` (`submodular_comp_ofDual_iff`) and duality by negation (`submodular_neg_iff`). - closure of the submodular cone under `add`, `sub`, `smul` by a nonnegative scalar, `finset_sum` and `pi_sum`. - precomposition with a `LatticeHom` or an `OrderIso`. - `Submodular.inf_const` and `Supermodular.sup_const`: truncating a monotone function from above or below preserves the inequality. - `Submodular.sup_le_add_of_disjoint`: with `0 ≤ f ⊥`, a submodular function is subadditive on disjoint elements. Both files use the current module conventions (`module`, `public section`, `@[expose]` on the definitions). Zulip: I introduced myself and the project in [Alberto Schiabel / jkomyno / submodularity](https://leanprover.zulipchat.com/#narrow/channel/113489-new-members/topic/Alberto.20Schiabel.20.2F.20jkomyno.20.2F.20submodularity/near/642663285). Two questions are still open there, and I am happy to follow whatever comes out of it: `Submodular` versus `IsSubmodular` naming, and whether `Mathlib/Order/Submodular/` is the right home. Related: #43824 adds a single-file version of the same material in `Mathlib/Order/Submodular.lean`, with `IsSubmodular`-style names, `[LE β]` assumptions and a `Finset` diminishing-returns lemma. It has been awaiting author since 2026-10-16. This PR is meant to supersede it. I have no relationship with the original author. AI assistance: the Lean was written with LLM assistance, using `fable-5.2` and `gemini 4 neon` with Lean 4 agent skills for proof search and Mathlib API lookup. I reviewed every declaration by hand: the definitions, the typeclass assumptions and each proof, and I re-ran the build and the style linters after the fixes. I confirm that I can explain and defend each design decision here without a model. I'm also manually editing this PR description to make it as readable for you maintainers as possible. Verification, on the last commit of this branch: - `lake build Mathlib.Order.Submodular.Basic`, no warnings. - `lake exe lint-style` on both files, clean. - No `sorry` in either file. Planned follow-ups, each a separate future PR (if you'd appreciate having them): - `Finset` diminishing returns: `Submodular.add_insert_le`, the equivalences `submodular_iff_add_insert_le` and `submodular_iff_pair_insert_le`, complement duality, and cardinality as a modular set function. - Closure under `finset_sum` and adding a constant. - `k`-submodular functions in `Mathlib/Order/Submodular/KSubmodular/`: allocations `α → Option κ`, `kInter` and `kUnion`, orthant submodularity, pairwise monotonicity, and the `k = 1` case reducing to `Submodular`. - DR-submodularity on `ι → ℕ`: `CoordConcave`, `DRSubmodular ↔ Submodular ∧ CoordConcave`, and the unary-expansion reduction `DRSubmodularOn f (Icc 0 u) ↔ Submodular (f ∘ latticeProj u)`. - `Submodular M.eRk` for a matroid, phrased against the existing `Matroid.eRk_inter_add_eRk_union_le`. - Further out: concave-of-modular composition, the Lovász extension with submodular and base polyhedra, and greedy `(1 - 1/e)` guarantees. These are probably a better fit in a separate, submodularity-specific package that imports `mathlib4`, rather than in `mathlib4`'s own core. t-order LLM-generated new-contributor 409/0 Mathlib.lean,Mathlib/Order/Submodular/Basic.lean,Mathlib/Order/Submodular/Defs.lean 3 3 ['github-actions', 'jkomyno'] nobody
0-2381
39 minutes ago
0-3281
53 minutes ago
0-3226
53 minutes
0

PRs on the review queue labelled 'easy'

Number Author Title Description Labels +/- Modified files (first 100) 📝 💬 All users who commented or reviewed Assignee(s) Updated Last status change total time in review blocks
45969 wwylele
author:wwylele
fix(MeasureTheory): correct namespace of NullMeasurableSet.const_smul The previous name was "MeasureTheory. **Measure.** NullMeasurableSet.const_smu". The "Measure." part looks accidentally from the surrounding namespace. This prohibited dot notation There was also a note on top of this lemma. I chose to preserve it as it tells a more complicated story yet to fix: the `NullMeasurableSet` counterpart of `MeasurableSet.const_smul` has already entered Mathlib as `NullMeasurableSet.smul`. Meanwhile, the `MeasurableSet` counterpart of `NullMeasurableSet.const_smul` is `MeasurableSet.const_smul₀` with a vast generalization. The potential generalization of `NullMeasurableSet.const_smul` needs to take a hypothesis `(hμ : ∀ a : G₀, a ≠ 0 → QuasiMeasurePreserving (a • ·) μ μ)`, so that new lemma probably deserves the name `NullMeasurableSet.const_smul₀`. --- AI usage disclosure: this was motivated by findings from when I was using Claude to golf a downstream project. All code written here was manual by me <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> easy t-measure-probability 5/1 Mathlib/MeasureTheory/Measure/Lebesgue/EqHaar.lean 1 2 ['github-actions', 'wwylele'] nobody
9-41902
9 days ago
9-42482
9 days ago
9-42427
9 days
0
43478 plp127
author:plp127
feat(Data/PFunctor): pointfree lemmas for map Prove `PFunctor.map_id` and `PFunctor.map_comp_map`, pointfree analogues of `PFunctor.id_map` and `PFunctor.map_map`. The names are chosen to match the corresponding lemmas for `LawfulFunctor`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data easy 5/0 Mathlib/Data/PFunctor/Univariate/Basic.lean 1 1 ['github-actions'] TwoFX
assignee:TwoFX
3-51251
3 days ago
77-41902
77 days ago
77-41989
77 days
0
43948 JX-Mo
author:JX-Mo
chore(RepresentationTheory/Coinduced): tech debt Remove five `backward.isDefEq.respectTransparency.types` and add a CoeFun instance for `coindV` to justify the existing `coe`-named lemmas. https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/.60CoeFun.60.20or.20.60.2Eval.60/with/630026437 t-algebra tech debt easy
label:t-algebra$
22/17 Mathlib/RepresentationTheory/Coinduced.lean 1 38 ['JX-Mo', 'Whysoserioushah', 'github-actions', 'jcommelin', 'jjdishere', 'leanprover-radar', 'mathlib-bors', 'mathlib-merge-conflicts'] nobody
3-12202
3 days ago
3-13226
3 days ago
50-83538
50 days
4
46218 urkud
author:urkud
feat(Topology/MetricSpace/Bounded): add `Metric.ediam_closedBall_le` Add `Metric.ediam_closedBall_le : ediam (closedBall x r) ≤ 2 * ENNReal.ofReal r`, the `closedBall` analogue of `Metric.ediam_closedEBall_le`. Upstreamed from the https://github.com/urkud/SardMoreira project. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-topology easy maintainer-merge 15/0 Mathlib/Topology/MetricSpace/Bounded.lean,Mathlib/Topology/MetricSpace/Pseudo/Defs.lean 2 3 ['github-actions', 'themathqueen'] nobody
1-35306
1 day ago
2-39138
2 days ago
2-65513
2 days
2

PRs on the review queue labelled 'tech debt' or 'longest-pole'

Number Author Title Description Labels +/- Modified files (first 100) 📝 💬 All users who commented or reviewed Assignee(s) Updated Last status change total time in review blocks
44040 kim-em
author:kim-em
chore: adaptation notes for the backward.privateInPublic uses blocked on lean4#14708 This PR adds an `#adaptation_note` at each `variable` declaration with an autoParam binder whose users need `backward.privateInPublic`. These uses (about 80 of the remaining option lines, in 14 files) are not removable on the Mathlib side: the autoParam helper declaration generated for a `variable` is always private, and any declaration using that variable in a public section silently elaborates to `sorry` without the option. This is https://github.com/leanprover/lean4/issues/14708. The note says which `set_option`s can go once that is fixed, and stops anyone from spending time on them before then. Each affected file was checked by removing its `true`-only option lines and observing the `sorry` warnings and the follow-on `autoParam … is not a constant` errors. It also deletes the one option line in `CategoryTheory/SmallObject/Iteration/ExtendToSucc` that turned out to be unnecessary. 🤖 Prepared with Claude Code tech debt LLM-generated 116/0 Mathlib/Algebra/Module/ZLattice/Covolume.lean,Mathlib/AlgebraicTopology/SimplicialSet/CompStruct.lean,Mathlib/AlgebraicTopology/SimplicialSet/StrictSegal.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/NonUnital.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Unital.lean,Mathlib/Analysis/Distribution/TemperedDistribution.lean,Mathlib/CategoryTheory/ComposableArrows/Basic.lean,Mathlib/CategoryTheory/Join/Basic.lean,Mathlib/CategoryTheory/Limits/Shapes/Reflexive.lean,Mathlib/CategoryTheory/LocallyCartesianClosed/ChosenPullbacksAlong.lean,Mathlib/CategoryTheory/Monoidal/Braided/Basic.lean,Mathlib/CategoryTheory/Monoidal/CommGrp_.lean,Mathlib/CategoryTheory/Monoidal/Functor.lean,Mathlib/CategoryTheory/Sites/Point/Basic.lean,Mathlib/CategoryTheory/SmallObject/Iteration/ExtendToSucc.lean 15 1 ['github-actions'] nobody
45-59242
1 month ago
61-51062
61 days ago
61-52192
61 days
0
43885 plp127
author:plp127
refactor: reduce defeq abuse in `Representation.asModule` Reduce defeq abuse around `Representation.asModule` by adding explicitly uses of `Representation.asModuleEquiv` to convert between `V` and `ρ.asModule`. Also reorganize some `@[simp]` lemmas and fix some naming issues. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebra tech debt
label:t-algebra$
70/89 Mathlib/RepresentationTheory/Basic.lean,Mathlib/RepresentationTheory/Intertwining.lean,Mathlib/RepresentationTheory/Rep/Iso.lean,Mathlib/RepresentationTheory/Submodule.lean,Mathlib/RepresentationTheory/Subrepresentation.lean 5 21 ['JX-Mo', 'github-actions', 'plp127'] nobody
41-51794
1 month ago
62-72865
62 days ago
66-68665
66 days
0
44712 plp127
author:plp127
chore: rename arguments to `Shrink.rec` Name the motive `motive` and name the minor premises according to their contents. While we're here, also unexpose `Shrink.rec`, which is the last exposed declaration in this file, so also remove the `@[expose]` from the `@[expose] public section` at the top of the file because none of the declarations are actually exposed. Also add a docstring. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-logic 10/10 Mathlib/Logic/Small/Defs.lean,scripts/nolints.json 2 2 ['github-actions', 'vihdzp'] nobody
41-33344
1 month ago
42-60301
42 days ago
42-60246
42 days
0
42561 SnirBroshi
author:SnirBroshi
feat(Order/RelSeries): order series by refinement Define a partial order on `RelSeries`, add basic lemmas for the operations (e.g. `p < p.append q`), and relate to `IsChain` on sets. This lets us spell "maximal chain" using series. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) tech debt t-order 151/5 Mathlib/Order/RelSeries.lean 1 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
26-68334
26 days ago
26-70529
26 days ago
106-30607
106 days
0
45450 mcdoll
author:mcdoll
chore(NumberTheory): replace anonymous constructor by .mk in `ArithmeticFunction` --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-number-theory tech debt 24/27 Mathlib/NumberTheory/ArithmeticFunction/Defs.lean,Mathlib/NumberTheory/ArithmeticFunction/LFunction.lean,Mathlib/NumberTheory/ArithmeticFunction/Misc.lean,Mathlib/NumberTheory/ArithmeticFunction/Moebius.lean,Mathlib/NumberTheory/ArithmeticFunction/VonMangoldt.lean,Mathlib/NumberTheory/ArithmeticFunction/Zeta.lean,Mathlib/NumberTheory/LSeries/Convolution.lean 7 1 ['github-actions'] nobody
24-51242
24 days ago
24-51921
24 days ago
24-51866
24 days
0
45392 vihdzp
author:vihdzp
chore: state Borel isomorphism theorem using `Uncountable` We also deprecate the specialization of it to `ℕ → Bool`, after proving the instance that allows to infer the uncountability of this type automatically. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-measure-probability tech debt 53/25 Mathlib/Basic/Countable/Defs.lean,Mathlib/LinearAlgebra/Dimension/ErdosKaplansky.lean,Mathlib/MeasureTheory/Constructions/Polish/Basic.lean,Mathlib/MeasureTheory/Constructions/Polish/EmbeddingReal.lean,Mathlib/SetTheory/Cardinal/Basic.lean,Mathlib/SetTheory/Cardinal/Finite.lean 6 1 ['github-actions'] nobody
24-28180
24 days ago
25-36420
25 days ago
25-43782
25 days
0
44363 Parcly-Taxel
author:Parcly-Taxel
chore: remove `set_option` in `Order.Nucleus` tech debt t-order 7/15 Mathlib/Order/Nucleus.lean 1 13 ['Parcly-Taxel', 'github-actions', 'grunweg', 'mathlib-merge-conflicts', 'mathlib-splicebot'] nobody
24-15296
24 days ago
25-15489
25 days ago
50-73487
50 days
0
44584 CBirkbeck
author:CBirkbeck
chore(AlgebraicTopology/FundamentalGroupoid): deprecate `transReflReparamAux` in favor of `qRight` Deprecate `Path.Homotopy.transReflReparamAux` and its lemmas: the function is `fun t ↦ unitInterval.qRight (t, 0)`, which `trans_refl_reparam` and `transRefl` now use. --- <!--redteam:v1 {"owner":"AI-DOOM-97fce5ac-e255-4515-b311-12ecf245ce72","findings":["RT-20261006-546cb9"],"patterns":["parallel-reparametrisation-helper"],"severity":"MAJOR"}--> 🤖 Generated with [Claude Code](https://claude.com/claude-code) t-algebraic-topology tech debt LLM-generated 10/12 Mathlib/AlgebraicTopology/FundamentalGroupoid/Basic.lean 1 1 ['github-actions', 'tb65536'] nobody
20-6455
20 days ago
22-85617
22 days ago
22-85562
22 days
0
45742 vihdzp
author:vihdzp
chore: recursor for `SignType` using the simp-normal forms --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Co-authored by @plp127 tech debt t-data 39/10 Mathlib/Basic/Sign/Basic.lean,Mathlib/Basic/Sign/Defs.lean,Mathlib/Data/EReal/Inv.lean 3 1 ['github-actions'] nobody
15-69784
15 days ago
15-72430
15 days ago
15-72375
15 days
0
45849 Whysoserioushah
author:Whysoserioushah
chore(Topology/Sheaves/Stalks): add implicit_reducible to stalk Extracted from [Stacks Project](https://github.com/AxiomMath/Stacks) formalization. co-authored-by: Axiom Formalization team --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt 4/9 Mathlib/Geometry/RingedSpace/PresheafedSpace.lean,Mathlib/Geometry/RingedSpace/Stalks.lean,Mathlib/Topology/Sheaves/Stalks.lean 3 1 ['github-actions'] nobody
12-67499
12 days ago
12-72629
12 days ago
12-72574
12 days
0
45889 vihdzp
author:vihdzp
refactor: rename `Cardinal.lt_aleph0_iff_finite` → `Cardinal.mk_lt_aleph0_iff` I claim that the older name is not good, since it doesn't mention `Cardinal.mk`. We also rename some similar surrounding theorems. This incidentally gets rid of two duplicate declarations. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-set-theory tech debt 88/94 Mathlib/Algebra/Module/SpanRank.lean,Mathlib/Combinatorics/Matroid/Rank/Cardinal.lean,Mathlib/Data/Set/Finite/Basic.lean,Mathlib/Data/W/Cardinal.lean,Mathlib/FieldTheory/CardinalEmb.lean,Mathlib/FieldTheory/FinTrdeg.lean,Mathlib/FieldTheory/Finiteness.lean,Mathlib/FieldTheory/IsAlgClosed/Classification.lean,Mathlib/LinearAlgebra/Dimension/ErdosKaplansky.lean,Mathlib/LinearAlgebra/Dimension/Finite.lean,Mathlib/LinearAlgebra/Dimension/FreeAndStrongRankCondition.lean,Mathlib/LinearAlgebra/Dimension/StrongRankCondition.lean,Mathlib/LinearAlgebra/FiniteDimensional/Basic.lean,Mathlib/ModelTheory/Algebra/Field/IsAlgClosed.lean,Mathlib/ModelTheory/Satisfiability.lean,Mathlib/Order/Filter/CardinalInter.lean,Mathlib/Order/Filter/Cocardinal.lean,Mathlib/RingTheory/Algebraic/Cardinality.lean,Mathlib/SetTheory/Cardinal/Basic.lean,Mathlib/SetTheory/Cardinal/CountableCover.lean,Mathlib/SetTheory/Cardinal/Finite.lean,Mathlib/SetTheory/Cardinal/Finsupp.lean,Mathlib/SetTheory/Cardinal/Subfield.lean,Mathlib/SetTheory/Ordinal/Basic.lean 24 1 ['github-actions'] nobody
11-32252
11 days ago
11-32291
11 days ago
11-32287
11 days
0
43045 plp127
author:plp127
feat: `Dyadic` is a localization Prove that `Dyadic` is a localization of the integers generated by inverting `2`. --- - [x] depends on: #43038 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data tech debt 97/0 Mathlib.lean,Mathlib/Data/Dyadic/IsLocalization.lean 2 13 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'metakunt', 'plp127', 'vihdzp'] nobody
10-43065
10 days ago
11-73288
11 days ago
11-73560
11 days
0
44026 kim-em
author:kim-em
chore: remove backward.privateInPublic in category theory, topology and analysis This PR removes the `backward.privateInPublic` option in 6 files across category theory, topology and analysis. In each case a private definition appeared in the statement of a public declaration, so it was already part of the public interface in all but name. The fix is to drop `private` from those definitions (and from the auxiliary definitions their bodies depend on in exposed sections), adding docstrings where they were missing. In `Analysis/InnerProductSpace/OfNorm` the auxiliary inner product `inner_` moves into the `InnerProductSpaceable` namespace rather than becoming a root-level name; the public lemmas `inner_.norm_sq`, `inner_.conj_symm` and `Continuous.inner_` already carried its name. In `Topology/Category/Compactum` the helper `cl` gets a mathematical docstring, and the two lemmas about it that are only used in proofs stay private. Files where a private *lemma* appeared in a public statement, and the files with file-wide `public section` restructuring, are handled in #44032. Names are otherwise kept as they were; suggestions for better names are welcome but are not needed for this PR. 🤖 Prepared with Claude Code tech debt 19/63 Mathlib/Analysis/InnerProductSpace/OfNorm.lean,Mathlib/CategoryTheory/Monoidal/Internal/FunctorCategory.lean,Mathlib/FieldTheory/Galois/Profinite.lean,Mathlib/Topology/Category/Compactum.lean,Mathlib/Topology/Category/TopCat/Limits/Konig.lean,Mathlib/Topology/MetricSpace/GromovHausdorff.lean 6 3 ['github-actions', 'jjdishere'] nobody
7-83381
7 days ago
62-34478
62 days ago
62-34423
62 days
0
37279 imalinowskip
author:imalinowskip
feat(Probability): multivariate CLT --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> <!-- [ ] depends on: #40345 --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) new-contributor t-measure-probability tech debt 210/18 Mathlib/MeasureTheory/Function/ConvergenceInDistribution.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/AEStronglyMeasurable.lean,Mathlib/MeasureTheory/Function/StronglyMeasurable/Basic.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/MeasureTheory/Measure/LevyConvergence.lean,Mathlib/MeasureTheory/Measure/ProbabilityMeasure.lean,Mathlib/Probability/CentralLimitTheorem.lean,Mathlib/Probability/CramerWold.lean,Mathlib/Probability/Distributions/Gaussian/Multivariate.lean,Mathlib/Probability/Moments/Variance.lean 10 66 ['EtienneC30', 'RemyDegenne', 'github-actions', 'imalinowskip', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] EtienneC30
assignee:EtienneC30
7-73413
7 days ago
11-70880
11 days ago
57-25019
57 days
0
45808 vihdzp
author:vihdzp
feat(GroupTheory/Coxeter/Basic): add theorems for `CoxeterMatrix.simple` These match and help golf existing theorems on `CoxeterSystem.simple`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> I'm unsure on whether we want to be reproving things for `CoxeterMatrix.simple` and `CoxeterSystem.simple`. See [Zulip](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Design.20of.20Coxeter.20systems/with/638594141). - [x] depends on: #45806 tech debt t-group-theory 42/13 Mathlib/GroupTheory/Coxeter/Basic.lean 1 4 ['github-actions', 'mathlib-dependent-issues', 'wwylele'] nobody
7-26184
7 days ago
11-25897
11 days ago
11-26443
11 days
1
44995 WenrongZou
author:WenrongZou
feat(RingTheory/MvFormalGroup): multivariate formal group definition This PR defines multivariate (including infinite dimensional) formal group laws over a commutative ring `R`. Main definitions: - `MvFormalGroup σ R`: a family `F = (F_i)_{i : σ}` of power series in two sets of variables `X, Y`, with zero constant coefficient, linear term `X_i + Y_i`, and associativity `F(F(X, Y), Z) = F(X, F(Y, Z))`. - `MvFormalGroup.IsComm`: the commutativity condition `F(X, Y) = F(Y, X)`. Main results: - `zero_add`, `add_zero`: `F(0, X) = X` and `F(X, 0) = X`. --- - [x] depends on: #44942 - [x] depends on: #44996 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory tech debt 289/0 Mathlib.lean,Mathlib/RingTheory/MvFormalGroup/Basic.lean 2 9 ['WenrongZou', 'github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'wwylele'] nobody
7-22783
7 days ago
8-79354
8 days ago
8-81377
8 days
0
43095 plp127
author:plp127
chore(Data/PFunctor): reduce defeq abuse around `PFunctor.W` Reduce the defeq abuse around `PFunctor.W` by adding some API. --- - [x] depends on: #43056 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-data tech debt 88/52 Mathlib/Data/PFunctor/Multivariate/W.lean,Mathlib/Data/PFunctor/Univariate/Basic.lean,Mathlib/Data/QPF/Univariate/Basic.lean 3 6 ['github-actions', 'mathlib-dependent-issues', 'plp127', 'vihdzp'] nobody
6-44532
6 days ago
79-82261
79 days ago
79-83043
79 days
0
43565 Parcly-Taxel
author:Parcly-Taxel
refactor(Archive/FriendshipGraphs): golf everything Also remove the file's `set_option`s and `@[expose]`. Like #43434, no deprecations are added since this is a leaf file in Archive. tech debt 103/292 Archive/Wiedijk100Theorems/FriendshipGraphs.lean 1 9 ['Parcly-Taxel', 'SnirBroshi', 'github-actions', 'mathlib-merge-conflicts'] jjdishere
assignee:jjdishere
5-51256
5 days ago
14-73955
14 days ago
75-40756
75 days
0
32840 joelriou
author:joelriou
refactor(CategoryTheory): remove the old Ext API As it is now possible to compute `Ext`-groups (defined using the derived category) using an injective resolution #32105 or a projective resolution #32816, the old `Ext` API (based on left derived functors) is removed. --- - [x] depends on: #44124 - [x] depends on: #44190 - [x] depends on: #32816 - [x] depends on: #32105 - [x] depends on: #32814 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-category-theory large-import tech debt 283/29 Mathlib.lean,Mathlib/Algebra/Homology/Embedding/Basic.lean,Mathlib/Algebra/Homology/Embedding/CochainComplex.lean,Mathlib/Algebra/Homology/HomotopyCategory/HomComplexIsStrictlyGE.lean,Mathlib/Algebra/Homology/LinearYonedaObj.lean,Mathlib/Algebra/Homology/LocalCohomology.lean,Mathlib/CategoryTheory/Abelian/Ext.lean,Mathlib/CategoryTheory/Linear/Yoneda.lean,Mathlib/RepresentationTheory/Homological/GroupCohomology/Basic.lean,Mathlib/RepresentationTheory/Homological/Resolution.lean 10 9 ['github-actions', 'joelriou', 'mathlib-bors', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mathlib4-merge-conflict-bot'] nobody
5-12473
5 days ago
5-13044
5 days ago
27-45379
27 days
0
45931 vihdzp
author:vihdzp
chore(SetTheory/Ordinal/CantorNormalForm): miscellaneous cleanup This PR does a few small things: * Give better names to the arguments of `CNF.rec`, as per our convention on recursors. * Use the `induction` tactic instead of applying `CNF.rec` explicitly. * Generalize `coeff_zero_left` and `coeff_one_left` syntactically, by proving the unapplied versions instead. * Remove a redundant argument from `CNF.opow_mul_add`, and from some theorems that depended on it. * Golf a few other proofs slightly. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #45930 t-set-theory tech debt 79/81 Mathlib/SetTheory/Ordinal/CantorNormalForm.lean 1 2 ['github-actions', 'mathlib-dependent-issues'] nobody
5-1740
5 days ago
5-6845
5 days ago
5-7545
5 days
1
41675 joelriou
author:joelriou
feat(AlgebraicTopology): pushout diagrams in the filtration of `Δ[p] ⊗ Δ[1]` This will be used in #42295 in order to construct morphisms from `Δ[p] ⊗ Δ[1]` out of the data of the images of the nondegenerate `(p + 1)`-simplices of `Δ[p] ⊗ Δ[1]`. --- - [x] depends on: #41656 - [x] depends on: #41655 - [x] depends on: #41624 - [x] depends on: #41617 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-algebraic-topology tech debt 244/13 Mathlib/AlgebraicTopology/SimplicialSet/AnodyneExtensions/UnionProd.lean,Mathlib/AlgebraicTopology/SimplicialSet/ProdStdSimplex.lean,Mathlib/AlgebraicTopology/SimplicialSet/ProdStdSimplexOne.lean,Mathlib/AlgebraicTopology/SimplicialSet/StdSimplex.lean,Mathlib/AlgebraicTopology/SimplicialSet/Subcomplex.lean,Mathlib/CategoryTheory/Monoidal/FunctorCategory.lean 6 19 ['github-actions', 'joelriou', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'robin-carlier'] nobody
4-15555
4 days ago
35-81357
35 days ago
75-9040
75 days
2
46055 WenrongZou
author:WenrongZou
chore(MvPowerSeries): avoid `DefEq` abuse In this PR, we try to fix the `backward.isDefEq.respectTransparency` in `MvPowerSeries` folder --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-ring-theory tech debt 70/130 Mathlib/RingTheory/MvPowerSeries/Basic.lean,Mathlib/RingTheory/MvPowerSeries/Equiv.lean,Mathlib/RingTheory/MvPowerSeries/Expand.lean,Mathlib/RingTheory/MvPowerSeries/LinearTopology.lean,Mathlib/RingTheory/MvPowerSeries/Order.lean,Mathlib/RingTheory/MvPowerSeries/PiTopology.lean,Mathlib/RingTheory/MvPowerSeries/Substitution.lean,Mathlib/RingTheory/MvPowerSeries/Trunc.lean 8 1 ['github-actions'] nobody
3-79698
3 days ago
6-58830
6 days ago
6-58775
6 days
0
46180 Nicola9Falciola
author:Nicola9Falciola
chore(Algebra/Module/Submodule/Invariant): remove all the `set_option` in the fille and api This PR removes all the defeq abuse in the file and adds small API lemmas such as the compatibility between `invtSubmodule` and `compatibleMaps`. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt
label:t-algebra$
21/14 Mathlib/Algebra/Module/Submodule/Invariant.lean 1 8 ['Nicola9Falciola', 'github-actions', 'themathqueen'] nobody
3-73810
3 days ago
3-77893
3 days ago
3-77838
3 days
0
45791 JonasReif
author:JonasReif
chore: remove obsolete proof workarounds Several proofs still carried workarounds marked by TODOs, porting notes, an adaptation note, or `erw`, for problems that have since been fixed: the missing lemmas now exist, or Lean no longer needs the hint. This PR removes those workarounds. Only proofs change; every statement stays the same. - `PullbackCone.isLimitOfFactors`: use `t.condition_assoc h` instead of the manual reassoc workaround - `Scheme.basicOpen_add_le`: use `Opens.mem_sup` (resolves the TODO) - `Cardinal.toNat_congr`: use `mk_congr_lift`, dropping the universe hint - `LieIdeal.map_of_image`: replace `erw [h]` with `exact h.subset` - `isPullback_inl_inl_coprodMap`: plain `simp` works now that `Scheme.Hom.mem_opensRange` exists (resolves the TODO) - `Proj.fromOfGlobalSections_preimage_basicOpen`: use `Scheme.Hom.mem_preimage` (resolves the TODO) - `Tuple.graph.card`: one-line injectivity proof - `StarModule.decomposeProdAdjoint`: drop the `erw` and its outdated note - `skyscraperPresheaf_isSheaf`: the universe annotation is no longer needed --- Created with Claude Opus 5.5 in Claude Code. 🤖 Generated with [Claude Code](https://claude.com/claude-code) tech debt new-contributor 11/29 Mathlib/Algebra/Lie/Ideal.lean,Mathlib/Algebra/Star/Module.lean,Mathlib/AlgebraicGeometry/Limits.lean,Mathlib/AlgebraicGeometry/ProjectiveSpectrum/Basic.lean,Mathlib/AlgebraicGeometry/Scheme.lean,Mathlib/CategoryTheory/Limits/Shapes/Pullback/Mono.lean,Mathlib/Data/Fin/Tuple/Sort.lean,Mathlib/SetTheory/Cardinal/ToNat.lean,Mathlib/Topology/Sheaves/Skyscraper.lean 9 9 ['JonasReif', 'Parcly-Taxel', 'github-actions', 'grunweg'] nobody
3-57803
3 days ago
3-60552
3 days ago
4-8480
4 days
0
45451 Parcly-Taxel
author:Parcly-Taxel
chore: remove transparency `set_option`s in `SimpleGraph`, part 1 These should be less controversial changes from #45430. tech debt t-combinatorics 14/33 Mathlib/Combinatorics/SimpleGraph/AdjMatrix.lean,Mathlib/Combinatorics/SimpleGraph/Clique.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/Finite.lean,Mathlib/Combinatorics/SimpleGraph/Connectivity/Subgraph.lean,Mathlib/Combinatorics/SimpleGraph/Ends/Defs.lean,Mathlib/Combinatorics/SimpleGraph/Finite.lean,Mathlib/Combinatorics/SimpleGraph/StronglyRegular.lean,Mathlib/Combinatorics/SimpleGraph/Subgraph.lean 8 1 ['github-actions'] SnirBroshi
assignee:SnirBroshi
3-21698
3 days ago
3-22211
3 days ago
24-46714
24 days
1
45453 Parcly-Taxel
author:Parcly-Taxel
chore: remove transparency `set_option`s in `SimpleGraph`, part 2 More fixes from #45430. * `ConnectedComponent.lift` now has `Reachable` in its hypotheses, which allows removing a `set_option`. * There was a long-standing typo in the statement of `Walk.ofBoxProdRight_boxProdRight`, which has been corrected. Equational lemmas for `Walk.ofBoxProd{Left,Right}` have been added too. * The golfed proof of `free_killCopies` was done by GPT-6.1 Sol, then hand-optimised. tech debt t-combinatorics LLM-generated 52/67 Mathlib/Combinatorics/SimpleGraph/Connectivity/Connected.lean,Mathlib/Combinatorics/SimpleGraph/Copy.lean,Mathlib/Combinatorics/SimpleGraph/Ends/Defs.lean,Mathlib/Combinatorics/SimpleGraph/LapMatrix.lean,Mathlib/Combinatorics/SimpleGraph/Prod.lean,Mathlib/Combinatorics/SimpleGraph/Subgraph.lean 6 1 ['github-actions'] SnirBroshi
assignee:SnirBroshi
3-21219
3 days ago
3-22034
3 days ago
24-41429
24 days
1
43948 JX-Mo
author:JX-Mo
chore(RepresentationTheory/Coinduced): tech debt Remove five `backward.isDefEq.respectTransparency.types` and add a CoeFun instance for `coindV` to justify the existing `coe`-named lemmas. https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/.60CoeFun.60.20or.20.60.2Eval.60/with/630026437 t-algebra tech debt easy
label:t-algebra$
22/17 Mathlib/RepresentationTheory/Coinduced.lean 1 38 ['JX-Mo', 'Whysoserioushah', 'github-actions', 'jcommelin', 'jjdishere', 'leanprover-radar', 'mathlib-bors', 'mathlib-merge-conflicts'] nobody
3-12202
3 days ago
3-13226
3 days ago
50-83538
50 days
4
43705 joelriou
author:joelriou
feat(Category/Abelian/Projective): interaction between `ProjectiveResolution.extMk` and the connecting morphism This is the dual result to #43224. Obtaining the dual version required introducing more API for the mapping cocone. --- - [x] depends on: #43224 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-category-theory tech debt increases-technical-debt 408/20 Mathlib/Algebra/Homology/DerivedCategory/Basic.lean,Mathlib/Algebra/Homology/DerivedCategory/ShortExact.lean,Mathlib/Algebra/Homology/DerivedCategory/SingleTriangle.lean,Mathlib/Algebra/Homology/DerivedCategory/SmallShiftedHom.lean,Mathlib/Algebra/Homology/HomotopyCategory/HomComplexShift.lean,Mathlib/Algebra/Homology/HomotopyCategory/HomComplexSingle.lean,Mathlib/Algebra/Homology/HomotopyCategory/MappingCocone.lean,Mathlib/Algebra/Homology/HomotopyCategory/Shift.lean,Mathlib/Algebra/Homology/HomotopyCategory/ShortExact.lean,Mathlib/CategoryTheory/Abelian/Injective/Ext.lean,Mathlib/CategoryTheory/Abelian/Projective/Ext.lean,Mathlib/CategoryTheory/Abelian/Projective/Extend.lean 12 7 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
3-11173
3 days ago
3-11831
3 days ago
34-25345
34 days
0
45528 joelriou
author:joelriou
chore(CategoryTheory/Limits): remove set_option for multiequalizers --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-category-theory tech debt 36/80 Mathlib/CategoryTheory/Limits/Preserves/Shapes/Multiequalizer.lean,Mathlib/CategoryTheory/Limits/Shapes/Equalizers.lean,Mathlib/CategoryTheory/Limits/Shapes/Multiequalizer.lean,Mathlib/Order/CompleteLattice/MulticoequalizerDiagram.lean 4 1 ['github-actions'] nobody
3-224
3 days ago
22-14851
22 days ago
22-14796
22 days
6
46176 Nicola9Falciola
author:Nicola9Falciola
chore(LinearAlgebra/Matrix/FixedDetMatrices): remove all the `set_option` in the file due to defeq abuse This PR adds a `_.mk` for `FixedDetMatrix` and small API lemmas to avoid defeq abuse later in the file removing all the remaining `set_options`. I have modified a couple of proofs also to save heartbeats. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt
label:t-algebra$
29/17 Mathlib/LinearAlgebra/Matrix/FixedDetMatrices.lean 1 1 ['github-actions'] nobody
2-82827
2 days ago
2-85175
2 days ago
3-60191
3 days
0
43232 Parcly-Taxel
author:Parcly-Taxel
refactor: `TrivSqZeroExt` extending `Prod` Define à la `Unitization` ([#mathlib4 > TrivSqZeroExt as a 2-field structure @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/TrivSqZeroExt.20as.20a.202-field.20structure/near/620183663)) ```lean structure TrivSqZeroExt (R : Type u) (M : Type v) extends R × M ``` This PR came out of investigating the source of the `DualQuaternion` slowdown in #43078. (`DualNumber R` is an abbrev for `TrivSqZeroExt R R`.) `Topology.Instances.TrivSqZeroExt` and `Analysis.Normed.Algebra.TrivSqZeroExt` were filled in with significant help from GPT-6.1 Sol. t-algebra tech debt LLM-generated
label:t-algebra$
360/290 Mathlib/Algebra/DualNumber.lean,Mathlib/Algebra/DualQuaternion.lean,Mathlib/Algebra/TrivSqZeroExt/Basic.lean,Mathlib/Algebra/TrivSqZeroExt/Ideal.lean,Mathlib/Analysis/Normed/Algebra/TrivSqZeroExt.lean,Mathlib/LinearAlgebra/ExteriorAlgebra/Basic.lean,Mathlib/LinearAlgebra/Matrix/DualNumber.lean,Mathlib/LinearAlgebra/TensorAlgebra/Basic.lean,Mathlib/RingTheory/DualNumber.lean,Mathlib/Topology/Instances/TrivSqZeroExt.lean 10 10 ['Parcly-Taxel', 'github-actions', 'mathlib-merge-conflicts', 'plp127'] nobody
2-80210
2 days ago
16-48358
16 days ago
25-68319
25 days
0
46248 felixpernegger
author:felixpernegger
chore(Basic): unsqueeze terminal `simp only`s Per style guide. A few terminal `simp only` remain, but they have to, due to stuff looping wrongly etc --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-data 90/91 Mathlib/Basic/Complex/Basic.lean,Mathlib/Basic/ENNReal/Action.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Basic/ENNReal/BigOperators.lean,Mathlib/Basic/ENNReal/Inv.lean,Mathlib/Basic/ENNReal/Operations.lean,Mathlib/Basic/ENNReal/Real.lean,Mathlib/Basic/ExistsUnique.lean,Mathlib/Basic/IsEmpty/Basic.lean,Mathlib/Basic/Logic/Basic.lean,Mathlib/Basic/NNReal/Basic.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/Basic/NNReal/Star.lean,Mathlib/Basic/Nontrivial/Basic.lean,Mathlib/Basic/Nontrivial/Defs.lean,Mathlib/Basic/PEquiv.lean,Mathlib/Basic/Real/Basic.lean,Mathlib/Basic/Real/Pointwise.lean,Mathlib/Basic/Sign/Basic.lean,Mathlib/Basic/Sign/Defs.lean 20 3 ['felixpernegger', 'github-actions', 'leanprover-radar'] nobody
2-79663
2 days ago
2-82924
2 days ago
2-82961
2 days
0
44743 vihdzp
author:vihdzp
refactor(Wiedijk100Theorems/AreaOfACircle): delete file The area formula for circles exists within Mathlib already, and in fact we also have formulas for the volume of an n-sphere. So we delete the file on the archive, in favor for the Mathlib theorem. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> Not sure if this is the right thing to do. Maybe we could change the link on 100.yaml, but still keep the archive file as an alternate proof of a similar result? t-measure-probability file-removed tech debt 13/140 Archive.lean,Archive/Wiedijk100Theorems/AreaOfACircle.lean,Mathlib/MeasureTheory/Measure/Lebesgue/VolumeOfBalls.lean,docs/100.yaml 4 4 ['Parcly-Taxel', 'github-actions', 'mathlib-merge-conflicts'] RemyDegenne
assignee:RemyDegenne
2-57891
2 days ago
2-58366
2 days ago
41-81841
41 days
0
40644 j-loreaux
author:j-loreaux
refactor: use `LinearMap.IsWeak` for `WeakBilin` This introduces `WeakBilin.linearEquiv : WeakBilin B ≃ₗ[𝕜] E` as the canonical map between a space `E` and its type synonym `WeakBilin B`, for `B : E →ₗ[𝕜] F →ₗ[𝕜] 𝕜`. This serves to provides an abstraction barrier between these defeq types. We then add `WeakBilin.pairing : WeakBilin B →ₗ[𝕜] F →ₗ[𝕜] 𝕜` as a copy of the bilinear map `B` where we exchange the domain via `LinearEquiv.arrowCongr`. Finally, we provide an instance of `LinearMap.IsWeak (WeakBilin.pairing B)`. This allows us to remove abuse of definitional equality in the API for `WeakBilin`, and to deprecate most of the basic results in favor of their `LinearMap.IsWeak` variants. The one result which we don't deprecate is `WeakBilin.continuous_of_continuous_eval`. This is because the specific version we can tag with `fun_prop`, but the more general version would not be suitable as a `fun_prop` lemma because the linear map `B` inducing the topology would be a metavariable, and cannot be inferred from the type. --- - [ ] depends on: #40489 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-analysis t-topology tech debt maintainer-merge 220/118 Mathlib/Analysis/LocallyConvex/Polar.lean,Mathlib/Analysis/LocallyConvex/WeakDual.lean,Mathlib/Analysis/LocallyConvex/WeakSpace.lean,Mathlib/Analysis/Normed/Module/WeakDual.lean,Mathlib/MeasureTheory/Measure/FiniteMeasure.lean,Mathlib/Topology/Algebra/Module/Spaces/CharacterSpace.lean,Mathlib/Topology/Algebra/Module/Spaces/PointwiseConvergenceCLM.lean,Mathlib/Topology/Algebra/Module/Spaces/WeakBilin.lean,Mathlib/Topology/Algebra/Module/Spaces/WeakDual.lean 9 6 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts', 'mcdoll'] mcdoll
assignee:mcdoll
2-54629
2 days ago
23-25023
23 days ago
23-24969
23 days
0
38393 staroperator
author:staroperator
refactor(ModelTheory): add typeclasses for algebraic symbols `Language.ring` and `Language.presburger` share the same symbols `0`, `1` and `+` and have duplicated instances on `Term` and `realize` simp lemmas. This PR makes these symbols certain typeclasses (similar to [`Language.IsOrdered`](https://leanprover-community.github.io/mathlib4_docs/Mathlib/ModelTheory/Order.html#FirstOrder.Language.IsOrdered)) and removes the duplication. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-logic tech debt 401/202 Mathlib.lean,Mathlib/ModelTheory/Algebra/Classes.lean,Mathlib/ModelTheory/Algebra/Field/IsAlgClosed.lean,Mathlib/ModelTheory/Algebra/Ring/Basic.lean,Mathlib/ModelTheory/Algebra/Ring/FreeCommRing.lean,Mathlib/ModelTheory/Arithmetic/Presburger/Basic.lean,Mathlib/ModelTheory/Arithmetic/Presburger/Definability.lean 7 10 ['fpvandoorn', 'github-actions', 'mathlib-merge-conflicts', 'staroperator'] fpvandoorn
assignee:fpvandoorn
2-33597
2 days ago
2-34005
2 days ago
55-44270
55 days
1
46133 thorimur
author:thorimur
chore: change uses of `TopologicalSpace.Opens.is_open'` to `TopologicalSpace.Opens.isOpen` This PR changes uses of the projection `TopologicalSpace.Opens` to `isOpen` and advises doing so more generally in that field's docstring. Note: it does not make `is_open'` private, though, as that would require making the constructor private too, preventing us from writing e.g. `{ carrier := ..., is_open' := ... }`. Moving to a smart constructor or linting against this projection is a larger change. --- - [x] depends on: #45389 <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-topology tech debt 173/172 Mathlib/AlgebraicGeometry/AffineScheme.lean,Mathlib/AlgebraicGeometry/AffineTransitionLimit.lean,Mathlib/AlgebraicGeometry/Artinian.lean,Mathlib/AlgebraicGeometry/Birational/Birational.lean,Mathlib/AlgebraicGeometry/Birational/Composition.lean,Mathlib/AlgebraicGeometry/Birational/RationalMap.lean,Mathlib/AlgebraicGeometry/Cover/QuasiCompact.lean,Mathlib/AlgebraicGeometry/GammaSpecAdjunction.lean,Mathlib/AlgebraicGeometry/Group/Smooth.lean,Mathlib/AlgebraicGeometry/IdealSheaf/Basic.lean,Mathlib/AlgebraicGeometry/Modules/Tilde.lean,Mathlib/AlgebraicGeometry/Morphisms/Affine.lean,Mathlib/AlgebraicGeometry/Morphisms/ClosedImmersion.lean,Mathlib/AlgebraicGeometry/Morphisms/Constructors.lean,Mathlib/AlgebraicGeometry/Morphisms/Flat.lean,Mathlib/AlgebraicGeometry/Morphisms/FlatRank.lean,Mathlib/AlgebraicGeometry/Morphisms/OpenImmersion.lean,Mathlib/AlgebraicGeometry/Morphisms/QuasiCompact.lean,Mathlib/AlgebraicGeometry/Morphisms/QuasiSeparated.lean,Mathlib/AlgebraicGeometry/Morphisms/Smooth.lean,Mathlib/AlgebraicGeometry/Morphisms/SurjectiveOnStalks.lean,Mathlib/AlgebraicGeometry/Morphisms/UnderlyingMap.lean,Mathlib/AlgebraicGeometry/Morphisms/UniversallyClosed.lean,Mathlib/AlgebraicGeometry/Normalization.lean,Mathlib/AlgebraicGeometry/OpenImmersion.lean,Mathlib/AlgebraicGeometry/PointsPi.lean,Mathlib/AlgebraicGeometry/ProjectiveSpectrum/Scheme.lean,Mathlib/AlgebraicGeometry/Properties.lean,Mathlib/AlgebraicGeometry/QuasiAffine.lean,Mathlib/AlgebraicGeometry/Sites/SmallAffineZariski.lean,Mathlib/AlgebraicGeometry/Spec.lean,Mathlib/AlgebraicGeometry/SpreadingOut.lean,Mathlib/AlgebraicGeometry/Stalk.lean,Mathlib/AlgebraicGeometry/StructureSheaf.lean,Mathlib/AlgebraicGeometry/ZariskisMainTheorem.lean,Mathlib/Geometry/Manifold/HasGroupoid.lean,Mathlib/Geometry/Manifold/IsManifold/InteriorBoundary.lean,Mathlib/Geometry/Manifold/Sheaf/LocallyRingedSpace.lean,Mathlib/Geometry/RingedSpace/Basic.lean,Mathlib/Geometry/RingedSpace/LocallyRingedSpace/HasColimits.lean,Mathlib/MeasureTheory/Integral/RieszMarkovKakutani/Real.lean,Mathlib/MeasureTheory/Measure/Content.lean,Mathlib/RingTheory/Spectrum/Prime/Chevalley.lean,Mathlib/RingTheory/Spectrum/Prime/FreeLocus.lean,Mathlib/RingTheory/Spectrum/Prime/TensorProduct.lean,Mathlib/RingTheory/Spectrum/Prime/Topology.lean,Mathlib/Topology/Category/TopCat/Opens.lean,Mathlib/Topology/Constructible.lean,Mathlib/Topology/ContinuousMap/T0Sierpinski.lean,Mathlib/Topology/JacobsonSpace.lean,Mathlib/Topology/LocalAtTarget.lean,Mathlib/Topology/OpenPartialHomeomorph/Basic.lean,Mathlib/Topology/OpenPartialHomeomorph/Constructions.lean,Mathlib/Topology/Order/Category/FrameAdjunction.lean,Mathlib/Topology/Sets/Closeds.lean,Mathlib/Topology/Sets/CompactOpenCovered.lean,Mathlib/Topology/Sets/Compacts.lean,Mathlib/Topology/Sets/OpenCover.lean,Mathlib/Topology/Sets/Opens.lean,Mathlib/Topology/Sheaves/Points.lean,Mathlib/Topology/Sheaves/Presheaf.lean,Mathlib/Topology/Sheaves/Skyscraper.lean,Mathlib/Topology/Sheaves/Stalks.lean,Mathlib/Topology/Spectral/Prespectral.lean 64 4 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
2-18611
2 days ago
2-69568
2 days ago
4-828
4 days
0
45670 user202729
author:user202729
chore(AlgebraicGeometry/EllipticCurve/Projective): remove `erw` in `Formula.lean` Reducing tech debt. The main reason why `erw` was needed in this file instead of `rw` is the following. - Background: Each point is represented by a function `P : Fin 3 → R`, and there's local notation `x` being `(0 : Fin 3)`, similar for `y` and `z`. So `P x` is the first coordinate of `P`. For a curve `W'` and a point `P`, `W'.dblXYZ P` is another point, its double i.e. `2 • P`. - There are functions to compute various operations on elliptic curves, for example, `W.dblY P` computes the `Y`-coordinate of `2 • P`. Of course, this can be equivalently written as `W.dblXYZ P y`. - The two forms `W.dblY P` and `W.dblXYZ P y` are not definitionally equal at the default transparency level. Depends on which lemma we want to apply, we need to convert the goal to use one form or the other. --- Personally, I think it's a better idea to normalize on the `W.dblXYZ P y` form, and keep the `W.dblY P` form as strictly an implementation detail if needed. In this case, the `XYZ` suffix wouldn't be needed either, and the main definitions would be: ``` * `WeierstrassCurve.Projective.neg`: The negation `-P` of a point `P`. * `WeierstrassCurve.Projective.dbl`: The double `2 • P` of a point `P`. * `WeierstrassCurve.Projective.negDbl`: The negated double `-(2 • P)` of a point `P`. ``` etc. Thoughts? Note that `W.dbl P y` is only 1 character longer than `W.dblY P`. Most lemmas that we want to apply are already stated in term of the point (except that many use `W.negY P` instead of `W.neg P y`, though currently `W.neg` doesn't exist). Also, there are (very) long `rw` chains. ([#mathlib4 > Is long &#96;rw&#96; chain bad?](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Is.20long.20.60rw.60.20chain.20bad.3F/with/637217759)) Ideas? Another idea: have a `array_index` tactic that evaluates `![a, b, c, d] 2` to `c` when the index is a known constant, for example. Currently there is `simp only [fin3_def_ext]` which obviously only works on length-3 arrays. new-contributor t-algebraic-geometry tech debt 59/24 Mathlib/AlgebraicGeometry/EllipticCurve/Projective/Formula.lean 1 5 ['Multramate', 'github-actions', 'tb65536'] nobody
1-79313
1 day ago
17-79115
17 days ago
17-79060
17 days
0
46111 Hagb
author:Hagb
chore(Order/RelSeries): tag definitions providing `RelSeries` with `implicit_reducible` These definitions are sometimes applied with `Fin _` whose the type-correctness needs unfolding the definition. For example, ``` def ofLE (x : RelSeries r) {s : SetRel α α} (h : r ≤ s) : RelSeries s where length := x.length toFun := x step := ... ``` is used with `ofLE s h n` (i.e. `(ofLE s h).toFun n`) where `(ofLE s h).toFun` is a `Fin ((ofLE s h).length + 1) → α` and `n` is in `Fin (s.length + 1)` instead of `Fin ((ofLE s h).length + 1)`, unless w.r.t. higher transparency. It would be possible to cast these `Fin _` or use `Fin (EXPR.length + 1)` (where `EXPR` is the expression of a `RelSeries r` such as `ofLE s h`), which are painful. This PR tags these definitions with `@[implicit_reducible]` so that they can be unfolded in `implicit` transparency. As a result, `set_option backward.*` in `Mathlib.Order.RelSeries` can be removed. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-order 33/56 Mathlib/Order/JordanHolder.lean,Mathlib/Order/RelSeries.lean 2 4 ['Hagb', 'github-actions', 'leanprover-radar', 'mathlib-merge-conflicts'] nobody
1-77132
1 day ago
1-78507
1 day ago
2-79550
2 days
0
46299 themathqueen
author:themathqueen
chore(Algebra): weakening `AlgEquiv` definitions to use nonunital --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt
label:t-algebra$
38/23 Mathlib/Algebra/Algebra/Equiv.lean,Mathlib/Algebra/Algebra/Opposite.lean,Mathlib/Algebra/Algebra/Pi.lean,Mathlib/Algebra/Algebra/Prod.lean 4 3 ['github-actions', 'leanprover-radar', 'themathqueen'] nobody
1-66899
1 day ago
1-68635
1 day ago
1-68580
1 day
0
44672 JovanGerb
author:JovanGerb
feat(Algebra/Homology/HomologicalComplex): use `to_dual` This PR uses `to_dual` on `HomologicalComplex`, making `ChainComplex` dual to `CochainComplex`. - The type of `CochainComplex.ofHom` and `CochainComplex.mkHom` changed: the direction of the equality flipped to match with the dual. - `HomologicalComplex.Hom.sqFrom` gained a `simps!` attribute to replace two manually written lemmas. - `ChainComplex.mkAux` and `ChainComplex.mkHomAux` needed to use `to_dual existing`, because `to_dual` currently doesn't like recursive definitions that use a match for the recursion. - `mkXIso` and `mk'XIso` and a few theorems didn't have duals before this PR. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #43804 tech debt 159/351 Mathlib/Algebra/Homology/ComplexShape.lean,Mathlib/Algebra/Homology/HomologicalComplex.lean,Mathlib/AlgebraicTopology/AlternatingFaceMapComplex.lean,Mathlib/CategoryTheory/Abelian/Injective/Resolution.lean 4 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-37721
1 day ago
1-38281
1 day ago
1-39240
1 day
0
40940 JovanGerb
author:JovanGerb
feat(CategoryTheory/Comma/StructuredArrow): use `to_dual` This PR generates declarations about `CostructuredArrow` from those about `StructuredArrow` using `to_dual`. This PR deprecates `hom_eq_iff` in favour of `ext_iff`/`hom_ext_iff`. `StructuredArrow.isoMk` and its dependencies are difficult to dualize for `to_dual`, so they are left as-is. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #40503 - [x] depends on: #42861 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) t-category-theory tech debt 157/423 Mathlib/CategoryTheory/Comma/Basic.lean,Mathlib/CategoryTheory/Comma/StructuredArrow/Basic.lean,Mathlib/CategoryTheory/Comma/StructuredArrow/CommaMap.lean,Mathlib/CategoryTheory/Filtered/Final.lean,Mathlib/CategoryTheory/Limits/Indization/ParallelPair.lean,Mathlib/Tactic/Translate/ToDual.lean,Mathlib/Topology/Category/Profinite/Extend.lean 7 9 ['JovanGerb', 'github-actions', 'joelriou', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-35956
1 day ago
1-38162
1 day ago
1-47458
1 day
0
46277 wrenna-robson
author:wrenna-robson
chore(GroupTheory/Perm/Support): split into smaller files Part of the `Equiv.Perm.support` refactor discussed on [Zulip](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/support.20of.20permutations.20on.20Type.20instead.20of.20Fintype/near/640706043): #46119 (move `IsSwap` and pow-apply lemmas) → #46277 (split `Support.lean`) → #46082 (rename to `supportFinset`) → #46126 (`Set`-valued `support`). This prepares for a `Set`-valued definition of `Equiv.Perm.support`, which needs no `Fintype` or `DecidableEq` assumptions. Splitting the file first separates the material that needs no finiteness assumptions from the current `Finset`-valued `support`, so that the later changes stay small and easy to review. Some splits have also been made to reduce unnecessary imports. Split `Mathlib/GroupTheory/Perm/Support.lean` into: * `Support/Basic.lean`: the `set_support_*` lemmas, with no finiteness assumptions; * `Support/Disjoint.lean`: the `Equiv.Perm.Disjoint` API that does not involve `support`; * `Support/Finset/Basic.lean`: the `Finset`-valued `Equiv.Perm.support` and its API; * `Support/Finset/Card.lean`: lemmas about the cardinality of `support`, including `fixed_point_card_lt_of_ne_one`; * `Support/NoncommProd.lean`: lemmas about `Finset.noncommProd` of permutations. This is a pure move: no declarations are renamed or restated. An LLM has been used in the preparation of this PR but as it contains no new content - i.e. it is just a move - I am omitting the LLM-generated tag. - [x] depends on: #46119 tech debt t-group-theory 733/601 Mathlib.lean,Mathlib/Algebra/Order/Rearrangement.lean,Mathlib/GroupTheory/Perm/ClosureSwap.lean,Mathlib/GroupTheory/Perm/Cycle/Factors.lean,Mathlib/GroupTheory/Perm/Finite.lean,Mathlib/GroupTheory/Perm/List.lean,Mathlib/GroupTheory/Perm/Sign.lean,Mathlib/GroupTheory/Perm/Support.lean,Mathlib/GroupTheory/Perm/Support/Basic.lean,Mathlib/GroupTheory/Perm/Support/Disjoint.lean,Mathlib/GroupTheory/Perm/Support/Finset/Basic.lean,Mathlib/GroupTheory/Perm/Support/Finset/Card.lean,Mathlib/GroupTheory/Perm/Support/NoncommProd.lean,Mathlib/LinearAlgebra/Matrix/SemiringInverse.lean 14 3 ['github-actions', 'mathlib-dependent-issues', 'mathlib-merge-conflicts'] nobody
1-4683
1 day ago
1-5909
1 day ago
1-15204
1 day
2
44427 xroblot
author:xroblot
feat(Tactic/NormNum): norm_num extension for Squarefree Add a `norm_num` extension deciding `Squarefree n` for numerals `n` in `ℕ` and `ℤ`. If `n` is not squarefree, the proof uses a witness `a > 1` with `a * a ∣ n`, found with `Nat.minSqFac`. If `n` is squarefree, the proof is a trial division of `n` by the odd numbers `k = 3, 5, 7, …`, keeping the invariant that every prime divisor of the cofactor is at least `k`. This is adapted from the Mathlib 3 extension by Mario Carneiro (mathlib#11666), which was left commented out in `Mathlib.Data.Nat.Squarefree` during the port. This commented-out code is removed, and the corresponding tests are restored. As for the `Nat.Prime` extension, the proof is a certificate rather than a kernel evaluation of `Nat.minSqFac` via `Nat.squarefree_iff_minSqFac`. The certificate is also faster to check, but, as for `Nat.Prime`, large numbers need a higher `maxRecDepth`. **Note**. I have read and checked the ordinary Lean statements and their proofs, but I am not familiar with metaprogramming, so I cannot really vouch for the meta code itself, which was written with the help of an LLM. A review by someone who is comfortable with `norm_num` extensions would be very welcome. Created with Claude Code 🤖 --- tech debt t-meta LLM-generated 198/204 Mathlib.lean,Mathlib/Data/Nat/Squarefree.lean,Mathlib/Tactic.lean,Mathlib/Tactic/NormNum/Squarefree.lean,MathlibTest/Tactic/NormNum/Ext.lean 5 2 ['github-actions', 'mathlib-merge-conflicts'] nobody
1-4414
1 day ago
10-20861
10 days ago
49-7250
49 days
0
45300 xroblot
author:xroblot
refactor(RingTheory/Ideal): generalize some absNorm lemmas and move primesEquiv This is the clean-up part of #42567, extracted so that the summability work can build on it. Two divisibility and positivity results about the absolute norm of an ideal are generalized from `ℤ` to a Dedekind domain, and from prime ideals to proper ideals, with the earlier versions deprecated. The equivalence between the height-one prime ideals of the integral closure of `ℤ` in `ℚ` and the prime numbers is moved to the Dedekind domain files, where it belongs, and redefined through the absolute norm rather than through a generator of the corresponding ideal of `ℤ`. It now assumes less, and the auxiliary API it used to be built from is deprecated without replacement. Finally, the equivalence between the height-one spectra of two isomorphic rings is reworked so that the surjectivity proofs have the expected type, which removes the need for a `backward.isDefEq` option. The mathematics and design are mine. Claude Code was used as a coding assistant and for the housekeeping around this PR. 🤖 tech debt 134/72 Mathlib/NumberTheory/NumberField/Completion/FinitePlace.lean,Mathlib/NumberTheory/Padics/HeightOneSpectrum.lean,Mathlib/RingTheory/DedekindDomain/Ideal/Lemmas.lean,Mathlib/RingTheory/Ideal/Int.lean,Mathlib/RingTheory/Ideal/Norm/AbsNorm.lean 5 9 ['github-actions', 'mathlib-merge-conflicts', 'tb65536', 'xroblot'] nobody
1-4374
1 day ago
3-7679
3 days ago
24-67471
24 days
1
45709 YaelDillies
author:YaelDillies
chore(Algebra/Order): make `Nonneg` a structure The goal is to eventually make `NNRat` and `NNReal` `abbrev`s for `Nonneg Rat` and `Nonneg Real`, and deduplicate their API. This is currently not possible due to prohibitive slowdowns when making their definition in terms of `Subtype` visible to automation. Generated by Claude Sonnet in many rounds of review by myself. Assisted-by: Claude Sonnet 5.5 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt t-order large-import LLM-generated
label:t-algebra$
766/354 Archive/Wiedijk100Theorems/AreaOfACircle.lean,Mathlib.lean,Mathlib/Algebra/Field/Rat.lean,Mathlib/Algebra/Order/Nonneg/Basic.lean,Mathlib/Algebra/Order/Nonneg/Defs.lean,Mathlib/Algebra/Order/Nonneg/Field.lean,Mathlib/Algebra/Order/Nonneg/Floor.lean,Mathlib/Algebra/Order/Nonneg/Interval.lean,Mathlib/Algebra/Order/Nonneg/Lattice.lean,Mathlib/Algebra/Order/Nonneg/Order.lean,Mathlib/Algebra/Order/Nonneg/Ring.lean,Mathlib/Analysis/Analytic/Composition.lean,Mathlib/Analysis/BoxIntegral/Integrability.lean,Mathlib/Analysis/CStarAlgebra/Basic.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Isometric.lean,Mathlib/Analysis/CStarAlgebra/ContinuousFunctionalCalculus/Order.lean,Mathlib/Analysis/CStarAlgebra/GelfandDuality.lean,Mathlib/Analysis/CStarAlgebra/Hom.lean,Mathlib/Analysis/CStarAlgebra/Matrix.lean,Mathlib/Analysis/CStarAlgebra/Multiplier.lean,Mathlib/Analysis/CStarAlgebra/Unitization.lean,Mathlib/Analysis/Complex/Basic.lean,Mathlib/Analysis/Complex/CauchyIntegral.lean,Mathlib/Analysis/Complex/Norm.lean,Mathlib/Analysis/Complex/OperatorNorm.lean,Mathlib/Analysis/Complex/UpperHalfPlane/Measure.lean,Mathlib/Analysis/ConstantSpeed.lean,Mathlib/Analysis/Convex/Cone/Closure.lean,Mathlib/Analysis/Convex/Segment.lean,Mathlib/Analysis/Convex/SpecificFunctions/Pow.lean,Mathlib/Analysis/InnerProductSpace/Basic.lean,Mathlib/Analysis/LocallyConvex/Asymptotics.lean,Mathlib/Analysis/Matrix/Normed.lean,Mathlib/Analysis/MeanInequalities.lean,Mathlib/Analysis/Normed/Algebra/Spectrum.lean,Mathlib/Analysis/Normed/Algebra/UnitizationL1.lean,Mathlib/Analysis/Normed/Field/Basic.lean,Mathlib/Analysis/Normed/Group/Constructions.lean,Mathlib/Analysis/Normed/Group/Continuity.lean,Mathlib/Analysis/Normed/Group/Hom.lean,Mathlib/Analysis/Normed/Group/Uniform.lean,Mathlib/Analysis/Normed/Lp/lpHolder.lean,Mathlib/Analysis/Normed/Module/Basic.lean,Mathlib/Analysis/Normed/Operator/Basic.lean,Mathlib/Analysis/Normed/Operator/Mul.lean,Mathlib/Analysis/Normed/Operator/NNNorm.lean,Mathlib/Analysis/Normed/Operator/NormedSpace.lean,Mathlib/Analysis/Normed/Operator/Prod.lean,Mathlib/Analysis/ODE/PicardLindelof.lean,Mathlib/Analysis/Quaternion.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Basic/NNReal/Basic.lean,Mathlib/Basic/NNReal/Defs.lean,Mathlib/Data/NNRat/Defs.lean,Mathlib/Data/Rat/Cast/Lemmas.lean,Mathlib/Data/Rat/Init.lean,Mathlib/FieldTheory/IntermediateField/Basic.lean,Mathlib/Geometry/Convex/Cone/Dual.lean,Mathlib/Geometry/Convex/Cone/Pointed.lean,Mathlib/MeasureTheory/Constructions/BorelSpace/Basic.lean,Mathlib/MeasureTheory/Function/ConditionalExpectation/Real.lean,Mathlib/MeasureTheory/Function/Jacobian.lean,Mathlib/MeasureTheory/Function/SimpleFuncDenseLp.lean,Mathlib/MeasureTheory/Function/SpecialFunctions/Basic.lean,Mathlib/MeasureTheory/Function/UniformIntegrable.lean,Mathlib/MeasureTheory/Integral/Bochner/Basic.lean,Mathlib/MeasureTheory/Integral/SetToL1/L1.lean,Mathlib/MeasureTheory/MeasurableSpace/Constructions.lean,Mathlib/MeasureTheory/Measure/Prokhorov.lean,Mathlib/MeasureTheory/Measure/Stieltjes.lean,Mathlib/NumberTheory/Modular.lean,Mathlib/NumberTheory/NumberField/CanonicalEmbedding/Basic.lean,Mathlib/Probability/Moments/IntegrableExpMul.lean,Mathlib/Probability/Moments/Tilted.lean,Mathlib/RingTheory/RootsOfUnity/Complex.lean,Mathlib/RingTheory/Valuation/ValuationSubring.lean,Mathlib/Topology/Algebra/Field.lean,Mathlib/Topology/Algebra/MetricSpace/Lipschitz.lean,Mathlib/Topology/Algebra/Order/Module.lean,Mathlib/Topology/Algebra/Ring/Real.lean,Mathlib/Topology/Bornology/Real.lean,Mathlib/Topology/ContinuousMap/Bounded/Basic.lean,Mathlib/Topology/ContinuousMap/Bounded/Normed.lean,Mathlib/Topology/Instances/NNReal/Lemmas.lean,Mathlib/Topology/Instances/Rat.lean,Mathlib/Topology/MetricSpace/Basic.lean,Mathlib/Topology/MetricSpace/Cauchy.lean,Mathlib/Topology/MetricSpace/HausdorffDimension.lean,Mathlib/Topology/MetricSpace/Lipschitz.lean,Mathlib/Topology/MetricSpace/ProperSpace/Real.lean,Mathlib/Topology/MetricSpace/Pseudo/Constructions.lean,Mathlib/Topology/MetricSpace/Thickening.lean,Mathlib/Topology/Order/Nonneg.lean,Mathlib/Topology/UniformSpace/Real.lean 95 7 ['github-actions', 'mathlib-merge-conflicts'] nobody
0-83210
23 hours ago
0-85253
23 hours ago
12-38802
12 days
0
45861 grunweg
author:grunweg
chore: rename three lemmas involving the name some_eq_coe Reference the actual coercion being used. The ENNReal renames deserve a careful look. Found using the linter in #45229: among the cases of misnamed coercion lemmas using WithTop.some, these are some more interesting cases. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-order maintainer-merge 34/28 Mathlib/Algebra/Order/Monoid/Unbundled/WithTop.lean,Mathlib/Analysis/BoxIntegral/Partition/Additive.lean,Mathlib/Analysis/BoxIntegral/Partition/Basic.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/Data/List/MinMax.lean,Mathlib/Order/WithBot.lean,Mathlib/Tactic/Echelon/Reflection.lean,Mathlib/Tactic/Inclusion/Extension/Interval/Basic.lean,Mathlib/Topology/Algebra/Ring/Real.lean,scripts/nolints_prime_decls.txt 11 11 ['YaelDillies', 'github-actions', 'grunweg', 'themathqueen'] nobody
0-80328
22 hours ago
11-84579
11 days ago
11-84743
11 days
0
45826 Parcly-Taxel
author:Parcly-Taxel
refactor: `Lex/Colex` as one-field structures Redefine ```lean structure Lex (α : Sort*) where /-- Equip a type with its lexicographic order. -/ toLex :: /-- The underlying element -/ ofLex : α ``` and similarly for `Colex`. Several rounds of Codex were used to repair some (but not all) of the proofs. t-order tech debt LLM-generated 1184/1076 Counterexamples/MapFloor.lean,Counterexamples/SeparableNotSecondCountable.lean,Counterexamples/ZeroDivisorsInAddMonoidAlgebras.lean,Mathlib/Algebra/CharP/Synonym.lean,Mathlib/Algebra/Field/Basic.lean,Mathlib/Algebra/MvPolynomial/SchwartzZippel.lean,Mathlib/Algebra/MvPolynomial/Variables.lean,Mathlib/Algebra/Order/Group/Action/Synonym.lean,Mathlib/Algebra/Order/Group/Equiv.lean,Mathlib/Algebra/Order/Group/PiLex.lean,Mathlib/Algebra/Order/Group/Synonym.lean,Mathlib/Algebra/Order/GroupWithZero/Action/Synonym.lean,Mathlib/Algebra/Order/GroupWithZero/Lex.lean,Mathlib/Algebra/Order/GroupWithZero/Synonym.lean,Mathlib/Algebra/Order/Module/Equiv.lean,Mathlib/Algebra/Order/Module/HahnEmbedding.lean,Mathlib/Algebra/Order/Module/Synonym.lean,Mathlib/Algebra/Order/Monoid/Lex.lean,Mathlib/Algebra/Order/Rearrangement.lean,Mathlib/Algebra/Order/Ring/Synonym.lean,Mathlib/Algebra/Vertex/HVertexOperator.lean,Mathlib/Analysis/Calculus/ContDiffHolder/Pointwise.lean,Mathlib/Combinatorics/Colex.lean,Mathlib/Combinatorics/SetFamily/KruskalKatona.lean,Mathlib/Data/DFinsupp/Lex.lean,Mathlib/Data/DFinsupp/WellFounded.lean,Mathlib/Data/Fin/Tuple/BubbleSortInduction.lean,Mathlib/Data/Fin/Tuple/Sort.lean,Mathlib/Data/Finsupp/Lex.lean,Mathlib/Data/Finsupp/MonomialOrder.lean,Mathlib/Data/Finsupp/MonomialOrder/DegLex.lean,Mathlib/Data/Finsupp/WellFounded.lean,Mathlib/Data/Fintype/Card.lean,Mathlib/Data/Fintype/Defs.lean,Mathlib/Data/Sum/Interval.lean,Mathlib/Order/CompleteLattice/PiLex.lean,Mathlib/Order/Extension/Well.lean,Mathlib/Order/Hom/Lex.lean,Mathlib/Order/Interval/Finset/Gaps.lean,Mathlib/Order/Interval/Lex.lean,Mathlib/Order/Lex.lean,Mathlib/Order/PSigma.lean,Mathlib/Order/PiLex.lean,Mathlib/Order/Prod/Lex/Basic.lean,Mathlib/Order/Prod/Lex/Hom.lean,Mathlib/Order/Sigma.lean,Mathlib/Order/Sum/Lattice.lean,Mathlib/Order/Sum/Order.lean,Mathlib/Order/WellFoundedSet.lean,Mathlib/RingTheory/HahnSeries/Basic.lean,Mathlib/RingTheory/HahnSeries/HahnEmbedding.lean,Mathlib/RingTheory/HahnSeries/Lex.lean,Mathlib/RingTheory/MvPolynomial/Symmetric/FundamentalTheorem.lean,Mathlib/RingTheory/MvPowerSeries/LexOrder.lean,Mathlib/RingTheory/Spectrum/Prime/ChevalleyComplexity.lean,Mathlib/SetTheory/Cardinal/Arithmetic.lean,Mathlib/SetTheory/Ordinal/Arithmetic.lean,Mathlib/SetTheory/Ordinal/Basic.lean,Mathlib/Topology/Order/Completion.lean,MathlibTest/NonemptyIntervalLex.lean 60 32 ['Parcly-Taxel', 'github-actions', 'mathlib-merge-conflicts', 'vihdzp'] nobody
0-39395
10 hours ago
4-12062
4 days ago
10-45604
10 days
0
46043 EtienneC30
author:EtienneC30
refactor: make `WithTop` and `WithBot` inductive types Some points to notice: - The order on `WithZero` given by [WithZero.le](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/GroupWithZero/Canonical.html#WithZero.le) is defined through defeq with `WithBot`, which no longer holds. Thus this PR also makes `WithZero` an inductive type and transfers the order through an equivalence passing through `Option`. - In `Mathlib.Order.Hom.WithTopBot` file, I can't make the lemmas generated by `simps!` for `withTop'` and `withBot'` dual to each other, while they are currently. I don't really understand what is going on. Declarations deleted without deprecation: - [WithBot.some_eq_coe](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Order/WithBot.html#WithBot.some_eq_coe), [WithTop.some_eq_coe](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Order/WithBot.html#WithTop.some_eq_coe): those are now syntactic equalities. - [WithTop.mul_coe_eq_bind](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/Ring/WithTop.html#WithTop.mul_coe_eq_bind), [WithBot.mul_coe_eq_bind](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/Ring/WithTop.html#WithBot.mul_coe_eq_bind) - [WithTop.coe_mul_eq_bind](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/Ring/WithTop.html#WithTop.coe_mul_eq_bind), [WithBot.coe_mul_eq_bind](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Order/Ring/WithTop.html#WithBot.coe_mul_eq_bind) - [WithOne.instMonad](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Group/WithOne/Defs.html#WithOne.instMonad), [WithZero.instMonad](https://leanprover-community.github.io/mathlib4_docs/Mathlib/Algebra/Group/WithOne/Defs.html#WithZero.instMonad) Zulip thread: https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/Identity.20equivalence.20between.20WithTop.2FWithBot.20and.20Option/with/639616431 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> large-import tech debt t-order 1133/964 Archive/RiemannStieltjes.lean,Counterexamples/HomogeneousPrimeNotPrime.lean,Mathlib/Algebra/Group/WithOne/Basic.lean,Mathlib/Algebra/Group/WithOne/Defs.lean,Mathlib/Algebra/Group/WithOne/Map.lean,Mathlib/Algebra/GroupWithZero/Range.lean,Mathlib/Algebra/GroupWithZero/WithZero.lean,Mathlib/Algebra/Order/GroupWithZero/Canonical.lean,Mathlib/Algebra/Order/Interval/Basic.lean,Mathlib/Algebra/Order/Monoid/ToMulBot.lean,Mathlib/Algebra/Order/Monoid/Unbundled/WithTop.lean,Mathlib/Algebra/Order/Ring/WithTop.lean,Mathlib/Algebra/Polynomial/BigOperators.lean,Mathlib/Algebra/Polynomial/Degree/Defs.lean,Mathlib/Algebra/Polynomial/Degree/Operations.lean,Mathlib/AlgebraicGeometry/EllipticCurve/Affine/Point.lean,Mathlib/Analysis/BoxIntegral/Box/Basic.lean,Mathlib/Analysis/BoxIntegral/Partition/Additive.lean,Mathlib/Analysis/BoxIntegral/Partition/Basic.lean,Mathlib/Analysis/BoxIntegral/Partition/Split.lean,Mathlib/Analysis/Convex/Combination.lean,Mathlib/Analysis/Convex/Jensen.lean,Mathlib/Analysis/Meromorphic/Order.lean,Mathlib/Analysis/SpecialFunctions/Pow/NNReal.lean,Mathlib/Basic/Countable/Basic.lean,Mathlib/Basic/ENNReal/Basic.lean,Mathlib/CategoryTheory/Presentable/CardinalDirectedPoset.lean,Mathlib/Combinatorics/SetFamily/AhlswedeZhang.lean,Mathlib/Data/ENat/Defs.lean,Mathlib/Data/ENat/Pow.lean,Mathlib/Data/Finset/Lattice/Fold.lean,Mathlib/Data/Finset/Lattice/Union.lean,Mathlib/Data/Finset/Max.lean,Mathlib/Data/Finset/NAry.lean,Mathlib/Data/Fintype/WithTopBot.lean,Mathlib/Data/Int/WithZero.lean,Mathlib/Data/List/MinMax.lean,Mathlib/Data/Ordmap/Invariants.lean,Mathlib/Data/Ordmap/Ordset.lean,Mathlib/GroupTheory/ArchimedeanDensely.lean,Mathlib/MeasureTheory/Constructions/BorelSpace/Real.lean,Mathlib/MeasureTheory/Constructions/BorelSpace/WithTop.lean,Mathlib/MeasureTheory/Group/Measure.lean,Mathlib/MeasureTheory/MeasurableSpace/Constructions.lean,Mathlib/Order/Category/BddLat.lean,Mathlib/Order/ConditionallyCompleteLattice/WithTop.lean,Mathlib/Order/Hom/WithTopBot.lean,Mathlib/Order/Interval/Basic.lean,Mathlib/Order/Interval/Finset/Defs.lean,Mathlib/Order/KrullDimension.lean,Mathlib/Order/Set.lean,Mathlib/Order/SuccPred/Basic.lean,Mathlib/Order/Sum/Order.lean,Mathlib/Order/TypeTags.lean,Mathlib/Order/WithBot.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Completion.lean,Mathlib/RingTheory/DedekindDomain/AdicValuation/Valuation.lean,Mathlib/RingTheory/DiscreteValuationRing/Basic.lean,Mathlib/RingTheory/MvPowerSeries/LexOrder.lean,Mathlib/RingTheory/OrderOfVanishing/Basic.lean,Mathlib/RingTheory/OrderOfVanishing/Noetherian.lean,Mathlib/RingTheory/Polynomial/Resultant/Basic.lean,Mathlib/RingTheory/UniqueFactorizationDomain/FactorSet.lean,Mathlib/RingTheory/Valuation/Discrete/IsDiscreteValuationRing.lean,Mathlib/Tactic/Echelon/Reflection.lean,Mathlib/Tactic/Inclusion/Extension/Interval/Basic.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/BinarySplit.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Exp.lean,Mathlib/Tactic/Inclusion/Extension/IntervalDyadicReal/Log.lean,Mathlib/Tactic/Inclusion/Extension/IntervalInt/BinarySplit.lean,Mathlib/Topology/Algebra/Valued/WithVal.lean,Mathlib/Topology/Compactification/OnePoint/Basic.lean,Mathlib/Topology/EMetricSpace/Defs.lean,Mathlib/Topology/EMetricSpace/Weak.lean,Mathlib/Topology/Instances/ENNReal/Lemmas.lean,Mathlib/Topology/Order/Lattice.lean,MathlibTest/DifferentialGeometry/Notation/Basic.lean 77 13 ['EtienneC30', 'eric-wieser', 'github-actions', 'mathlib-merge-conflicts', 'plp127', 'vihdzp'] nobody
0-15329
4 hours ago
0-17091
4 hours ago
3-62283
3 days
0
46266 EtienneC30
author:EtienneC30
refactor: remove the coercion from `SemilinearMapClass` to `SemilinearMap` Deals with `SemilinearMapClass` in #31365. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> - [x] depends on: #45954 t-algebra tech debt
label:t-algebra$
191/152 Mathlib/Algebra/Algebra/Bilinear.lean,Mathlib/Algebra/Algebra/Equiv.lean,Mathlib/Algebra/Algebra/Hom.lean,Mathlib/Algebra/Algebra/NonUnitalHom.lean,Mathlib/Algebra/Algebra/Subalgebra/Basic.lean,Mathlib/Algebra/Algebra/Subalgebra/Tower.lean,Mathlib/Algebra/Category/CoalgCat/Basic.lean,Mathlib/Algebra/Category/CoalgCat/ComonEquivalence.lean,Mathlib/Algebra/Module/Equiv/Defs.lean,Mathlib/Algebra/Module/LinearMap/Defs.lean,Mathlib/Algebra/Order/Module/PositiveLinearMap.lean,Mathlib/Algebra/Polynomial/Taylor.lean,Mathlib/Algebra/Star/LinearMap.lean,Mathlib/Algebra/Star/Subalgebra.lean,Mathlib/Analysis/CStarAlgebra/CStarMatrix.lean,Mathlib/Analysis/CStarAlgebra/CompletelyPositiveMap.lean,Mathlib/Analysis/CStarAlgebra/PositiveLinearMap.lean,Mathlib/Analysis/Convex/LinearIsometry.lean,Mathlib/Analysis/InnerProductSpace/Orthogonal.lean,Mathlib/Analysis/InnerProductSpace/Projection/Basic.lean,Mathlib/Analysis/Matrix/HermitianFunctionalCalculus.lean,Mathlib/Analysis/Normed/Algebra/Spectrum.lean,Mathlib/Analysis/Normed/Operator/Basic.lean,Mathlib/Analysis/Normed/Operator/LinearIsometry.lean,Mathlib/Analysis/SpecialFunctions/ContinuousFunctionalCalculus/PosPart/Basic.lean,Mathlib/Data/Matrix/Basic.lean,Mathlib/FieldTheory/Minpoly/Field.lean,Mathlib/FieldTheory/NormalizedTrace.lean,Mathlib/LinearAlgebra/LinearDisjoint.lean,Mathlib/LinearAlgebra/Matrix/Kronecker.lean,Mathlib/LinearAlgebra/SymmetricAlgebra/Basic.lean,Mathlib/LinearAlgebra/TensorProduct/Submodule.lean,Mathlib/LinearAlgebra/Trace.lean,Mathlib/NumberTheory/Modular.lean,Mathlib/RepresentationTheory/Coinvariants.lean,Mathlib/RepresentationTheory/Invariants.lean,Mathlib/RepresentationTheory/Rep/Res.lean,Mathlib/RingTheory/Adjoin/Basic.lean,Mathlib/RingTheory/Bialgebra/Basic.lean,Mathlib/RingTheory/Bialgebra/Hom.lean,Mathlib/RingTheory/Bialgebra/TensorProduct.lean,Mathlib/RingTheory/Coalgebra/Basic.lean,Mathlib/RingTheory/Coalgebra/Convolution.lean,Mathlib/RingTheory/Coalgebra/Equiv.lean,Mathlib/RingTheory/Coalgebra/Hom.lean,Mathlib/RingTheory/Coalgebra/TensorProduct.lean,Mathlib/RingTheory/DedekindDomain/LinearDisjoint.lean,Mathlib/RingTheory/Flat/Equalizer.lean,Mathlib/RingTheory/GradedAlgebra/AlgHom.lean,Mathlib/RingTheory/GradedAlgebra/TensorProduct.lean,Mathlib/RingTheory/LocalProperties/Exactness.lean,Mathlib/RingTheory/LocalRing/Quotient.lean,Mathlib/RingTheory/Localization/BaseChange.lean,Mathlib/RingTheory/Localization/Module.lean,Mathlib/RingTheory/TensorProduct/Basic.lean,Mathlib/RingTheory/TensorProduct/Maps.lean 56 11 ['EtienneC30', 'github-actions', 'mathlib-dependent-issues', 'mathlib-splicebot', 'themathqueen'] nobody
0-1833
30 minutes ago
0-8429
2 hours ago
0-34575
9 hours
0
46344 EtienneC30
author:EtienneC30
refactor: rename `SemilinearEquivClass.semilinearEquiv` to `LinearEquiv.ofClass` The namespace is `LinearEquiv` to allow for anonymous dot notation. --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> t-algebra tech debt maintainer-merge
label:t-algebra$
10/6 Mathlib/Algebra/Module/Equiv/Defs.lean,Mathlib/NumberTheory/NumberField/Basic.lean,Mathlib/RingTheory/Coalgebra/Equiv.lean 3 3 ['github-actions', 'themathqueen'] nobody
0-477
7 minutes ago
0-2632
42 minutes ago
0-2577
42 minutes
0
46345 EtienneC30
author:EtienneC30
refactor: remove the coercion from `BialgEquivClass` Part of #31365 --- <!-- Your PR title will become the first line of the commit message. In this box, the text above the `---` (if not empty) will be appended to the commit message, and can be used to give additional context or details. Please leave a blank newline before the `---`, otherwise GitHub will format the text above it as a title. For details on the "pull request lifecycle" in mathlib, please see: https://leanprover-community.github.io/contribute/index.html In particular, note that most reviewers will only notice your PR if it passes the continuous integration checks. Please ask for help on https://leanprover.zulipchat.com if needed. When merging, all the commits will be squashed into a single commit listing all co-authors. Co-authors in the squash commit are gathered from two sources: First, all authors of commits to this PR branch are included. Thus, one way to add co-authors is to include at least one commit authored by each co-author among the commits in the pull request. If necessary, you may create empty commits to indicate co-authorship, using commands like so: git commit --author="Author Name <author@email.com>" --allow-empty -m "add Author Name as coauthor" Second, co-authors can also be listed in lines at the very bottom of the commit message (that is, directly before the `---`) using the following format: Co-authored-by: Author Name <author@email.com> If you are moving or deleting declarations, please include these lines at the bottom of the commit message (before the `---`, and also before any "Co-authored-by" lines) using the following format: Moves: - Vector.* -> List.Vector.* - ... Deletions: - Nat.bit1_add_bit1 - ... Any other comments you want to keep out of the PR commit should go below the `---`, and placed outside this HTML comment, or else they will be invisible to reviewers. If this PR depends on other PRs, please list them below this comment, using the following format: - [ ] depends on: #abc [optional extra text] - [ ] depends on: #xyz [optional extra text] --> tech debt t-ring-theory 2/5 Mathlib/RingTheory/Bialgebra/Equiv.lean 1 1 ['github-actions', 'themathqueen'] nobody
0-430
7 minutes ago
0-1491
23 minutes ago
0-1436
23 minutes
0

This page collects anonymous visit counts for usage reporting (no cookies, no IP addresses stored). See the Mathlib Initiative privacy policy.