From a01fd16011fe837c83fda062716e392dc0a27a44 Mon Sep 17 00:00:00 2001 From: Jack O'Connor Date: Thu, 10 Sep 2020 17:38:35 -0400 Subject: [PATCH] add some horizontal rules to the C readme --- c/README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/c/README.md b/c/README.md index b6f205b..f7d8cc8 100644 --- a/c/README.md +++ b/c/README.md @@ -71,6 +71,8 @@ void blake3_hasher_init( Initialize a `blake3_hasher` in the default hashing mode. +--- + ```c void blake3_hasher_update( blake3_hasher *self, @@ -80,6 +82,8 @@ void blake3_hasher_update( Add input to the hasher. This can be called any number of times. +--- + ```c void blake3_hasher_finalize( const blake3_hasher *self, @@ -103,6 +107,8 @@ void blake3_hasher_init_keyed( Initialize a `blake3_hasher` in the keyed hashing mode. The key must be exactly 32 bytes. +--- + ```c void blake3_hasher_init_derive_key( blake3_hasher *self, @@ -122,6 +128,8 @@ database at runtime. A good default format for the context string is This function is intended for application code written in C. For language bindings, see `blake3_hasher_init_derive_key_raw` below. +--- + ```c void blake3_hasher_init_derive_key_raw( blake3_hasher *self, @@ -140,6 +148,8 @@ which takes the context as a C string. If you need to use arbitrary bytes as a context string in application code, consider whether you're violating the requirement that context strings should be hardcoded. +--- + ```c void blake3_hasher_finalize_seek( const blake3_hasher *self,