Log
-
Lint `empty_enum` is now `empty_enums` by Caio 3 weeks ago
-
Make the id conflict resolution path clearer by Caio 2 months ago
-
Clearer probe_was_incomplete definition by Caio 2 months ago
-
Use Self:: where possible by Caio 2 months ago
-
Add release date to Changelog by Caio 3 months ago
-
Prepare for v1.0.0 💬 by Caio 3 months ago
Experience tells me that as soon as I release this something will pop up so here I am, goading the Fates. The API hasn't changed in a long while, so it isn't much of a concern. Not every dependency is stable, but they rarely change. A paced major version bump simply to update deps is perfectly fine
-
Remove redundant lint 💬 by Caio 4 months ago
> error: lint `clippy::string_to_string` has been removed: `clippy:implicit_clone` covers those cases The implicit_clone lint is enabled
-
Fix debug_assert message by Caio 4 months ago
-
Ensure wrapped errors are Sync by Caio 5 months ago
-
Use format strings where possible by Caio 6 months ago
-
Remove deprecated lint match_on_vec_items 💬 by Caio 6 months ago
The 'indexing-slicing' replacement is way too broad for my taste, so there's nothing to replace it.
-
Fix intra-doc link to Foca::add_broadcast by Caio 6 months ago
-
Enable and fix missing_const_for_fn lint by Caio 9 months ago
-
Use intra-docs links by Caio 10 months ago
-
Upgrade uuid dev-dependency to v1 💬 by Caio 11 months ago
Yay stable targets
-
Move piggyback checks into Message type by Caio 11 months ago
-
Prepare for v0.19.0 release by Caio a year ago
-
Upgrade to bincode 2, still std and serde-based by Caio a year ago
-
Unexpose test methods under cfg test 💬 by Caio a year ago
The `missing_docs` lint now seems to look within `test` cfg too. This is just to appease it.
-
Elide simplistic lifetime annotations by Caio a year ago
-
Upgrade to rand 0.9 by Caio a year ago
-
Only use updates_buf when handling incoming data by Caio a year ago
-
Prepare for v0.18.0 release by Caio a year ago
-
Use choice_buf when announcing to down members 💬 by Caio a year ago
Doesn't really matter which buf is used here since there's no interaction, but choice_buf is the right one to prevent confusion before I properly clean this mess.
-
Properly avoid allocs when refuting suspicion 💬 by Caio a year ago
This patch fixes a case where foca would unecessarily alloc when handling a message. Debug builds would crash under this scenario but went uncaught for a long while because my watchdog simply restarted it :x The data flow is still a tree instead of a graph so things are still sane, but this is starting to look like code from a language without RAII :clown_face:
-
Extract scheduler loop so its easier to grok by Caio a year ago
-
New (unstable) notification on failed probe by Caio a year ago
-
Add parameter to skip broadcasts on apply_many by Caio a year ago
-
Add new, experimental, feture gated notifications 💬 by Caio 2 years ago
This patch introduces Notification::{DataSent,DataReceived} which allows peeking into the interaction between peers without having to deal with traces -
Notification enum now holds references 💬 by Caio 2 years ago
I want to extend notifications without worrying too much about causing allocs for (potentially) unused data Not particularly nice, but I think this is still a better dev experience than slapping a bunch of "on_$something" methods in the Runtime trait with a default no-op impl