Skip to content

Use char instead of char8_t#8

Merged
MarioIvancik merged 1 commit into
mainfrom
remove_char8_t
Jul 28, 2025
Merged

Use char instead of char8_t#8
MarioIvancik merged 1 commit into
mainfrom
remove_char8_t

Conversation

@MarioIvancik
Copy link
Copy Markdown
Contributor

@MarioIvancik MarioIvancik commented Jul 28, 2025

char8_t is not known by old compilers

Summary by CodeRabbit

  • Refactor
    • Improved type handling for network option settings to ensure compatibility.
  • Chores
    • Added an internal check to confirm system compatibility regarding character size.

@MarioIvancik MarioIvancik requested a review from koudis July 28, 2025 12:35
@MarioIvancik MarioIvancik self-assigned this Jul 28, 2025
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jul 28, 2025

Walkthrough

A static assertion was introduced to ensure that the size of char is 1 byte. Additionally, in the Context class methods createConnection and reconnect, the type cast for the setsockopt call was changed from (char8_t *) to (char *). No other logic or control flow was modified.

Changes

Cohort / File(s) Change Summary
Static Assertion and Type Cast Update
source/Context.cpp
Added a static assertion for char size; changed type cast in setsockopt calls from (char8_t *) to (char *) in two methods.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch remove_char8_t

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
🪧 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 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

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (3)
source/Context.cpp (3)

16-17: static_assert does not guarantee an 8-bit byte – revise the check

sizeof(char) is always 1 by definition, even on targets where a “byte” is wider than 8 bits.
If the intention is to emulate char8_t, assert on the bit-width instead:

+#include <climits>
-static_assert(sizeof(char) == 1, "Size of char must be 1 byte");
+static_assert(CHAR_BIT == 8, "Platform must use 8-bit bytes");

This captures the real requirement and avoids a misleading assertion that can never fail on a conforming implementation.


24-29: Prefer void*/const void* over char* for setsockopt

setsockopt expects a pointer to const void. Casting to char* works but is noisy and may trigger warnings on stricter compilers. A safer, clearer call is:

- if (setsockopt(socket_, IPPROTO_TCP, TCP_NODELAY, (char *)&flag, sizeof(int)) < 0) {
+ if (setsockopt(socket_, IPPROTO_TCP, TCP_NODELAY,
+                reinterpret_cast<const void*>(&flag), sizeof(flag)) < 0) {

Also note the use of sizeof(flag) for readability.


48-52: Duplicate cast issue – apply the same fix in reconnect()

Replicate the reinterpret_cast<const void*>(&flag) change here to keep both call sites consistent and warning-free.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7c1d291 and fdfabbb.

📒 Files selected for processing (1)
  • source/Context.cpp (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: Mayt34
PR: bringauto/transparent-module#1
File: source/external_server_api.cpp:151-162
Timestamp: 2024-10-09T05:03:50.249Z
Learning: In `source/external_server_api.cpp`, within the `destroy` function, the use of `reinterpret_cast` is necessary instead of `static_cast` because using `static_cast` causes compilation errors.
Learnt from: Mayt34
PR: bringauto/transparent-module#1
File: source/external_server_api.cpp:151-162
Timestamp: 2024-10-04T07:15:00.452Z
Learning: In `source/external_server_api.cpp`, within the `destroy` function, the use of `reinterpret_cast` is necessary instead of `static_cast` because using `static_cast` causes compilation errors.
source/Context.cpp (2)

Learnt from: Mayt34
PR: bringauto/transparent-module#1
File: source/external_server_api.cpp:151-162
Timestamp: 2024-10-09T05:03:50.249Z
Learning: In source/external_server_api.cpp, within the destroy function, the use of reinterpret_cast is necessary instead of static_cast because using static_cast causes compilation errors.

Learnt from: Mayt34
PR: bringauto/transparent-module#1
File: source/external_server_api.cpp:151-162
Timestamp: 2024-10-04T07:15:00.452Z
Learning: In source/external_server_api.cpp, within the destroy function, the use of reinterpret_cast is necessary instead of static_cast because using static_cast causes compilation errors.

🧬 Code Graph Analysis (1)
source/Context.cpp (1)
include/Context.hpp (1)
  • Context (12-107)

@MarioIvancik MarioIvancik merged commit da71a5c into main Jul 28, 2025
1 check passed
@koudis koudis deleted the remove_char8_t branch October 17, 2025 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants