With Chroutine, you can easily develop highly concurrent programs in C++ and write code with synchronization semantics.
Create a chroutine is very simple:
ENGIN.create_chroutine([](void *){
while (1) {
SPDLOG(INFO, "hello Chroutine 1, looping");
SLEEP(1000);
}
}, nullptr);
ENGIN.create_chroutine([](void *){
SPDLOG(INFO, "hello Chroutine 2");
SLEEP(1000);
SPDLOG(INFO, "hello Chroutine 2, exit now");
}, nullptr);
You can also run the examples and see the code to learn more:
├── channel_example
│ ├── CMakeLists.txt
│ └── test_channel.cpp
├── chutex_example
│ ├── CMakeLists.txt
│ └── test_chutex.cpp
├── CMakeLists.txt
├── http_client_example
│ ├── CMakeLists.txt
│ └── test_main.cpp
├── raw_tcp_client_example
│ ├── CMakeLists.txt
│ └── raw_tcp_client_example.cpp
├── rpc_example
│ ├── CMakeLists.txt
│ ├── test_client
│ │ ├── CMakeLists.txt
│ │ ├── test_client.cpp
│ │ ├── test_client.hpp
│ │ └── test_client_main.cpp
│ ├── test_server.cpp
│ ├── test_server.hpp
│ └── test_server_main.cpp
├── sched_test
│ ├── CMakeLists.txt
│ └── test_sched.cpp
├── stack_test
│ ├── CMakeLists.txt
│ └── test_stack.cpp
├── tcp_echo_server_example
│ ├── CMakeLists.txt
│ └── test_echo_server.cpp
├── test_chroutine.cpp
└── timer_example
├── CMakeLists.txt
└── test_timer.cpp
$ cd examples/build
$ ./configure.sh
$ cd build
$ make- CentOS Linux release 7.4.1708, x86_64
- gcc (GCC) 4.8.5 20150623
my system: CentOS Linux release 7.4.1708
sudo yum install autoconf automake autogen libtool shtool build-essential pkg-config libgflags-dev libgtest-dev clang libc++-devgit clone https://github.com/grpc/grpc
cd grpc
git submodule update --init
make
[sudo] make installif get configure error:
configure in doc/example fails with "cannot find install-sh, install.sh, or shtool in "." "./.." "./../..""try:
cd third_party/protobuf
autoreconf -i -v -fgit submodule update --init will download third party code, try to download yourself and put them in right place if failed in China:
Submodule 'third_party/abseil-cpp' (https://github.com/abseil/abseil-cpp) registered for path 'third_party/abseil-cpp'
Submodule 'third_party/benchmark' (https://github.com/google/benchmark) registered for path 'third_party/benchmark'
Submodule 'third_party/bloaty' (https://github.com/google/bloaty.git) registered for path 'third_party/bloaty'
Submodule 'third_party/boringssl' (https://github.com/google/boringssl.git) registered for path 'third_party/boringssl'
Submodule 'third_party/boringssl-with-bazel' (https://boringssl.googlesource.com/boringssl) registered for path 'third_party/boringssl-with-bazel'
Submodule 'third_party/cares/cares' (https://github.com/c-ares/c-ares.git) registered for path 'third_party/cares/cares'
Submodule 'third_party/gflags' (https://github.com/gflags/gflags.git) registered for path 'third_party/gflags'
Submodule 'third_party/googletest' (https://github.com/google/googletest.git) registered for path 'third_party/googletest'
Submodule 'third_party/protobuf' (https://github.com/google/protobuf.git) registered for path 'third_party/protobuf'
Submodule 'third_party/zlib' (https://github.com/madler/zlib) registered for path 'third_party/zlib'it was build but not installed:
cd third_party/protobuf
sudo make installcd proto_def
sh gen.sh test.protoYou should see four files:
├── proto_code
│ ├── test.grpc.pb.cc
│ ├── test.grpc.pb.h
│ ├── test.pb.cc
│ └── test.pb.h
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent