urlyy

I'll take it.

@chaokunyang Is ForyJava hasn’t updated the `writeClassInfo` logic for Integer based on `compressInt()` yet? I may need to temporarily disable `RustXlangTest.java`.

> Could we update java implementation in this PR too? I will try.

1. Need to refactor `fory-derive/object/util.rs::compute_struct_version_hash()`. The `typeid` for `i32` is treated as `INT32` at compile time, which causes a version hash mismatch error. 2. `CrossLanguageTest.java` also occurs errors and the...

@chaokunyang Can we modify the format of `version_hash`? The reason is that Rust needs to compute the `version_hash` at compile time for different compression scenarios, which requires calculating **$2^5$** hashes...

1. Currently, ForyRust requires users to use `#[fory(compress_int)]` or `#[fory(compress_int=true/false)]` on a type to set whether `compress_int` is enabled for that type. ForyRust will directly compute the `version_hash` at compile...

Still needs to address #2886 #2887, you can first review my approach and code.

Currently, the behavior of `int::fory_read_data()` is determined by the local `fory`'s `is_compress_int()`. Do we need to change it so that `Serializer#fory_read_data(remote_type_id)` performs different read operations based on the `type_id` that...

> We can support `#fory(compress=False)` for pure rust in this pr, so we don't have to support java annotation or python `field` in this pr OK, I will implement the...

I have a question: It seems that the commit logs in Fory’s history are mostly PR descriptions and not related to the local commits. In your actions, does `Get &...