Skip to content

Conversation

@raman-maker
Copy link
Contributor

Added dot.

@giordano giordano changed the title . or , missing in this line 39 Add missing dot at the end of sentence Nov 1, 2025
@giordano
Copy link
Member

giordano commented Nov 1, 2025

I changed the title to be slightly more descriptive, referencing "line 39" in a commit message is quite useless.

@Keno
Copy link
Member

Keno commented Nov 1, 2025

Happy to merge this, but that whole sentence construction there is a bit unfortunate.

@raman-maker
Copy link
Contributor Author

raman-maker commented Nov 1, 2025

Starting by default with 1 interactive thread, as well as the 1 worker thread, was made as such in Julia 1.12 If the number of threads is set to 1 by either doing -t1 or JULIA_NUM_THREADS=1 an interactive thread will not be spawned.

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Contributor Author

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 now julia -t1 is equivalent to julia -t,0 that is no interactive thread will be assigned or spawned.

Is my above suggestion better?

Copy link
Member

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.

Copy link
Contributor Author

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.

Copy link
Contributor Author

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.

Copy link
Member

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.

Copy link
Contributor Author

@raman-maker raman-maker Nov 7, 2025

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants