Skip to content
This repository was archived by the owner on Apr 25, 2025. It is now read-only.

exnref name vs. externref #114

Closed
jayphelps opened this issue Jun 9, 2020 · 2 comments
Closed

exnref name vs. externref #114

jayphelps opened this issue Jun 9, 2020 · 2 comments

Comments

@jayphelps
Copy link
Contributor

Since anyref was changed to only be opaque host references and thus renamed to externref I wanted to voice my opinion that the name "exnref" is too close to externref. Definitely bikeshedding--and we don't have to make any decisions immediately per say--but I wanted to bring it up in case the actual solution was to rename externref instead of exnref (probably not, but ?)

I don't have any preferred alternative names at this point, but seems like adding a c and/or p in there could be one way. Or alternatively there's been talk floated over the years several times about the future of this primitive being used for other non-exceptional events, in which case maybe a name more similar to event would be appropriate.

If there was discussion elsewhere about this that I missed (e.g. CG meeting I missed), apologies. This kinda sucks since it was already changed at least once before. Ultimately I just wanted to at least plant the discussion flag before any ships sail and see if I'm alone in this.

aheejin pushed a commit to aheejin/exception-handling that referenced this issue Jun 15, 2020
Incorporate active/passive segments into instantiation. While doing so, drop the notion of segment types as well as initelem/initdata administrative instructions and express the latter in terms of table.init and memory.init instructions. Adjust interpreter accordingly.
@aheejin
Copy link
Member

aheejin commented Jun 16, 2020

Yes it's not great that they became similar, but I'm also not sure if if is a problem. If you have a good alternative name, please suggest.

@aheejin
Copy link
Member

aheejin commented Oct 12, 2020

Closing this, as we decided to remove exnref in Sep 15 CG meeting.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants