-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe "explicit"-style WIT package grammar #340
Describe "explicit"-style WIT package grammar #340
Conversation
This enables the inclusion of multiple package definitions in a sngle `.wit` file, as discussed in WebAssembly#313.
An interesting consequence of being able to intermix files that have |
This is great—it would allow round-trip serialization of a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks for working on this!
Does this look good to merge, or would we like to wait for any additional implementation feedback? |
I'm happy to merge - do y'all do contributor-triggered merges, or
maintainer?
…On Fri, May 10, 2024, 07:58 Luke Wagner ***@***.***> wrote:
Does this look good to merge, or would we like to wait for any additional
implementation feedback?
—
Reply to this email directly, view it on GitHub
<#340 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4JX6POMR2FZQSGQ36QUB3ZBTOARAVCNFSM6AAAAABGDPSG5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBUG43DAMRSG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Mostly the latter. For WIT changes, I've generally been trying to keep WIT.md reflective of what is actually in the WIT toolchains (or, if not, gating the feature via a unicode emoji), so I was mostly curious if the implementation of this feature has been implemented and merged. |
This hasn't yet been merged into wasm-tools (or others as far as I know). That being said I think it's reasonable to merge here 👍 |
Ah thanks. Do you think it might be merged soonish, or would it make sense to emoji-gate this feature? |
I've not been working on it myself, but @azaslavsky I recall you were working on an initial implementation I think? |
@alexcrichton I am. Its fallen a bit on my priority list due to $dayjob concerns, but I should have the revised PR up by end of week. |
bytecodealliance/wasm-tools#1577 implementing this has merged, so I think this can land as well? |
Awesome, thanks again! |
Do not write with additional braces for single-file, multi-package format. WebAssembly/component-model#340 bytecodealliance/wasm-tools#1577
Do not write with additional braces for single-file, multi-package format. WebAssembly/component-model#340 bytecodealliance/wasm-tools#1577
Do not write with additional braces for single-file, multi-package format. WebAssembly/component-model#340 bytecodealliance/wasm-tools#1577
Do not write with additional braces for single-file, multi-package format. WebAssembly/component-model#340 bytecodealliance/wasm-tools#1577
This enables the inclusion of multiple package definitions in a single
.wit
file, as discussed in#313.