This is an automated email from the ASF dual-hosted git repository.

chaokunyang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-fury-site.git

commit 8a4aeb88420c8cfd8d81c0453a74419f963fb07e
Author: chaokunyang <[email protected]>
AuthorDate: Sat Apr 13 05:59:58 2024 +0000

    🔄 synced local 'docs/specification/' with remote 'docs/specification/'
---
 docs/specification/xlang_serialization_spec.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/specification/xlang_serialization_spec.md 
b/docs/specification/xlang_serialization_spec.md
index e01ec92..15094c5 100644
--- a/docs/specification/xlang_serialization_spec.md
+++ b/docs/specification/xlang_serialization_spec.md
@@ -29,11 +29,9 @@ also introduce more complexities compared to static 
serialization frameworks. So
 - int16: a 16-bit signed integer.
 - int32: a 32-bit signed integer.
 - var_int32: a 32-bit signed integer which use fury var_int32 encoding.
-- fixed_int32: a 32-bit signed integer which use two's complement encoding.
 - int64: a 64-bit signed integer.
 - var_int64: a 64-bit signed integer which use fury PVL encoding.
 - sli_int64: a 64-bit signed integer which use fury SLI encoding.
-- fixed_int64: a 64-bit signed integer which use two's complement encoding.
 - float16: a 16-bit floating point number.
 - float32: a 32-bit floating point number.
 - float64: a 64-bit floating point number including NaN and Infinity.
@@ -53,6 +51,7 @@ also introduce more complexities compared to static 
serialization frameworks. So
   interoperability between array and list.
     - array: multidimensional array which every sub-array can have different 
sizes but all have same type.
     - bool_array: one dimensional int16 array.
+    - int8_array: one dimensional int8 array.
     - int16_array: one dimensional int16 array.
     - int32_array: one dimensional int32 array.
     - int64_array: one dimensional int64 array.


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

Reply via email to