You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 5952 Reporter: oliver Status: acknowledged (set by @damiendoligez on 2013-06-19T12:02:19Z) Resolution: open Priority: normal Severity: feature Version: 4.00.0 Category: standard library Has duplicate:#3877 Monitored by:@gasche mehdi
Bug description
Hashtbl module should have a function, that give back a list of all keys of a table.
Hashtbl.keys should report every key only once!
I coded this very often myself.
I think other people also do.
(In contrary a Hashtbl.values might not be that necessary, because the Hashtbl.keys-reult plus some list stuff, or the Hashtbl.fold function can then be used. But Hashtbl.keys needs more coding effort.)
The text was updated successfully, but these errors were encountered:
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
Original bug ID: 5952
Reporter: oliver
Status: acknowledged (set by @damiendoligez on 2013-06-19T12:02:19Z)
Resolution: open
Priority: normal
Severity: feature
Version: 4.00.0
Category: standard library
Has duplicate: #3877
Monitored by: @gasche mehdi
Bug description
Hashtbl module should have a function, that give back a list of all keys of a table.
Hashtbl.keys should report every key only once!
I coded this very often myself.
I think other people also do.
(In contrary a Hashtbl.values might not be that necessary, because the Hashtbl.keys-reult plus some list stuff, or the Hashtbl.fold function can then be used. But Hashtbl.keys needs more coding effort.)
The text was updated successfully, but these errors were encountered: