I'm thinking about cases where you are using existing java libraries
that you don't want to/can't re-write to have Clojure specific code in
them. I think the rule for dealing with conflicts would be to give me
the value for the String if it's there, if it's not, try to give me
the value for the Keyword that corresponds to the String.
On Oct 13, 9:33 am, Aaron Brooks <[EMAIL PROTECTED]> wrote:
> All,
>
> I would think that changing or wrapping the map would create confusion
> and additional overhead. In my mind the most natural interaction would
> be to provide a way for Java code to create references to keywords:
>
> x = map.get(clojure.keyword("foo")); // ... or something along
> these lines
>
> I'll take a look at the Clojure code but I expect that this would be
> easy to do. Any methods that try to mash strings and keywords into the
> same space seems like it would be mostly application specific as it
> would need to resolve cases where identically named keywords and
> strings exist. The only safe cases would be when a map exclusively
> contains strings or keywords.
>
> Naturally, wouldn't want to demand that you don't want to do what, in
> fact, you want to do. I think Clojure would best cater to the safe,
> predictable cases and leave the hairy cases up to individual
> developers.
>
> -Aaron
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
