Conversation
I was mocking up a witx description for #322 and had a use for an `option` type. Of course, I could also just emit a variant manually, or reuse `expected` by omitting the error type, but `option` better conveys the sense that the `none` case doesn't necessarily represent an error.
|
That would be a nice addition! In |
|
The code here looks fine to me, but I would hesitate because I'm not sure whether we want to continue to enhance the current ABI of WASI since it makes it more complicated to support in a future with support for a new ABI. I've been working on an Do you think it would be better for me to try to land by "abi next" work and get |
|
Ah, cool. I'm ok waiting for the new ABI; this was just for some prototyping I was doing. |
|
Ok! I'll work on cleaning that up for a PR this week. |
|
Ok I posted #422 which has |
3 participants
I was mocking up a witx description for #322 and had a use for an
optiontype. Of course, I could also just emit a variant manually,or reuse
expectedby omitting the error type, butoptionbetterconveys the sense that the
nonecase doesn't necessarily representan error.