Skip to content

When to use "implementation-defined" abstract operation? #92

@anba

Description

@anba

Some abstract operations are marked as "implementation-defined abstract operation", but have fully defined steps. I think the intention for "implementation-defined" is that no steps at all are defined. Normal abstract operations can have "implementation-defined" sub-steps and still don't need to be defined as "implementation-defined abstract operations".

(This issue is also present in ECMA-402.)

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