Well, more seriously, I would be against any facility that prevents me from
doing something potentially useful that I might want to do. Sprinkling
potential problem spots with io! might make more sense in an application
than a library.
On Thu, May 30, 2013 at 1:27 PM, Gary Trakhman wrote:
> Wha
What if you really want the 'bad' effects on retries? We need io! versions
and non-io! versions of side-effect functions :-)
On Thu, May 30, 2013 at 1:24 PM, Sean Corfield wrote:
> On Thu, May 30, 2013 at 1:10 AM, Alex Baranosky
> wrote:
> > Do any of you ever use io! ? I've never used it, bu
On Thu, May 30, 2013 at 1:10 AM, Alex Baranosky
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
> wrote:
>> The point is to mark side-effecting code so that you can'
Thanks guys. Now i understand its for "marking" functions containing io so
that they blow up if they are used inside transactions. I am still
learning clojure and i have decided to take some time to understand every
function in the core API.
Josh.
On Thu, May 30, 2013 at 11:10 AM, Alex Baranosk
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:
> 2013/5/30 Josh Kamau
>
>> Whats the point of using io! inside dosync if all it does is make
2013/5/30 Josh Kamau
> Whats the point of using io! inside dosync if all it does is make an
> exception to be thrown?
The point is to mark side-effecting code so that you can't accidentally use
it in a transaction.
--
MK
http://github.com/michaelklishin
http://twitter.com/michaelklishin
--
Yep,wrap code that has side effects, prevent it to be evaluated in STM
transaction.
2013/5/30 Maik Schünemann
> I think It stops other code to wrap around the code with the explicit io!
> call.
> Its declarative way of saying: I am doing io! DONT USE me inside a dosync.
>
>
> On Thu, May 30, 20
I think It stops other code to wrap around the code with the explicit io!
call.
Its declarative way of saying: I am doing io! DONT USE me inside a dosync.
On Thu, May 30, 2013 at 7:47 AM, Josh Kamau wrote:
> Hi ;
>
> Whats the point of using io! inside dosync if all it does is make an
> excepti
Hi ;
Whats the point of using io! inside dosync if all it does is make an
exception to be thrown? Please someone make me understand.
Regards.
Josh
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googl
