2 Pull requests merged by 2 people

• Fix WIT.md example

  #493 merged Apr 8, 2025

• Separately gate error-context from async

  #489 merged Apr 3, 2025

2 Pull requests opened by 1 person

• Restrict 'strongly-unique' predicate to prevent further bindgen conflicts

  #494 opened Apr 7, 2025

• Make {stream,future}.new return both a readable and writable end

  #497 opened Apr 10, 2025

5 Issues closed by 2 people

• Gate MVP example conflicts with BNF

  #480 closed Apr 8, 2025

• Rust guest async bindings: low-overhead streams with no copies difficult to make memory safe

  #471 closed Apr 3, 2025

• Should `{future,stream}.close-{readable,writable}` take ownership of the error-context?

  #469 closed Apr 3, 2025

• Require-error-on-close may be a composability hazard

  #472 closed Apr 3, 2025

• Defer `error-context` to after 0.3.0

  #474 closed Apr 3, 2025

3 Issues opened by 1 person

• Refactor binary encoding of canon builtins for easier future extensibilty

  #496 opened Apr 8, 2025

• Subtask cancellation

  #495 opened Apr 8, 2025

• Refactoring event codes with respect to recent changes

  #492 opened Apr 3, 2025

12 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• How instantiate, argument and namespace interactive?

  #483 commented on Apr 3, 2025 • 0 new comments

• Allow non-canonical type alignment?

  #258 commented on Apr 3, 2025 • 0 new comments

• Resources with a function name that is the same as the resource name does not work in all languages

  #478 commented on Apr 7, 2025 • 0 new comments

• CABI: Add a `resource.consume` method for owned handles

  #238 commented on Apr 8, 2025 • 0 new comments

• Separately owned handles for read/write ends of futures/streams

  #475 commented on Apr 8, 2025 • 0 new comments

• Ambiguity between "operation cancelled" and "0-length operation completed"

  #490 commented on Apr 8, 2025 • 0 new comments

• async: How does cross-task communication work?

  #459 commented on Apr 8, 2025 • 0 new comments

• Toolchain conventions and `context.get`

  #485 commented on Apr 8, 2025 • 0 new comments

• async: Is it possible to have a background task?

  #460 commented on Apr 8, 2025 • 0 new comments

• Interaction with the memory64 proposal

  #22 commented on Apr 8, 2025 • 0 new comments

• Allow stream.{read,write}s of length 0 to query/signal readiness

  #444 commented on Apr 8, 2025 • 0 new comments

• Document some conventions for `context.{get,set}`

  #491 commented on Apr 8, 2025 • 0 new comments