Implement Linpack benchmark in Rust

[sweep-ai[bot]]

PR Feedback (click)

• [ ] 👍 Sweep Did Well
• [ ] 👎 Sweep Needs Improvement

  Description

  This PR implements the Linpack benchmark in Rust. The Linpack benchmark is a measure of a computer's floating-point rate of execution. The implementation follows the algorithm used in the Go, JavaScript, and PHP implementations of the Linpack benchmark. The Rust code is placed in rust/linpack/Linpack.rs and includes necessary imports, constants, and functions.

Summary of Changes

• Created rust/linpack/Linpack.rs file
• Implemented Linpack benchmark in Rust, following the algorithm used in the Go, JavaScript, and PHP implementations
• Used rust/primes/Atkin.rs and rust/mandelbrot/Simple.rs as a guide for Rust syntax and style
• Updated rust/benchmark.yml to include the new Rust Linpack benchmark in the benchmark tests
• Added necessary imports, constants, and functions to the Rust Linpack implementation
• Implemented the main function to run the Linpack benchmark and print the results
• Ensured code follows consistent Rust coding conventions and style

Please review and merge this PR.

Fixes #5.

---

🎉 Latest improvements to Sweep:

• Sweep can now passively improve your repository! Check out Rules to learn more.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-ai[bot]]

Rollback Files For Sweep

• [ ] Rollback changes to rust/linpack/Linpack.rs
• [ ] Rollback changes to rust/benchmark.yml

[sweep-ai[bot]]

Apply Sweep Rules to your PR?

• [ ] Apply: All docstrings and comments should be up to date.
• [ ] Apply: Commit messages should clearly describe the purpose of the changes made.
• [ ] Apply: When merging pull requests, make sure to include the branch name and a brief description of the changes.
• [ ] Apply: Code should be properly indented and follow consistent spacing conventions.
• [ ] Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• [ ] Apply: Avoid unnecessary whitespace at the end of lines or empty lines at the end of files.