GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add JSRemote<JSObject> by kateinoigakukun · Pull Request #711 · swiftwasm/JavaScriptKit

Conversation

@kateinoigakukun

@kateinoigakukun kateinoigakukun commented Mar 31, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

#704

Add JSRemote<JSObject> API for accessing JSObjects without transfer

The new API allows creating a handle for a JSObject that remains
on its original JavaScript thread and hopping back to that thread
to access the object when needed. This is useful for cases where the
object cannot be transferred to another thread, but occasional access
is still required or when we want to guarantee that an object is always
accessed on the same thread for safety (it should be statically
guaranteed with strict Sendable checking, but modules with language mode
5 don't have that).

Example:

let document = JSObject.global.document.object!
let remoteDocument = JSRemote(document)

let executor = try await WebWorkerTaskExecutor(numberOfThreads: 1)
let title = try await Task(executorPreference: executor) {
    try await remoteDocument.withJSObject { document in
        document.title.string ?? ""
    }
}.value

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

gn-adin-b and gn-andrew-lu reacted with rocket emoji
All reactions
  • 🚀 2 reactions
@kateinoigakukun kateinoigakukun changed the title Add JSRemote<JSObject> with typed-throws owner-thread access Add JSRemote<JSObject> Mar 31, 2026
@kateinoigakukun
kateinoigakukun force-pushed the issue-704 branch 3 times, most recently from c82cab3 to e032560 Compare April 2, 2026 15:58
@kateinoigakukun
kateinoigakukun marked this pull request as ready for review April 2, 2026 15:58
@kateinoigakukun
Add JSRemote<JSObject> API for accessing JSObjects without transfer
5887f87
The new API allows creating a handle for a `JSObject` that remains
on its original JavaScript thread and hopping back to that thread
to access the object when needed. This is useful for cases where the
object cannot be transferred to another thread, but occasional access
is still required or when we want to guarantee that an object is always
accessed on the same thread for safety (it should be statically
guaranteed with strict Sendable checking, but modules with language mode
5 don't have that).

Example:

```swift
let document = JSObject.global.document.object!
let remoteDocument = JSRemote(document)

let executor = try await WebWorkerTaskExecutor(numberOfThreads: 1)
let title = try await Task(executorPreference: executor) {
    try await remoteDocument.withJSObject { document in
        document.title.string ?? ""
    }
}.value
```
@kateinoigakukun
kateinoigakukun force-pushed the issue-704 branch from e032560 to 5887f87 Compare April 2, 2026 16:05
@kateinoigakukun
kateinoigakukun merged commit df32a66 into main Apr 2, 2026
12 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@kateinoigakukun
kateinoigakukun deleted the issue-704 branch April 2, 2026 16:27
@kateinoigakukun kateinoigakukun mentioned this pull request May 15, 2026
Support cancellation of tasks with FetchHTTPClient apple/swift-http-api-proposal#157
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@kateinoigakukun
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.