On Thu, May 30, 2013 at 1:10 AM, Alex Baranosky <alexander.barano...@gmail.com> wrote: > Do any of you ever use io! ? I've never used it, but could see using it if > I had a transaction-heavy application. > > On Wed, May 29, 2013 at 11:43 PM, Michael Klishin > <michael.s.klis...@gmail.com> wrote: >> The point is to mark side-effecting code so that you can't accidentally >> use it in a transaction.
I gather the intent is for *all* side-effecting code to be wrapped in io! so that you can't accidentally use it with STM transactions? The only places in Clojure and its contribs that use this are: * await - clojure.core * await-for - clojure.core * transaction - java.jdbc (deprecated) * db-transaction - java.jdbc It sounds like all inserts and updates in java.jdbc should also be wrapped in io! and I would expect io! to be needed in a lot of other places in Clojure libraries across the board...? -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
