Skip to content

Design of "Functions and Classes"? #2420

Open
@jmdyck

Description

@jmdyck

(This is a follow-up to #2417 (comment); I didn't want to send that discussion off-topic.)

Does clause 15 (Functions and Classes) have a 'design'? E.g., guidelines that would inform a decision about where new stuff goes?

Currently, it looks pretty haphazard to me. E.g., "Async Function Definitions" and "Async Arrow Function Definitions" are adjacent; okay so then why isn't "Async Generator Function Definitions" grouped with them? Maybe it 'wants' to be close to "Generator Function Definitions", but then why doesn't that apply to the other Async clauses?

And the placement of "ClassDefinitions" (between two Async clauses) seems odd.

Clause 27 ("Control Abstraction Objects"), which deals with some of the same categories, also seems jumbled.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions