ThisingL opened a new pull request, #2868: URL: https://github.com/apache/fory/pull/2868
<!-- **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? The xlang serialization specification has been updated with significant improvements for compile-time code generation and cross-language compatibility. Key motivations: 1. Clearer field categorization: The new 6-group field ordering provides better structure and makes compile-time implementation more straightforward 2. Consistent hashing: New murmurhash3-based algorithm ensures deterministic type hash calculation across all language implementations 3. Simplified serialization logic: Each field type group now has explicit serialization rules, reducing ambiguity <!-- Describe the purpose of this PR. --> ## What does this PR do? Updates the Go codegen implementation to align with the xlang serialization specification , ensuring full compatibility with reflection-based serialization and other language implementations. <!-- Describe the details of this PR. --> ## Related issues More details can see in pr (#2793) <!-- Is there any related issue? If this PR closes them you say say fix/closes: - #xxxx0 - #xxxx1 - Fixes #xxxx2 --> ## Does this PR introduce any user-facing change? <!-- If any user-facing interface changes, please [open an issue](https://github.com/apache/fory/issues/new/choose) describing the need to do so and update the document if necessary. Delete section if not applicable. --> - [ ] Does this PR introduce any public API change? - [ ] Does this PR introduce any binary protocol compatibility change? ## 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]
