Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the Raft library compatible with no_std environments. #1

Merged
merged 1 commit into from
Oct 6, 2023

Conversation

dzmitry-huba
Copy link
Collaborator

The std target implementation remains unchanged. The majority of changes are switching to using core and alloc where std used to be. The no_std flavor uses no_std compatible collections and synchronization primitives. The thiserror crate doesn't have no_std support hence the error types where reimplemented manually. The code generation for the protobuf is also doesn't have no_std support so to minimize the changes throghout the codebase instead the change contains modified autogenerated wrappers for the Prost generated code.

The std target implementation remains unchanged. The majority of changes are switching to using core and alloc
where std used to be. The no_std flavor uses no_std compatible collections and synchronization primitives.
The thiserror crate doesn't have no_std support hence the error types where reimplemented manually. The code
generation for the protobuf is also doesn't have no_std support so to minimize the changes throghout the
codebase instead the change contains modified autogenerated wrappers for the Prost generated code.
@dzmitry-huba dzmitry-huba merged commit f312b19 into master Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant