WebAssembly / interface-types

Other
641 stars 57 forks source link

Video Call: August 29th 2019 #56

Closed jgravelle-google closed 4 years ago

jgravelle-google commented 4 years ago

No registration required. Email jgravelle [ at ] google (dot) com for the meeting link. (Meeting will use Zoom software)

Meeting will start at 12noon PDT, and will last one hour (until 1pm PDT).

Please suggest agenda items as comments on this issue.


Notes here

lukewagner commented 4 years ago

Proposed agenda item: defer (from #60)

jgravelle-google commented 4 years ago

Some chatting about records might be worth doing (#61)

Specifically, should we explicitly model reading values out of memory? (Probably)

pchickey commented 4 years ago

Another topic - do we want a byte-vector type that corresponds to the string type, except without any restriction about containing unicode code points? It is required to implement many interfaces in WASI, or essentially anything that gets strings from an untrusted source.

jgravelle-google commented 4 years ago

This is an interesting question. I would say: yes absolutely, that is a critical use-case to support. I think we either need a special ByteArray, or we need a Sequence\<Uint8> that we can be pretty sure about optimizing well. The trick is, which of those is the better approach, and is dependent on a few other topics. But yeah let's discuss more.

pchickey commented 4 years ago

one more topic: pruning the issues. There have been at least 2 major shifts since some of the early issues were filed and most can be closed

jgravelle-google commented 4 years ago

Notes here