Andreas Rossberg
Andreas Rossberg
Any updates on this PR?
This PR is 5 years old and received no reaction from multiple pings over the past year. Unless there is visible activity, I will take the liberty to close it.
@zapashcanon, do you still intend to rebase and land this PR, or shall I close it?
Yeah, this is analogous to `ref.func`, where we go from `ref.func $x` to `ref.func 𝑎𝑑𝑑𝑟`, essentially overloading the mnemonic. We should probably have a better naming scheme for administrative instructions...
The only convention I could think of so far is to add a prime to the administrative versions, which we e.g. used in the OOPSLA'19 memory model paper. How about...
Hm, yeah, but then all ref patterns should still follow a consistent naming scheme as well.
Well, we should find a convention that works uniformly for more than just references. For example, we have `invoke` which is just `call'`, threads have `wait'`, and possibly others. And...
It's currently called `invoke` (on main repo), but relates to `call` in exactly the same way as `ref.func` relates to `ref.func` with addr. Ideally, they should use the same convention.
Yes, I agree with @dschuff. Stating the existence of opaque data is one piece, but the more important part is to specify that it has identity and how that is...
Also, not to forget that web engines are rather special beasts, and the drawbacks of multiple tiers usually do not apply to non-web use cases.