On Monday, October 2, 2017 at 11:04:52 PM UTC+2, Didier wrote:
>
> > Even in an impure language such as Common Lisp we frown on such LET forms
>
> True, but as far as I know, in Common Lisp, the condition handler is
> always in scope of where the error happened, so I wouldn't face this
> proble
king outlier significance
amd64 Linux 3.16.0-4-amd64 4 cpu(s)
OpenJDK 64-Bit Server VM 24.121-b00
Runtime arguments: -Dfile.encoding=UTF-8 -XX:+TieredCompilation
-XX:TieredStopAtLevel=1 -XX:-OmitStackTraceInFastThrow
-Dclojure.compile.path=/home/bertschi/GitRepos/Vorlesungen/PS2/target/classes
-
For a lecture I have implemented the write-skew example from Mark
Volkmann's article:
(defn write-skew []
(let [cats (ref 1)
dogs (ref 1)
john (future
(dosync
(when (< (+ @cats @dogs) 3)
(alter cats inc
mary (future
Hi Zach,
you might want to look at this paper explaining how to write a correct
macroexpand-all (which requires a code walker) in Common Lisp:
http://www.merl.com/publications/TR1993-017/
The compiler certainly has to do something like that, but might not do all
of the macroexpansion before sta
Hi Sean,
thanks for the link, but I did look at Elm before and read the papers a
couple month ago ... as far as I remember the implementation somewhat
follows FrTime/Flapjax, but with an additional async expression, which does
not prevent glitches.
Best,
Nils
On Tuesday, September 3, 2
Hi David,
On Tuesday, September 3, 2013 5:28:13 PM UTC+2, David Nolen wrote:
>
> On Tue, Sep 3, 2013 at 10:47 AM, bertschi
>
> > wrote:
>
>> As far as I know, Haskell has Chan data types in its concurrency
>> extensions, but I have never seen them in FRP
Hi,
thanks for your remarks.
@Timothy: Yes, looks like I mis-understand the main motivation for
core.async or I'm just not used to see my programs as an assembly like
sending data boxes around ;-)
On Tuesday, September 3, 2013 4:20:19 PM UTC+2, David Nolen wrote:
>
> Which also creates a resou
Hi,
recently I got interested core.async (also thanks to great blog post such
as the ones by David Nolen) and wanted to understand better how it compares
to other reactive libraries, in particular coming from the research on
Functional Reactive Programming (FRP).
Compared to FRP, core.async ap
