bump up rain.interpreter.interface

[0xgleb]

Motivation

We need the Rust code from rain.math.float in the orderbook and that's accessed via rain.interpreter.interface submodule in rain.interpreter submodule

Solution

bump up rain.interpreter.interface

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Summary by CodeRabbit

Summary by CodeRabbit

• Chores
  • Updated internal dependencies to the latest version.

[coderabbitai]

Walkthrough

This change updates the subproject commit reference for lib/rain.interpreter.interface to a newer commit. Additionally, it modifies the parseDecimalFloatPacked function in LibParseLiteralDecimal.sol to use a different parsing method that returns separate coefficient and exponent values, which are then packed into a float representation. No other code or functionality has been modified.

Changes

File(s)	Change Summary
lib/rain.interpreter.interface (submodule)	Updated subproject commit reference to a newer commit hash.
src/lib/parse/literal/LibParseLiteralDecimal.sol	Modified parseDecimalFloatPacked to call parseDecimalFloatInline returning coefficient and exponent, then pack them into a float.

Possibly related issues

• bump up rain.interpreter.interface #346: This issue involves updating the rain.interpreter.interface subproject commit reference, which matches the change in this PR.

Possibly related PRs

• bump int #323: Updates the subproject commit reference for lib/rain.interpreter.interface in a similar manner and includes changes to LibParseLiteralDecimal.sol.
• bump int #319: Also updates the subproject commit reference for lib/rain.interpreter.interface, differing only in the specific commit targeted.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 322686a and 141d052.

📒 Files selected for processing (1)

• src/lib/parse/literal/LibParseLiteralDecimal.sol (2 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: 0xgleb
PR: rainlanguage/rain.interpreter#333
File: crates/test_fixtures/src/lib.rs:99-102
Timestamp: 2025-06-09T07:47:06.227Z
Learning: User 0xgleb prefers to keep the current signer registration pattern in LocalEvm test fixture where all other signers are registered with the default wallet, rather than simplifying it to have each wallet sign independently.

⏰ Context from checks skipped due to timeout of 90000ms (10)

• GitHub Check: rainix (ubuntu-latest, rainix-sol-artifacts)
• GitHub Check: rainix (macos-latest, rainix-rs-test)
• GitHub Check: rainix (ubuntu-latest, test-wasm-build)
• GitHub Check: rainix (ubuntu-latest, rainix-sol-test)
• GitHub Check: rainix (ubuntu-latest, rainix-rs-test)
• GitHub Check: rainix (macos-latest, rainix-rs-artifacts)
• GitHub Check: rainix (ubuntu-latest, rainix-sol-static)
• GitHub Check: rainix (ubuntu-latest, rainix-rs-static)
• GitHub Check: rainix (ubuntu-latest, rainix-rs-artifacts)
• GitHub Check: git-clean

🔇 Additional comments (3)

src/lib/parse/literal/LibParseLiteralDecimal.sol (3)

8-8: LGTM! Import correctly added for the refactored packing logic.

The import of LibDecimalFloat is properly added and necessary for the packLossless function used in the refactored implementation.

---

21-21: LGTM! Manual packing correctly implemented.

The return statement properly uses LibDecimalFloat.packLossless to pack the coefficient and exponent, maintaining the same return type and interface. The use of packLossless indicates no precision should be lost in the refactoring.

---

18-19: Approve the refactored parsing call.

The change from parseDecimalFloatPacked to parseDecimalFloatInline correctly separates parsing from packing operations. The destructuring properly handles the four return values with descriptive variable names.

Please verify that the behavior remains equivalent to the previous implementation:

#!/bin/bash
# Description: Verify that parseDecimalFloatInline + packLossless produces equivalent results to parseDecimalFloatPacked

# Search for usage patterns of the old parseDecimalFloatPacked function
rg -A 5 -B 5 "parseDecimalFloatPacked"

# Search for tests related to decimal float parsing to ensure coverage
rg -A 10 -B 5 "parseDecimalFloatPacked|LibParseLiteralDecimal" --type=sol

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

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.