Fix test, format, version to publish

[youknowone]

Summary by CodeRabbit

• Chores

  • Bumped package version to 0.1.1.

• Refactor

  • Streamlined internal data initialization and formatting for improved maintainability without changing runtime behavior or public APIs.

• Tests

  • Enhanced test setup with minor import adjustments to support clearer, more reliable test cases.

No user-facing functionality changes; behavior remains consistent with previous release.

[coderabbitai]

Walkthrough

Version bumped in Cargo.toml. Added a test-only Vec import in src/lib.rs. In src/tables.rs, adjusted static table initializers to slice-based forms, tweaked formatting in to_title match arms, and changed the derived_property module declaration to inline empty form.

Changes

Cohort / File(s)	Summary of Changes
Version bump Cargo.toml	Crate version updated from 0.1.0 to 0.1.1.
Test-scoped import src/lib.rs	Added use alloc::vec::Vec; inside #[cfg(test)] mod tests for test collection usage.
Tables and module formatting src/tables.rs	Converted Lt_table r3/r6 initializers to slice-based forms; minor formatting updates in to_title match arms; changed pub mod derived_property { } to pub mod derived_property {}.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20–30 minutes

Poem

I thump my paws—a tidy hop!
A patch of bytes, a version pop.
Slices trimmed, the tables neat,
Tests now fetch a Vec so sweet.
A module’s braces close in style—
Ship the crate with a rabbit’s smile. 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 0ddc7fe and 8da99ea.

📒 Files selected for processing (3)

• Cargo.toml (1 hunks)
• src/lib.rs (1 hunks)
• src/tables.rs (2 hunks)

🔇 Additional comments (6)

Cargo.toml (1)

3-3: Version bump to 0.1.1 looks good.

Ready for publish from a manifest perspective.

src/lib.rs (1)

103-103: Good fix: bring Vec into scope for no_std tests.

This resolves collect::<Vec<_>>() in the test module without pulling in std.

src/tables.rs (4)

63-63: Generated-table formatting churn only.

Trailing zeros/line wraps unchanged semantically; table lengths remain intact.

Also applies to: 75-75, 80-81

---

90-90: Inline empty module style is fine.

pub mod derived_property {} is equivalent; reduces one newline.

---

95-97: Match-arm formatting only; behavior unchanged.

None => [c, '\0', '\0'] and trailing comma on Some(index) are idiomatic and keep diffs minimal.

---

65-65: BoolTrie r3 and r6 fields are &'static [u64] — confirmed that both slice references match expectations.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-test

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.