Andreas Rossberg

Don't assume that everybody coming to this site for information knows their way around git or GitHub. ;) As somebody interested in PL history, I think historic documents have a...

@RossTate, I agree, though it should be noted that the Java specs you link to correspond more to what's in the spec repo, whereas the current discussion is about design...

Agreed with @binji. Where we link them from the org page it should likewise be made clear that these are historical docs.

As a general principle, all modes or attributes should actually be orthogonal to modules. That is, no properties should be attached to modules as a whole, since that would break...

Well, you can always introduce some explicit grouping mechanism in the hints themselves if necessary. Even if you could drop incompatible hints in modular program transformations, that seems to partially...

Can we simplify that further to ``` dataval ::= string | '(' 'i8' i8+ ')' | '(' 'i16' i16+ ')' | '(' 'i32' i32+ ')' | '(' 'i64' i64+ ')'...

Yeah, in fact, t.const might even create an ambiguity for passive segments.

The restrictions on the Instance (and even the Module) constructor were rather controversial, even among Chromium devs. The web platform team insisted, while others thought there is no coherent reason...

> > The nested loop structure, the thing that reducibility guarantees, is > pretty much thrown away at the start. [...] I checked the current > WebAssembly implementations in JavaScriptCore,...

I share some of @tiziano88's sentiment. How a module is signed, what structure signatures have, how they are associated, how they are validated, may differ significantly between eco systems. So...