Andreas Rossberg

Not necessarily. Books may either have an author or an editor, proceedings have only editors. See [here](https://www.openoffice.org/bibliographic/bibtex-defs.html). FWIW, `report` is not an official bibtex entry type. Maybe use `misc` instead,...

We tried to maintain such regularity in the beginning, but as the language evolves, it is almost impossible to maintain it. Instruction sets tend to be much more irregular than...

In the most general version of what @lukewagner describes, there would be a pre-version of every form of module-level declaration: imports, exports, definitions. _Inside_ a module, the only observable difference...

Thanks for looking into this, this looks like a good direction. A few comments: - A monolithic `custom` flag probably isn't enough. Different implementations or tools may choose to recognise...

> Thanks for the feedback! > > * A monolithic custom flag probably isn't enough. [...] > > Though for the python test runner we probably want an all-or-nothing that...

@yuri91, I've been working on this over the past weeks. See [this branch](https://github.com/WebAssembly/annotations/tree/unignore) for my current attempt ([diff to annotations main](https://github.com/WebAssembly/annotations/compare/unignore)). Was a bit more tricky than I thought, and...

Mmh, yes, I see the problem. And it's indeed not clear how to fix that nicely. In general, a custom encoder would need to be able to inquire the byte...

Depends on what you mean by "absolute" offset. ;) I would interpret that as offset in the whole binary, but that would not work if you want to be able...

@yuri91, sorry for the radio silence, I haven't found the time to look at the changes properly yet. From a quick glance, I think this is a reasonable step to...

> * `(union T T)` would not be a valid interface type (validation/subtyping rules need to be better written up here) Shouldn't this be fine and result in `{0: T}...