Skip to content

don't combine stream/future ctors so aggressively - #249

Merged
dicej merged 1 commit into
bytecodealliance:mainfrom
dicej:future-stream-ctors
Sep 11, 2026
Merged

don't combine stream/future ctors so aggressively#249
dicej merged 1 commit into
bytecodealliance:mainfrom
dicej:future-stream-ctors

Conversation

@dicej

@dicej dicej commented Sep 11, 2026

Copy link
Copy Markdown
Collaborator

Previously, we would only emit one such constructor function per future or stream "canonical" payload type, where canonicalization would combine structurally equal (but not necessarily nominally equal) types. Since we encode the name of the payload type in the name of the constructor function, that made it hard to predict which names would be generated. Now we deduplicate based on the mangled name instead.

Previously, we would only emit one such constructor function per future or
stream "canonical" payload type, where canonicalization would combine
structurally equal (but not necessarily nominally equal) types.  Since we encode
the name of the payload type in the name of the constructor function, that made
it hard to predict which names would be generated.  Now we deduplicate based on
the mangled name instead.
@dicej
dicej force-pushed the future-stream-ctors branch from fea1272 to c79d7ea Compare September 11, 2026 22:10
@dicej
dicej merged commit 33bee20 into bytecodealliance:main Sep 11, 2026
4 checks passed
@dicej
dicej deleted the future-stream-ctors branch September 11, 2026 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant