Create cargo.yml

[Dargon789]

Summary by Sourcery

Add a CircleCI configuration to run Rust formatting checks and tests via cargo.yml

CI:

• Introduce a build-and-test job using cimg/rust:1.90.0 to run cargo fmt and cargo test
• Add caching for Cargo dependencies and build artifacts

[sourcery-ai]

Reviewer's Guide

This PR introduces a new CircleCI pipeline configuration (cargo.yml) to automate Rust formatting checks, testing, and dependency caching using the cimg/rust Docker image.

File-Level Changes

Change	Details	Files
Add CircleCI pipeline for Rust cargo workflow	Define build-and-test job with cimg/rust:1.90.0 Docker image Add steps for checkout, restoring and saving cargo caches Run cargo fmt -- --check and cargo test commands Configure ci workflow to trigger the build-and-test job	.circleci/cargo.yml

---

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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request establishes a foundational continuous integration pipeline for the project by adding a CircleCI configuration file. This new setup automates the essential steps of checking code formatting, running tests, and managing Rust dependencies through caching, which will ensure code quality and accelerate development cycles.

Highlights

• New CI Configuration: Introduces a new CircleCI configuration file (.circleci/cargo.yml) to automate build and test processes for Rust projects.
• Rust Toolchain: Specifies the use of cimg/rust:1.90.0 Docker image, ensuring a consistent Rust environment for CI runs.
• Automated Checks: Configures the CI to automatically run cargo fmt -- --check for code formatting validation and cargo test for unit and integration testing.
• Dependency Caching: Implements caching for Cargo dependencies (Cargo.lock, ~/.cargo, target) to speed up subsequent CI runs.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• You’re running cargo fmt and cargo test twice—remove the duplicate commands after saving the cache to streamline the job.
• Consider splitting the Cargo registry and target directory into separate cache keys so you don’t invalidate your entire cache when one part changes.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- You’re running cargo fmt and cargo test twice—remove the duplicate commands after saving the cache to streamline the job.
- Consider splitting the Cargo registry and target directory into separate cache keys so you don’t invalidate your entire cache when one part changes.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request introduces a new CircleCI workflow for the Rust project. The configuration is a good start, but it contains duplicated steps that should be removed for efficiency. I've also suggested adding cargo clippy to the pipeline to improve code quality and catch common issues early. Please see my detailed comments.