From: Benedikt Grundmann <Benedikt-Grundmann@web.de>
To: caml-list@inria.fr
Subject: [Caml-list] Map.iter unspecified order of visiting -- reason?
Date: Tue, 18 Nov 2003 09:49:42 +0100 [thread overview]
Message-ID: <200311180949.42786.Benedikt-Grundmann@web.de> (raw)
To cite the manual of Map:
val iter : (key -> 'a -> unit) -> 'a t -> unit
iter f m applies f to all bindings in map m. f receives the key as first
argument, and the associated value as second argument. The order in which the
bindings are passed to f is unspecified.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Any special reason to do so? I mean the source code actually implements
ordered visiting and it is indeed one of the great advantages of using a Map
instead of a Hashtbl (the other it being sideeffect free). So why not
document / require it to visit the keys in an well defined order with regard
to the ordering function?
Cheers,
Bene
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2003-11-18 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200311180949.42786.Benedikt-Grundmann@web.de \
--to=benedikt-grundmann@web.de \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).