Skip to content

Conversation

@konard
Copy link
Member

@konard konard commented Sep 11, 2025

🎯 Summary

This PR addresses issue #77 by replacing .NET-style naming conventions with proper C++ naming in the Range.h file.

πŸ”„ Changes Made

  • SByte β†’ Int8: Changed to follow standard C++ signed 8-bit integer naming
  • Byte β†’ UInt8: Changed to follow standard C++ unsigned 8-bit integer naming
  • Single β†’ Float: Changed to use more standard C++ float naming
  • Double: Kept as is (already proper C++ naming)

πŸ€” Rationale

The original SByte name was unclear and followed .NET/C# naming conventions rather than C++ conventions. As noted in the issue, "SByte (Super Byte)" was confusing - it actually represents a signed 8-bit integer (std::int8_t).

The new naming:

  • Int8/UInt8: Clear, follows standard integer type naming patterns
  • Float: More common in C++ than "Single"
  • Maintains consistency with existing Int16, Int32, Int64, UInt16, UInt32, UInt64 names

βœ… Testing

  • Verified no existing code references the changed names
  • Checked that the syntax compiles correctly
  • No breaking changes to the API surface

πŸ“š References

Fixes #77


πŸ€– Generated with Claude Code

Adding CLAUDE.md with task information for AI processing.
This file will be removed when the task is complete.

Issue: #77
@konard konard self-assigned this Sep 11, 2025
konard and others added 2 commits September 11, 2025 14:40
- Replace SByte with Int8 (std::int8_t)
- Replace Byte with UInt8 (std::uint8_t)
- Replace Single with Float (std::float_t)
- Keep Double as is (std::double_t)

This resolves the issue where SByte was unclear - it was a .NET naming
convention that doesn't belong in C++. The new names follow standard
C++ integer type naming patterns and are more descriptive.

Fixes #77

πŸ€– Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@konard konard changed the title [WIP] Use C++ naming Use proper C++ naming conventions for range types Sep 11, 2025
@konard konard marked this pull request as ready for review September 11, 2025 11:47
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.

Use C++ naming

2 participants