Skip to content

chore: use @[inherit_doc] more and remove some nolints#11905

Closed
grunweg wants to merge 4 commits intomasterfrom
MR-inherit-doc
Closed

chore: use @[inherit_doc] more and remove some nolints#11905
grunweg wants to merge 4 commits intomasterfrom
MR-inherit-doc

Conversation

@grunweg
Copy link
Copy Markdown
Contributor

@grunweg grunweg commented Apr 4, 2024

@grunweg grunweg added awaiting-review awaiting-CI This PR does not pass CI yet. This label is automatically removed once it does. labels Apr 4, 2024
@grunweg grunweg force-pushed the MR-inherit-doc branch 2 times, most recently from 378de14 to 3bf0631 Compare April 4, 2024 22:08
@ghost ghost added merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) and removed merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) labels Apr 4, 2024
@github-actions github-actions bot removed the awaiting-CI This PR does not pass CI yet. This label is automatically removed once it does. label Apr 4, 2024
@digama0
Copy link
Copy Markdown
Member

digama0 commented Apr 5, 2024

Should the "mathport expr" lines be kept or can they be removed?

These were actually never meant to go in the file, they are basically debugging information and only useful on significantly broken mathport files. You can safely remove all of them.

@ghost ghost added the merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) label Apr 5, 2024
@grunweg
Copy link
Copy Markdown
Contributor Author

grunweg commented Apr 5, 2024

Split out #11921 and #11922 with the "new documentation" changes.

@ghost ghost removed the merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) label Apr 5, 2024
mathlib-bors bot pushed a commit that referenced this pull request Apr 5, 2024
…11907)

and tweak formatting of some doc comments

Extracted from #11905.
@ghost ghost added the merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) label Apr 5, 2024
Remove mathport names of these declarations.
@ghost ghost removed the merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) label Apr 5, 2024
@ghost ghost added the blocked-by-other-PR This PR depends on another PR (this label is automatically managed by a bot) label Apr 5, 2024
mathlib-bors bot pushed a commit that referenced this pull request Apr 6, 2024
[Quoting](#11905 (comment)) `@digama0`:
> These were actually never meant to go in the file, they are basically debugging information and only useful on significantly broken mathport files. You can safely remove all of them.
@ghost ghost removed the blocked-by-other-PR This PR depends on another PR (this label is automatically managed by a bot) label Apr 6, 2024
@ghost
Copy link
Copy Markdown

ghost commented Apr 6, 2024

This PR/issue depends on:

@ghost ghost added the merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) label Apr 6, 2024
@ghost ghost added merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) and removed merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) labels Apr 6, 2024
@ghost ghost removed the merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) label Apr 6, 2024
Copy link
Copy Markdown
Contributor

@j-loreaux j-loreaux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! This is a chore that definitely needed doing. Admittedly, what I'm about to ask is a nontrivial amount of work, but it would be really nice if you could check all the docstrings for the things that are referenced and make sure they mention what the notation is. That way the user can be aware in both directions.

Zsqrtd (-1)
#align gaussian_int GaussianInt

@[inherit_doc]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we really be putting this on local notation?

Copy link
Copy Markdown
Contributor Author

@grunweg grunweg Apr 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've filed #11942 with more such changes :-) I'm doing this for ~two reasons:

  1. Why not, does it hurt?
    1'. These changes remove some nolint entries, so something somewhere cares about this.
  2. If I encounter some local notation in the middle of a file, that might not be obvious to me --- so showing some information hover seems useful.
    As this is local notation, there is no sense in updating the referenced declaration's docstring. (If there is, I'd argue this notation should be scoped, but not local.) Hence, a bare inherit_doc feels appropriate.

I'm happy to move these changes to the other PR if you prefer.


open scoped ComplexConjugate

@[inherit_doc]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same comment

@j-loreaux j-loreaux added awaiting-author A reviewer has asked the author a question or requested changes. documentation Improvements or additions to documentation and removed awaiting-review labels Apr 7, 2024
xgenereux pushed a commit that referenced this pull request Apr 15, 2024
…11907)

and tweak formatting of some doc comments

Extracted from #11905.
xgenereux pushed a commit that referenced this pull request Apr 15, 2024
[Quoting](#11905 (comment)) `@digama0`:
> These were actually never meant to go in the file, they are basically debugging information and only useful on significantly broken mathport files. You can safely remove all of them.
@ghost ghost added the merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot) label Apr 15, 2024
atarnoam pushed a commit that referenced this pull request Apr 16, 2024
…11907)

and tweak formatting of some doc comments

Extracted from #11905.
atarnoam pushed a commit that referenced this pull request Apr 16, 2024
[Quoting](#11905 (comment)) `@digama0`:
> These were actually never meant to go in the file, they are basically debugging information and only useful on significantly broken mathport files. You can safely remove all of them.
uniwuni pushed a commit that referenced this pull request Apr 19, 2024
…11907)

and tweak formatting of some doc comments

Extracted from #11905.
uniwuni pushed a commit that referenced this pull request Apr 19, 2024
[Quoting](#11905 (comment)) `@digama0`:
> These were actually never meant to go in the file, they are basically debugging information and only useful on significantly broken mathport files. You can safely remove all of them.
callesonne pushed a commit that referenced this pull request Apr 22, 2024
…11907)

and tweak formatting of some doc comments

Extracted from #11905.
callesonne pushed a commit that referenced this pull request Apr 22, 2024
[Quoting](#11905 (comment)) `@digama0`:
> These were actually never meant to go in the file, they are basically debugging information and only useful on significantly broken mathport files. You can safely remove all of them.
@grunweg
Copy link
Copy Markdown
Contributor Author

grunweg commented Jan 12, 2025

Closing: #20376 has done most of this; #20684 and #20683 perform similar work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-author A reviewer has asked the author a question or requested changes. documentation Improvements or additions to documentation merge-conflict The PR has a merge conflict with master, and needs manual merging. (this label is managed by a bot)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants