Skip to content

Optimize bytes_to_u64#194

Merged
leynos merged 3 commits intomainfrom
codex/optimize-bytes_to_u64-implementation
Jul 7, 2025
Merged

Optimize bytes_to_u64#194
leynos merged 3 commits intomainfrom
codex/optimize-bytes_to_u64-implementation

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jul 6, 2025

Summary

  • remove byteorder dependency
  • optimise bytes_to_u64 using direct slice parsing
  • update docs example to show new approach
  • fix formatting

Testing

  • make fmt
  • make lint
  • make test
  • nixie *.md **/*.md

https://chatgpt.com/codex/tasks/task_e_686a872b0e648322b158f6130fc906d1

Summary by Sourcery

Remove the byteorder dependency and replace cursor-based parsing in bytes_to_u64 with direct slice-to-integer conversions, and update documentation examples and formatting accordingly.

Enhancements:

  • Optimize bytes_to_u64 by using a generic parse_bytes function and direct array conversions instead of io::Cursor and byteorder APIs
  • Eliminate byteorder crate usage throughout the codebase

Build:

  • Remove byteorder from Cargo.toml dependencies

Documentation:

  • Update documentation examples to use slice.try_into() and from_be_bytes/from_le_bytes instead of byteorder methods
  • Fix minor formatting in the multi-layered testing strategy document

Replace Cursor and ReadBytesExt with direct byte slice parsing using from_be_bytes/from_le_bytes. Removes byteorder dependency and updates docs.
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jul 6, 2025

Reviewer's Guide

This PR streamlines length‐prefix parsing by removing the byteorder dependency, refactors bytes_to_u64 to use direct slice conversions via parse_bytes and native from_be_bytes/from_le_bytes, updates documentation examples to match the new approach, and cleans up formatting across markdown files.

Class diagram for removal of byteorder dependency

classDiagram
    class byteorder {
        -BigEndian
        -LittleEndian
        -ReadBytesExt
    }
    class frame {
        -byteorder dependency removed
    }
    frame --|> byteorder : removed
Loading

File-Level Changes

Change Details Files
Refactor bytes_to_u64 to use direct slice parsing
  • Replace Cursor-based reads with direct index and parse_bytes helper
  • Switch to from_be_bytes/from_le_bytes for u{16,32,64} conversions
  • Retain single-byte case via u64::from on bytes[0]
src/frame.rs
Eliminate byteorder dependency and related code
  • Remove byteorder imports and ReadBytesExt usage
  • Delete byteorder crate entry from Cargo.toml and lock file
  • Drop io::Cursor usage for prefix parsing
src/frame.rs
Cargo.toml
Cargo.lock
docs/rust-binary-router-library-design.md
Update documentation examples to use slice-based conversion
  • Refactor frame decoding example to use u32::from_be_bytes
  • Remove outdated ReadBytesExt snippet and import
  • Adjust code snippets to reflect new parsing approach
docs/rust-binary-router-library-design.md
Clean up formatting in markdown docs
  • Normalize spacing around cargo tarpaulin line
  • Fix minor whitespace inconsistencies
docs/multi-layered-testing-strategy.md

Possibly linked issues

  • #0: The PR optimizes bytes_to_u64 by removing io::Cursor and byteorder using direct slice parsing, as suggested in the issue.

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 6, 2025

Summary by CodeRabbit

  • Chores
    • Removed the dependency on the external byteorder library.
  • Documentation
    • Updated documentation to reflect the removal of the byteorder dependency and clarified code examples.
    • Fixed minor formatting in testing strategy documentation.
  • Refactor
    • Simplified internal byte conversion logic for improved clarity and maintainability.

Summary by CodeRabbit

  • Refactor

    • Simplified byte conversion logic to use Rust's standard library methods, removing the dependency on the external byteorder library.
    • Improved internal checks and documentation for byte conversion functions.
  • Chores

    • Removed the byteorder dependency from the project configuration.
  • Documentation

    • Updated documentation to reflect the removal of the byteorder dependency and clarified byte conversion logic.
    • Fixed minor formatting issues in testing strategy documentation.

Walkthrough

The changes remove the dependency on the byteorder crate from the codebase and update all relevant code to use Rust's standard library for byte order conversions. Documentation is also updated to reflect these internal changes, and a minor formatting fix is made in a documentation file.

Changes

File(s) Change Summary
Cargo.toml Removed the byteorder dependency from the dependencies list.
src/frame.rs Refactored bytes_to_u64 to use standard library byte conversions; removed byteorder usage and imports.
docs/rust-binary-router-library-design.md Updated code examples and explanations to use standard library methods instead of byteorder.
docs/multi-layered-testing-strategy.md Fixed minor formatting by removing an extra space after a period.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant FrameModule

    Caller->>FrameModule: bytes_to_u64(slice, size, endian)
    alt Supported size and valid slice
        FrameModule->>FrameModule: Convert slice to array
        FrameModule->>FrameModule: Use from_be_bytes/from_le_bytes
        FrameModule-->>Caller: Return u64 value
    else Unsupported size or short slice
        FrameModule-->>Caller: Return error
    end
Loading

Possibly related issues

Possibly related PRs

Suggested reviewers

  • codescene-delta-analysis

Poem

A crate called byteorder hops away,
Now Rust’s own bytes come out to play.
With slices and arrays, conversions are neat,
No more external crates to greet!
Docs are tidied, code is bright—
Rabbits love to keep things light! 🐇✨


📜 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 77fa5cc and 9cd5f84.

📒 Files selected for processing (1)
  • src/frame.rs (2 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
`**/*.rs`: Comment why, not what. Explain assumptions, edge cases, trade-offs, o...

**/*.rs: Comment why, not what. Explain assumptions, edge cases, trade-offs, or complexity. Don't echo the obvious.
Comments must use en-GB-oxendict spelling and grammar.
Function documentation must include clear examples.
Every module must begin with a module level (//!) comment explaining the module's purpose and utility.
Document public APIs using Rustdoc comments (///) so documentation can be generated with cargo doc.
Place function attributes after doc comments.
Do not use return in single-line functions.
Use predicate functions for conditional criteria with more than two branches.
Lints must not be silenced except as a last resort.
Lint rule suppressions must be tightly scoped and include a clear reason.
Prefer expect over allow.
Prefer .expect() over .unwrap().
Clippy warnings MUST be disallowed.
Fix any warnings emitted during tests in the code itself rather than silencing them.
Where a function is too long, extract meaningfully named helper functions adhering to separation of concerns and CQRS.
Where a function has too many parameters, group related parameters in meaningfully named structs.
Where a function is returning a large error consider using Arc to reduce the amount of data returned.
Write unit and behavioural tests for new functionality. Run both before and after making any change.
Prefer immutable data and avoid unnecessary mut bindings.
Handle errors with the Result type instead of panicking where feasible.
Avoid unsafe code unless absolutely necessary and document any usage clearly.

📄 Source: CodeRabbit Inference Engine (AGENTS.md)

List of files the instruction was applied to:

  • src/frame.rs
`**/*.rs`: * Seek to keep the cyclomatic complexity of functions no more than 12...

**/*.rs: * Seek to keep the cyclomatic complexity of functions no more than 12.

  • Adhere to single responsibility and CQRS

  • Place function attributes after doc comments.

  • Do not use return in single-line functions.

  • Move conditionals with >2 branches into a predicate function.

  • Avoid unsafe unless absolutely necessary.

  • Every module must begin with a //! doc comment that explains the module's purpose and utility.

  • Comments must use en-GB-oxendict spelling and grammar.

  • Lints must not be silenced except as a last resort.

    • #[allow] is forbidden.
    • Only narrowly scoped #[expect(lint, reason = "...")] is allowed.
    • No lint groups, no blanket or file-wide suppression.
    • Include FIXME: with link if a fix is expected.
  • Use rstest fixtures for shared setup and to avoid repetition between tests.

  • Replace duplicated tests with #[rstest(...)] parameterised cases.

  • Prefer mockall for mocks/stubs.

  • Prefer .expect() over .unwrap()

  • Ensure that any API or behavioural changes are reflected in the documentation in docs/

  • Ensure that any completed roadmap steps are recorded in the appropriate roadmap in docs/

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

  • src/frame.rs
