I just want to say this is quite intriguing, I think it would be very
appealing to have a standard library built on this idea (a modification of
Temptory?), perhaps with some more fleshed out examples of IO splits before
really digging in.
On Thu, Mar 21, 2019, 8:18 PM gmhwxi wrote:
>
> One
This looks interesting, will follow up if/when I will got something from it
:)
--
You received this message because you are subscribed to the Google Groups
"ats-lang-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
The problem, as I understand it, is very common in practice.
The solution you outlined in Haskell is what I call a "closed-world"
solution.
What do I mean by a "closed-world" solution? For instance, in LISP, there
are a lot of functions that are like: creating a resource, using it
and then
Thanks for directions to investigate!
>
--
You received this message because you are subscribed to the Google Groups
"ats-lang-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ats-lang-users+unsubscr...@googlegroups.com.
To view this discussion
Thanks!
There are quite a few issues mentioned in your message. Let me address them
separately.
>>The point of `IO` data type in pure language is not about precision. It's
purpose is to control where the source and distribution of side-effects in
your program.
In haskell, it is done in an
