-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Merged by Bors] - chore(Mathlib/Tactic/ToAdditive/Frontend): isolate the to_additive
attribute implementation in a new file Tactic.ToAdditive.Frontend
(2/2)
#14750
Conversation
PR summary 11a78505f3Import 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> |
@[to_additive]
attrs in Mathlib.Init.ZeroOne
attribute @[to_additive]
commands in Mathlib.Init.ZeroOne
Dear @Komyyy I still don't understand why the file |
@jcommelin |
I think you can do the "isolation" part before moving the commands in |
attribute @[to_additive]
commands in Mathlib.Init.ZeroOne
to_additive
attribute implementation in a new file Tactic.ToAdditive.Frontend
@jcommelin |
Thanks. This is now an atomic change. bors d+ |
✌️ Komyyy can now approve this pull request. To approve and merge a pull request, simply reply with |
bors r+ |
…attribute implementation in a new file `Tactic.ToAdditive.Frontend` (#14750) This PR is needed to move `attribute [to_additive]` commands in `Mathlib.Init.ZeroOne`.
bors r- |
Canceled. |
to_additive
attribute implementation in a new file Tactic.ToAdditive.Frontend
to_additive
attribute implementation in a new file Tactic.ToAdditive.Frontend
(2/2)
This PR/issue depends on: |
f231146
to
11a7850
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maintainer merge
🚀 Pull request has been placed on the maintainer queue by YaelDillies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 🎉
bors merge
…attribute implementation in a new file `Tactic.ToAdditive.Frontend` (2/2) (#14750) Ideally, we want to move the `attribute [to_additive]` commands in `Init.ZeroOne` into `Tactic.ToAdditive` without any other changes. However, the `to_additive` attribute is initialized in the file and cannot be included in the same file. So it would be necessary to isolate the original `to_additive` attribute implementation in a new file `Tactic.ToAdditive.Frontend`, and create an new file `Tactic.ToAdditive` as a placeholder for the `attribute [to_additive]` commands in `Init.ZeroOne`. But if we put these two changes in the same PR, git cannot recognizes that `Tactic.ToAdditive` is renamed, so we split the PR.
Pull request successfully merged into master. Build succeeded: |
to_additive
attribute implementation in a new file Tactic.ToAdditive.Frontend
(2/2)to_additive
attribute implementation in a new file Tactic.ToAdditive.Frontend
(2/2)
Ideally, we want to move the
attribute [to_additive]
commands inInit.ZeroOne
intoTactic.ToAdditive
without any other changes.However, the
to_additive
attribute is initialized in the file and cannot be included in the same file.So it would be necessary to isolate the original
to_additive
attribute implementation in a new fileTactic.ToAdditive.Frontend
, and create an new fileTactic.ToAdditive
as a placeholder for theattribute [to_additive]
commands inInit.ZeroOne
.But if we put these two changes in the same PR, git cannot recognizes that
Tactic.ToAdditive
is renamed, so we split the PR.to_additive
attribute implementation in a new fileTactic.ToAdditive.Frontend
(1/2) #14816