Skip to content

Consider adding negative Test For Invalid BigInt literals #5133

Open
Open
Consider adding negative Test For Invalid BigInt literals#5133

Description

@calvinalkan
calvinalkan
opened on Sep 10, 2026

Test262 appears to lack coverage ensuring that the BigInt suffix must be lowercase n.

For example, this should fail during parsing:

/*---
features: [BigInt]
negative:
  phase: parse
  type: SyntaxError
---*/

$DONOTEVALUATE();

1N;

Activity

  1. ljharb commented on Sep 11, 2026

    @ljharb
    ljharb
    on Sep 11, 2026
    Member

    The spec doesn't actually mandate that that fails, since engines are unfortunately allowed a wide latitude in what additional syntax they support. Thus, it would (sadly) be incorrect to add such a negative test.

    Is there an engine you're aware of that supports that syntax?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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