me12345 2017-02-25 00:03:12
Hello. Any sweet pussies here, that would like to meet an adorable Estonian man?
MarcelineVQ 2017-02-25 00:17:01
if there were I doubt that'd be the line that sealed the deal
flxw 2017-02-25 00:24:24
and it would depend on what language extensions he's using in his haskell code.
rmrfroot 2017-02-25 00:29:26
flxw: he's probably one of those persons that uses A LOT of CPP macros and wraps *everything* in `unsafePerformIO`
cocreature 2017-02-25 00:29:39
rmrfroot: that's disgusting
rmrfroot 2017-02-25 00:30:36
cocreature: that was the most digusting thing I could think of :D
rmrfroot 2017-02-25 00:30:36
what can we do to make it worse?
cocreature 2017-02-25 00:30:41
rmrfroot: put some unsafeCoerce in there and it becomes even more disgusting
int-e 2017-02-25 00:32:31
. o O ( unsafePerformIO "wraps" code in the same way that a pair of scissors "wraps" a present. )
flxw 2017-02-25 00:32:32
sorry, I am still learning to write more ellegant haskell, so I don't know all the tricks yet to make it really bad. :)
rmrfroot 2017-02-25 00:32:51
cocreature: never hard about that one before, reading this "converts a value from any type to any other type." made me shiver
cocreature 2017-02-25 00:33:28
rmrfroot: it's basically "types? who needs that anyway, I'll just pretend it has a different type"
int-e 2017-02-25 00:33:41
(scissors may be involved in wrapping presents, and the wrap may even be beautiful, but noone would attribute the result to the scissors.)
rmrfroot 2017-02-25 00:34:03
pfff, types? never heard of such atrocity.
int-e 2017-02-25 00:34:17
rmrfroot: so which type of programmer are you...
rmrfroot 2017-02-25 00:34:59
ine-e: the one that writes jokes in as much source code comments as possible
rmrfroot 2017-02-25 00:35:03
sorry, int-e
rmrfroot 2017-02-25 00:36:20
int-e: and you? :)
int-e 2017-02-25 00:37:22
mostly lazy
int-e 2017-02-25 00:37:40
(I would elaborate but it doesn't seem worth the effort)
rmrfroot 2017-02-25 00:37:52
*baa-duumm-tisssh*
rmrfroot 2017-02-25 00:37:56
good one!
rmrfroot 2017-02-25 00:38:48
#haskell always has the best kind of jokes, too bad no one I know will ever understand them :(
flxw 2017-02-25 00:42:31
A question about MonadFail. I first came across it when writing some validation code in an Attoparsec based parser. And I find the idea of having an inteface to fail, with implementations which make sense for the different monads quite neat, actually. But some people seem to not like MonadFail at all. Why is that? I mean, one just doesn't need to implmenent fail for monads for which it is not appropriate, no?
flxw 2017-02-25 00:43:48
(and as I understand it, fail is a great way to not throw exceptions uniformly, modulo IO)
