chore: use @[inherit_doc] more and remove some nolints#11905
chore: use @[inherit_doc] more and remove some nolints#11905
Conversation
378de14 to
3bf0631
Compare
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. |
Remove mathport names of these declarations.
[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.
|
This PR/issue depends on:
|
j-loreaux
left a comment
There was a problem hiding this comment.
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] |
There was a problem hiding this comment.
Should we really be putting this on local notation?
There was a problem hiding this comment.
I've filed #11942 with more such changes :-) I'm doing this for ~two reasons:
- Why not, does it hurt?
1'. These changes remove some nolint entries, so something somewhere cares about this. - 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] |
[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.
[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.
[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.
[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.
mathport name: <expression>lines #11928