[Merged by Bors] - chore(Bicategory/Strict): move around files related to strict bicategories#30134
Closed
callesonne wants to merge 4 commits intoleanprover-community:masterfrom
Closed
[Merged by Bors] - chore(Bicategory/Strict): move around files related to strict bicategories#30134callesonne wants to merge 4 commits intoleanprover-community:masterfrom
callesonne wants to merge 4 commits intoleanprover-community:masterfrom
Conversation
This was referenced Oct 2, 2025
PR summary 3a826f51e1Import changes for modified filesNo significant changes to the import graph Import changes for all files
Declarations diffNo declarations were harmed in the making of this PR! 🐙 You can run this locally as follows## summary with just the declaration names:
./scripts/declarations_diff.sh <optional_commit>
## more verbose report:
./scripts/declarations_diff.sh long <optional_commit>The doc-module for No changes to technical debt.You can run this locally as
note: file note: file |
Contributor
|
Thanks! |
1 task
mathlib-bors bot
pushed a commit
that referenced
this pull request
Oct 2, 2025
…ories (#30134) This PR moves around some files in preparation for #30132, which introduces the notion of "strict" pseudofunctors. I want to add this new definition to the file `Bicategory/Functor/Strict.lean`, which already contains API for pseudofunctors *between* strict bicategories. My addition is about strict pseudofunctors between arbitrary bicategories. To make the distinction more clear I have decided to rearrange the file structure slightly. First I created a folder `Bicategory/Strict/` to which I move the file `Bicategory/Strict.lean` (as `Bicategory/Strict/Basic.lean`). Then I move the current file `Bicategory/Functor/Strict.lean` to `Bicategory/Strict/Pseudofunctor.lean` as I believe this fits better with the contents of the file. Then the name `Bicategory/Functor/Strict.lean` is freed up to contain the notion of a "strict" pseudofunctor in the upcoming #30132.
Contributor
|
Pull request successfully merged into master. Build succeeded: |
mitchell-horner
pushed a commit
to mitchell-horner/mathlib4
that referenced
this pull request
Oct 6, 2025
…ories (leanprover-community#30134) This PR moves around some files in preparation for leanprover-community#30132, which introduces the notion of "strict" pseudofunctors. I want to add this new definition to the file `Bicategory/Functor/Strict.lean`, which already contains API for pseudofunctors *between* strict bicategories. My addition is about strict pseudofunctors between arbitrary bicategories. To make the distinction more clear I have decided to rearrange the file structure slightly. First I created a folder `Bicategory/Strict/` to which I move the file `Bicategory/Strict.lean` (as `Bicategory/Strict/Basic.lean`). Then I move the current file `Bicategory/Functor/Strict.lean` to `Bicategory/Strict/Pseudofunctor.lean` as I believe this fits better with the contents of the file. Then the name `Bicategory/Functor/Strict.lean` is freed up to contain the notion of a "strict" pseudofunctor in the upcoming leanprover-community#30132.
BeibeiX0
pushed a commit
to BeibeiX0/mathlib4
that referenced
this pull request
Nov 7, 2025
…ories (leanprover-community#30134) This PR moves around some files in preparation for leanprover-community#30132, which introduces the notion of "strict" pseudofunctors. I want to add this new definition to the file `Bicategory/Functor/Strict.lean`, which already contains API for pseudofunctors *between* strict bicategories. My addition is about strict pseudofunctors between arbitrary bicategories. To make the distinction more clear I have decided to rearrange the file structure slightly. First I created a folder `Bicategory/Strict/` to which I move the file `Bicategory/Strict.lean` (as `Bicategory/Strict/Basic.lean`). Then I move the current file `Bicategory/Functor/Strict.lean` to `Bicategory/Strict/Pseudofunctor.lean` as I believe this fits better with the contents of the file. Then the name `Bicategory/Functor/Strict.lean` is freed up to contain the notion of a "strict" pseudofunctor in the upcoming leanprover-community#30132.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR moves around some files in preparation for #30132, which introduces the notion of "strict" pseudofunctors.
I want to add this new definition to the file
Bicategory/Functor/Strict.lean, which already contains API for pseudofunctors between strict bicategories. My addition is about strict pseudofunctors between arbitrary bicategories.To make the distinction more clear I have decided to rearrange the file structure slightly. First I created a folder
Bicategory/Strict/to which I move the fileBicategory/Strict.lean(asBicategory/Strict/Basic.lean). Then I move the current fileBicategory/Functor/Strict.leantoBicategory/Strict/Pseudofunctor.leanas I believe this fits better with the contents of the file. Then the nameBicategory/Functor/Strict.leanis freed up to contain the notion of a "strict" pseudofunctor in the upcoming #30132.