[coro_rpc] fix rest_rpc_protocol_server (#354)

alibaba · Jul 6, 2023 · d297154 · d297154
1 parent d972193
commit d297154
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/README.md b/README.md
@@ -379,7 +379,7 @@ These CMake options is used for yalantinglibs developing/installing itself. They
 |BUILD_UNIT_TESTS|ON|
 |BUILD_*(BUILD_CORO_RPC, BUILD_STRUCT_PACK etc)|ON|
 |COVERAGE_TEST|OFF|
-|GENERATE_BENCHMARK_DATA|OFF|
+|GENERATE_BENCHMARK_DATA|ON|
 |CORO_RPC_USE_OTHER_RPC|ON|
 
 ### ylt config option

diff --git a/src/coro_rpc/examples/user_defined_rpc_protocol/rest_rpc/config/rest_rpc_protocol.hpp b/src/coro_rpc/examples/user_defined_rpc_protocol/rest_rpc/config/rest_rpc_protocol.hpp
@@ -17,9 +17,9 @@
 
 #include <variant>
 
-#include "coro_io/io_context_pool.hpp"
-#include "coro_rpc/coro_rpc/router.hpp"
 #include "msgpack_protocol.hpp"
+#include "ylt/coro_io/io_context_pool.hpp"
+#include "ylt/coro_rpc/impl/router.hpp"
 
 namespace coro_rpc {
 namespace protocol {

diff --git a/website/docs/en/guide/what_is_yalantinglibs.md b/website/docs/en/guide/what_is_yalantinglibs.md
@@ -379,7 +379,7 @@ These CMake options is used for yalantinglibs developing/installing itself. They
 |BUILD_UNIT_TESTS|ON|
 |BUILD_*(BUILD_CORO_RPC, BUILD_STRUCT_PACK etc)|ON|
 |COVERAGE_TEST|OFF|
-|GENERATE_BENCHMARK_DATA|OFF|
+|GENERATE_BENCHMARK_DATA|ON|
 |CORO_RPC_USE_OTHER_RPC|ON|
 
 ### ylt config option

diff --git a/website/docs/zh/guide/what_is_yalantinglibs.md b/website/docs/zh/guide/what_is_yalantinglibs.md
@@ -344,7 +344,7 @@ async_simple是一个C++20协程库，提供各种轻量且易用的组件，帮
 |BUILD_UNIT_TESTS|ON|
 |BUILD_*(BUILD_CORO_RPC, BUILD_STRUCT_PACK 等)|ON|
 |COVERAGE_TEST|OFF|
-|GENERATE_BENCHMARK_DATA|OFF|
+|GENERATE_BENCHMARK_DATA|ON|
 |CORO_RPC_USE_OTHER_RPC|ON|
 
 ### ylt 配置项

diff --git a/website/docs/zh/struct_pack/struct_pack_type_system.md b/website/docs/zh/struct_pack/struct_pack_type_system.md
@@ -333,7 +333,7 @@ assert(res->nick_name.has_value()==false);
 注意，在修改字段的过程中，如果想保证兼容性，必须遵循只增不改原则：
 
 1. 只增：新添加的字段必须是`struct_pack::compatible<T, version_number>`类型，且version_number必须大于上一次填入的版本号。
-2. 不该：不修改/删除任何一个旧的字段。
+2. 不改：不修改/删除任何一个旧的字段。
 
 如果删去/修改了旧的`struct_pack::compatible<T, version_number>`类型，或者新增的`struct_pack::compatible<T, version_number>`类型版本号不是递增的，则两个结构体不能相互兼容，并且在两个不同版本之间序列化/反序列化的行为是**未定义**的！