bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
Subject: Re: [PATCH] hamt: New module.
Date: Sat, 03 Apr 2021 19:02:42 +0200	[thread overview]
Message-ID: <4067647.8lqFNFinqB@omega> (raw)
In-Reply-To: <20210403092502.1418071-1-marc.nieper+gnu@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

Hi Marc,

> +	hamt: New module.
> +	This module provides (persistent) hash array mapped tries.
> +	* MODULES.html.sh: Add hamt.
> +	* lib/hamt.c: New file.
> +	* lib/hamt.h: New file.
> +	* modules/hamt: New file.
> +	* modules/hamt-tests: New file.
> +	* tests/test-hamt.c: New file.

Would you like to write a bit of documentation for the Gnulib manual
about it? It does not need to copy the extensive comments in hamt.h.
It need only answer the questions:
  - What is a HAMT?
  - When would I (a programmer) make use of it? How does it compare
    to other container data types?
  - What is the Gnulib module name and the include file name?

I think it would fit into the section "Container data types"
https://www.gnu.org/software/gnulib/manual/html_node/Container-data-types.html .

Find attached the start of a diff to add this documentation.

Bruno

[-- Attachment #2: hamt-doc-start.diff --]
[-- Type: text/x-patch, Size: 722 bytes --]

diff --git a/doc/containers.texi b/doc/containers.texi
index 15c915b..6a9b22e 100644
--- a/doc/containers.texi
+++ b/doc/containers.texi
@@ -35,6 +35,9 @@ log
 Gnulib provides several generic container data types.  They can be used
 to organize collections of application-defined objects.
 
+@node Ordinary containers
+@subsection Ordinary container data types
+
 @multitable @columnfractions .15 .5 .1 .1 .15
 @headitem Data type
 @tab Details
@@ -599,6 +602,11 @@ For C++, Gnulib provides a C++ template class for each of these container data t
 @tab @code{"gl_omap.hh"}
 @end multitable
 
+@node Specialized containers
+@subsection Specialized container data types
+
+HAMT ...
+
 @ifnottex
 @unmacro log
 @end ifnottex

  reply	other threads:[~2021-04-03 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  9:25 [PATCH] hamt: New module Marc Nieper-Wißkirchen
2021-04-03 17:02 ` Bruno Haible [this message]
2021-04-03 18:59   ` Marc Nieper-Wißkirchen
2021-04-03 19:55     ` Bruno Haible
2021-04-03 20:32       ` Marc Nieper-Wißkirchen
2021-04-03 21:44         ` Bruno Haible
2021-04-05 13:02 ` Bruno Haible
2021-04-05 13:16   ` Marc Nieper-Wißkirchen
2021-04-05 15:02     ` static analyzers Bruno Haible

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4067647.8lqFNFinqB@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=marc.nieper+gnu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).