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

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


    from ec7d639c9 🔄 synced local 'docs/specification/' with remote 
'docs/specification/'
     new 6fc7732e6 🔄 synced local 'docs/specification/' with remote 
'docs/specification/'
     new 9792ff646 🔄 created local 'docs/compiler/' from remote 'docs/compiler/'
     new c29fef4d4 🔄 synced local 'static/img/benchmarks/' with remote 
'docs/benchmarks/'

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 docs/compiler/_category_.json                  |    4 +
 docs/compiler/compiler-guide.md                |  612 ++++++++++++
 docs/compiler/fdl-syntax.md                    | 1188 ++++++++++++++++++++++++
 docs/compiler/generated-code.md                |  828 +++++++++++++++++
 docs/compiler/index.md                         |  206 ++++
 docs/compiler/proto-vs-fdl.md                  |  507 ++++++++++
 docs/compiler/type-system.md                   |  449 +++++++++
 docs/specification/xlang_serialization_spec.md |   12 +-
 docs/specification/xlang_type_mapping.md       |  110 +--
 static/img/benchmarks/cpp/README.md            |   24 +-
 static/img/benchmarks/cpp/throughput.png       |  Bin 52502 -> 48028 bytes
 11 files changed, 3867 insertions(+), 73 deletions(-)
 create mode 100644 docs/compiler/_category_.json
 create mode 100644 docs/compiler/compiler-guide.md
 create mode 100644 docs/compiler/fdl-syntax.md
 create mode 100644 docs/compiler/generated-code.md
 create mode 100644 docs/compiler/index.md
 create mode 100644 docs/compiler/proto-vs-fdl.md
 create mode 100644 docs/compiler/type-system.md


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

Reply via email to