Skip to content

Improve Web Documentation#212

Open
daxpedda wants to merge 1 commit into
rust-windowing:masterfrom
daxpedda:web-doc
Open

Improve Web Documentation#212
daxpedda wants to merge 1 commit into
rust-windowing:masterfrom
daxpedda:web-doc

Conversation

@daxpedda
Copy link
Copy Markdown
Member

@daxpedda daxpedda commented Mar 9, 2026

Fix some leftovers from #192.

Comment thread src/web.rs
Comment on lines -6 to -19
///
/// ## Thread-Safety
///
/// WASM objects are usually bound to the main UI "thread" belonging to the
/// top-level webpage. Therefore this type is `!Send` and `!Sync`. It cannot be
/// sent to or used from other threads.
///
/// Note that this type does not contain any WASM objects. However,
/// it is kept `!Send` and `!Sync` for the event that WASM objects are
/// added to this type.
///
/// However, this status quo may change in the future, due to the adoption of
/// atomics in WASM code. Therefore this type may be made `Send` and `Sync` as
/// part of a non-breaking change.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why is this removed?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Same reason as #209 (comment): it doesn't make any sense on an empty type.

We might want to consider making it Send + Sync right now. I can't think of a reason not to.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think we need to do more work to actually figure out the semantics of what a "display handle" is meant to be before we can really make this distinction.

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants