search

Hoverbear / old-raft-rs

[Incomplete] A Raft implementation in Rust
https://hoverbear.github.io/raft-rs/raft/
MIT License
266 stars 41 forks source link

moving to stable #112

Open tbg opened 8 years ago

tbg commented 8 years ago

I noticed that raft-rs almost builds on stable (only the socket_timeout feature which is used in a single location requires nightly). The tests don't pass, but I think (but haven't checked) that that's mostly the way we use serde (which can be taken care of). Is getting to stable sooner rather than later interesting or do we not care?

Hoverbear commented 8 years ago

I'd be open towards moving to stable, but don't consider it a huge priority as there is some fun stuff in nightly that we might be able to harness as we refine.

danburkert commented 8 years ago

In theory I support moving to stable, but at this point I don't think it's possible. My understanding is that even if raft can move away from all feature flags, it still requires that all dependencies build on stable as well, right?

danburkert commented 8 years ago

FWIW the work I've been doing on wal and nonblocking capnproto both use a few feature flags.

droundy commented 6 years ago

I would personally prefer to have raft-rs work on stable, although having it be itself stable is higher priority.