-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Add missing dot at the end of sentence #60016
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
base: master
Are you sure you want to change the base?
Conversation
Added dot.
|
I changed the title to be slightly more descriptive, referencing "line 39" in a commit message is quite useless. |
|
Happy to merge this, but that whole sentence construction there is a bit unfortunate. |
Yes, I agree It is confusing sentence. Can you suggest correct sentence form of that line? https://julialang.org/blog/2025/10/julia-1.12-highlights/#new_multi-threading_features |
|
|
||
| !!! compat "Julia 1.12" | ||
| Starting by default with 1 interactive thread, as well as the 1 worker thread, was made as such in Julia 1.12 | ||
| Starting by default with 1 interactive thread, as well as the 1 worker thread, was made as such in Julia 1.12. |
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.
| Starting by default with 1 interactive thread, as well as the 1 worker thread, was made as such in Julia 1.12. | |
| The default number of threads changed in Julia 1.12. Prior versions default to 1 (default thread pool) thread. |
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.
After Julia 1.12 release Julia by default now starts with one worker thread and one interactive thread that is equivalent of
julia -t1,1(1 default + 1 interactive thread). So nowjulia -t1is equivalent tojulia -t,0that is no interactive thread will be assigned or spawned.
Is my above suggestion better?
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.
The information is fine, but the wording could use improvement.
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 leave it to experts to make good sentence.
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.
@giordano Here in the first line should they be replaced by we?
Because finalizers can interrupt any code, they must be very careful in how they interact with any global state.
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.
No, I think it's fine to personify finalizers.
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.
What should i do to get this merged? what changes are you waiting for merge?
Added dot.