You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From #2705, when publishing shared worker messages, or replying to an individual message, we should enable values to be transferred.
I don't think a second "transfer list" API is a good fit for the shared worker API. Perhaps we could add a chaining API like .transferring(buffer1, messagePort2).publish({buffer1, messagePort2}) and .transferring(buffer1, messagePort2).reply({buffer1, messagePort2}).
Values can only be transferred once. This also means we can't add this to the .broadcast() method.
From #2705, when publishing shared worker messages, or replying to an individual message, we should enable values to be transferred.
I don't think a second "transfer list" API is a good fit for the shared worker API. Perhaps we could add a chaining API like
.transferring(buffer1, messagePort2).publish({buffer1, messagePort2})
and.transferring(buffer1, messagePort2).reply({buffer1, messagePort2})
.Values can only be transferred once. This also means we can't add this to the
.broadcast()
method.See:
ava/plugin.d.ts
Line 35 in 0e5cc7d
ava/plugin.d.ts
Line 41 in 0e5cc7d
The text was updated successfully, but these errors were encountered: