Use proper C++ naming conventions for range types #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π― 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 namingByteβUInt8: Changed to follow standard C++ unsigned 8-bit integer namingSingleβFloat: Changed to use more standard C++ float namingDouble: Kept as is (already proper C++ naming)π€ Rationale
The original
SBytename 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 patternsFloat: More common in C++ than "Single"Int16,Int32,Int64,UInt16,UInt32,UInt64namesβ Testing
π References
Fixes #77
π€ Generated with Claude Code