reliable broadcast channel to atomic broadcast channel
Noted that Tokio is a bad idea for async
Designed a C api async
Noted that my too clever by half sfinae code has been obsolted by concepts.
Can make callbacks that can access the full lambda
machinery, while the same machinery is still usable
in C and from C, and thus in rust and lua, and from
rust and lua.
modified: docs/libraries/cpp_automatic_memory_management.md
The magic univeral lowest denominator C code, which can be used by
and make use of, higher level language constructs such as
lambdas, being
(**p)(p, ptrEvent);
Where p points at or into a blob that contains a pointer to
C calling convention code that knows how the blob is structured.
allowing us to structure it arbitarily, apart from information
that the event dispatcher needs to know.
seems, because you typically want to communicate with multiple peers at
the same time.
Minor updates, and moved files to more meaningful locations,
which required updating links.
to the new cool style imitating other successful open
software movements.
But all my navbars are the same navbar. The point of the new
style is to make information readily available.
We will want multiple button bars in the navbar, and possibly a
related materials sidebar. Or perhaps simply link pages.
We also need to change the introductory paragraph in every page
to the abstract style.
a distributed hash table byzantine fault tolerant
Slight clarification on scalability
Figured out how to make variable length integers that
will be represented in correct order in a patricia
merkle tree.
and a banner.
Broke all my existing markdown builds, because I
have a hundred files that do not fit the new machinery
And now I have to provide navbars for each directory,
and update the mkdocs.sh in each directory
And add a recursive invocation of mkdocs in subdirectories
