-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Couple of small docs fixes #18784
Couple of small docs fixes #18784
Conversation
Would it make sense to have Travis/AppVeyor run |
@@ -3059,14 +3059,6 @@ Return `true` if `A` is a subset of or equal to `S`. | |||
issubset | |||
|
|||
""" | |||
stringmime(mime, x) |
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.
Was this copied out of helpdb
and someone forgot to remove 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.
@@ -1545,7 +1565,7 @@ Internals | |||
julia> M.f() | |||
(1,2) | |||
|
|||
With @macroexpand the expression expands where @macroexpand appears in the code (module M). With macroexpand the expressions expands in the current module where the code was finally called. Note that when calling macroexpand or @macroexpand directly from the REPL, both of these contexts coincide, hence there is no difference. | |||
With ``@macroexpand`` the expression expands where ``@macroexpand`` appears in the code (module ``M``\ ). With ``macroexpand`` the expressions expands in the current module where the code was finally called (REPL). Note that when calling ``macroexpand`` or ``@macroexpand`` directly from the REPL, both of these contexts coincide, hence there is no difference. |
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.
ref #18660 (comment) I think we should delete this (REPL)
parenthetical both here and at the source, since it's confusing and not very general.
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 my comment #18660 (comment) there.
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.
Updated accordingly.
Yes we should do some sort of doc building on CI. Last time I tried I couldn't come up with something that didn't result in too frequently recompiling the system image. And the doc building mechanism will probably be changing soon. |
I believe I need this PR in order to fix the issues Tony mentions here: #18484 (comment) |
With `@macroexpand` the expression expands where `@macroexpand` appears in the code (module `M`). | ||
With `macroexpand` the expressions expands in the current module where the code was finally called (REPL). | ||
With `@macroexpand` the expression expands where `@macroexpand` appears in the code (module | ||
`M` in the example). With `macroexpand` the expressions expands in the current module where |
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.
"expression expands", right?
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 guess so. Anything else?
...which where probably forgotten to commit in other PRs.
bd8a913
to
1aca433
Compare
...which where probably forgotten to commit in other PRs.