Skip to content

fix: scan consecutive test comments without recursion - #24

Open
everton-dgn wants to merge 1 commit into
webpro-nl:mainfrom
everton-dgn:fix/scan-consecutive-test-comments-iteratively
Open

everton-dgn wants to merge 1 commit into
webpro-nl:mainfrom
everton-dgn:fix/scan-consecutive-test-comments-iteratively

Conversation

@everton-dgn

Copy link
Copy Markdown

A long sequence of comment lines inside [[ ... ]] could exhaust the call stack before reaching the expression. Scan those comments in a loop while keeping ordinary newline tokens, token offsets and pending heredocs intact.

Add a 20,000-comment regression and preservation cases for CRLF, lexer windows, embedded hashes and heredocs. All 2,064 tests pass across the test files, along with build, typecheck, lint and formatting. The five focused tests also pass as compiled JavaScript on Node 20; the source tests ran on Node 24. Bash accepts and executes the same large input.

A long sequence of comment lines inside [[ ... ]] could exhaust the call stack before reaching the expression. Scan those comments in a loop while keeping ordinary newline tokens, token offsets and pending heredocs intact.

Add a 20,000-comment regression and preservation cases for CRLF, lexer windows, embedded hashes and heredocs. All 2,064 tests pass across the test files, along with build, typecheck, lint and formatting. The five focused tests also pass as compiled JavaScript on Node 20; the source tests ran on Node 24. Bash accepts and executes the same large input.
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.

1 participant