-
Notifications
You must be signed in to change notification settings - Fork 839
[Merged by Bors] - doc: fix recurring instances of "this files" #30719
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
Conversation
PR summary 0d837987e5Import 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
|
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! LGTM with the changes below fixed.
`β` is T₂ and `𝔖` covers `α` | ||
* `UniformOnFun.tendsto_iff_tendstoUniformlyOn`: | ||
`𝒱(α, β, 𝔖 uβ)` is indeed the uniform structure of `𝔖`-convergence | ||
`𝒱(α, β, 𝔖, uβ)` is indeed the uniform structure of `𝔖`-convergence |
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.
I'd need domain expertise to verify this. Are you absolutely sure this is correct? Otherwise, please split this into a separate PR.
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.
I am pretty sure. The original, 𝒱(α, β, 𝔖 uβ)
never actually shows up elsewhere in this file, whereas 𝒱(α, β, 𝔖, uβ)
shows up 5 times in different docstrings in this file. I can't imagine anything else than this being the intended meaning.
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.
See e.g. the definition of this structure on lines 40-42
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.
If you're still unconvinced I can revert it.
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.
This looks correct to me, but really shouldn't go in this PR. I'm happy to let you off this one time, but mixing a tricky change in with 30 boring changes means a person reviewing the boring stuff will give up at the tricky stuff and leave before finishing, and the person looking for tricky stuff will skip your review because it looks boring.
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.
Just wanted to say that I'm grateful, not for you letting me off the hook, @eric-wieser, but for you so clearly explaining why this mixing is a bad idea. This psychological point is something that makes perfect sense when you point it out, but that I hadn't thought properly about. I guess part of the problem is that I don't have a well-developed sense of what is and isn't trivial. But I'll keep this in mind.
Please try to resist the urge to do this, as it makes review slower; or if you do, use |
Co-authored-by: Michael Rothgang <rothgang@math.uni-bonn.de>
Strongly agree! You like fast reviews (as do I), and having a PR do only one thing makes it much faster. |
Good point. I had just been working with a bunch of typo PRs, and those tend to end up quite heterogeneous in content anyway, so I didn't connect that the "this files"-related changes could be (very) quickly merged on their own. Oh well. |
-awaiting-author |
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.
This looks ok to me now. Please summarize explicitly in the description any change that isn't "this files". @grunweg, are you happy?
Can you update the PR description as requested and ping me again once you've done this, please? I strongly presume I'll be happy then and just merge it. Thanks! |
@grunweg: PR description is now updated with a summary of the drive-by changes. -awaiting-author |
I'm happy now! |
I noticed that there were a lot of instances of the typo "this files" in the repo. I fixed these while doing some drive-by typo fixes in the files I touched while I was at it. The drive-by fixes are due to Codex and consist of: - Minor textual tweaks to improve flow of sentences. - Punctuation, like adding commas and full stops where appropriate in sentences. - Trimming superfluous white space and adding missing white space. - Swapping a `∪`-operator for a `∩`, where the latter was intended. - Swapping `𝒱(α, β, 𝔖 uβ)` for `𝒱(α, β, 𝔖, uβ)` where the latter was intended.
Build failed (retrying...): |
I noticed that there were a lot of instances of the typo "this files" in the repo. I fixed these while doing some drive-by typo fixes in the files I touched while I was at it. The drive-by fixes are due to Codex and consist of: - Minor textual tweaks to improve flow of sentences. - Punctuation, like adding commas and full stops where appropriate in sentences. - Trimming superfluous white space and adding missing white space. - Swapping a `∪`-operator for a `∩`, where the latter was intended. - Swapping `𝒱(α, β, 𝔖 uβ)` for `𝒱(α, β, 𝔖, uβ)` where the latter was intended.
Build failed: |
bors r+ |
I noticed that there were a lot of instances of the typo "this files" in the repo. I fixed these while doing some drive-by typo fixes in the files I touched while I was at it. The drive-by fixes are due to Codex and consist of: - Minor textual tweaks to improve flow of sentences. - Punctuation, like adding commas and full stops where appropriate in sentences. - Trimming superfluous white space and adding missing white space. - Swapping a `∪`-operator for a `∩`, where the latter was intended. - Swapping `𝒱(α, β, 𝔖 uβ)` for `𝒱(α, β, 𝔖, uβ)` where the latter was intended.
Pull request successfully merged into master. Build succeeded: |
I noticed that there were a lot of instances of the typo "this files" in the repo. I fixed these while doing some drive-by typo fixes in the files I touched while I was at it.
The drive-by fixes are due to Codex and consist of:
∪
-operator for a∩
, where the latter was intended.𝒱(α, β, 𝔖 uβ)
for𝒱(α, β, 𝔖, uβ)
where the latter was intended.