Remove old bindings

[0xgleb]

Motivation

We don't want to maintain old versions of the interpreter

Solution

Remove old Rust bindings

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

• Refactor
  • Removed support for several older interface versions and modules, including legacy parser and interpreter bindings.
  • Cleaned up public APIs by removing outdated module exports and related documentation.
• Chores
  • Deleted obsolete code and test files associated with deprecated interfaces and modules.

[coderabbitai]

Walkthrough

The changes remove support for older Solidity interface bindings and parser logic from the Rust codebase. Specifically, bindings for outdated interpreter, store, and parser interfaces are deleted. The parser module's v1 implementation, its trait, struct, and associated tests are removed. Related module declarations and exports are also cleaned up.

Changes

File(s)	Change Summary
crates/bindings/src/lib.rs	Removed bindings for IInterpreterV2, IInterpreterV3, IInterpreterStoreV1, IInterpreterStoreV2, IParserV1.
crates/eval/src/dispatch.rs	Deleted file; removed CreateEncodedDispatch struct, its encode function, and related unit test.
crates/eval/src/lib.rs	Removed public module declaration for dispatch.
crates/parser/src/lib.rs	Removed public module declaration and re-export for v1.
crates/parser/src/v1.rs	Deleted file; removed Parser trait, ParserV1 struct, trait impls, and all associated async tests.

Sequence Diagram(s)

No sequence diagram generated as the changes are limited to removals and do not introduce or modify control flow.

---

📜 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 898d03b and 17238e1.

📒 Files selected for processing (5)

• crates/bindings/src/lib.rs (0 hunks)
• crates/eval/src/dispatch.rs (0 hunks)
• crates/eval/src/lib.rs (0 hunks)
• crates/parser/src/lib.rs (0 hunks)
• crates/parser/src/v1.rs (0 hunks)

💤 Files with no reviewable changes (5)

• crates/eval/src/lib.rs
• crates/eval/src/dispatch.rs
• crates/parser/src/lib.rs
• crates/bindings/src/lib.rs
• crates/parser/src/v1.rs

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

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

✨ 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

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