feat: Add IfToLower and IfToUpper functions for converting ASCII strings to lowercase and uppercase respectively

[sixcolors]

This pull request adds two new functions, IfToLower and IfToUpper, to the codebase. These functions allow for converting ASCII strings to lowercase and uppercase respectively. The functions have been implemented and tested, and benchmarks have been included to compare their performance with the existing ToLower and ToUpper functions.

The target use case is when there is a high probability that the string is already in the correct case.

Summary by CodeRabbit

• New Features
  • Introduced conditional string conversion functions for optimizing text case adjustments.
• Tests
  • Added unit and benchmark tests for the new string conversion functionalities, ensuring performance improvements.

[coderabbitai]

Walkthrough

This update introduces new functions IfToLower and IfToUpper to conditionally convert ASCII strings to lowercase or uppercase, enhancing performance by checking existing case conditions before conversion. It also expands the testing suite with benchmark and unit tests for these functions, including a specific benchmark for IfToLower with origin header type URLs, ensuring efficiency and reliability.

Changes

Files	Changes
strings.go	Added IfToLower and IfToUpper functions Added benchmark tests for custom IfToUpper and IfToLower functions Added benchmark test for IfToLower function with an origin header type URL
strings_test.go	Added unit tests for IfToUpper and IfToLower functions

🐰✨
In a burrow deep and wide,
A rabbit worked with pride.
Strings of letters, high and low,
Now swiftly change, they flow.
To upper, lower, with a hop,
Performance gains that won't stop.
Celebrate, for now, we've shown,
How swiftly text can be grown.
🌟🐇

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between b1e3dbb and 3717ffb.

Files selected for processing (2)

• strings.go (1 hunks)
• strings_test.go (2 hunks)

Additional comments: 2

strings.go (1)

• 29-85: The IfToLower and IfToUpper functions are designed to optimize ASCII string case conversion by checking the string's current case before performing any conversion. This approach is efficient for strings already in the desired case but introduces a limitation for non-ASCII characters due to direct byte manipulation. Consider documenting this limitation or extending support to handle non-ASCII characters more gracefully.

strings_test.go (1)

• 90-103: The unit tests for IfToLower and IfToUpper effectively cover various scenarios, including strings already in the target case, mixed-case strings, and strings fully in the opposite case. To ensure comprehensive coverage, consider adding tests for non-ASCII characters, given the functions' focus on ASCII strings. This addition would help validate the behavior or document the limitations for non-ASCII inputs.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 3717ffb and edefd68.

Files selected for processing (1)

• strings.go (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• strings.go

[sixcolors]

Xeon X5675 Benchmark checking Origin header type string:

[sixcolors]

Apple M2 Max Benchmark checking Origin header type string: