chore: use rust edition 2024

[mantricjavier]

Description and Motivation

Fixes #134

Related Issues

---

Checklist:

• I have read MANTRA's contribution guidelines.
• My pull request has a sound title and description (not something vague like Update index.md)
• All existing and new tests are passing.
• I updated/added relevant documentation.
• The code is formatted properly just fmt.
• Clippy doesn't report any issues just lint.
• I have regenerated the schemas if needed with just schemas.

Summary by CodeRabbit

• Chores
  • Upgraded the project to a newer programming language edition, enhancing support for modern features and performance improvements behind the scenes.

[coderabbitai]

Warning

Rate limit exceeded

@mantricjavier has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 21 minutes and 26 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 4ed3ef4 and 5e4f0c3.

📒 Files selected for processing (1)

• .github/workflows/ci-test-lints.yaml (2 hunks)

Walkthrough

The update modifies the Rust workspace’s Cargo.toml file by changing the edition field from "2021" to "2024". This update is isolated to the configuration file and does not affect dependencies or workspace members.

Changes

File	Summary
Cargo.toml	Updated Rust edition from "2021" to "2024".

Poem

I’m a rabbit, hopping through the code,
Edition’s leaping to a brighter road.
Rust grows modern, swift, and true,
With "2024" shining like morning dew.
Happy hops in the coding groove! 🐇💻

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a253619 and 4ed3ef4.

📒 Files selected for processing (1)

• Cargo.toml (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Tests and Lints

Cargo.toml

[error] 1-1: Failed to parse manifest. Feature edition2024 is required but not stabilized in this version of Cargo (1.80.0). Consider trying a newer version of Cargo.

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

• GitHub Check: Validate schemas are up to date

[coderabbitai]

⚠️ Potential issue

Critical Issue: Unsupported Rust Edition 2024 in Current Cargo Version

The upgrade to edition = "2024" is not supported by Cargo version 1.80.0 (as reflected by the pipeline failure). Please ensure that the build environment (CI and local tooling) uses a Cargo version that supports the Rust 2024 edition (for example, by switching to an appropriate nightly or updating to a newer stable release). If updating the toolchain is not feasible, consider reverting to a stable edition until full support is available.

[mantricjavier]

todo: revise formatting both locally and with the IDE