Dave Bakker

Just for clarity; are recursive datatypes themselves the problem, or the fact that they might form circular references at runtime? The former does not automatically introduce the latter.

Thanks for the detailed response! I'm not sure I understand everything, but I think it's more productive to hold off my follow-up questions until there is something more fleshed out...

> Great writeup! "Yes", you're right on. Nice. Thanks for confirming! The explainer gets into the weeds pretty quickly. To me, it would have been helpful if there was some...

How do "worlds" & "interfaces" relate to components? During the 22 Sept. WASI meeting @fibonacci1729 provided a brief answer. However, I didn't quite understand. :sweat_smile: Would you mind explaining here?...

When posed as an either/or question, I'm ambivalent. I don't think default values are inherently better than option types or vice versa. They can both fill each other's role to...

> With option, the interface says "however your language expresses a missing parameter, do that, then communicate this to me as the none case. I think languages like Java, C#,...

> The time to consider adding exclusive-borrow would be in the Preview3 timeframe in conjunction with future/stream. Makes sense!👍 > The idea would be to add a new handle type,...

I might be missing something fundamental here, but: You mention the original handle is left intact and usable over the duration of the call. I can see how the handle...

> Unfortunately, we don't have any good way to reflect mutability in a component-level signature I'm fine with focusing on "exclusivity" instead. How I understand it now: 1. There are...

An other use for annotations could be to instruct code generators to emit specialized types, rather than their low-level representation: ```rs #[type-hint("wasi:snapshot1/timestamp")] type timestamp = u64; #[type-hint("wasi:snapshot1/local-date-time")] type local-date-time =...