Implement vector color and ray compatibility
This commit is contained in:
11
README.md
11
README.md
@@ -52,9 +52,12 @@ Running `cargo test --workspace` is intentionally red during the shim stage.
|
||||
## Native implementation progress
|
||||
|
||||
Milestone 04 implementation has begun. `libremetaverse-types` now provides
|
||||
native UUID, incremental CRC-32, and little-endian floating-point byte helpers.
|
||||
UUID protocol bytes use explicit network order while `compat::Guid` conversions
|
||||
preserve the mixed-endian .NET byte-array layout. The remaining Types surfaces
|
||||
stay visibly failure-only until their owning milestone issues are completed.
|
||||
native UUID, incremental CRC-32, little-endian floating-point byte helpers,
|
||||
Vector2/Vector3/Vector3d/Vector4 arithmetic and serialization, Color4 color
|
||||
conversion, and Ray storage. UUID protocol bytes use explicit network order
|
||||
while `compat::Guid` conversions preserve the mixed-endian .NET byte-array
|
||||
layout. Vector and color byte encodings are explicitly little-endian and do not
|
||||
depend on host architecture. The remaining Types surfaces stay visibly
|
||||
failure-only until their owning milestone issues are completed.
|
||||
The controlled audit aggregates every expected failure by standardized C#
|
||||
member ID and rejects unrelated fixture, assertion, compile, or symbol errors.
|
||||
|
||||
Reference in New Issue
Block a user