Skip to content

SymbolTableType::Lambda #5942

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 11, 2025
Merged

Conversation

youknowone
Copy link
Member

@youknowone youknowone commented Jul 11, 2025

Summary by CodeRabbit

  • New Features

    • Lambda expressions are now explicitly distinguished from regular functions in symbol table analysis, improving clarity in scope handling.
    • Added support for setting function type parameters at runtime via an intrinsic operation.
  • Improvements

    • Enhanced symbol table output to display lambda scopes separately from function scopes.

Copy link
Contributor

coderabbitai bot commented Jul 11, 2025

Walkthrough

The changes introduce a new Lambda variant to the SymbolTableType enum, updating symbol table logic to distinguish lambdas from regular functions. Additionally, an intrinsic function for setting function type parameters is activated and handled in the VM, enabling runtime assignment of type parameters to function objects.

Changes

File(s) Change Summary
compiler/codegen/src/symboltable.rs Added Lambda to SymbolTableType, updated Display and symbol table logic to handle lambdas distinctly.
compiler/core/src/bytecode.rs Activated enum variant SetFunctionTypeParams = 4 in IntrinsicFunction2.
vm/src/frame.rs Added handler for SetFunctionTypeParams intrinsic, setting __type_params__ on function objects at runtime.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant VM
    participant FunctionObject

    User->>VM: Call intrinsic SetFunctionTypeParams(func, type_params)
    VM->>FunctionObject: set_attr("__type_params__", type_params)
    FunctionObject-->>VM: Attribute set
    VM-->>User: Return updated function object
Loading

Poem

In the warren of code, a new path unfurls,
Lambdas now hop with their own little twirls.
Type parameters set, with a whisk of the paw,
Intrinsics and symbols—oh, what I saw!
The bytecode now sparkles, the VM’s in tune,
A rabbit’s delight, under the compiler’s moon.
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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 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.

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
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: 0

🧹 Nitpick comments (1)
compiler/core/src/bytecode.rs (1)

414-416: Minor doc / typo cleanup

// PrepReraiseS tar = 1, contains an extraneous space after the S. While unrelated to functionality, it’s a readability papercut.

-        // PrepReraiseS tar = 1,
+        // PrepReraiseStar = 1,
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2f94a63 and 7248138.

📒 Files selected for processing (3)
  • compiler/codegen/src/symboltable.rs (4 hunks)
  • compiler/core/src/bytecode.rs (1 hunks)
  • vm/src/frame.rs (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.rs`: Follow the default rustfmt code style (`cargo fmt` to format) Always ...

**/*.rs: Follow the default rustfmt code style (cargo fmt to format)
Always run clippy to lint code (cargo clippy) before completing tasks. Fix any warnings or lints that are introduced by your changes
Follow Rust best practices for error handling and memory management
Use the macro system (pyclass, pymodule, pyfunction, etc.) when implementing Python functionality in Rust

📄 Source: CodeRabbit Inference Engine (.github/copilot-instructions.md)

List of files the instruction was applied to:

  • vm/src/frame.rs
  • compiler/core/src/bytecode.rs
  • compiler/codegen/src/symboltable.rs
🧠 Learnings (1)
compiler/codegen/src/symboltable.rs (1)
Learnt from: CR
PR: RustPython/RustPython#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-06-30T10:08:48.858Z
Learning: Applies to **/*.rs : Use the macro system (`pyclass`, `pymodule`, `pyfunction`, etc.) when implementing Python functionality in Rust
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
  • GitHub Check: Check the WASM package and demo
  • GitHub Check: Run snippets and cpython tests on wasm-wasi
  • GitHub Check: Run snippets and cpython tests (windows-latest)
  • GitHub Check: Check Rust code with rustfmt and clippy
  • GitHub Check: Run tests under miri
  • GitHub Check: Run snippets and cpython tests (macos-latest)
  • GitHub Check: Run snippets and cpython tests (ubuntu-latest)
  • GitHub Check: Run rust tests (macos-latest)
  • GitHub Check: Ensure compilation on various targets
  • GitHub Check: Run rust tests (ubuntu-latest)
  • GitHub Check: Run rust tests (windows-latest)
🔇 Additional comments (6)
compiler/core/src/bytecode.rs (1)

414-420: Confirm marshal/version bump – new discriminant SetFunctionTypeParams = 4 enters the wire format

Enabling this variant introduces a previously-unused tag (4) in the IntrinsicFunction2 enum that is marshalled as a raw u8.

If any compiled bytecode or persisted snapshot created before this PR already emitted the value 4 for a different meaning (e.g. due to the gaps at 1-3 being skipped), deserialization will now mis-interpret that byte and crash or misbehave.
Please double-check:

  1. The bytecode‐marshal version header (MARSHAL_VERSION or equivalent) is bumped, or
  2. We are certain no historical artefacts can contain the tag 4, and
  3. Integration tests exercising (de)serialisation are updated.

If uncertainty exists, bumping the version is the safer route.

vm/src/frame.rs (1)

2289-2294: LGTM: Clean implementation of SetFunctionTypeParams intrinsic function.

The implementation correctly handles setting the __type_params__ attribute on function objects. The approach follows the established pattern for intrinsic functions and appropriately relies on the compiler to generate correct bytecode with proper argument types.

compiler/codegen/src/symboltable.rs (4)

83-83: LGTM! Well-structured enum variant addition.

The addition of Lambda to the SymbolTableType enum is clean and follows the existing pattern. This enables proper distinction between lambda expressions and regular functions in the symbol table hierarchy.


94-94: LGTM! Consistent Display implementation.

The Display trait implementation for the new Lambda variant follows the established pattern and uses appropriate lowercase naming consistent with other variants.


498-498: LGTM! Logical grouping of function-like scopes.

The match arm correctly groups SymbolTableType::Function and SymbolTableType::Lambda together, as they should be handled identically in comprehension analysis. This maintains the existing behavior while supporting the new lambda scope type.


1145-1145: LGTM! Proper lambda scope differentiation.

The change from SymbolTableType::Function to SymbolTableType::Lambda when entering lambda scopes enables proper differentiation between lambda expressions and regular functions in the symbol table, which aligns with the PR objectives.

@youknowone youknowone merged commit 8b6c78c into RustPython:main Jul 11, 2025
22 of 23 checks passed
@youknowone youknowone deleted the symbol-table-lambda branch July 11, 2025 04:35
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