🔇 Additional comments (2)
src/frame.rs (2)

37-42: Well-designed helper function that reduces code duplication.

The parse_bytes helper function elegantly abstracts the common pattern of slicing and converting fixed-size byte arrays to u64. The use of const generics ensures type safety whilst the closure parameter provides flexibility for different conversion methods.


71-79: Excellent refactoring that removes external dependencies.

The match arms now use Rust's native byte conversion methods (from_be_bytes, from_le_bytes) instead of the byteorder crate. This approach is more efficient and reduces dependencies whilst maintaining the same functionality.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in a Comment
  • Commit Unit Tests in branch codex/optimize-bytes_to_u64-implementation

🪧 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 auto-generate unit tests to generate unit tests for 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.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @leynos - I've reviewed your changes and they look great!

Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments

### Comment 1
<location> `src/frame.rs:55` </location>
<code_context>
 /// let buf = [0x00, 0x10, 0x20, 0x30];
 /// assert_eq!(bytes_to_u64(&buf, 2, Endianness::Big).unwrap(), 0x0010);
 /// ```
+///
+/// # Panics
+/// Panics if a valid `size` is provided but `bytes` is shorter than `size`.
+/// This should never occur as the length check above guards against it.
 pub fn bytes_to_u64(bytes: &[u8], size: usize, endianness: Endianness) -> io::Result<u64> {
     if !matches!(size, 1 | 2 | 4 | 8) {
</code_context>

<issue_to_address>
Documented panic is technically unreachable but could be enforced with debug_assert.

Adding debug_assert!(bytes.len() >= size) before the match would make this invariant explicit and help catch logic errors during development.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread src/frame.rs Outdated
@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jul 6, 2025

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 6, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jul 6, 2025

@sourcery-ai review

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

  • Since you already return an Err when bytes.len() < size, the debug_assert! for slice length is redundant—consider removing it to simplify the code.
  • A small helper or macro for converting the first N bytes into a u64 (e.g. fn parse_bytes<const N: usize>(bytes: &[u8], f: fn([u8; N]) -> u64)) could reduce the repetition across the match arms.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Since you already return an Err when `bytes.len() < size`, the `debug_assert!` for slice length is redundant—consider removing it to simplify the code.
- A small helper or macro for converting the first N bytes into a u64 (e.g. `fn parse_bytes<const N: usize>(bytes: &[u8], f: fn([u8; N]) -> u64)`) could reduce the repetition across the match arms.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jul 6, 2025

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 6, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Remove debug assertion and introduce helper for converting prefix bytes. Improves clarity and reduces repetition.
@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jul 6, 2025

@sourcery-ai review

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @leynos - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@leynos leynos merged commit f416d9b into main Jul 7, 2025
5 checks passed
@leynos leynos deleted the codex/optimize-bytes_to_u64-implementation branch July 7, 2025 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant