@see-also-concurrency-caveat[]} + +...@defproc[(hash-domain [hash hash?]) + (listof any/c)]{ +Returns a list of the keys of @scheme[hash] in an unspecified order. + +See @scheme[hash-map] for information about modifying @scheme[hash] +during @scheme[hash-domain]. @see-also-concurrency-caveat[]}+...@defproc[(hash-range [hash hash?]) + (listof any/c)]{ +Returns a list of the values of @scheme[hash] in an unspecified order. + +See @scheme[hash-map] for information about modifying @scheme[hash] +during @scheme[hash-range]. @see-also-concurrency-caveat[]}
I would rename `hash-domain' => 'hash-keys' and 'hash-range' => 'hash-values'. The documentation refers to them this way and 'keys'/'values' are the popular way of talking about hashes. (Also the sequence names you can give to `for' are in-hash-keys and in-hash-values).
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
