typochon @typochon@functional.cafe

@otini https://www.youtube.com/watch?v=ThVdNWmW8ok 😏

I successfully managed to bring the number of reduce/reduce conflicts in my grammar from 12 to 75 and then to 354. I'm not really good at this, am I^^?

@cblp If you are interested, the slides for his lectures are here : http://www.cse.chalmers.se/~rjmh/MGS2019/

The one on this particular problem was on Wednesday :) http://www.cse.chalmers.se/~rjmh/MGS2019/Day%204%20Lecture%20-%20Effective%20properties.pdf

@cblp I was at the Midlands Graduate School this year where John Hughes was invited speaker and he talked precisely about this kind of problem :)

By default the generators are uniform, so they must be tuned to make sure they generate tests for the corner cases. One advice was to write some unit tests for the problem in question, and then tune the generators to make sure these unit tests (and tests similar) will be generated.

I nearly had the occasion to cite a paper published in the « Proceedings of the USSR Academy of Sciences ». But turns out it's not really relevant enough

Robin Milner's soul forever trapped in a book, I guess

@otini
\iffalse.......\fi

😉

@epicmorphism I'm not quite sure. After thinking about it I think it might have something to do with the desugaring of rec-constructs (for ArrowLoop). There is none there, but it could be the « do nothing » desugaring for this construct, I don't know

I've tried to see if the optimized core looks any better, but since GHC lifts all the definitions it can to the top level, it's impossible to guess what it really looks like. I mean it's possible, you just have to track down in your head around 100 intermediate defintions (not a hyperbole)

I'm working on FRP right now, and for the paper we're righting, I wanted to know precisely how proc-notation was desugared. I knew it was not ideal, but it's even worse than I thought^^

On the photo is what the following expression gets desugared into:
proc x -> do
y <- sf -< x
z <- sg -< y
z <- sh -< (y,z)
returnA -< (z,y)

(Deduced from unoptimized core)

And here's the Hackage link (after much fear because the documentation wouldn't appear^^)

https://hackage.haskell.org/package/pattern-matcher-0.1.0.0

Aaaaand with some delay (due to pesky PhD work and marking), here it is!

https://gitlab.com/chupin/pattern-matcher

I'd be delighted if people want to review the code or contribute 😊 I'll see to publish it on Hackage in the coming days.

Thanks a lot to @otini for reviewing the documentation!