I don't know, but it seems like a bad smell that you can't find your
joy by using the built-in state management constructs
( a bad smell in general, not saying on your side or on clojure side )
2010/2/7 James Reeves <weavejes...@googlemail.com>:
> Hi folks,
>
> Would those more knowledgable about Clojure care to weigh in on
> whether it be a good idea to create a custom class inheriting from
> IDeref? I've been considering creating session proxy objects (to be
> later replaced with protocols) that would respond to deref calls, e.g.
>
> (def session
> (proxy [IDeref] []
> (deref [this]
> (read-session (.store this)))
> (store [this]
> {:type ::memory-store})))
>
> Is this a good idea, or is it considered bad practice to use IDeref in
> anything apart from core Clojure concurrently primitives?
>
> - James
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with your
> first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
