Skip to content

Jsligo: adopt TypeScript behavior on `_` variable

Rémi requested to merge 1692-wildcard-is-parsed-as-a-variable-in-jsligo into dev

Motivation and Context

we did not conform to Ts on _ variable.
Closes #1692 (closed)

Description

_ is now a valid variable/pattern name in JsLigo.
Breaking change: if multiple _ variable are bound in the same scope, it will result in an error (duplicate block-scoped variable) just as in TypeScript

Component

  • compiler
  • website
  • webide
  • vscode-plugin
  • debugger

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Performance improvement (non-breaking change that improves performance)
  • None (change with no changelog)

Changelog

Breaking change: if multiple _ variable are bound in the same scope, it will result in an error (duplicate block-scoped variable) just as in TypeScript

Checklist:

  • If a new syntax has been introduced, put a message on slack ligo-lsp
  • Changes follow the existing coding style (use dune @fmt to check).
  • Tests for the changes have been added (for bug fixes / feature).
  • Documentation has been updated.
  • Changelog description has been added (if appropriate).
  • Start titles under ## Changelog section with #### (if appropriate).
  • There is no image or uploaded file in changelog
  • Examples in changed behaviour have been added to the changelog (for breaking change / feature).
Edited by Rémi

Merge request reports