Update to use witx tagged unions#165
Conversation
a2228d4 to
8443958
Compare
|
I don't understand why the Azure windows build failed but the github windows build succeeded. Do we need to keep the Azure pipelines around anymore? |
5785f39 to
f3c4f53
Compare
|
Rebased on master, and submodule points at WASI master - ready to go @sunfishcode |
|
This PR contains a change to remove The Azure Pipeline rules build wasi-libc, which the Github Action rules don't do yet. If we moved that over to Github Actions, then we could drop the Azure Pipelines. @pchickey And just to confirm, this change doesn't change the ABI, right? |
|
Are the markers still useful for the musl parts of the code (where we will most likely want to periodically update)? |
|
The markers may be useful in musl ( Correct, there is no ABI change, thats what you're supposed to be able to convince yourself from the changes summarized in the description. |
we decided to abandon the upstream code guarded by #ifdef __wasilibc_unmodified_upstream // non-anonymous unions because these changes are sprawling and those guards are of diminishing importance
fake required arguments are no good
f3c4f53 to
0f50362
Compare
|
rebased after #167 merged to master |
sunfishcode
left a comment
There was a problem hiding this comment.
I agree; let's keep the __wasilibc_unmodified_upstream markers in musl for now, but removing them in libc-bottom-half now makes sense.
Implements changes proposed in WebAssembly/WASI#220.
Changes to generated code for union types
$subscriptionCurrent Master
Tagged Unions
$eventCurrent Master
Tagged Unions
$prestatCurrent Master
Tagged Unions