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

exnref name vs. externref #114

Closed
Closed
@jayphelps

Description

@jayphelps

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions