From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id PAA21190; Wed, 1 Aug 2001 15:12:42 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id PAA21186 for ; Wed, 1 Aug 2001 15:12:42 +0200 (MET DST) Received: from beaune.inria.fr (beaune.inria.fr [128.93.8.3]) by nez-perce.inria.fr (8.11.1/8.10.0) with ESMTP id f71DCfn03068 for ; Wed, 1 Aug 2001 15:12:41 +0200 (MET DST) Received: by beaune.inria.fr (8.8.8/1.1.22.3/14Sep99-0328PM) id PAA0000004246; Wed, 1 Aug 2001 15:12:41 +0200 (MET DST) Date: Wed, 1 Aug 2001 15:12:41 +0200 (MET DST) From: Damien Doligez Message-Id: <200108011312.PAA0000004246@beaune.inria.fr> To: caml-list@inria.fr Subject: Re: [Caml-list] "super-compaction" of values Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk >From: Markus Mottl >would return "la" unchanged but "lb" would now share the common structure >with list_a (= la) (also when inserted in any other order). Look for "hash-consing" in the (LISP) literature. But doing it for arbitrary types looks complex. > * Support automatic GC? Or should the user make sure that possible > administrative memory overhead is prevented by telling "'a t" that > some value need not be remembered for sharing with further values > anymore. The "automatic" version is probably less efficient and > much more complicated. Module Weak is here to help you solve this problem. -- Damien ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr