Skip to content

feat(parser): add tuple-binding shorthands - #151

Merged
Seddryck merged 1 commit into
mainfrom
feat/tuple-binding-shorthands
Sep 10, 2026
Merged

Seddryck merged 1 commit into
mainfrom
feat/tuple-binding-shorthands

Conversation

@Seddryck

Copy link
Copy Markdown
Owner

Parse f~ and ~f as distinct tuple-binding shorthand syntax in pipelines and nested expressions. Preserve function identity, prefix/postfix direction, authored text, and individual name/tilde spans through TupleBindingShorthandSyntax; leave function eligibility and runtime lowering downstream.

A stateless scanner enforces adjacency even around named comment extras. Add syntax documentation, highlighting, malformed-input recovery coverage, Unicode span checks, and incremental-edit tests. Update three existing malformed-input recovery snapshots for the new parser states.

Validation:

  • npm run generate: generated artifacts are reproducible.
  • npm test: 366 grammar cases and 5 Node tests passed.
  • dotnet test Expressif.Syntax.sln: 475 tests passed on each of .NET 8, 9, and 10.
  • Native Node binding built with MSBuild using ImportDirectoryBuildProps=false and ImportDirectoryBuildTargets=false to exclude the repository's .NET-only properties.
  • git diff --check: passed.

close #150

@coderabbitai

coderabbitai Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 9759039f-ae39-46a8-8231-0b21b062f273


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parse prefix and postfix tuple-binding shorthands

1 participant