Lann

> Bike shedding resource syntax: &42 or '42 for borrow, or do we need a borrow value since it can be inferred from the type We don't technically need _any_...

It sounds like expectations differ quite a bit depending on expected use case. @chenyan2002 could you say more about what you're looking to do with this feature?

Thoughts on abstract syntax: I would like the option to serialize handles to (and from) arbitrary value syntax. The most visible use for this today would be [wasi-http `fields`](https://github.com/WebAssembly/wasi-http/blob/14a19b388f4828604a08ede2af8ee1285c020113/wit-0.3.0-draft/types.wit#L148); for...

Thoughts on concrete syntax: I can see the case for new token(s) to help visually identify handles, especially in output. I'm not sure that there is much value in distinguishing...

> If we don't have a syntactic difference for owned and borrowed, it's hard to know what `#1` refers to without looking at the underlying WIT type. Do you mean...

I suppose I am weakly against additional syntax for borrows given all the alternatives made available by supporting arbitrary values: `#[42]`, `#(42)`, `#"&42"`, `#borrow(42)`, `#-42`, `#b42` That said, this is...

I'm broadly in favor of adding some kind of documentation about this. Some questions/thoughts: - "Graceful shutdown" won't be meaningful for all guests; what (if any) _default_ behavior should be...

> Ultimately, neither the host nor the spec need to care about _how_ the guest decides to wrap up. This is probably true when the host is the caller but...

> Soon - the current functions will rename "set" to "append" > Soon - A decision will be made about whether these function signatures will return a future-of-an-error-type where the...

Would it be sufficient to say that `set` and `append` _may_ change the case of `name`? I'd also be interested in the origin of this: ``` /// The names and...