-
-
Notifications
You must be signed in to change notification settings - Fork 15.7k
Clarify examples related to Sync and SyncView
#162621
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
Merged
+43
−30
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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 gives a "This example is not tested on wasm" warning in the docs https://doc.rust-lang.org/nightly/std/sync/struct.SyncView.html#examples which is a bit weird. Perhaps this and the original
Atomicexample should gate ontarget_has_threadsinstead?This isn't super accurate anyway since we have wasm targets with threads and non-wasm targets without threads, it just happens that the wasm target in CI is the only thing we flag.
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 for your suggestion.
My concern is that
target_has_threadsdoesn't guarantee thatstd::thread::spawnis supported.For example, on
wasm32-unknown-unknown, enabling+atomicsmakessinglethread()returnfalse, which enablestarget_has_threads. However, std still selects the unsupported thread backend, whereThread::newalways returnsUNSUPPORTED_PLATFORM.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.
That's a good point too. Opened a discussion at #t-libs > Skipping doctests without thread::spawn