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/fory.git
The following commit(s) were added to refs/heads/main by this push:
new 990a1abd1 chore: fix typos (#2424)
990a1abd1 is described below
commit 990a1abd18133704c87b3cb66d549d3db24d6448
Author: co63oc <[email protected]>
AuthorDate: Fri Jul 18 14:32:57 2025 +0800
chore: fix typos (#2424)
<!--
**Thanks for contributing to 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 (incubating)** community has restrictions on the
naming of pr titles. You can also find instructions in
[CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md).
- 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.
-->
## What does this PR do?
fix typos
<!-- Describe the purpose of this PR. -->
## Related issues
<!--
Is there any related issue? Please attach here.
- #xxxx0
- #xxxx1
- #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.
-->
- [ ] 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.
-->
---
bazel/arrow/pyarrow_configure.bzl | 2 +-
ci/format.sh | 2 +-
docs/guide/java_serialization_guide.md | 4 ++--
docs/specification/java_serialization_spec.md | 2 +-
docs/specification/xlang_serialization_spec.md | 2 +-
go/fory/fory.go | 2 +-
6 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/bazel/arrow/pyarrow_configure.bzl
b/bazel/arrow/pyarrow_configure.bzl
index ecb82c5f6..3c2207059 100644
--- a/bazel/arrow/pyarrow_configure.bzl
+++ b/bazel/arrow/pyarrow_configure.bzl
@@ -132,7 +132,7 @@ def _symlink_genrule_for_dir(
dest_dir: directory to create symlink in.
genrule_name: genrule name.
src_files: list of source files instead of src_dir.
- dest_files: list of corresonding destination files.
+ dest_files: list of corresponding destination files.
Returns:
genrule target that creates the symlinks.
diff --git a/ci/format.sh b/ci/format.sh
index 56fe26aa8..b80b26a9d 100755
--- a/ci/format.sh
+++ b/ci/format.sh
@@ -11,7 +11,7 @@ set -euox pipefail
SHELLCHECK_VERSION_REQUIRED="0.7.1"
install_nodejs() {
- #intall nodejs
+ #install nodejs
filename="node-v16.17.1-linux-x64"
pkg="$filename.tar.gz"
NODE_URL="https://nodejs.org/dist/v16.17.1/$pkg";
diff --git a/docs/guide/java_serialization_guide.md
b/docs/guide/java_serialization_guide.md
index 3d1907184..deb32f0d3 100644
--- a/docs/guide/java_serialization_guide.md
+++ b/docs/guide/java_serialization_guide.md
@@ -701,7 +701,7 @@ Note that this implementation provides better performance
at the cost of flexibi
When implementing a serializer for a custom Map type, you must extend
`MapSerializer` or `AbstractMapSerializer`. The key difference between these
two is that `AbstractMapSerializer` can serialize a class which has a map-like
structure but is not a java Map subtype.
-Similiar to collection serializer, this is a special parameter
`supportCodegenHook` needs be configured:
+Similar to collection serializer, this is a special parameter
`supportCodegenHook` needs be configured:
- When `true`:
- Enables optimized access to map elements and JIT compilation for better
performance
@@ -710,7 +710,7 @@ Similiar to collection serializer, this is a special
parameter `supportCodegenHo
- Recommended for most maps
- When `false`:
- - Uses interfaced-based element access and dynamic serializer dispatch for
elements, which have higer cost
+ - Uses interfaced-based element access and dynamic serializer dispatch for
elements, which have higher cost
- More flexible for custom map types
- Required when map has special serialization needs
- Handles complex map implementations
diff --git a/docs/specification/java_serialization_spec.md
b/docs/specification/java_serialization_spec.md
index 3a8d4bbe5..2aa12b5f2 100644
--- a/docs/specification/java_serialization_spec.md
+++ b/docs/specification/java_serialization_spec.md
@@ -393,7 +393,7 @@ which will be encoded by elements header, each use one bit:
- If the collection has null, use the second bit `0b10` of the header to flag
it. If ref tracking is enabled for this
element type, this flag is invalid.
- If the collection element types are not declared type, use the 3rd bit
`0b100` of the header to flag it.
-- If the collection element types are different, use the 4rd bit `0b1000`
header to flag it.
+- If the collection element types are different, use the 4th bit `0b1000`
header to flag it.
By default, all bits are unset, which means all elements won't track ref, all
elements are same type, not null and
the actual element is the declared type in the custom class field.
diff --git a/docs/specification/xlang_serialization_spec.md
b/docs/specification/xlang_serialization_spec.md
index 58ac5778b..66ced9319 100644
--- a/docs/specification/xlang_serialization_spec.md
+++ b/docs/specification/xlang_serialization_spec.md
@@ -615,7 +615,7 @@ which will be encoded by elements header, each use one bit:
- If the elements have null, use the second bit `0b10` of the header to flag
it. If ref tracking is enabled for this
element type, this flag is invalid.
- If the element types are not the declared type, use the 3rd bit `0b100` of
the header to flag it.
-- If the element types are different, use the 4rd bit `0b1000` header to flag
it.
+- If the element types are different, use the 4th bit `0b1000` header to flag
it.
By default, all bits are unset, which means all elements won't track ref, all
elements are same type, not null and
the actual element is the declared type in the custom type field.
diff --git a/go/fory/fory.go b/go/fory/fory.go
index f3ae6ad7a..06bc2d6cf 100644
--- a/go/fory/fory.go
+++ b/go/fory/fory.go
@@ -356,7 +356,7 @@ func (f *Fory) Deserialize(buf *ByteBuffer, v interface{},
buffers []*ByteBuffer
isCallBackFlag := bitmap&CallBackFlag == CallBackFlag
if isCallBackFlag {
if buffers == nil {
- return fmt.Errorf("uffers shouldn't be null when the
serialized stream is " +
+ return fmt.Errorf("buffers shouldn't be null when the
serialized stream is " +
"produced with buffer_callback not null")
}
f.buffers = buffers
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
