From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Enge <andreas@enge.fr>
Subject: Re: [PATCH] Add cereal + sparsehash
Date: Wed, 2 Dec 2015 09:48:21 +0100
Message-ID: <20151202084821.GA6872@debian.eduroam.u-bordeaux.fr>
References: <idjvb8oapmi.fsf@bimsb-sys02.mdc-berlin.net>
	<20151130200606.GD10869@debian>
	<idj8u5ea1op.fsf@bimsb-sys02.mdc-berlin.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50903)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1a435d-0003Tb-7j
	for guix-devel@gnu.org; Wed, 02 Dec 2015 03:48:41 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1a435Y-0000I6-8i
	for guix-devel@gnu.org; Wed, 02 Dec 2015 03:48:41 -0500
Received: from mout.kundenserver.de ([217.72.192.74]:52622)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1a435X-0000I1-Vv
	for guix-devel@gnu.org; Wed, 02 Dec 2015 03:48:36 -0500
Content-Disposition: inline
In-Reply-To: <idj8u5ea1op.fsf@bimsb-sys02.mdc-berlin.net>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>

On Tue, Dec 01, 2015 at 11:44:06AM +0100, Ricardo Wurmus wrote:
> I’d like to do this, but I’m pretty bad at naming things.  How about a
> new module “datastructures.scm” where this could comfortably fit in?

I also did not know a good name, so did not suggest anything concrete...
I like your suggestion; we could rename boost.scm to datastructures.scm
and move the hash package there.

What do you think?

Andreas