Skip to content

Update function parsing docs#62

Merged
leynos merged 3 commits into
mainfrom
codex/revise-function-parsing-design.md-for-recursion
Jul 6, 2025
Merged

Update function parsing docs#62
leynos merged 3 commits into
mainfrom
codex/revise-function-parsing-design.md-for-recursion

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jul 6, 2025

Summary

  • document recursive strategy for parsing nested types
  • note improved delimiter error reporting in parameter lists

Testing

  • make fmt
  • make lint
  • make test
  • make markdownlint
  • make nixie

https://chatgpt.com/codex/tasks/task_e_6869c3c79e7883229f5450143aa47bab

Summary by Sourcery

Revise the function parsing design documentation to highlight the fully recursive handling of nested type delimiters and improved error reporting for missing or mismatched delimiters in parameter lists.

Documentation:

  • Document that parse_type_expr now recursively parses matching delimiters for nested types without an external stack
  • Describe improved ParseError::Delimiter and ParseError::UnclosedDelimiter diagnostics with expected vs. actual tokens
  • Clarify how missing colons, names, and types are reported with accurate span attachments in parameter parsing

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jul 6, 2025

Reviewer's Guide

This PR refines the function-parsing design documentation to describe a fully recursive strategy for nested type parsing and to detail improved error diagnostics for missing delimiters and colons in parameter lists.

File-Level Changes

Change Details Files
Describe fully recursive nested-type parsing in parse_type_expr
  • Explain delegation to parse_type_expr upon encountering any opening delimiter
  • Detail recursive calls for matching (), [], {}, <> without an external stack
  • Illustrate handling of deeply nested types like Vec<Map<string, Vec>>
docs/function-parsing-design.md
Clarify enhanced error reporting for delimiters and missing colons
  • Note that MissingColon attaches the span of the terminating comma or parenthesis
  • Describe ParseError::Delimiter recording expected vs actual tokens
  • Specify UnclosedDelimiter emitted when leftover openings remain after parsing
docs/function-parsing-design.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 6, 2025

Warning

Rate limit exceeded

@leynos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 56 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 8af3f1d and 35b454f.

📒 Files selected for processing (1)
  • docs/function-parsing-design.md (1 hunks)

Summary by CodeRabbit

  • Documentation
    • Improved and clarified documentation for parsing behaviour and error reporting, including details on recursive parsing of nested delimiters and enhanced explanations of error diagnostics.

Walkthrough

The documentation for the parsing functions parse_name_type_pairs and parse_type_expr was revised for greater clarity. Updates include a clearer explanation of recursive parsing, error reporting, and the roles of helper functions, along with more precise descriptions of how errors are diagnosed and reported.

Changes

File(s) Change Summary
docs/function-parsing-design.md Revised documentation for parse_name_type_pairs and parse_type_expr to clarify parsing logic, recursion, error handling, and helper function roles.

Possibly related PRs

Poem

In the warren of code where the parsers dwell,
Rabbits revised the docs to tell
Of errors caught and names made clear,
Delimiters nested—no need to fear!
With helper paws and careful prose,
The parsing tale precisely grows.
🐇📜

✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in a Comment
  • Commit Unit Tests in branch codex/revise-function-parsing-design.md-for-recursion

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey @leynos - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd98f09 and 8af3f1d.

📒 Files selected for processing (1)
  • docs/function-parsing-design.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
`docs/**/*.md`: Documentation must use en-GB-oxendict spelling and grammar (with the exception of 'license' which is to be left unchanged for community consistency).

docs/**/*.md: Documentation must use en-GB-oxendict spelling and grammar (with the exception of 'license' which is to be left unchanged for community consistency).

📄 Source: CodeRabbit Inference Engine (AGENTS.md)

List of files the instruction was applied to:

  • docs/function-parsing-design.md
`**/*.md`: Markdown paragraphs and bullet points must be wrapped at 80 columns. Code blocks must be wrapped at 120 columns. Tables and headings must not be wrapped.

**/*.md: Markdown paragraphs and bullet points must be wrapped at 80 columns.
Code blocks must be wrapped at 120 columns.
Tables and headings must not be wrapped.

📄 Source: CodeRabbit Inference Engine (AGENTS.md)

List of files the instruction was applied to:

  • docs/function-parsing-design.md
`**/*.md`: * Avoid 2nd person or 1st person pronouns ("I", "you", "we") * Use en...

**/*.md: * Avoid 2nd person or 1st person pronouns ("I", "you", "we")

  • Use en-oxendic spelling and grammar.
  • Paragraphs and bullets must be wrapped to 80 columns, except where a long URL would prevent this (in which case, silence MD013 for that line)
  • Code blocks should be wrapped to 120 columns.
  • Headings must not be wrapped.

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

  • docs/function-parsing-design.md
🪛 LanguageTool
docs/function-parsing-design.md

[uncategorized] ~29-~29: Possible missing comma found.
Context: ...arameter list. Whenever it encounters a colon it delegates to parse_type_expr. That...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~37-~37: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...inating comma or parenthesis is attached so diagnostics point at the error. Helper ...

(COMMA_COMPOUND_SENTENCE_2)


[style] ~38-~38: Would you like to use the Oxford spelling “finalize”? The spelling ‘finalise’ is also correct.
Context: ... functions collect_parameter_name and finalise_parameter keep the main loop small. E...

(OXFORD_SPELLING_Z_NOT_S)

⏰ Context from checks skipped due to timeout of 240000ms (1)
  • GitHub Check: build-test
🔇 Additional comments (1)
docs/function-parsing-design.md (1)

40-44: Wrap long sentences to 80 columns

The following lines slightly exceed 80 characters; insert hard breaks after
“nodes” and “tokens” to satisfy the markdown wrapping rule.

-`ParseError::MissingType`. `parse_type_expr` skips whitespace and comment nodes
-and reports mismatched delimiters with a `ParseError::Delimiter` that records
-the expected and actual tokens. Unclosed delimiters produce
-`ParseError::UnclosedDelimiter` once parsing stops.
+`ParseError::MissingType`. `parse_type_expr` skips whitespace and comment nodes  
+and reports mismatched delimiters with a `ParseError::Delimiter` that records  
+the expected and actual tokens. Unclosed delimiters produce  
+`ParseError::UnclosedDelimiter` once parsing stops.

Likely an incorrect or invalid review comment.

Comment thread docs/function-parsing-design.md
Comment thread docs/function-parsing-design.md Outdated
leynos and others added 2 commits July 6, 2025 01:52
…compliance

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@leynos leynos merged commit 73b4d14 into main Jul 6, 2025
2 checks passed
@leynos leynos deleted the codex/revise-function-parsing-design.md-for-recursion branch July 6, 2025 00:53
@coderabbitai coderabbitai Bot mentioned this pull request Jul 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant