Skip to content

feat: improving mysel#2432

Open
benfdking wants to merge 2 commits intomainfrom
working_on_mysel
Open

feat: improving mysel#2432
benfdking wants to merge 2 commits intomainfrom
working_on_mysel

Conversation

@benfdking
Copy link
Copy Markdown
Collaborator

No description provided.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 652b9ea094

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

])
.to_matchable()])
.config(|this| {
this.terminators = vec![Ref::keyword("END").to_matchable()];
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid generic END terminator in ProcedureStatements

ProcedureStatements runs in greedy mode but stops on a bare END, which causes BEGIN ... END blocks to terminate at the first inner END token and breaks nested control-flow blocks such as IF ... END IF inside a procedure body. In practice, a block like BEGIN IF (...) THEN ... END IF; END; now produces unparsable sections at IF/END IF because the outer body is trimmed before the inner statement can match; the terminator needs to distinguish the outer END from END IF/WHILE/LOOP/REPEAT (or otherwise avoid a single-token END cutoff).

Useful? React with 👍 / 👎.

@github-actions
Copy link
Copy Markdown
Contributor

Benchmark for 02f0ca5

Click to view benchmark
Test Base PR %
DepthMap::from_parent 52.0±1.03µs 53.7±3.51µs +3.27%
fix_complex_query 11.6±0.09ms 11.7±0.18ms +0.86%
fix_superlong 147.1±2.92ms 154.1±3.82ms +4.76%
parse_complex_query 4.1±0.04µs 4.2±0.05µs +2.44%
parse_expression_recursion 7.2±0.07µs 7.1±0.07µs -1.39%
parse_simple_query 1035.1±37.27ns 1106.7±18.79ns +6.92%

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