-
Notifications
You must be signed in to change notification settings - Fork 35
hashtable API #73
Comments
What do you think about this? |
|
When those functions are given, I'm not sure what the word "map" means (map-map will make me mad!). Other words such as "dict" or "table" or etc is more suitable, aren't they? |
How about having |
I have some alternatives:
idea? |
Indeed! |
@wasabiz @zeptometer
|
Hi, all. Thinking this over for a month, I started to feel like changing dictionaries to object-to-object hashtable is not a bad idea. In the previous reply I complained about that idea by giving two reasons, and now I found they are solvable ones.
I can find only a little uses of dictionary c APIs just by searching current sources codes. It will not require a big change.
Python uses the name "dictionary" to such object. This strongly encourages the change. Please let me know your positions. Thanks. |
Implementation here: picrin-scheme/libpicrin#30 |
I think that is natural extension. Well.. I wish there was way to designate equality: just eq?, eqv?, equal? is enough, like make-hash-table of Common Lisp. |
Hmm... I, kind of, agreed. But actually when you use dictionaries only with symbols you can get performance as nice as eq?-based hash tables. I'm not sure this is the case in future version some more eager optimization process say JIT is landed, though. |
@wasabiz I'm for to make dictionary obj-obj map. If you have plan to introduce keywords to picrin, discuss performance then. |
changed. |
No description provided.
The text was updated successfully, but these errors were encountered: