ariesdevil opened a new pull request, #3080:
URL: https://github.com/apache/fory/pull/3080

   <!--
   **Thanks for contributing to Apache Fory™.**
   
   **If this is your first time opening a PR on fory, you can refer to 
[CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md).**
   
   Contribution Checklist
   
       - The **Apache Fory™** community has requirements on the naming of pr 
titles. You can also find instructions in 
[CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md).
   
       - Apache Fory™ has a strong focus on performance. If the PR you submit 
will have an impact on performance, please benchmark it first and provide the 
benchmark result here.
   -->
   
   ## Why?
   
   To support serialization of `i128` and `isize` types in Rust, which are 
needed for cross-language interoperability and broader type coverage.
   
   ## What does this PR do?
   
   This PR adds support for `i128` and `isize` types:
   
   1. **Buffer operations**: Added `write_i128`, `write_isize`, `read_i128`, 
`read_isize` methods to `buffer.rs`
   2. **Type IDs**: Added `INT128` (78) and `ISIZE` (79) type identifiers to 
`types.rs`
   3. **Serializer implementations**: Added `Serializer` and `ForyDefault` 
implementations for `i128` and `isize` in `number.rs`
   
   Note: `isize` is serialized as `i64` for cross-platform compatibility just 
like `usize` since `isize` varies by architecture (32-bit on x86, 64-bit on 
x86_64).
   
   ## Related issues
   
   None
   
   ## Does this PR introduce any user-facing change?
   
   - [x] Does this PR introduce any public API change?
     - Yes, adds new public types support: `i128` and `isize` can now be 
serialized/deserialized
   - [ ] Does this PR introduce any binary protocol compatibility change?
     - No, this adds new type IDs (78, 79) without changing existing protocol
   
   ## Benchmark
   
   <!--
   When the PR has an impact on performance (if you don't know whether the PR 
will have an impact on performance, you can submit the PR first, and if it will 
have impact on performance, the code reviewer will explain it), be sure to 
attach a benchmark data here.
   
   Delete section if not applicable.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to