Continue improving operator documentation#61127
Merged
Merged
Conversation
phrasing tweaks
rokke-git
force-pushed
the
rokke-git-patch-1
branch
6 times, most recently
from
February 23, 2026 03:31
716ff33 to
24f738b
Compare
rokke-git
force-pushed
the
rokke-git-patch-1
branch
from
February 23, 2026 13:42
24f738b to
27acfd2
Compare
fingolfin
reviewed
Feb 23, 2026
fingolfin
reviewed
Feb 23, 2026
Contributor
Author
|
it would prob also be good to fix the |
rokke-git
force-pushed
the
rokke-git-patch-1
branch
from
February 23, 2026 16:35
7ba39b8 to
e766aa6
Compare
Member
|
I'll look closer into this tonight or tomorrow |
fingolfin
reviewed
Feb 23, 2026
fingolfin
reviewed
Feb 24, 2026
rokke-git
force-pushed
the
rokke-git-patch-1
branch
3 times, most recently
from
February 24, 2026 05:29
314c778 to
c0a6e69
Compare
rokke-git
force-pushed
the
rokke-git-patch-1
branch
2 times, most recently
from
February 24, 2026 05:52
ea04e55 to
431ef44
Compare
rokke-git
force-pushed
the
rokke-git-patch-1
branch
from
February 24, 2026 06:00
431ef44 to
820c2dd
Compare
Contributor
|
Nice work. Thanks @rokke-git! |
mkitti
pushed a commit
to mkitti/julia
that referenced
this pull request
May 22, 2026
I've bumped my head against this section of the documentation quite a number of times (JuliaLang#61055, JuliaLang#60928, JuliaLang#58763), but it looks like I just missed a pr which massively improved it (JuliaLang#60286). While it caught a number of things I wanted fixed, there are still some tweaks which should be added for correctness. changes: - consolidates duplicated juxtaposition note - corrects the straight up wrong ordering of `'` and `::` - adds `...` and `,` and `->` and unary `:` - adds footnotes for a number of exceptions relating to various operators - `.` and `:` must have no spaces - `:`, `..`, `'` cannot be dot-distributed - `:` parses into groups of three - 2-argument `~` is not defined in main - `?:` precedence is asymmetric - assignment operators get weird with commas pinging @moble who did the previous pr
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
4 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.
I've bumped my head against this section of the documentation quite a number of times (#61055, #60928, #58763), but it looks like I just missed a pr which massively improved it (#60286). While it caught a number of things I wanted fixed, there are still some tweaks which should be added for correctness.
changes:
'and::...and,and->and unary:.and:must have no spaces:,..,'cannot be dot-distributed:parses into groups of three~is not defined in main?:precedence is asymmetricpinging @moble who did the previous pr