| 2023-04-17 00:00:36 +0200 | <maralorn> | Is there a way to get the size of the transitive closure of a value? |
| 2023-04-17 00:01:25 +0200 | wroathe | (~wroathe@user/wroathe) (Ping timeout: 240 seconds) |
| 2023-04-17 00:01:36 +0200 | <maralorn> | I mean so to say the life memory if only that value were a gcroot. |
| 2023-04-17 00:01:38 +0200 | <geekosaur> | more performant for the constructors that can be tagged; it has to go to the info table for the others |
| 2023-04-17 00:04:41 +0200 | Me-me | (~Me-me@146.102.215.218.dyn.iprimus.net.au) |
| 2023-04-17 00:05:51 +0200 | Me-me | (~Me-me@146.102.215.218.dyn.iprimus.net.au) (Remote host closed the connection) |
| 2023-04-17 00:06:04 +0200 | wroathe | (~wroathe@50.205.197.50) |
| 2023-04-17 00:06:04 +0200 | wroathe | (~wroathe@50.205.197.50) (Changing host) |
| 2023-04-17 00:06:04 +0200 | wroathe | (~wroathe@user/wroathe) |
| 2023-04-17 00:06:33 +0200 | <maralorn> | So they don’t have a more compact representation in memory, just lookups are a bit quicker? |
| 2023-04-17 00:06:46 +0200 | <geekosaur> | yes |
| 2023-04-17 00:07:49 +0200 | gurkenglas | (~gurkengla@dynamic-046-114-182-107.46.114.pool.telefonica.de) (Ping timeout: 276 seconds) |
| 2023-04-17 00:09:09 +0200 | gurkenglas | (~gurkengla@dynamic-046-114-180-034.46.114.pool.telefonica.de) |
| 2023-04-17 00:09:14 +0200 | <geekosaur> | (gc still needs the info table) |
| 2023-04-17 00:10:45 +0200 | enoq | (~enoq@2a05:1141:1f5:5600:b9c9:721a:599:bfe7) (Quit: enoq) |
| 2023-04-17 00:25:29 +0200 | jmdaemon | (~jmdaemon@user/jmdaemon) |
| 2023-04-17 00:32:25 +0200 | ryantrinkle | (~ryantrink@140.174.248.64) (Ping timeout: 265 seconds) |
| 2023-04-17 00:34:20 +0200 | <maralorn> | Reading: https://stackoverflow.com/questions/3254758/memory-footprint-of-haskell-data-types Why do unary datatypes need a header? |
| 2023-04-17 00:34:32 +0200 | Me-me | (~Me-me@146.102.215.218.dyn.iprimus.net.au) |
| 2023-04-17 00:34:39 +0200 | Me-me | (~Me-me@146.102.215.218.dyn.iprimus.net.au) (Changing host) |
| 2023-04-17 00:34:39 +0200 | Me-me | (~Me-me@user/me-me) |
| 2023-04-17 00:34:54 +0200 | <maralorn> | I understand it if there are multiple constructors. |
| 2023-04-17 00:40:34 +0200 | <c_wraith> | maralorn: so the GC knows which fields are pointers it needs to traverse |
| 2023-04-17 00:41:23 +0200 | AlexNoo_ | AlexNoo |
| 2023-04-17 00:41:32 +0200 | <maralorn> | Ah, I see. |
| 2023-04-17 00:41:42 +0200 | <c_wraith> | (and for that matter, how many fields the constructor has) |
| 2023-04-17 00:43:04 +0200 | <geekosaur> | that's why I said gc needs the info table even with pointer tagging |
| 2023-04-17 00:43:25 +0200 | <geekosaur> | size and pointer bitmap, at minimum |
| 2023-04-17 00:44:31 +0200 | <maralorn> | Yea |
| 2023-04-17 00:45:00 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
| 2023-04-17 00:45:44 +0200 | ryantrinkle | (~ryantrink@140.174.248.64) |
| 2023-04-17 00:47:22 +0200 | <geekosaur> | (and I've just realized that bitmap is likely why tuple size is capped at 63) |
| 2023-04-17 00:47:46 +0200 | wroathe | (~wroathe@user/wroathe) (Quit: leaving) |
| 2023-04-17 00:48:01 +0200 | Tuplanolla | (~Tuplanoll@91-159-68-236.elisa-laajakaista.fi) (Quit: Leaving.) |
| 2023-04-17 00:48:12 +0200 | <c_wraith> | I've seen some code using records with over 100 fields. GHC must have a different representation at some point... |
| 2023-04-17 00:48:53 +0200 | <geekosaur> | or the bitmap is stored in an Array# or similar, I guess |
| 2023-04-17 00:49:26 +0200 | <geekosaur> | but tuples are still a bit "special" |
| 2023-04-17 00:54:23 +0200 | bitmapper | (uid464869@id-464869.lymington.irccloud.com) |
| 2023-04-17 00:54:49 +0200 | heinz9 | (~trace@user/trace) (Remote host closed the connection) |
| 2023-04-17 00:55:50 +0200 | NiceBird | (~NiceBird@185.133.111.196) (Ping timeout: 246 seconds) |
| 2023-04-17 00:57:59 +0200 | acidjnk | (~acidjnk@p200300d6e715c491dc796c235bb1f77a.dip0.t-ipconnect.de) (Ping timeout: 246 seconds) |
| 2023-04-17 01:04:41 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
| 2023-04-17 01:07:08 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
| 2023-04-17 01:10:05 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
| 2023-04-17 01:18:52 +0200 | <maralorn> | Still a bit confused. I am inspecting the heap of my program combined with print debugging what I think is the state. If I calculate correctly I have a very clear understanding how many constructors of my types appear and they all make sense. Including the number of texts. But then ARR_WORDS is roughly to big by a factor 10. |
| 2023-04-17 01:19:19 +0200 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2023-04-17 01:19:26 +0200 | <maralorn> | I suspect that most of ARR_WORDS are Texts, because when I switch from text 2.0 to 1.x the size of ARR_WORDS doubles. |
| 2023-04-17 01:19:46 +0200 | <maralorn> | Also I don’t see any bytestring constructors or similar on the heap. |
| 2023-04-17 01:21:53 +0200 | <geekosaur> | right, ByteString is allocated from pinned memory instead of the heap |
| 2023-04-17 01:22:21 +0200 | <maralorn> | But with 15k Texts using 23M (with utf-16 everything ascii) that gives me an average Text length of 750 characters, but my texts are on average less than 32 characters. |
| 2023-04-17 01:22:55 +0200 | <geekosaur> | that I don't know |
| 2023-04-17 01:23:35 +0200 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 255 seconds) |
| 2023-04-17 01:23:42 +0200 | <maralorn> | geekosaur: So memory used by bytestring does not appear in the eventlog profile? |
| 2023-04-17 01:24:02 +0200 | jpds | (~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds) |
| 2023-04-17 01:25:22 +0200 | <geekosaur> | I don't know offhand how pinned memory shows up in the eventlog, I just know it won't show as heap memory |
| 2023-04-17 01:25:29 +0200 | <maralorn> | Anyway by size of the constructors I have only about 30 bytestrings alive at any time. |
| 2023-04-17 01:25:51 +0200 | <geekosaur> | other profiling tools have a separate "heap" entry called PINNED |
| 2023-04-17 01:26:11 +0200 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) |
| 2023-04-17 01:26:25 +0200 | gurkenglas | (~gurkengla@dynamic-046-114-180-034.46.114.pool.telefonica.de) (Ping timeout: 240 seconds) |
| 2023-04-17 01:27:28 +0200 | APic | (apic@apic.name) (Read error: Connection reset by peer) |
| 2023-04-17 01:27:31 +0200 | falafel | (~falafel@2603-8000-d700-115c-1fbb-7fdc-aa80-ebf8.res6.spectrum.com) (Ping timeout: 250 seconds) |
| 2023-04-17 01:27:48 +0200 | <maralorn> | I wonder if I am keeping alive files I read in by parsing subtexts out of them. And maybe the Text is now just a pointer to the whole file with start and end? |
| 2023-04-17 01:28:16 +0200 | <geekosaur> | possibly. iirc you are encouraged to copy slices to avoid that |
| 2023-04-17 01:28:45 +0200 | <geekosaur> | although hm, in that case it should really have only one copy of it with multiple slice pointers? |
| 2023-04-17 01:29:21 +0200 | <c_wraith> | if it's a lazy bytestring, it could be multiple pinned chunks |
| 2023-04-17 01:33:51 +0200 | <maralorn> | It would make sense in my case because I am reading 2k files with each a few thousand bytes but only parse a tiny substring out of each of them. |
| 2023-04-17 01:37:45 +0200 | jpds | (~jpds@gateway/tor-sasl/jpds) |
| 2023-04-17 01:39:49 +0200 | son0p | (~ff@181.136.122.143) |
| 2023-04-17 01:41:02 +0200 | <geekosaur> | https://hackage.haskell.org/package/text-2.0.2/docs/Data-Text.html#v:copy |
| 2023-04-17 01:41:19 +0200 | <geekosaur> | and yes, in that case you're likely keeping the whole file live |
| 2023-04-17 01:47:40 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 01:49:22 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 01:49:45 +0200 | merijn | (~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 240 seconds) |
| 2023-04-17 01:51:11 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:e40f:1779:8d3b:ad7d) (Remote host closed the connection) |
| 2023-04-17 01:51:48 +0200 | <maralorn> | Yeah, that was it. |
| 2023-04-17 01:52:25 +0200 | <maralorn> | I think I spend roughly 12 hours learning heap profiling, today. |
| 2023-04-17 01:53:26 +0200 | <maralorn> | Reduced the memory footprint of my program from 80MB to 8MB. \o/ |
| 2023-04-17 01:54:17 +0200 | mauke_ | (~mauke@user/mauke) |
| 2023-04-17 01:55:29 +0200 | <yushyin> | nice~ |
| 2023-04-17 01:55:45 +0200 | mauke | (~mauke@user/mauke) (Ping timeout: 240 seconds) |
| 2023-04-17 01:55:45 +0200 | mauke_ | mauke |
| 2023-04-17 02:01:50 +0200 | califax | (~califax@user/califx) (Remote host closed the connection) |
| 2023-04-17 02:02:04 +0200 | <juri_> | very nice. |
| 2023-04-17 02:02:44 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 02:03:27 +0200 | califax | (~califax@user/califx) |
| 2023-04-17 02:04:01 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 02:04:45 +0200 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 240 seconds) |
| 2023-04-17 02:05:02 +0200 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) |
| 2023-04-17 02:10:24 +0200 | pieguy128 | (~pieguy128@bas1-montreal02-65-92-163-233.dsl.bell.ca) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2023-04-17 02:10:36 +0200 | <maralorn> | The sneakiest leak was a missing ' at a modify' … But that was quite quick to find. |
| 2023-04-17 02:10:46 +0200 | pieguy128 | (~pieguy128@bas1-montreal02-65-92-163-233.dsl.bell.ca) |
| 2023-04-17 02:12:12 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) |
| 2023-04-17 02:18:34 +0200 | dmwit | (~dmwit@2600:4040:2654:5e00:2111:3b68:aad:9bda) |
| 2023-04-17 02:21:31 +0200 | <dmwit> | Okay, dumb question. GHC has a runtime system that I assume has some data structure for tracking what memory it's allocated so it can give me unallocated space when I need some more. C's malloc presumably also has a data structure tracking what memory is allocated. I assume the two structures aren't kept in synch with each other, yet I never have |
| 2023-04-17 02:21:31 +0200 | <dmwit> | to worry about it anyway. What's up with that? |
| 2023-04-17 02:23:06 +0200 | <geekosaur> | they're completely unrelated systems. the closest you get to C's malloc arena in Haskell is pinned memory, but they're not identical |
| 2023-04-17 02:23:29 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:e40f:1779:8d3b:ad7d) |
| 2023-04-17 02:23:53 +0200 | <dmwit> | I agree they're unrelated. So how come they don't step on each other? Like, when GHC says "I'll give you some memory at 0x1000", how does the unrelated unsynchronized malloc system know not to hand out 0x1000 after that? |
| 2023-04-17 02:24:18 +0200 | <geekosaur> | you normally have to care only if you're sharing memory between C and Haskell; this is why ForeignPtr exists, so you can call a C-side free on memory obtained from a FFI call |
| 2023-04-17 02:24:44 +0200 | <geekosaur> | each one allocates and keeps track of its own pages |
| 2023-04-17 02:24:44 +0200 | <jackdk> | The other part of the answer is "sometimes you do", when writing FFI code you want to make sure that whatever native cleanup function gets run when you GC the `ForeignPtr`: https://hackage.haskell.org/package/base-4.17.0.0/docs/GHC-ForeignPtr.html#v:addForeignPtrFinalizer |
| 2023-04-17 02:25:12 +0200 | <jackdk> | Oh, geekosaur ahead of me with the answer already |
| 2023-04-17 02:25:18 +0200 | <geekosaur> | so they won't both hand you 0x1000 because only one of them will "own" that page |
| 2023-04-17 02:25:47 +0200 | <dmwit> | How does GHC (say) detect whether it owns 0x1000 or not? |
| 2023-04-17 02:26:42 +0200 | <geekosaur> | each one mmap()s pages. neither does so by fixed address (that is reserved for the dynamic loader and initial process setup), they request "next available page" |
| 2023-04-17 02:27:10 +0200 | <geekosaur> | and that page then belongs to either the malloc arena or ghc's heap until munmap()ed |
| 2023-04-17 02:27:35 +0200 | <dmwit> | Oh, sure, so the OS arbitrates. That makes sense. |
| 2023-04-17 02:28:16 +0200 | <geekosaur> | there are also raw interfaces to mmap on hackage so you can in effect allocate your own pages from the OS, and neither malloc() nor the ghc heap will use those pages because they didn't obtain them from the OS |
| 2023-04-17 02:28:37 +0200 | <dmwit> | neat! |
| 2023-04-17 02:29:03 +0200 | <geekosaur> | (this is ignoring things like compact regions which are again distinct page allocations from the OS that can't collide with each other or the C / Haskell heaps) |
| 2023-04-17 02:29:25 +0200 | zeenk | (~zeenk@188.26.30.104) (Quit: Konversation terminated!) |
| 2023-04-17 02:29:57 +0200 | ski | idly ponders `sbrk' in Haskell |
| 2023-04-17 02:30:16 +0200 | <geekosaur> | I don't think sbrk even exists as such any more |
| 2023-04-17 02:30:34 +0200 | <geekosaur> | everything is mmap() based these days |
| 2023-04-17 02:31:22 +0200 | <geekosaur> | in particular glibc switched from brk/sbrk to mmap a couple decades ago |
| 2023-04-17 02:32:31 +0200 | <geekosaur> | (originally it was only used for large allocations, then eventually they switched everything over) |
| 2023-04-17 02:33:37 +0200 | <geekosaur> | otherwise you run into issues with shared object locations; brk isn't smart enough to "route around" those, but mmap will just give you the next available page after the shared object |
| 2023-04-17 02:33:58 +0200 | dmwit | (~dmwit@2600:4040:2654:5e00:2111:3b68:aad:9bda) (Ping timeout: 260 seconds) |
| 2023-04-17 02:34:04 +0200 | <ski> | "On Linux, sbrk() is implemented as a library function that uses the brk() system call, and does some internal bookkeeping so that it can return the old break value.", hmm |
| 2023-04-17 02:34:21 +0200 | <geekosaur> | oh., it is still there? |
| 2023-04-17 02:34:35 +0200 | <ski> | might still be using `mmap', even if not mentioned there |
| 2023-04-17 02:34:44 +0200 | <geekosaur> | I think that internal bookkeeping thing has been around ever since v7 unix though |
| 2023-04-17 02:35:02 +0200 | <geekosaur> | but the world was simpler back then so the bookkeeping was minimal |
| 2023-04-17 02:35:31 +0200 | captnemo | (~captnemo@193.32.127.232) |
| 2023-04-17 02:35:53 +0200 | <geekosaur> | internal pointer initialized to _end and bumped with every sbrk call |
| 2023-04-17 02:36:07 +0200 | ski | nods |
| 2023-04-17 02:37:48 +0200 | <ski> | "On error, (void *) -1 is returned" -- also a bit curious |
| 2023-04-17 02:38:02 +0200 | <geekosaur> | hysterical raisins |
| 2023-04-17 02:38:10 +0200 | <ski> | i can imagine |
| 2023-04-17 02:38:30 +0200 | <geekosaur> | syscalls (or former syscalls) always returned -1 on error, even if they returned pointers |
| 2023-04-17 02:39:02 +0200 | <ski> | iirc `NULL' is allowed to be all bits `1' |
| 2023-04-17 02:39:27 +0200 | <geekosaur> | because the syscall exit stuff in the kernel set a cpu flag to indicate error and the generic syscall return mechanism in userspace set the accumulator to -1 if that cpu flag was set |
| 2023-04-17 02:40:15 +0200 | <ski> | carry flag ? or some flag for this specific purpose ? |
| 2023-04-17 02:40:25 +0200 | <geekosaur> | I think carry, yeh |
| 2023-04-17 02:40:45 +0200 | <ski> | *nod*, makes sense |
| 2023-04-17 02:41:06 +0200 | <geekosaur> | but it may depend on the actual CPU, some have for example overflow flags that might have been used instead |
| 2023-04-17 02:41:16 +0200 | <ski> | yea |
| 2023-04-17 02:41:30 +0200 | <ski> | (signed overflow, i assume) |
| 2023-04-17 02:41:39 +0200 | ft | (~ft@87.122.10.136) (Ping timeout: 260 seconds) |
| 2023-04-17 02:42:46 +0200 | <ski> | i guess that generic syscall return mechanism deals with switching stacks and restoring context and so |
| 2023-04-17 02:43:04 +0200 | <geekosaur> | yep |
| 2023-04-17 02:45:05 +0200 | <ski> | (i was disassembling some old software (language implementation) from 1986, and noticed that it installed an interrupt handler that would manually add a new frame on the stack, before switching memory configuration. the new frame would, at end of interrupt code, restore memory config, and clean up its own frame from the stack) |
| 2023-04-17 02:47:15 +0200 | jero98772 | (~jero98772@2800:484:1d84:9000::1) (Ping timeout: 250 seconds) |
| 2023-04-17 02:47:44 +0200 | tzh_ | (~tzh@c-24-21-73-154.hsd1.wa.comcast.net) |
| 2023-04-17 02:49:35 +0200 | tzh | (~tzh@c-24-21-73-154.hsd1.or.comcast.net) (Ping timeout: 260 seconds) |
| 2023-04-17 03:00:22 +0200 | jero98772 | (~jero98772@2800:484:1d84:9000::1) |
| 2023-04-17 03:01:32 +0200 | fallenleaves | (~fallenlea@2a00:23c6:6815:f01:74f1:90b2:aa8b:ef87) |
| 2023-04-17 03:02:27 +0200 | <geekosaur> | (to complete the story about the carry flag, if it was set the accumulator had the error code. so the asm trampoline from the syscall interface had to write that to errno if the carry flag was set) |
| 2023-04-17 03:04:13 +0200 | nate1 | (~nate@98.45.169.16) |
| 2023-04-17 03:05:25 +0200 | fallenleaves | (~fallenlea@2a00:23c6:6815:f01:74f1:90b2:aa8b:ef87) (Quit: Leaving) |
| 2023-04-17 03:06:24 +0200 | _leo___ | (~emmanuelu@user/emmanuelux) (Quit: au revoir) |
| 2023-04-17 03:07:31 +0200 | pieguy128 | (~pieguy128@bas1-montreal02-65-92-163-233.dsl.bell.ca) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2023-04-17 03:07:55 +0200 | pieguy128 | (~pieguy128@bas1-montreal02-65-92-163-233.dsl.bell.ca) |
| 2023-04-17 03:08:45 +0200 | nate1 | (~nate@98.45.169.16) (Ping timeout: 240 seconds) |
| 2023-04-17 03:10:37 +0200 | albet70 | (~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection) |
| 2023-04-17 03:12:07 +0200 | <ski> | (aye .. KERNAL uses a similar interface, for many of its jumptable public routines) |
| 2023-04-17 03:12:17 +0200 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2023-04-17 03:16:44 +0200 | albet70 | (~xxx@2400:8902::f03c:92ff:fe60:98d8) |
| 2023-04-17 03:24:06 +0200 | Sgeo | (~Sgeo@user/sgeo) |
| 2023-04-17 03:35:50 +0200 | dmwit | (~dmwit@2600:4040:2654:5e00:2111:3b68:aad:9bda) |
| 2023-04-17 03:37:42 +0200 | hsw | (~hsw@2001-b030-2303-0104-0172-0025-0012-0132.hinet-ip6.hinet.net) (Remote host closed the connection) |
| 2023-04-17 03:38:13 +0200 | hsw | (~hsw@2001-b030-2303-0104-0172-0025-0012-0132.hinet-ip6.hinet.net) |
| 2023-04-17 03:38:30 +0200 | <dmwit> | From the logs it looks like my last few messages didn't go through. One was just "thank you" to the folks that answered. |
| 2023-04-17 03:39:00 +0200 | <dmwit> | The other: I understand you can't ask GHC to make a new OS thread to run your computation on. But you can pin a Haskell thread to an OS thread, and sometimes have to when using the FFI. Does this mean I may get into a situation where two threads unavoidable contend with each other? Like, they're both compute bound, and both bound to the same OS |
| 2023-04-17 03:39:00 +0200 | <dmwit> | thread so they can't switch CPUs to avoid each other. If so, is there a way to deal with that? |
| 2023-04-17 03:39:11 +0200 | <dmwit> | (Purely theoretical. I'm not facing this as a problem that needs solving. Just shower thoughts.) |
| 2023-04-17 03:39:44 +0200 | Angelz | (Angelz@angelz.oddprotocol.org) (Ping timeout: 248 seconds) |
| 2023-04-17 03:40:26 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) |
| 2023-04-17 03:41:11 +0200 | jpds | (~jpds@gateway/tor-sasl/jpds) (Remote host closed the connection) |
| 2023-04-17 03:44:17 +0200 | jpds | (~jpds@gateway/tor-sasl/jpds) |
| 2023-04-17 03:45:14 +0200 | <monochrom> | Despite other people's paranoid scaremongering, my understanding is that the only way two Haskell threads are bound to the same OS thread is that the first Haskell thread calls C, C calls Haskell back, this is how the 2nd Haskell thread is created in the first place, to run the "Haskell" in "C calls Haskell back". Due to this sequential, 1st-thread-is-still-waiting-for-this-chain-to-return nature, there cannot be contention between the two, they can't |
| 2023-04-17 03:45:14 +0200 | <monochrom> | run concurrently. |
| 2023-04-17 03:45:35 +0200 | <monochrom> | See also my http://www.vex.net/~trebla/haskell/ghc-conc-ffi.xhtml |
| 2023-04-17 03:45:35 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) (Ping timeout: 260 seconds) |
| 2023-04-17 03:48:39 +0200 | <monochrom> | If you obtain the bound thread by forkOS, it is bound to a fresh OS thread. The designers know to do this to eliminate the contention you worried about. |
| 2023-04-17 03:50:58 +0200 | dmwit | (~dmwit@2600:4040:2654:5e00:2111:3b68:aad:9bda) (Ping timeout: 260 seconds) |
| 2023-04-17 03:54:31 +0200 | xff0x | (~xff0x@2405:6580:b080:900:cdd4:c060:73da:4d99) (Ping timeout: 240 seconds) |
| 2023-04-17 03:56:47 +0200 | dmwit | (~dmwit@pool-96-241-148-210.washdc.fios.verizon.net) |
| 2023-04-17 03:57:58 +0200 | <dmwit> | Thanks. I'm reading. But "forkOS is bound to a fresh OS thread" more or less completely answers the question. I guess this is a statement of "this is what happens" rather than "this is what is promised", right? |
| 2023-04-17 03:58:36 +0200 | <monochrom> | This one is promised. |
| 2023-04-17 04:00:13 +0200 | <dmwit> | Huh. The docs for Control.Concurrent don't appear to promise "fresh", only "bound". |
| 2023-04-17 04:01:12 +0200 | <monochrom> | IIRC it's in one of the papers. |
| 2023-04-17 04:01:42 +0200 | <monochrom> | To the effect of "this is a no-brainer, obviously the whole system would be pointless otherwise". |
| 2023-04-17 04:02:02 +0200 | <dmwit> | 👍 |
| 2023-04-17 04:02:25 +0200 | FinnElija | (~finn_elij@user/finn-elija/x-0085643) (Killed (NickServ (Forcing logout FinnElija -> finn_elija))) |
| 2023-04-17 04:02:25 +0200 | finn_elija | (~finn_elij@user/finn-elija/x-0085643) |
| 2023-04-17 04:02:25 +0200 | finn_elija | FinnElija |
| 2023-04-17 04:06:38 +0200 | <dmwit> | "Can several Haskell threads be bound to the same OS thread? There are several reasons why this is not possible:" sweet |
| 2023-04-17 04:09:04 +0200 | td_ | (~td@i53870922.versanet.de) (Ping timeout: 248 seconds) |
| 2023-04-17 04:10:47 +0200 | td_ | (~td@i53870920.versanet.de) |
| 2023-04-17 04:11:49 +0200 | barak | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) |
| 2023-04-17 04:13:18 +0200 | captnemo | (~captnemo@193.32.127.232) (Ping timeout: 265 seconds) |
| 2023-04-17 04:18:22 +0200 | Angelz | (Angelz@2605:6400:30:fc15:9bd1:2217:41cd:bb15) |
| 2023-04-17 04:34:10 +0200 | pavonia | (~user@user/siracusa) (Quit: Bye!) |
| 2023-04-17 04:40:29 +0200 | xff0x | (~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp) |
| 2023-04-17 04:41:41 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:e40f:1779:8d3b:ad7d) (Remote host closed the connection) |
| 2023-04-17 04:47:29 +0200 | nate1 | (~nate@98.45.169.16) |
| 2023-04-17 05:00:17 +0200 | finn_elija | (~finn_elij@user/finn-elija/x-0085643) |
| 2023-04-17 05:00:17 +0200 | FinnElija | (~finn_elij@user/finn-elija/x-0085643) (Killed (NickServ (Forcing logout FinnElija -> finn_elija))) |
| 2023-04-17 05:00:17 +0200 | finn_elija | FinnElija |
| 2023-04-17 05:01:34 +0200 | barak | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) (Remote host closed the connection) |
| 2023-04-17 05:01:57 +0200 | barak | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) |
| 2023-04-17 05:02:05 +0200 | dmwit | (~dmwit@pool-96-241-148-210.washdc.fios.verizon.net) (Quit: Client closed) |
| 2023-04-17 05:02:28 +0200 | pieguy128 | (~pieguy128@bas1-montreal02-65-92-163-233.dsl.bell.ca) (Ping timeout: 252 seconds) |
| 2023-04-17 05:03:03 +0200 | pieguy128 | (~pieguy128@bras-base-mtrlpq5031w-grc-56-65-92-162-12.dsl.bell.ca) |
| 2023-04-17 05:07:55 +0200 | barak | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) (Ping timeout: 248 seconds) |
| 2023-04-17 05:12:57 +0200 | barak | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) |
| 2023-04-17 05:16:05 +0200 | _xor | (~xor@74.215.46.17) (Quit: brb) |
| 2023-04-17 05:20:57 +0200 | szkl | (uid110435@id-110435.uxbridge.irccloud.com) (Quit: Connection closed for inactivity) |
| 2023-04-17 05:22:25 +0200 | barak | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) (Ping timeout: 265 seconds) |
| 2023-04-17 05:25:28 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:e40f:1779:8d3b:ad7d) |
| 2023-04-17 05:28:13 +0200 | jero98772 | (~jero98772@2800:484:1d84:9000::1) (Remote host closed the connection) |
| 2023-04-17 05:34:38 +0200 | barak | (~barak@77.125.91.113) |
| 2023-04-17 05:38:18 +0200 | mei | (~mei@user/mei) (Ping timeout: 255 seconds) |
| 2023-04-17 05:38:40 +0200 | machinedgod | (~machinedg@d198-53-218-113.abhsia.telus.net) (Ping timeout: 276 seconds) |
| 2023-04-17 05:42:16 +0200 | mei | (~mei@user/mei) |
| 2023-04-17 05:46:22 +0200 | merijn | (~merijn@86-86-29-250.fixed.kpn.net) |
| 2023-04-17 05:48:25 +0200 | nate1 | (~nate@98.45.169.16) (Ping timeout: 240 seconds) |
| 2023-04-17 05:51:15 +0200 | merijn | (~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 260 seconds) |
| 2023-04-17 05:55:50 +0200 | biberu | (~biberu@user/biberu) (Read error: Connection reset by peer) |
| 2023-04-17 05:59:46 +0200 | biberu | (~biberu@user/biberu) |
| 2023-04-17 06:00:00 +0200 | mei | (~mei@user/mei) (Ping timeout: 260 seconds) |
| 2023-04-17 06:03:31 +0200 | mei | (~mei@user/mei) |
| 2023-04-17 06:06:24 +0200 | Fischmiep | (~Fischmiep@user/Fischmiep) (Ping timeout: 265 seconds) |
| 2023-04-17 06:14:35 +0200 | Fischmiep | (~Fischmiep@user/Fischmiep) |
| 2023-04-17 06:25:25 +0200 | Fischmiep | (~Fischmiep@user/Fischmiep) (Ping timeout: 240 seconds) |
| 2023-04-17 06:29:26 +0200 | mbuf | (~Shakthi@49.207.178.186) |
| 2023-04-17 06:46:56 +0200 | Fischmiep | (~Fischmiep@user/Fischmiep) |
| 2023-04-17 06:47:07 +0200 | Square2 | (~Square4@user/square) |
| 2023-04-17 06:47:57 +0200 | Square2 | (~Square4@user/square) (Client Quit) |
| 2023-04-17 06:48:27 +0200 | Square2 | (~Square4@user/square) |
| 2023-04-17 06:54:59 +0200 | motherfsck | (~motherfsc@user/motherfsck) |
| 2023-04-17 06:55:45 +0200 | Fischmiep | (~Fischmiep@user/Fischmiep) (Ping timeout: 240 seconds) |
| 2023-04-17 06:56:18 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) |
| 2023-04-17 07:03:47 +0200 | barak | (~barak@77.125.91.113) (Remote host closed the connection) |
| 2023-04-17 07:03:57 +0200 | barak | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) |
| 2023-04-17 07:04:24 +0200 | jargon | (~jargon@174-22-213-236.phnx.qwest.net) (Ping timeout: 265 seconds) |
| 2023-04-17 07:06:13 +0200 | vglfr | (~vglfr@46.96.159.156) |
| 2023-04-17 07:06:51 +0200 | vglfr | (~vglfr@46.96.159.156) (Remote host closed the connection) |
| 2023-04-17 07:06:58 +0200 | barak_ | (~barak@77.125.91.113) |
| 2023-04-17 07:09:38 +0200 | barak | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) (Ping timeout: 246 seconds) |
| 2023-04-17 07:10:42 +0200 | vglfr | (~vglfr@46.96.159.156) |
| 2023-04-17 07:16:38 +0200 | trev | (~trev@user/trev) |
| 2023-04-17 07:16:53 +0200 | adanwan | (~adanwan@gateway/tor-sasl/adanwan) (Remote host closed the connection) |
| 2023-04-17 07:17:09 +0200 | adanwan | (~adanwan@gateway/tor-sasl/adanwan) |
| 2023-04-17 07:21:17 +0200 | bgs | (~bgs@212-85-160-171.dynamic.telemach.net) |
| 2023-04-17 07:22:50 +0200 | takuan | (~takuan@178-116-218-225.access.telenet.be) |
| 2023-04-17 07:23:14 +0200 | trev | (~trev@user/trev) (Quit: trev) |
| 2023-04-17 07:24:29 +0200 | trev | (~trev@user/trev) |
| 2023-04-17 07:27:05 +0200 | harveypwca | (~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) |
| 2023-04-17 07:39:33 +0200 | edwtjo | (~edwtjo@fsf/member/edwtjo) (Quit: WeeChat 3.8) |
| 2023-04-17 07:39:37 +0200 | <ujjwalgupta[m]> | <L29Ah> "ujjwal gupta: apparently it's..." <- https://downloads.haskell.org/ghc/latest/docs/users_guide/profiling.html#rules-for-attributing-costs |
| 2023-04-17 07:39:37 +0200 | <ujjwalgupta[m]> | As per this Laziness shouldn't affect the cost centre stack. Also all the functions are evaluated mostly not sure if laziness can be the culprit here. 🤔 |
| 2023-04-17 07:40:25 +0200 | <ujjwalgupta[m]> | https://downloads.haskell.org/ghc/latest/docs/users_guide/profiling.html#rules-for-attributing-costs |
| 2023-04-17 07:40:25 +0200 | <ujjwalgupta[m]> | As per this Laziness shouldn't affect the cost centre stack. Also all the functions are evaluated mostly not sure if laziness can be the culprit here. 🤔 |
| 2023-04-17 07:41:13 +0200 | <ujjwalgupta[m]> | CC jade |
| 2023-04-17 07:43:33 +0200 | notzmv | (~zmv@user/notzmv) (Ping timeout: 265 seconds) |
| 2023-04-17 07:46:33 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) (Ping timeout: 255 seconds) |
| 2023-04-17 07:46:40 +0200 | barak_ | (~barak@77.125.91.113) (Remote host closed the connection) |
| 2023-04-17 07:46:57 +0200 | barak_ | (~barak@77.125.91.113) |
| 2023-04-17 07:51:10 +0200 | barak_ | (~barak@77.125.91.113) (Remote host closed the connection) |
| 2023-04-17 07:51:27 +0200 | barak_ | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) |
| 2023-04-17 07:52:19 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 250 seconds) |
| 2023-04-17 07:52:45 +0200 | Techcable | (~Techcable@user/Techcable) (Ping timeout: 250 seconds) |
| 2023-04-17 07:54:20 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-04-17 07:57:19 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Quit: WeeChat 3.8) |
| 2023-04-17 08:04:59 +0200 | barak__ | (~barak@77.125.91.113) |
| 2023-04-17 08:05:02 +0200 | Square2 | Square |
| 2023-04-17 08:07:24 +0200 | barak_ | (~barak@2a0d:6fc2:68c0:a400:74a7:4a2d:bdfd:481e) (Ping timeout: 252 seconds) |
| 2023-04-17 08:17:08 +0200 | adanwan | (~adanwan@gateway/tor-sasl/adanwan) (Remote host closed the connection) |
| 2023-04-17 08:17:28 +0200 | adanwan | (~adanwan@gateway/tor-sasl/adanwan) |
| 2023-04-17 08:18:56 +0200 | bgs | (~bgs@212-85-160-171.dynamic.telemach.net) (Remote host closed the connection) |
| 2023-04-17 08:23:55 +0200 | barak__ | (~barak@77.125.91.113) (Ping timeout: 256 seconds) |
| 2023-04-17 08:24:13 +0200 | mmhat | (~mmh@p200300f1c7106ee3ee086bfffe095315.dip0.t-ipconnect.de) |
| 2023-04-17 08:25:08 +0200 | barak | (~barak@2a02:14f:83:1a53:93c8:3a8d:cf2e:727d) |
| 2023-04-17 08:27:56 +0200 | ski | idly notes that ujjwalgupta[m] repeated those messages |
| 2023-04-17 08:29:34 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 08:30:41 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 08:32:59 +0200 | califax | (~califax@user/califx) (Remote host closed the connection) |
| 2023-04-17 08:33:25 +0200 | califax | (~califax@user/califx) |
| 2023-04-17 08:33:28 +0200 | barak_ | (~barak@77.125.91.113) |
| 2023-04-17 08:36:05 +0200 | barak | (~barak@2a02:14f:83:1a53:93c8:3a8d:cf2e:727d) (Ping timeout: 250 seconds) |
| 2023-04-17 08:45:37 +0200 | mncheckm | (~mncheck@193.224.205.254) |
| 2023-04-17 08:50:39 +0200 | Inst | (~Inst@2601:6c4:4081:54f0:bc9e:a2ec:406a:de9f) |
| 2023-04-17 08:51:03 +0200 | <Inst> | A question for Rustacaeans here: how does Haskell compare to Rust in terms of terseness, readability, and prototyping speed? |
| 2023-04-17 08:55:37 +0200 | Techcable | (~Techcable@user/Techcable) |
| 2023-04-17 09:00:40 +0200 | <mon_aaraj> | I think Rust is on par with Haskell in terms of readability for a few things, usually less readable than Haskell, but more readable than pretty much most other imperative languages I've used. Prototyping speed is obviously not as good as Haskell's, but it's not something to scoff at. Generally I think it's a bit worse than Haskell in most aspects, but way better than most other languages in all aspects. |
| 2023-04-17 09:01:06 +0200 | <Inst> | sorry, it's more a useless brain fart |
| 2023-04-17 09:01:15 +0200 | <Inst> | was wondering if Haskell could be marketed at something between Rust and Python |
| 2023-04-17 09:01:43 +0200 | <mon_aaraj> | I think that sends people a very wrong idea about Haskell. |
| 2023-04-17 09:02:04 +0200 | <Inst> | I mean at its core, it's an academic language where the needs of the research community are prioritized first, at least, that's my impression of it |
| 2023-04-17 09:02:06 +0200 | lortabac | (~lortabac@2a01:e0a:541:b8f0:7db4:b835:940f:b2a6) |
| 2023-04-17 09:02:30 +0200 | <Inst> | it's a useful production language, but the production guys don't get precedence |
| 2023-04-17 09:02:45 +0200 | shriekingnoise | (~shrieking@186.137.175.87) (Ping timeout: 240 seconds) |
| 2023-04-17 09:03:06 +0200 | <mon_aaraj> | It's a language where the vocal part of the community gets what it wants. |
| 2023-04-17 09:03:27 +0200 | <mon_aaraj> | When you find something that's not in Haskell, or no one's done it yet, it generally means not enough people wanted it. |
| 2023-04-17 09:04:26 +0200 | <mon_aaraj> | Nevertheless, I don't really think a change in marketing will put Haskell anywhere on the map for anyone, at least for people that haven't seen it yet. |
| 2023-04-17 09:04:27 +0200 | <[exa]> | people should not be so hesitant to go and try a new language |
| 2023-04-17 09:04:40 +0200 | szkl | (uid110435@id-110435.uxbridge.irccloud.com) |
| 2023-04-17 09:05:56 +0200 | <mon_aaraj> | I think that the thing that will change people's viewpoint in Haskell is simply companies adopting it. Which one might argue depends on marketing, but that couldn't be farther from the truth. It depends on more development going into the language to polish it more. Improving the complier and documentation around the language. And also on people deciding to write software in it, so that they become "killer apps" for the language. |
| 2023-04-17 09:06:39 +0200 | <mon_aaraj> | Pandoc is one such project and it's helped people get pleasantly surprised when they figure out it's made in Haskell. Wire is also one of those apps, though less well known, and I don't know if it's production ready. |
| 2023-04-17 09:07:21 +0200 | <mon_aaraj> | Bottom line is, write more code to get Haskell closer and closer to being more accepted in the mainstream. And documentation. And participate in proposals, documentation suggestions. |
| 2023-04-17 09:07:28 +0200 | <Inst> | I guess that goes into Peter Drucker's talk about European firms (of his era); in his time, American firms started with market research and marketing design first, then made products, whereas European firms of his era began with products, then looked for ways to sell it. |
| 2023-04-17 09:07:33 +0200 | <mon_aaraj> | * documentation suggestions, improving the ecosystem. |
| 2023-04-17 09:07:41 +0200 | <Inst> | I guess that's fundamentally an academic approach; come up with some novelty, try to figure out how to commercialize it. |
| 2023-04-17 09:08:10 +0200 | <Inst> | This? |
| 2023-04-17 09:08:10 +0200 | <Inst> | https://hackage.haskell.org/package/wires |
| 2023-04-17 09:08:46 +0200 | <Inst> | or this, rather |
| 2023-04-17 09:08:47 +0200 | <Inst> | https://hackage.haskell.org/package/wires |
| 2023-04-17 09:08:49 +0200 | <Inst> | https://github.com/wireapp?language=haskell |
| 2023-04-17 09:09:12 +0200 | <mon_aaraj> | https://github.com/wireapp/wire-server |
| 2023-04-17 09:10:03 +0200 | <mon_aaraj> | Personally, all language popularity I've seen is of people getting locked into using them. It was never the marketing of such languages. It was the opinion of the masses and the pre-existing codebases that use it. Where Haskell is a relatively small portion. |
| 2023-04-17 09:10:09 +0200 | <Inst> | The thing is, when it comes to corporate users, Rust is the hot new thing if they want a more experimental / esoteric language; we lost Tsuru to Rust, sadly |
| 2023-04-17 09:10:36 +0200 | <mon_aaraj> | I don't call them losses. People are interested in what they like. It's fine if they want to try out a how new thing. |
| 2023-04-17 09:10:48 +0200 | acidjnk | (~acidjnk@p200300d6e715c491dc796c235bb1f77a.dip0.t-ipconnect.de) |
| 2023-04-17 09:10:50 +0200 | <mon_aaraj> | And Haskell is definitely the more esoteric language here. |
| 2023-04-17 09:10:58 +0200 | <Inst> | I think if you want correctness at all costs, you do Idris or some other dependently-typed language, if you want performance at all costs with memory-safety and type-safety, play with Rust, if you want speed at all costs, without care for scalability, Python |
| 2023-04-17 09:11:22 +0200 | <mon_aaraj> | That sounds like a skewed list. |
| 2023-04-17 09:11:24 +0200 | <probie> | If you want ease of refactoring, go with Haskell |
| 2023-04-17 09:11:44 +0200 | <Inst> | Haskell is, unfortunately, in the middle of the pack; i.e, compared to the DT langs, it has a more mature ecosystem, compared to Rust, it has better prototyping speed and productivity, compared to Python, it has better performance and safety |
| 2023-04-17 09:11:56 +0200 | <jackdk> | I call that the "sweet spot" |
| 2023-04-17 09:11:57 +0200 | <Inst> | but that can also be seen as a strength; a swiss army knife |
| 2023-04-17 09:13:03 +0200 | <mon_aaraj> | No one wants "correctness at all costs" or puts that into their mind when trying to learn a language. People don't go into Idris thinking "I'm going to use this language to write a totally correct application". They are either interested in Idris because of it's features, or they want to prove some theorems and wish to try out or prefe Idris. Same for performance, type-safety, or speed without care (which Python isn't speedy, I don't know why |
| 2023-04-17 09:13:03 +0200 | <mon_aaraj> | someone would go for it) |
| 2023-04-17 09:13:31 +0200 | <mon_aaraj> | When people want to learn a language, it hits a sweet spot for them. No one thinks in absolute. They notice a set of features that they like and think are useful. |
| 2023-04-17 09:13:43 +0200 | <mon_aaraj> | s/absolute/absolutes/ |
| 2023-04-17 09:14:31 +0200 | <Inst> | the only drawback I think is that we make learning Haskell too difficult, when Gabriella Gonzalez goes the route of: "please hack more and hack earlier in learning Haskell" |
| 2023-04-17 09:14:46 +0200 | <mon_aaraj> | When you ask someone why they use Python, they wouldn't say "Oh, because I prefer speed at all costs!". They'll say some generic "good" statements about it and it's ecosystem or the reason they're locked into it. Everyone has their values. |
| 2023-04-17 09:14:52 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 252 seconds) |
| 2023-04-17 09:15:04 +0200 | <Inst> | people get scared of Haskell, when it's really just main = do; go |
| 2023-04-17 09:15:11 +0200 | <Inst> | idiomatic and type-level Haskell is hard |
| 2023-04-17 09:15:20 +0200 | <Inst> | trashy Haskell that works isn't worse than any other language |
| 2023-04-17 09:15:49 +0200 | <Inst> | for corporate users, letting them know that anyone can code in Haskell if you don't demand it to be good Haskell, that a choice is available, should be a relief |
| 2023-04-17 09:16:01 +0200 | lisbeths | (uid135845@id-135845.lymington.irccloud.com) |
| 2023-04-17 09:16:53 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-04-17 09:16:55 +0200 | <Inst> | "Here's IORef. When you use it, someone will clean up after you for the first 6 weeks. If you're still using it after that and not a senior developer, you're either transferred off the team or fired" |
| 2023-04-17 09:17:19 +0200 | hugo | (znc@verdigris.lysator.liu.se) (Ping timeout: 265 seconds) |
| 2023-04-17 09:17:24 +0200 | <mon_aaraj> | That shouldn't be taught to beginners. At least not as one of the first things. |
| 2023-04-17 09:18:34 +0200 | <mon_aaraj> | The thing with people learning Haskell is that they think they have to choose a project that works for it. Or they think that they can't do multiple things at once and can only read a book and never do any projects while reading it. That's the wrong way to do it. It's emphasized in the general programming world that if you want to learn or figure something out, you have to write it. Experiment in code. |
| 2023-04-17 09:19:20 +0200 | bitmapper | (uid464869@id-464869.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2023-04-17 09:19:20 +0200 | <mon_aaraj> | The only thing people should keep in their mind from moving from Python to Haskell, is that just like they made tons of projects in Python to learn it (at least that's what I did), they need to make tons of projects in Haskell to learn it. |
| 2023-04-17 09:19:50 +0200 | <jackdk> | I don't think I can adequately express how much I disagree with "someone will clean up after you; learn by this deadline or you're fired" as a teaching style, a management discipline, or a way to get any sort of positive response out of anyone |
| 2023-04-17 09:20:23 +0200 | <mon_aaraj> | Yes. I don't think it's healthy at all to teach bad practices as one of the first things in a resource. |
| 2023-04-17 09:21:14 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 09:21:32 +0200 | hugo | (znc@verdigris.lysator.liu.se) |
| 2023-04-17 09:21:47 +0200 | <mon_aaraj> | I think one thing that would massively boost Haskell learning and usage would be good documentation in the haskell.org website. OCaml has a whole tutorial in their website that gets people up and running and give some pretty decent knowledge of the language, we can do that as well. |
| 2023-04-17 09:22:21 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 09:22:43 +0200 | coot | (~coot@213.134.170.228) |
| 2023-04-17 09:23:00 +0200 | <mon_aaraj> | We do... "have" one... But, you know. |
| 2023-04-17 09:23:00 +0200 | <mon_aaraj> | https://www.haskell.org/tutorial/intro.html |
| 2023-04-17 09:23:00 +0200 | <mon_aaraj> | It's a bit... |
| 2023-04-17 09:24:28 +0200 | <mon_aaraj> | The sad thing is that there's a lot of outdated resources. Probably one of the most harmful things. Like outdated Stack Overflow answers. If I had enough rep I'd try to go through and edit them, but I don't. |
| 2023-04-17 09:24:47 +0200 | <Inst> | I mean we could easily follow Rust or Go when it comes to tutorial documentation on the website. |
| 2023-04-17 09:25:02 +0200 | <Inst> | Haskell Phrasebook is pretty good, and they actually teach mutable variables (using TVar of all things!) very early on |
| 2023-04-17 09:25:25 +0200 | <jackdk> | Why though? You are going to fight the language at every turn if you try to write haskell using mutable vars |
| 2023-04-17 09:25:42 +0200 | <mon_aaraj> | Yeah I don't get this obsession with mutable variables. |
| 2023-04-17 09:26:00 +0200 | <jackdk> | mon_aaraj: That intro is indeed "gentle". I'm reminded of the intro to Python that I read, which happened to hit the same common knowledge I had at the time and so I started coding very quickly. Revisiting the Gentle Introduction has the same vibe; it's concise and builds off assumed knowledge that I actually have now. |
| 2023-04-17 09:26:01 +0200 | <mon_aaraj> | The Haskell Phrasebook is very devoid of a lot of useful things. |
| 2023-04-17 09:26:48 +0200 | <mon_aaraj> | jackdk: Yeah, the issue is that the content is not presented in the most beautiful manner, to put it lightly. |
| 2023-04-17 09:26:56 +0200 | <jackdk> | mon_aaraj: If you want to modernising SO answers, feel free to DM me and I can try reviewing them. (I have a fair amount of rep, but not on haskell tags; unsure if that matters) |
| 2023-04-17 09:27:05 +0200 | <Inst> | I learned Haskell as a first language; but I understand a lot of learners freak out and give up when they're forced to do everything without mutation. |
| 2023-04-17 09:27:27 +0200 | <mon_aaraj> | When I first learned Haskell, that wasn't the case. |
| 2023-04-17 09:27:29 +0200 | <Inst> | The idea is just to give them an escape hatch, if you can't grok it or do it without mutation, here's a mutable, or more preferably, STRef |
| 2023-04-17 09:27:45 +0200 | <Inst> | You're a successful case, whereas there's people who ran off at recursion, and people who ran off at monads |
| 2023-04-17 09:27:57 +0200 | <mon_aaraj> | I did run off at Monads. |
| 2023-04-17 09:28:11 +0200 | <mon_aaraj> | And recursion gave me a run for my money, as well. |
| 2023-04-17 09:28:18 +0200 | <jackdk> | I would instead teach accumulating parameters and recursion of a helper function, which matches the idioms the learner will see in the wild, |
| 2023-04-17 09:28:23 +0200 | <mon_aaraj> | The issue I had with Haskell when I first started is that the resources were very scattered, though. Not the Monads or the recursion. |
| 2023-04-17 09:28:44 +0200 | <Inst> | yeah, I tell people who freak out at Haskell "you can do virtually everything you do with mutation with accumulating parameters" |
| 2023-04-17 09:29:01 +0200 | <mon_aaraj> | If the resources were as good as Rust's are right now, I would've probably "gotten" Haskell way earlier. |
| 2023-04-17 09:29:01 +0200 | <Inst> | and honestly, you're right, accum parameters are idiomatic |
| 2023-04-17 09:29:18 +0200 | <Inst> | and correct, because the compiler, I'm told, will TCO it into a for loop much of the time |
| 2023-04-17 09:29:34 +0200 | <Inst> | outperformed a literal for loop via STref in benchmarks, iirc |
| 2023-04-17 09:29:36 +0200 | <jackdk> | Recursion's utility is not immediately obvious; I used to have an errata card for my BASIC cartridge that said they took it out |
| 2023-04-17 09:30:01 +0200 | gmg | (~user@user/gehmehgeh) |
| 2023-04-17 09:30:15 +0200 | <probie> | Into a "for loop"? What hardware are you running? :p |
| 2023-04-17 09:30:22 +0200 | <Inst> | I still don't understand why we bother with recursive data structures; as I've mentioned elsewhere, the Racketeers teach recursion starting with recursive data structures, because for recursive data structures, recursion is just natural |
| 2023-04-17 09:30:32 +0200 | tzh_ | (~tzh@c-24-21-73-154.hsd1.wa.comcast.net) (Quit: zzz) |
| 2023-04-17 09:30:43 +0200 | <Inst> | iirc, the way I understand it |
| 2023-04-17 09:31:17 +0200 | <Inst> | recursive data structures expand dynamically at runtime, whereas non-recursive data structures are fixed, but that doesn't seem like a strong enough argument |
| 2023-04-17 09:32:03 +0200 | gmg | (~user@user/gehmehgeh) (Remote host closed the connection) |
| 2023-04-17 09:32:22 +0200 | <mon_aaraj> | Inst: I don't understand? Aren't those conflicting things? |
| 2023-04-17 09:32:44 +0200 | gmg | (~user@user/gehmehgeh) |
| 2023-04-17 09:33:03 +0200 | <Inst> | what's conflicting? |
| 2023-04-17 09:34:06 +0200 | <mon_aaraj> | You ask why we bother with recursive data structures, and say that racketeers teach using them because recursion is natural for those data structures. Doesn't that mean what we're "bothering" with is good? |
| 2023-04-17 09:34:24 +0200 | gensyst | (~gensyst@user/gensyst) |
| 2023-04-17 09:34:51 +0200 | <Inst> | i mean, i try to convert recursion to dynamic programming when i can |
| 2023-04-17 09:35:20 +0200 | <Inst> | it imposes a cost in many cases, except that with the case of recursive data structures |
| 2023-04-17 09:35:23 +0200 | <gensyst> | Is there such a thing as "writing friendly progress report (e.g. % completed) to stdout" for multithreaded programs? I'm thinking % progress for each thread going on each line, and lines getting removed (or stacked on top) as threads complete. |
| 2023-04-17 09:35:26 +0200 | <gensyst> | Has someone worked on this? |
| 2023-04-17 09:35:27 +0200 | cfricke | (~cfricke@user/cfricke) |
| 2023-04-17 09:35:35 +0200 | <mon_aaraj> | Um, I still don't understand that first sentence. I'm very confused what recursion has to do with dynamic programming. |
| 2023-04-17 09:35:38 +0200 | <Inst> | recursion is the optimal way to work with recursive data structures |
| 2023-04-17 09:36:07 +0200 | <Inst> | well, the point of racketeers preferring recursive data types to teach recursion is because recursive algorithms are optimal for recursive data structures |
| 2023-04-17 09:36:21 +0200 | <Inst> | you're not supposed to be using recursive factorial or fibonacci |
| 2023-04-17 09:36:48 +0200 | <Inst> | they consider it forced, and not a good demonstration of recursion |
| 2023-04-17 09:37:03 +0200 | <Inst> | i literally got Haskell to outperform Rust because of recursive factorial ;) |
| 2023-04-17 09:37:23 +0200 | <Inst> | iirc, there's a primeswing algorithm that I don't understand |
| 2023-04-17 09:37:36 +0200 | <mon_aaraj> | That's.... a _very_ weird line of thought? Like the last 12 messages you sent I can't really make logical sense out of. |
| 2023-04-17 09:37:40 +0200 | <Inst> | sorry |
| 2023-04-17 09:37:42 +0200 | <Inst> | a bit drunk |
| 2023-04-17 09:37:47 +0200 | <Inst> | forget it, maybe later |
| 2023-04-17 09:37:47 +0200 | <[exa]> | mon_aaraj: typically dynamic programs are very recursively defined where you memoize a lot of the recursion with some clever caching scheme |
| 2023-04-17 09:38:14 +0200 | <Inst> | as far as I understand, in an imperative language, dynamic programming is better than recursion, when you can translate the recursion to dynamic programming efficiently |
| 2023-04-17 09:38:24 +0200 | <mon_aaraj> | What does "dynamic programs" mean here? Like programs written in Python? |
| 2023-04-17 09:38:42 +0200 | <[exa]> | mon_aaraj: https://en.wikipedia.org/wiki/Dynamic_programming |
| 2023-04-17 09:39:27 +0200 | <mon_aaraj> | Ah. I suppose the name just confused me. |
| 2023-04-17 09:39:37 +0200 | _ht | (~Thunderbi@28-52-174-82.ftth.glasoperator.nl) |
| 2023-04-17 09:40:41 +0200 | <Hecate> | mon_aaraj: yes it's fairly overloaded |
| 2023-04-17 09:40:52 +0200 | <[exa]> | yeah it's been named in like 60ties and no one cared to really push for a better one yet |
| 2023-04-17 09:41:18 +0200 | <Inst> | tabFib u = go 1 1 u; where go _ b 1 = b; go a b n = go (a + b) a (n-1) |
| 2023-04-17 09:41:38 +0200 | <probie> | Dynamic Programming is Dynamic Programming. I'm not sure if I'd normally connect "Dynamic Programs" to "Dynamic Programming" |
| 2023-04-17 09:41:53 +0200 | kenran | (~user@user/kenran) |
| 2023-04-17 09:42:13 +0200 | <Inst> | could do that via a for loop instead and still outperform |
| 2023-04-17 09:42:36 +0200 | <darkling> | One talks about "Integer Programs" when doing Integer Programming, so I guess you could do the same for DP. |
| 2023-04-17 09:43:12 +0200 | <Inst> | unmemoFib u | u `elem` [1,2] = 1; unmemoFib u = unmemoFib (u-1) + unmemoFib (u-2) |
| 2023-04-17 09:44:01 +0200 | <Inst> | canonical fib is still via matrices or binet |
| 2023-04-17 09:45:20 +0200 | azimut | (~azimut@gateway/tor-sasl/azimut) (Ping timeout: 255 seconds) |
| 2023-04-17 09:46:11 +0200 | nate1 | (~nate@98.45.169.16) |
| 2023-04-17 09:46:16 +0200 | <Inst> | i wonder how long it'll take to compute unmemoFib 100? ugh |
| 2023-04-17 09:46:43 +0200 | <jackdk> | gensyst: https://hackage.haskell.org/package/concurrent-output maybe? |
| 2023-04-17 09:48:25 +0200 | <probie> | Inst: That's version with the accumulator is "fast" because after TCO you end up with something like (in some psuedo imperative code) { a = 1; b = 1; go: if (n == 1) return b; a, b, n = a+b, b, n-1; goto go; }. That involves a lot less book-keeping than a for loop |
| 2023-04-17 09:48:28 +0200 | <jade[m]> | Inst: ~2^99 slower than unmemoFib 1? |
| 2023-04-17 09:51:01 +0200 | nate1 | (~nate@98.45.169.16) (Ping timeout: 240 seconds) |
| 2023-04-17 09:51:38 +0200 | ubert1 | (~Thunderbi@p200300ecdf114f254c3df6d95498bb99.dip0.t-ipconnect.de) |
| 2023-04-17 09:55:48 +0200 | machinedgod | (~machinedg@d198-53-218-113.abhsia.telus.net) |
| 2023-04-17 09:59:43 +0200 | vglfr | (~vglfr@46.96.159.156) (Ping timeout: 250 seconds) |
| 2023-04-17 10:01:08 +0200 | <gensyst> | jackdk, thanks!!! exactly what i'm after! |
| 2023-04-17 10:01:24 +0200 | <jitrs[m]> | @pl \hole -> f x hole y |
| 2023-04-17 10:01:24 +0200 | <lambdabot> | flip (f x) y |
| 2023-04-17 10:03:54 +0200 | falafel | (~falafel@2603-8000-d700-115c-1838-e7fa-9b4f-bace.res6.spectrum.com) |
| 2023-04-17 10:04:23 +0200 | merijn | (~merijn@185.143.104.11) |
| 2023-04-17 10:09:12 +0200 | hugo | (znc@verdigris.lysator.liu.se) (Ping timeout: 255 seconds) |
| 2023-04-17 10:09:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:09:45 +0200 | barak_ | (~barak@77.125.91.113) (Ping timeout: 240 seconds) |
| 2023-04-17 10:09:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:09:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:10:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:10:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:10:21 +0200 | tango | (~tango@5-157-196-109.itvmedia.pl) |
| 2023-04-17 10:10:22 +0200 | tango | (~tango@5-157-196-109.itvmedia.pl) (Write error: Broken pipe) |
| 2023-04-17 10:10:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:10:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:10:36 +0200 | tango88 | (~tango88@5-157-196-109.itvmedia.pl) |
| 2023-04-17 10:10:38 +0200 | ub | (~Thunderbi@p200300ecdf114f258f5f321c9488c19d.dip0.t-ipconnect.de) |
| 2023-04-17 10:10:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:10:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:10:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:10:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:11:05 +0200 | ubert | (~Thunderbi@p548c84d6.dip0.t-ipconnect.de) (Ping timeout: 240 seconds) |
| 2023-04-17 10:11:05 +0200 | ubert1 | ubert |
| 2023-04-17 10:11:06 +0200 | ubert | 068AAFKQ3 |
| 2023-04-17 10:11:06 +0200 | ub | 030AAFWAZ |
| 2023-04-17 10:11:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:11:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:11:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:11:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:11:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:11:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:11:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:11:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:12:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:12:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:12:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:12:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:12:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:12:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:13:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:13:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:13:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:13:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:13:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:13:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:13:38 +0200 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2023-04-17 10:13:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:13:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:14:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:14:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:14:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:14:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:14:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:14:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:14:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:14:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:15:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:15:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:15:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:15:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:15:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:15:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:15:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:15:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:16:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:16:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:16:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:16:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:16:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:16:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:16:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:16:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:17:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:17:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:17:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:17:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:17:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:17:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:17:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:17:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:18:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:18:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:18:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:18:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:18:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:18:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:18:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:18:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:19:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:19:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:19:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:19:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:19:42 +0200 | hugo | (znc@verdigris.lysator.liu.se) |
| 2023-04-17 10:19:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:19:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:19:56 +0200 | gurkenglas | (~gurkengla@dynamic-046-114-180-034.46.114.pool.telefonica.de) |
| 2023-04-17 10:20:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:20:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:20:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:20:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:20:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:20:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:20:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:20:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:20:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:21:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:21:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:21:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:21:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:21:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:21:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:21:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:22:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:22:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:22:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:22:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:22:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:22:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:22:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:22:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:23:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:23:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:23:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:23:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:23:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:23:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:23:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:23:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:24:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:24:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:24:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:24:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:24:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:24:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:24:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:24:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:25:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:25:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:25:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:25:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:25:37 +0200 | ubert | (~Thunderbi@p548c84d6.dip0.t-ipconnect.de) |
| 2023-04-17 10:25:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:25:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:25:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:25:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:26:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:26:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:26:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:26:26 +0200 | 030AAFWAZ | (~Thunderbi@p200300ecdf114f258f5f321c9488c19d.dip0.t-ipconnect.de) (Ping timeout: 265 seconds) |
| 2023-04-17 10:26:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:26:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:26:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:26:55 +0200 | _xor | (~xor@74.215.46.17) |
| 2023-04-17 10:26:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:26:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:27:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:27:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:27:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:27:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:27:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:27:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:28:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:28:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:28:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:28:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:28:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:28:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:28:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:28:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:29:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:29:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:29:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:29:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:29:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:29:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:29:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:29:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:30:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:30:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:30:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:30:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:30:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:30:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:30:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:30:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:31:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:31:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:31:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:31:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:31:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:31:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:31:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:31:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:32:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:32:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:32:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:32:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:32:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:32:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:32:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:32:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:33:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:33:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:33:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:33:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:33:43 +0200 | merijn | (~merijn@185.143.104.11) (Ping timeout: 265 seconds) |
| 2023-04-17 10:33:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:33:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:33:47 +0200 | jpds1 | (~jpds@gateway/tor-sasl/jpds) |
| 2023-04-17 10:33:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:33:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:34:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:34:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:34:16 +0200 | <tango88> | Hi, I was wondering how exactly deriving Eq instance works, which led me to trying to find the mechanism description in Haskell Report 2010, but to no avail (seems extremely simple, but still couldn't find decisive information about it; 11.1 appears to be the place to look for it). Does the report define how exactly is Eq derived? |
| 2023-04-17 10:34:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:34:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:34:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:34:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:35:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:35:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:35:09 +0200 | _xor | (~xor@74.215.46.17) (Quit: brb) |
| 2023-04-17 10:35:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:35:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:35:32 +0200 | <mauke> | @where ops |
| 2023-04-17 10:35:32 +0200 | <lambdabot> | byorgey Cale conal copumpkin dcoutts dibblego dolio edwardk geekosaur glguy jmcarthur johnw mniip monochrom quicksilver shachaf shapr ski |
| 2023-04-17 10:35:35 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:35:35 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:35:44 +0200 | jpds | (~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds) |
| 2023-04-17 10:35:49 +0200 | <mauke> | lambdap237's connection is flapping |
| 2023-04-17 10:35:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:35:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:36:05 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:36:05 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:36:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:36:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:36:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:36:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:36:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:36:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:37:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:37:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:37:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:37:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:37:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:37:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:37:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:37:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:38:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:38:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:38:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:38:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:38:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:38:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:38:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:38:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:39:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:39:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:39:18 +0200 | <mauke> | tango88: yes, 11.1 is the spec for derived Eq instances |
| 2023-04-17 10:39:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:39:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:39:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:39:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:39:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:39:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:40:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:40:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:40:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:40:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:40:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:40:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:41:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:41:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:41:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:41:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:41:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:41:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:41:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:42:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:42:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:42:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:42:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:42:30 +0200 | 068AAFKQ3 | (~Thunderbi@p200300ecdf114f254c3df6d95498bb99.dip0.t-ipconnect.de) (Remote host closed the connection) |
| 2023-04-17 10:42:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:42:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:42:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:42:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:43:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:43:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:43:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:43:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:43:23 +0200 | merijn | (~merijn@195.114.232.94) |
| 2023-04-17 10:43:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:43:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:43:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:43:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:44:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:44:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:44:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:44:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:44:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:44:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:44:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:44:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:45:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:45:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:45:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:45:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:45:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:45:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:45:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:45:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:46:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:46:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:46:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:46:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:46:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:46:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:46:53 +0200 | <tango88> | mauke: Although the chapter is extremely short, I couldn't find decisive information regarding the deriving mechanism - for example "returning True if constructors match or have defined Eq instance". Does the report skip this definition and expect compiler to provide sanest solution or maybe is it implicitly defined and I'm just missing it? |
| 2023-04-17 10:46:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:46:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:47:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:47:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:47:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:47:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:47:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:47:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:47:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:47:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:48:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:48:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:48:27 +0200 | <mauke> | tango88: huh. technically I guess the report places no constraints on derived (==) :-) |
| 2023-04-17 10:48:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:48:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:48:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:48:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:48:51 +0200 | <tango88> | mauke: i see, thanks |
| 2023-04-17 10:48:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:48:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:49:00 +0200 | <mauke> | tango88: I think it is assumed that the generated Eq instance is compatible with Ord, which specifies lexicographic ordering |
| 2023-04-17 10:49:10 +0200 | <mauke> | might be a genuine spec bug, though :-) |
| 2023-04-17 10:49:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:49:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:49:20 +0200 | use-value | (~Thunderbi@2a00:23c6:8a03:2f01:9de4:e162:b48:6951) |
| 2023-04-17 10:49:22 +0200 | ChanServ | +o shachaf |
| 2023-04-17 10:49:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:49:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:49:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:49:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:50:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:50:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:50:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:50:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 10:50:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 10:50:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 10:50:42 +0200 | shachaf | +b lambdap237!*@*$##fix_your_connection |
| 2023-04-17 10:50:48 +0200 | shachaf | -o shachaf |
| 2023-04-17 10:51:39 +0200 | acidjnk | (~acidjnk@p200300d6e715c491dc796c235bb1f77a.dip0.t-ipconnect.de) (Ping timeout: 260 seconds) |
| 2023-04-17 10:51:45 +0200 | acidjnk_new | (~acidjnk@p200300d6e715c4911dc1249c1b9c31fa.dip0.t-ipconnect.de) |
| 2023-04-17 10:53:14 +0200 | <mauke> | tango88: the more I think about it, the more I think you've found a bug/oversight in the report |
| 2023-04-17 10:54:08 +0200 | harveypwca | (~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) (Quit: Leaving) |
| 2023-04-17 10:57:00 +0200 | <mauke> | hah. bug reports are to be sent to the haskell-prime group, whose website is gone and whose mailing list is dead |
| 2023-04-17 10:57:57 +0200 | dextaa | (~DV@user/dextaa) (Quit: Ping timeout (120 seconds)) |
| 2023-04-17 10:58:13 +0200 | APic | (apic@apic.name) |
| 2023-04-17 10:58:22 +0200 | dextaa | (~DV@user/dextaa) |
| 2023-04-17 11:05:36 +0200 | nitr0gen | (~nitr0gen@2405:201:a:a9d5:29f7:7ac1:3e43:bce) |
| 2023-04-17 11:07:14 +0200 | jpds1 | (~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds) |
| 2023-04-17 11:07:16 +0200 | <merijn> | I'm sure we'll get Haskell Prime any moment now |
| 2023-04-17 11:08:13 +0200 | gmg | (~user@user/gehmehgeh) (Remote host closed the connection) |
| 2023-04-17 11:08:26 +0200 | gnalzo | (~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) |
| 2023-04-17 11:10:42 +0200 | kuribas | (~user@ip-188-118-57-242.reverse.destiny.be) |
| 2023-04-17 11:11:58 +0200 | <probie> | I think the way to get Haskell Prime is for someone to write another Haskell compiler to force the need for a spec, except I also want to bootstrap it, so can they actually write two (with one not in Haskell) and/or make it buildable with hugs? |
| 2023-04-17 11:12:03 +0200 | Axman6 | (~Axman6@user/axman6) (Ping timeout: 240 seconds) |
| 2023-04-17 11:13:59 +0200 | <merijn> | If you wanna do that, I'd start from UHC, not hugs, tbh |
| 2023-04-17 11:16:32 +0200 | <[Leary]> | The deriving mechanism must assume full transparency, so the Eq laws already constitute a full specification. Unfortunately, section 6.3.1 does not include those laws... |
| 2023-04-17 11:17:46 +0200 | <probie> | Isn't UHC written in Haskell? Hugs is written in C which makes it bootstrap friendly |
| 2023-04-17 11:19:21 +0200 | <merijn> | probie: Hugs has also been dead for far longer and less support for Haskell2010/extension than UHC :p |
| 2023-04-17 11:21:08 +0200 | jpds1 | (~jpds@gateway/tor-sasl/jpds) |
| 2023-04-17 11:22:28 +0200 | barcisz | (~barcisz@79.191.65.29.ipv4.supernova.orange.pl) |
| 2023-04-17 11:26:12 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) |
| 2023-04-17 11:27:49 +0200 | falafel | (~falafel@2603-8000-d700-115c-1838-e7fa-9b4f-bace.res6.spectrum.com) (Ping timeout: 265 seconds) |
| 2023-04-17 11:29:46 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:e40f:1779:8d3b:ad7d) (Remote host closed the connection) |
| 2023-04-17 11:35:14 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 11:36:48 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 11:42:07 +0200 | robosexual | (~spaceoyst@5.165.10.6) |
| 2023-04-17 11:42:13 +0200 | econo | (uid147250@user/econo) (Quit: Connection closed for inactivity) |
| 2023-04-17 11:46:05 +0200 | tango88 | (~tango88@5-157-196-109.itvmedia.pl) (Quit: Client closed) |
| 2023-04-17 11:52:35 +0200 | tango88 | (~tango88@5-157-196-109.itvmedia.pl) |
| 2023-04-17 12:00:26 +0200 | phma_ | (phma@2001:5b0:210d:6758:ea1f:1d6e:9ba6:7e12) |
| 2023-04-17 12:00:41 +0200 | phma | (~phma@2001:5b0:211b:b518:b882:9716:7840:b9e6) (Read error: Connection reset by peer) |
| 2023-04-17 12:03:23 +0200 | tango88 | (~tango88@5-157-196-109.itvmedia.pl) (Quit: Client closed) |
| 2023-04-17 12:06:04 +0200 | xff0x | (~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp) (Ping timeout: 276 seconds) |
| 2023-04-17 12:06:35 +0200 | acidjnk_new | (~acidjnk@p200300d6e715c4911dc1249c1b9c31fa.dip0.t-ipconnect.de) (Ping timeout: 248 seconds) |
| 2023-04-17 12:09:43 +0200 | __monty__ | (~toonn@user/toonn) |
| 2023-04-17 12:10:46 +0200 | acidjnk | (~acidjnk@p200300d6e715c49189eeee6d6a223043.dip0.t-ipconnect.de) |
| 2023-04-17 12:14:02 +0200 | naine[m] | (~naine-env@2001:470:69fc:105::3:2e57) |
| 2023-04-17 12:15:27 +0200 | nain | (~nain@169.150.218.79) |
| 2023-04-17 12:23:18 +0200 | <probie> | and since our goal is Haskell prime, I'll go back to my alternate request: One GHC competitor (written in Haskell) and one other compiler/interpreter to bootstrap it (written in C/Scheme/Common Lisp/any other language I can bootstrap to from something "simple" like C or Forth) |
| 2023-04-17 12:28:17 +0200 | <int-e> | how much money are you going to pay to make this wish come true? |
| 2023-04-17 12:28:29 +0200 | <int-e> | there aren't many brownie points to earn here |
| 2023-04-17 12:29:56 +0200 | <int-e> | both nhc and jhc were strong ghc competitors once but kind of died |
| 2023-04-17 12:30:16 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:a8fa:974a:df0c:83d2) |
| 2023-04-17 12:30:18 +0200 | <c_wraith> | you quickly run into the problem that a lot more people care about new features than having multiple implementations |
| 2023-04-17 12:30:45 +0200 | <int-e> | for better or worse, self-hosting is the norm for compilers |
| 2023-04-17 12:33:17 +0200 | enoq | (~enoq@2a05:1141:1f5:5600:b9c9:721a:599:bfe7) |
| 2023-04-17 12:34:31 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:a8fa:974a:df0c:83d2) (Ping timeout: 240 seconds) |
| 2023-04-17 12:35:37 +0200 | <probie> | I'll pay in exposure :p Jokes aside, whilst a "GHC competitor" was just to force Haskell Prime to materialise, I do actually want my toolchain bootstrappable, and would be willing to spend some of my own time to make happen |
| 2023-04-17 12:36:19 +0200 | <jackdk> | probie: we should talk |
| 2023-04-17 12:37:17 +0200 | <int-e> | probie: people die of exposure |
| 2023-04-17 12:41:55 +0200 | <int-e> | I understand the desire, but I have a hard time imagining a world where an alternative Haskell implementation actually gains traction, as long as ghc is maintained at the pace it's being maintained right now. |
| 2023-04-17 12:48:09 +0200 | <Hecate> | I think our best bet is in a modular GHC |
| 2023-04-17 12:48:25 +0200 | <Hecate> | where people can plug components like the external STG interpreter, another frontend, etc |
| 2023-04-17 12:50:05 +0200 | pyook | (~puke@user/puke) (Ping timeout: 240 seconds) |
| 2023-04-17 12:52:21 +0200 | ChanServ | +o litharge |
| 2023-04-17 12:52:21 +0200 | litharge | -bo lambdap237!*@*$##fix_your_connection litharge |
| 2023-04-17 12:52:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:52:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:52:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:52:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:52:53 +0200 | phma_ | phma |
| 2023-04-17 12:52:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:52:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:53:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:53:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:53:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:53:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:53:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:53:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:53:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:53:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:54:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:54:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:54:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:54:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:54:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:54:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:55:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:55:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:55:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:55:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:55:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:55:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:55:43 +0200 | <int-e> | who banned this last... shachaf? |
| 2023-04-17 12:55:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:55:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:56:05 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:56:05 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:56:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:56:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:56:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:56:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:56:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:56:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:57:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:57:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:57:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:57:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:57:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:57:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:57:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:57:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:58:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:58:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:58:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:58:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:58:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:58:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:58:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:58:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:59:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:59:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:59:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:59:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:59:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:59:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 12:59:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 12:59:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:00:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:00:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:00:13 +0200 | pyook | (~puke@user/puke) |
| 2023-04-17 13:00:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:00:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:00:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:00:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:00:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:00:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:01:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:01:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:01:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:01:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:01:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:01:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:01:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:01:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:02:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:02:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:02:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:02:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:02:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:02:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:02:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:02:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:03:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:03:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:03:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:03:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:03:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:03:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:03:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:03:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:04:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:04:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:04:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:04:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:04:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:04:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:04:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:04:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:04:59 +0200 | xff0x | (~xff0x@2405:6580:b080:900:1f6d:bb02:ed12:309d) |
| 2023-04-17 13:05:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:05:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:05:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:05:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:05:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:05:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:05:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:05:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:06:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:06:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:06:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:06:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:06:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:06:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:06:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:06:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:07:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:07:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:07:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:07:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:07:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:07:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:07:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:07:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:08:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:08:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:08:13 +0200 | bitmapper | (uid464869@id-464869.lymington.irccloud.com) |
| 2023-04-17 13:08:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:08:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:08:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:08:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:08:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:08:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:09:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:09:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:09:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:09:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:09:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:09:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:09:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:09:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:10:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:10:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:10:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:10:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:10:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:10:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:10:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:10:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:11:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:11:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:11:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:11:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:11:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:11:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:11:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:11:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:12:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:12:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:12:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:12:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:12:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:12:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:12:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:12:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:13:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:13:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:13:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:13:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:13:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:13:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:13:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:13:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:14:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:14:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:14:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:14:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:14:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:14:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:14:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:14:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:15:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:15:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:15:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:15:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:15:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:15:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:15:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:15:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:16:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:16:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:16:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:16:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:16:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:16:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:16:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:16:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:17:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:17:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:17:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:17:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:17:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:17:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:18:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:18:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:18:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:18:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:18:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:18:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:18:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:18:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:19:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:19:05 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:19:05 +0200 | ryantrinkle | (~ryantrink@140.174.248.64) (Ping timeout: 240 seconds) |
| 2023-04-17 13:19:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:19:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:19:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:19:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:19:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:19:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:20:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:20:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:20:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:20:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:20:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:20:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:20:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:20:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:21:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:21:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:21:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:21:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:21:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:21:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:21:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:21:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:22:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:22:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:22:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:22:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:22:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:22:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:22:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:22:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:23:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:23:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:23:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:23:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:23:35 +0200 | mmhat | (~mmh@p200300f1c7106ee3ee086bfffe095315.dip0.t-ipconnect.de) (Quit: WeeChat 3.8) |
| 2023-04-17 13:23:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:23:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:23:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:23:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:24:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:24:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:24:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:24:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:24:25 +0200 | kenran | (~user@user/kenran) (Ping timeout: 240 seconds) |
| 2023-04-17 13:24:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:24:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:24:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:24:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:25:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:25:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:25:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:25:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:25:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:25:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:25:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:25:55 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:26:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:26:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:26:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:26:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:26:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:26:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:26:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:26:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:27:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:27:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:27:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:27:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:27:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:27:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:27:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:27:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:28:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:28:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:28:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:28:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:28:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:28:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:28:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:28:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:29:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:29:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:29:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:29:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:29:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:29:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:30:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:30:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:30:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:30:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:30:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:30:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:30:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:30:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:31:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:31:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:31:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:31:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:31:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:31:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:31:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:31:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:32:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:32:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:32:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:32:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:32:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:32:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:32:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:32:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:33:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:33:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:33:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:33:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:33:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:33:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:33:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:33:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:34:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:34:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:34:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:34:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:34:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:34:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:34:49 +0200 | vglfr | (~vglfr@37.73.131.184) |
| 2023-04-17 13:34:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:34:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:35:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:35:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:35:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:35:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:35:27 +0200 | jinsl- | (~jinsl@2408:8207:2552:dc20:211:32ff:fec8:6aea) (Quit: ZNC - https://znc.in) |
| 2023-04-17 13:35:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:35:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:35:38 +0200 | jinsl | (~jinsl@2408:8207:2552:dc20:211:32ff:fec8:6aea) |
| 2023-04-17 13:35:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:35:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:36:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:36:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:36:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:36:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:36:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:36:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:36:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:36:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:37:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:37:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:37:20 +0200 | vglfr | (~vglfr@37.73.131.184) (Remote host closed the connection) |
| 2023-04-17 13:37:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:37:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:37:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:37:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:37:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:37:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:38:10 +0200 | vglfr | (~vglfr@37.73.131.184) |
| 2023-04-17 13:38:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:38:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:38:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:38:26 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:38:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:38:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:38:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:38:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:39:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:39:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:39:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:39:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:39:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:39:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:39:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:39:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:40:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:40:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:40:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:40:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:40:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:40:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:41:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:41:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:41:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:41:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:41:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:41:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:41:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:41:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:42:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:42:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:42:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:42:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:42:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:42:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:42:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:42:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:43:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:43:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:43:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:43:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:43:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:43:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:43:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:43:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:44:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:44:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:44:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:44:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:44:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:44:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:44:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:44:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:45:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:45:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:45:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:45:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:45:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:45:35 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:45:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:45:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:46:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:46:05 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:46:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:46:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:46:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:46:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:46:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:46:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:47:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:47:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:47:24 +0200 | <nain> | Hi, I am looking at the Summer of Haskell Program with interest in being a mentee. |
| 2023-04-17 13:47:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:47:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:47:36 +0200 | ryantrinkle | (~ryantrink@140.174.248.64) |
| 2023-04-17 13:47:41 +0200 | nate1 | (~nate@98.45.169.16) |
| 2023-04-17 13:47:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:47:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:47:49 +0200 | <nain> | I have only recently discovered Haskell, and have been going through the intro and help pages. |
| 2023-04-17 13:47:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:47:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:48:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:48:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:48:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:48:29 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:48:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:48:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:48:52 +0200 | <nain> | I have taken a look at the ideas page too. And found three tasks of interest, that I _may_ be able to tackle (with some help :) |
| 2023-04-17 13:48:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:48:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:49:06 +0200 | <jackdk> | Welcome nain; I'm not involved on SoH but hopefully there are some here who are |
| 2023-04-17 13:49:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:49:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:49:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:49:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:49:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:49:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:50:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:50:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:50:04 +0200 | <nain> | Hi jackdk, thank you ^^. Nice to meet you. |
| 2023-04-17 13:50:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:50:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:50:15 +0200 | <jackdk> | regardless, this is a good place to ask haskell questions as you learn |
| 2023-04-17 13:50:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:50:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:50:31 +0200 | <jackdk> | lambdap237 knock it off mate |
| 2023-04-17 13:50:38 +0200 | <nain> | Oh, that's good. |
| 2023-04-17 13:50:40 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 13:50:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:50:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:51:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:51:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:51:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:51:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:51:31 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 240 seconds) |
| 2023-04-17 13:51:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:51:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:51:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:51:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:51:57 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 13:52:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:52:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:52:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:52:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:52:30 +0200 | nate1 | (~nate@98.45.169.16) (Ping timeout: 260 seconds) |
| 2023-04-17 13:52:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:52:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:52:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:52:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:52:55 +0200 | <nain> | So, is this the right place to ask about SoH tasks and discuss their suitablity given my knowledge/skills? |
| 2023-04-17 13:53:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:53:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:53:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:53:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:53:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:53:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:53:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:53:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:53:57 +0200 | <ncf> | @where ops |
| 2023-04-17 13:53:58 +0200 | <lambdabot> | byorgey Cale conal copumpkin dcoutts dibblego dolio edwardk geekosaur glguy jmcarthur johnw mniip monochrom quicksilver shachaf shapr ski |
| 2023-04-17 13:54:08 +0200 | acidjnk | (~acidjnk@p200300d6e715c49189eeee6d6a223043.dip0.t-ipconnect.de) (Ping timeout: 248 seconds) |
| 2023-04-17 13:54:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:54:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:54:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:54:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:54:33 +0200 | <ncf> | (please ban lambdap237) |
| 2023-04-17 13:54:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:54:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:54:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:54:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:55:03 +0200 | <int-e> | (and convince litharge to not undo that within 2 hours) |
| 2023-04-17 13:55:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:55:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:55:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:55:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:55:35 +0200 | <jackdk> | I don't know, nain. It's the channel named on the SoH contact page, which also suggests emailing the committee |
| 2023-04-17 13:55:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:55:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:55:49 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) |
| 2023-04-17 13:55:56 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) |
| 2023-04-17 13:55:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:55:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:56:05 +0200 | Vq | (~vq@90-227-192-206-no77.tbcn.telia.com) (Ping timeout: 240 seconds) |
| 2023-04-17 13:56:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:56:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:56:25 +0200 | nain | giggles, is that a key lambdabot? enumerating nicks.. perhaps |
| 2023-04-17 13:56:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:56:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:56:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:56:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:57:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:57:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:57:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:57:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:57:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:57:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:57:36 +0200 | <nain> | jackdk: Yeah. I'll send them a mail in a bit. Thought I'd ask here first. |
| 2023-04-17 13:57:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:57:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:57:58 +0200 | <nain> | Before mailing a committee . Sounds scary lol. hehe |
| 2023-04-17 13:58:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:58:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:58:16 +0200 | <jackdk> | I don't know who's in that space and online right now |
| 2023-04-17 13:58:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:58:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:58:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:58:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 13:58:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:58:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:59:02 +0200 | <gensyst> | ForeignPtr stuff is fine when the "close" function in C returns void. But is there a way to do robust ForeignPtr when the C "close" function returns e.g. integer that needs to be handled? (i.e. if the C "close" function returns != 0, then throw exception) |
| 2023-04-17 13:59:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:59:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:59:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:59:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:59:35 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:59:35 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 13:59:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 13:59:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:00:05 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:00:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:00:13 +0200 | <jackdk> | I would write a wrapper around the actual finaliser and attach the wrapper to the ForeignPtr. Put the wrapper code in your repo (cbits/ is a common name for this sort of thing) and tell cabal about it |
| 2023-04-17 14:00:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:00:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:00:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:00:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:00:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:00:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:00:53 +0200 | <nain> | That's okay. Thanks for the help and welcome ! |
| 2023-04-17 14:01:01 +0200 | <jackdk> | No worries |
| 2023-04-17 14:01:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:01:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:01:23 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:01:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:01:33 +0200 | <gensyst> | jackdk, ah a wrapper c function that returns void? but that only pushes the question further: what would that wrapper do with the int? |
| 2023-04-17 14:01:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:01:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:01:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:01:54 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:02:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:02:10 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:02:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:02:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:02:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:02:41 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:02:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:02:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:03:07 +0200 | Vq | (~vq@90-227-192-206-no77.tbcn.telia.com) |
| 2023-04-17 14:03:11 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:03:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:03:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:03:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:03:40 +0200 | <jackdk> | I dunno, you could find a way to get that value back into Haskell-land. Or instead of using garbage-collected values, only provide bracket-style functions so you force the cleanup and check there |
| 2023-04-17 14:03:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:03:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:03:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:03:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:04:10 +0200 | <jackdk> | or, if you wanna get really fancy, use a linear resource interface that returns the value in a way that it must be checked and dealt with |
| 2023-04-17 14:04:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:04:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:04:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:04:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:04:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:04:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:04:48 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 248 seconds) |
| 2023-04-17 14:04:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:04:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:05:14 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:05:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:05:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:05:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:05:44 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Quit: WeeChat 3.8) |
| 2023-04-17 14:05:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:05:46 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:06:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:06:01 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:06:05 +0200 | <gensyst> | jackdk, "find a way to get that value back into Haskell-land" any quick tips on this? |
| 2023-04-17 14:06:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:06:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:06:17 +0200 | <gensyst> | any standard established ways out there? |
| 2023-04-17 14:06:31 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:06:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:06:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:06:49 +0200 | <jackdk> | I'm not an FFI wizard, so not really :/. can you say more about this resource you're getting from FFI? |
| 2023-04-17 14:07:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:07:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:07:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:07:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:07:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:07:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:07:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:07:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:08:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:08:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:08:19 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:08:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:08:21 +0200 | <gensyst> | jackdk, https://libzip.org/documentation/zip_fopen.html and corresponding https://libzip.org/documentation/zip_fclose.html |
| 2023-04-17 14:08:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:08:35 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:08:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:08:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:09:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:09:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:09:08 +0200 | robosexual | (~spaceoyst@5.165.10.6) (Quit: Konversation terminated!) |
| 2023-04-17 14:09:12 +0200 | <gensyst> | jackdk, of course i could get unprofessional and just ignore that close int |
| 2023-04-17 14:09:18 +0200 | <gensyst> | but that's not the way. |
| 2023-04-17 14:09:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:09:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:09:35 +0200 | <jackdk> | https://github.com/nih-at/libzip/blob/401ef3dd977066bc8f9b9ae53ce60934501b47d0/lib/zip_fclose.c#L41 |
| 2023-04-17 14:09:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:09:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:09:52 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:09:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:10:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:10:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:10:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:10:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:10:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:10:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:10:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:10:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:11:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:11:08 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:11:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:11:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:11:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:11:40 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:11:50 +0200 | <gensyst> | jackdk, do you have anything particular in mind there? |
| 2023-04-17 14:11:54 +0200 | <jackdk> | It's not the way. If you use finalisers then you're probably looking at some kind of funky way to push the int into an IORef or something, but I think you'd have a nicer interface if you went with a bracket-style function |
| 2023-04-17 14:11:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:11:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:12:06 +0200 | <jackdk> | No, just pointing out the source isn't really doing much in fclose |
| 2023-04-17 14:12:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:12:13 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:12:20 +0200 | szkl | (uid110435@id-110435.uxbridge.irccloud.com) (Quit: Connection closed for inactivity) |
| 2023-04-17 14:12:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:12:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:12:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:12:44 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:12:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:12:59 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:13:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:13:16 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:13:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:13:30 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:13:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:13:45 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:14:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:14:00 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:14:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:14:17 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:14:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:14:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:14:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:14:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:15:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:15:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:15:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:15:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:15:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:15:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:15:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:15:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:16:01 +0200 | <gensyst> | jackdk, i was able to do a bracket-based interface but it didn't work well with streaming APIs |
| 2023-04-17 14:16:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:16:02 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:16:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:16:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:16:18 +0200 | <gensyst> | if I can "decouple" the closing (and leave it for GC), it lends itself better for streaming |
| 2023-04-17 14:16:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:16:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:16:46 +0200 | <gensyst> | as a first iteration i'll ignore that int (for now). hopefully someone has some tips on the IORef shenanigans? |
| 2023-04-17 14:16:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:16:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:17:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:17:05 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:17:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:17:21 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:17:24 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) |
| 2023-04-17 14:17:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:17:36 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:17:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:17:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:18:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:18:07 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:18:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:18:22 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:18:37 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:18:38 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:18:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:18:53 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:19:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:19:09 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:19:24 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:19:25 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:19:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:19:39 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:19:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:19:56 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:20:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:20:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:20:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:20:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:20:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:20:43 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:20:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:20:58 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:21:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:21:12 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:21:27 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:21:28 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:21:30 +0200 | <jackdk> | gensyst: you could do the streaming inside the bracket, or hand it all off to resourcet (which lets you do the finalise step explicitly; I remember using this to make a servant server forward a stream correctly) |
| 2023-04-17 14:21:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:21:42 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:21:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:21:57 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:22:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:22:15 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:22:32 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:22:33 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:22:47 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:22:48 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:23:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:23:03 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:23:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:23:18 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:23:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:23:34 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:23:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:23:49 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:24:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:24:04 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:24:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:24:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:24:35 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:24:35 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection) |
| 2023-04-17 14:24:42 +0200 | <gensyst> | jackdk, thanks! i'll look into this |
| 2023-04-17 14:24:44 +0200 | <gensyst> | lots of options :) |
| 2023-04-17 14:24:50 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:24:51 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:24:55 +0200 | gensyst | (~gensyst@user/gensyst) (Quit: Leaving) |
| 2023-04-17 14:25:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:25:06 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:25:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) |
| 2023-04-17 14:25:20 +0200 | ChanServ | +o litharge |
| 2023-04-17 14:25:20 +0200 | lambdap237 | (~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer) |
| 2023-04-17 14:25:20 +0200 | litharge | +b lambdap237!*@*$##fix_your_connection |
| 2023-04-17 14:25:31 +0200 | litharge | -o litharge |
| 2023-04-17 14:25:34 +0200 | <jackdk> | litharge: thank you |
| 2023-04-17 14:30:51 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 14:32:08 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 14:32:34 +0200 | kenran | (~user@user/kenran) |
| 2023-04-17 14:36:39 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 246 seconds) |
| 2023-04-17 14:38:25 +0200 | acidjnk | (~acidjnk@p200300d6e715c49189eeee6d6a223043.dip0.t-ipconnect.de) |
| 2023-04-17 14:38:45 +0200 | Axman6 | (~Axman6@user/axman6) |
| 2023-04-17 14:39:11 +0200 | pavonia | (~user@user/siracusa) |
| 2023-04-17 14:40:43 +0200 | barak | (~barak@2a02:14f:83:1a53:7b83:8bb3:658f:78a9) |
| 2023-04-17 14:43:00 +0200 | dcleonarski | (~user@2804:d51:4793:c800:b0e2:a2e8:89a0:4c46) |
| 2023-04-17 14:47:57 +0200 | NiceBird | (~NiceBird@185.133.111.196) |
| 2023-04-17 14:49:13 +0200 | gurkenglas | (~gurkengla@dynamic-046-114-180-034.46.114.pool.telefonica.de) (Ping timeout: 276 seconds) |
| 2023-04-17 14:50:40 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) |
| 2023-04-17 14:55:45 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) (Quit: oac) |
| 2023-04-17 14:56:02 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) |
| 2023-04-17 14:56:53 +0200 | nitr0gen | (~nitr0gen@2405:201:a:a9d5:29f7:7ac1:3e43:bce) (Ping timeout: 246 seconds) |
| 2023-04-17 14:57:15 +0200 | use-value | (~Thunderbi@2a00:23c6:8a03:2f01:9de4:e162:b48:6951) (Ping timeout: 248 seconds) |
| 2023-04-17 14:57:37 +0200 | nitr0gen | (~nitr0gen@2409:4040:e82:1671:ae38:aa31:cf75:1903) |
| 2023-04-17 14:59:35 +0200 | ryantrinkle | (~ryantrink@140.174.248.64) (Ping timeout: 260 seconds) |
| 2023-04-17 15:03:37 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) (Ping timeout: 252 seconds) |
| 2023-04-17 15:14:01 +0200 | acidjnk | (~acidjnk@p200300d6e715c49189eeee6d6a223043.dip0.t-ipconnect.de) (Ping timeout: 265 seconds) |
| 2023-04-17 15:15:43 +0200 | jmdaemon | (~jmdaemon@user/jmdaemon) (Ping timeout: 252 seconds) |
| 2023-04-17 15:21:12 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) |
| 2023-04-17 15:22:33 +0200 | Vq | (~vq@90-227-192-206-no77.tbcn.telia.com) (Ping timeout: 250 seconds) |
| 2023-04-17 15:22:56 +0200 | ryantrinkle | (~ryantrink@140.174.248.64) |
| 2023-04-17 15:23:40 +0200 | edwtjo | (~edwtjo@h-155-4-52-185.A213.priv.bahnhof.se) |
| 2023-04-17 15:23:40 +0200 | edwtjo | (~edwtjo@h-155-4-52-185.A213.priv.bahnhof.se) (Changing host) |
| 2023-04-17 15:23:40 +0200 | edwtjo | (~edwtjo@fsf/member/edwtjo) |
| 2023-04-17 15:25:25 +0200 | euandreh | (~Thunderbi@189.6.18.7) |
| 2023-04-17 15:26:07 +0200 | barcisz | (~barcisz@79.191.65.29.ipv4.supernova.orange.pl) (Quit: Connection closed) |
| 2023-04-17 15:26:28 +0200 | barcisz | (~barcisz@79.191.65.29.ipv4.supernova.orange.pl) |
| 2023-04-17 15:31:27 +0200 | barcisz | (~barcisz@79.191.65.29.ipv4.supernova.orange.pl) (Quit: Connection closed) |
| 2023-04-17 15:33:13 +0200 | barcisz | (~barcisz@79.191.65.29.ipv4.supernova.orange.pl) |
| 2023-04-17 15:33:55 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:944e:aa4f:ecfd:acab) |
| 2023-04-17 15:34:14 +0200 | Vq | (~vq@90-230-208-28-no77.tbcn.telia.com) |
| 2023-04-17 15:35:38 +0200 | lisbeths | (uid135845@id-135845.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2023-04-17 15:35:41 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 15:37:18 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 15:38:09 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:944e:aa4f:ecfd:acab) (Ping timeout: 250 seconds) |
| 2023-04-17 15:41:34 +0200 | Square | (~Square4@user/square) (Ping timeout: 265 seconds) |
| 2023-04-17 15:41:54 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) (Quit: segfaultfizzbuzz) |
| 2023-04-17 15:53:42 +0200 | acidjnk | (~acidjnk@p200300d6e715c4910c85db67594b9b68.dip0.t-ipconnect.de) |
| 2023-04-17 15:59:55 +0200 | CiaoSen | (~Jura@ip-109-43-178-39.web.vodafone.de) |
| 2023-04-17 16:03:22 +0200 | gnalzo | (~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8) |
| 2023-04-17 16:03:27 +0200 | barak | (~barak@2a02:14f:83:1a53:7b83:8bb3:658f:78a9) (Ping timeout: 246 seconds) |
| 2023-04-17 16:11:52 +0200 | Me-me | (~Me-me@user/me-me) (Quit: Going offline, see ya! (www.adiirc.com)) |
| 2023-04-17 16:17:18 +0200 | nain | (~nain@169.150.218.79) (Ping timeout: 255 seconds) |
| 2023-04-17 16:19:58 +0200 | ajf___[m] | (~ajfmatrix@2001:470:69fc:105::2:5be3) |
| 2023-04-17 16:20:54 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) |
| 2023-04-17 16:23:38 +0200 | nain | (~nain@169.150.218.82) |
| 2023-04-17 16:25:58 +0200 | hochata | (~user@user/hochata) |
| 2023-04-17 16:32:06 +0200 | jero98772 | (~jero98772@2800:484:1d84:9000::1) |
| 2023-04-17 16:40:33 +0200 | nitr0gen | (~nitr0gen@2409:4040:e82:1671:ae38:aa31:cf75:1903) (Ping timeout: 250 seconds) |
| 2023-04-17 16:42:03 +0200 | motherfsck | (~motherfsc@user/motherfsck) (Ping timeout: 255 seconds) |
| 2023-04-17 16:45:26 +0200 | shriekingnoise | (~shrieking@186.137.175.87) |
| 2023-04-17 16:46:05 +0200 | nain | (~nain@169.150.218.82) (Ping timeout: 240 seconds) |
| 2023-04-17 16:47:25 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) |
| 2023-04-17 16:48:05 +0200 | <segfaultfizzbuzz> | so CPUs have speculative execution for serial calculations. is there such a thing as speculative parallelization? |
| 2023-04-17 16:48:26 +0200 | <dminuoso> | Yes. |
| 2023-04-17 16:48:41 +0200 | <dminuoso> | And that possibility is one of the reasons why Haskell is called non-strict, and not lazy. |
| 2023-04-17 16:48:48 +0200 | <segfaultfizzbuzz> | oh interesting |
| 2023-04-17 16:49:03 +0200 | <dminuoso> | And GHC even has *some* very rudimentary specualtive parallelization logic |
| 2023-04-17 16:49:04 +0200 | <segfaultfizzbuzz> | can you elaborate? |
| 2023-04-17 16:49:07 +0200 | <segfaultfizzbuzz> | oh fascinating |
| 2023-04-17 16:49:10 +0200 | <dminuoso> | Well |
| 2023-04-17 16:49:25 +0200 | <dminuoso> | Say you have `if a then b else c` |
| 2023-04-17 16:49:53 +0200 | <mauke> | the sparks stuff? |
| 2023-04-17 16:50:02 +0200 | <dminuoso> | Nothing stops GHC from speculatively forcing b and c before a even, as long as a potential bottom doesnt break the semantics. |
| 2023-04-17 16:50:21 +0200 | elain4 | (~textual@static-71-251-226-194.rcmdva.fios.verizon.net) |
| 2023-04-17 16:50:24 +0200 | <dminuoso> | So whatever paralellism you have, it cant have bottoms propagate like they do in visible semantics |
| 2023-04-17 16:51:20 +0200 | <dminuoso> | Because say `a` evaluates to True, and `c` diverses, the expression cant diverse. |
| 2023-04-17 16:51:54 +0200 | <dminuoso> | s/diverse/diverge/ |
| 2023-04-17 16:52:27 +0200 | <segfaultfizzbuzz> | when you say "force b and c", should i equate that to "see whether b evaluates to a bottom, and whether c evaluates to a bottom"? |
| 2023-04-17 16:52:50 +0200 | <dminuoso> | okay say you have `f x = ... where x = if a then b else c` |
| 2023-04-17 16:52:58 +0200 | <mauke> | force = evaluate |
| 2023-04-17 16:52:58 +0200 | <segfaultfizzbuzz> | yes |
| 2023-04-17 16:53:05 +0200 | <dminuoso> | You could, in principle, force (that is bring into WHNF) b and c when f is entered in parallel |
| 2023-04-17 16:53:22 +0200 | <dminuoso> | sorry `f arg = ... x ... where x = if a then b else c` |
| 2023-04-17 16:54:03 +0200 | <mauke> | "evaluates to a bottom" isn't quite straightforward because bottom includes infinite loops |
| 2023-04-17 16:54:06 +0200 | jargon | (~jargon@174-22-213-236.phnx.qwest.net) |
| 2023-04-17 16:54:07 +0200 | <dminuoso> | But imagine `a` evaluates to `True`, and `c` diverges, that parallel/early evaluation of `c` cant blow up the evaluation of `f arg` |
| 2023-04-17 16:54:14 +0200 | <segfaultfizzbuzz> | i think i understand -- run b and c at the same time as or before a, and in parallel |
| 2023-04-17 16:54:44 +0200 | <dminuoso> | segfaultfizzbuzz: right! and a bottom of a branch not taken cant propagate |
| 2023-04-17 16:54:59 +0200 | <dminuoso> | so the runtime would have to have some provision for that to allow |
| 2023-04-17 16:55:13 +0200 | Sgeo | (~Sgeo@user/sgeo) |
| 2023-04-17 16:55:19 +0200 | <dminuoso> | segfaultfizzbuzz: its by the way why we have `pseq` |
| 2023-04-17 16:55:35 +0200 | <dminuoso> | because `seq a b` doesnt mandate that `a` is evaluated *before* b. |
| 2023-04-17 16:55:40 +0200 | <dminuoso> | Merely that it *is* evaluated when b is forced. |
| 2023-04-17 16:55:47 +0200 | <dminuoso> | pseq gives that guarantee |
| 2023-04-17 16:56:10 +0200 | <segfaultfizzbuzz> | i think i can translate that to "evaluating c can't totally starve the evaluation of a" |
| 2023-04-17 16:56:22 +0200 | <dminuoso> | well even worse, `seq a b` could be rearranged into `seq b (seq a b)` |
| 2023-04-17 16:56:24 +0200 | <mauke> | technically, 'seq a b' doesn't mandate that 'a' is evaluated at all when 'b' is forced |
| 2023-04-17 16:56:47 +0200 | motherfsck | (~motherfsc@user/motherfsck) |
| 2023-04-17 16:57:04 +0200 | <segfaultfizzbuzz> | haskell could figure out that both b and c evaluate to 42 and skip evaluating a? |
| 2023-04-17 16:57:05 +0200 | merijn | (~merijn@195.114.232.94) (Ping timeout: 240 seconds) |
| 2023-04-17 16:57:10 +0200 | ddellacosta | (~ddellacos@143.244.47.70) (Quit: WeeChat 3.8) |
| 2023-04-17 16:57:22 +0200 | <dminuoso> | segfaultfizzbuzz: if ghc can do that, sure. thats just called constant folding. |
| 2023-04-17 16:57:37 +0200 | <mauke> | nah, that's illegal (for 'if a then b else c') |
| 2023-04-17 16:57:44 +0200 | <segfaultfizzbuzz> | ok so on a related topic: |
| 2023-04-17 16:57:50 +0200 | <segfaultfizzbuzz> | or, i think this is related i should say: |
| 2023-04-17 16:57:53 +0200 | <dminuoso> | mauke: why is that illegal? |
| 2023-04-17 16:58:05 +0200 | <dminuoso> | it's just a join point. |
| 2023-04-17 16:58:20 +0200 | ddellacosta | (~ddellacos@143.244.47.70) |
| 2023-04-17 16:58:25 +0200 | <segfaultfizzbuzz> | i have been introduced to a variety of good coding practices via rust and now feel dependent on having a compiler enforce these practices |
| 2023-04-17 16:58:28 +0200 | <mauke> | my gut feeling says that 'if a then b else c' must force 'a' |
| 2023-04-17 16:58:29 +0200 | <dminuoso> | oh you mean because a is not forced? |
| 2023-04-17 16:58:32 +0200 | <dminuoso> | mmm |
| 2023-04-17 16:58:35 +0200 | <segfaultfizzbuzz> | one of the most important ones is the phenomenon of the Result type |
| 2023-04-17 16:58:52 +0200 | <dminuoso> | mauke: im almost entirely sure it doesnt. |
| 2023-04-17 16:59:05 +0200 | <dminuoso> | but only almost :p |
| 2023-04-17 16:59:06 +0200 | <segfaultfizzbuzz> | now, you can panic in rust, so unfortunately it is not the case that every single error condition is handled explicitly by the Result type |
| 2023-04-17 16:59:11 +0200 | <dminuoso> | lets check the haskell report |
| 2023-04-17 16:59:15 +0200 | <segfaultfizzbuzz> | but in practice i can't say that i have ever encountered a panic |
| 2023-04-17 16:59:26 +0200 | <segfaultfizzbuzz> | haskell on the other hand has exceptions and asynchronous exceptions |
| 2023-04-17 16:59:34 +0200 | <dminuoso> | ` A case expression is evaluated by pattern matching the expression e against the individual alternatives. The alternatives are tried sequentially, from top to bottom.` |
| 2023-04-17 16:59:34 +0200 | <segfaultfizzbuzz> | these make me nervous |
| 2023-04-17 16:59:37 +0200 | <dminuoso> | Mmm |
| 2023-04-17 16:59:44 +0200 | <segfaultfizzbuzz> | my question regarding haskell is: |
| 2023-04-17 16:59:47 +0200 | <dminuoso> | mauke: I guess you're right |
| 2023-04-17 16:59:53 +0200 | <dminuoso> | mauke: that formulation leaves no wiggle room. |
| 2023-04-17 17:00:23 +0200 | <segfaultfizzbuzz> | is the phenomenon of the exception in haskell some kind of logically inevitable design choice |
| 2023-04-17 17:00:48 +0200 | <segfaultfizzbuzz> | or does the Result paradigm in rust make this more of a dated thing |
| 2023-04-17 17:00:50 +0200 | <mauke> | I think the best you can do is rewrite to 'seq a 42' if you discover that b and c always reduce to 42 |
| 2023-04-17 17:00:58 +0200 | <mauke> | where "you" = the compiler |
| 2023-04-17 17:01:42 +0200 | sadmax | (~user@64.130.91.66) |
| 2023-04-17 17:01:51 +0200 | <segfaultfizzbuzz> | that is to say, would the world haskell language prefer to reduce or eliminate exceptions and replace them with Result types, if we could snap our fingers |
| 2023-04-17 17:02:05 +0200 | <mauke> | segfaultfizzbuzz: now we're getting into "total function" territory |
| 2023-04-17 17:02:18 +0200 | <segfaultfizzbuzz> | i don't think Result requires totality,... |
| 2023-04-17 17:03:20 +0200 | <dolio> | Result is the same thing as Either, isn't it? |
| 2023-04-17 17:03:24 +0200 | <mauke> | yeah |
| 2023-04-17 17:03:36 +0200 | <segfaultfizzbuzz> | my comment is not about having the option to use a Result type |
| 2023-04-17 17:04:01 +0200 | <mauke> | (or using the option type as a result) |
| 2023-04-17 17:04:02 +0200 | <segfaultfizzbuzz> | my comment is, the haskell ecosystem has exceptions everywhere (i think??) and exceptions are a preferred method of error handling |
| 2023-04-17 17:04:18 +0200 | <segfaultfizzbuzz> | (in contrast to rust, where panic is for something really awful) |
| 2023-04-17 17:04:21 +0200 | <mauke> | (asynchronous) exceptions are absolutely not preferred for error handling |
| 2023-04-17 17:04:26 +0200 | <segfaultfizzbuzz> | oh? |
| 2023-04-17 17:04:40 +0200 | <segfaultfizzbuzz> | so "exception" in haskell is like "panic" in rust? |
| 2023-04-17 17:04:48 +0200 | <mauke> | in pure code? I'd say yes |
| 2023-04-17 17:04:49 +0200 | <segfaultfizzbuzz> | because exception in python is for anything |
| 2023-04-17 17:05:25 +0200 | <mauke> | you have to distinguish between errors in pure code and exception effects in monads (or something like that) |
| 2023-04-17 17:05:28 +0200 | <mauke> | :t catch |
| 2023-04-17 17:05:29 +0200 | <lambdabot> | Exception e => IO a -> (e -> IO a) -> IO a |
| 2023-04-17 17:05:46 +0200 | <mauke> | ^ that looks well behaved to me |
| 2023-04-17 17:06:03 +0200 | lortabac | (~lortabac@2a01:e0a:541:b8f0:7db4:b835:940f:b2a6) (Quit: WeeChat 2.8) |
| 2023-04-17 17:06:44 +0200 | <mauke> | :t throwIO |
| 2023-04-17 17:06:45 +0200 | <lambdabot> | Exception e => e -> IO a |
| 2023-04-17 17:06:48 +0200 | <mauke> | :t throw |
| 2023-04-17 17:06:49 +0200 | <lambdabot> | Exception e => e -> a |
| 2023-04-17 17:06:54 +0200 | <mauke> | ^ that's the weird one |
| 2023-04-17 17:07:23 +0200 | <mauke> | I woulcnd't try to catch those errors except as a last resort |
| 2023-04-17 17:10:17 +0200 | Guest17 | (~Guest17@2401:4900:126d:1ed:1569:dad9:4996:db21) |
| 2023-04-17 17:11:22 +0200 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.8) |
| 2023-04-17 17:11:45 +0200 | dolio | (~dolio@130.44.134.54) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2023-04-17 17:11:46 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) (Remote host closed the connection) |
| 2023-04-17 17:13:10 +0200 | dolio | (~dolio@130.44.134.54) |
| 2023-04-17 17:14:20 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) |
| 2023-04-17 17:14:45 +0200 | vglfr | (~vglfr@37.73.131.184) (Ping timeout: 240 seconds) |
| 2023-04-17 17:15:30 +0200 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 260 seconds) |
| 2023-04-17 17:16:02 +0200 | dolio | (~dolio@130.44.134.54) (Client Quit) |
| 2023-04-17 17:17:00 +0200 | dolio | (~dolio@130.44.134.54) |
| 2023-04-17 17:18:21 +0200 | phma | (phma@2001:5b0:210d:6758:ea1f:1d6e:9ba6:7e12) (Read error: Connection reset by peer) |
| 2023-04-17 17:18:59 +0200 | phma | (~phma@host-67-44-208-106.hnremote.net) |
| 2023-04-17 17:22:47 +0200 | eggplantade | (~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) |
| 2023-04-17 17:24:45 +0200 | Inst | (~Inst@2601:6c4:4081:54f0:bc9e:a2ec:406a:de9f) (Ping timeout: 250 seconds) |
| 2023-04-17 17:25:15 +0200 | CiaoSen | (~Jura@ip-109-43-178-39.web.vodafone.de) (Ping timeout: 255 seconds) |
| 2023-04-17 17:29:52 +0200 | [itchyjunk] | (~itchyjunk@user/itchyjunk/x-7353470) |
| 2023-04-17 17:36:47 +0200 | nain | (~nain@169.150.218.82) |
| 2023-04-17 17:37:40 +0200 | bitmapper | (uid464869@id-464869.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2023-04-17 17:44:43 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) (Ping timeout: 276 seconds) |
| 2023-04-17 17:47:17 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Ping timeout: 250 seconds) |
| 2023-04-17 17:49:11 +0200 | nate1 | (~nate@98.45.169.16) |
| 2023-04-17 17:49:20 +0200 | motherfsck | (~motherfsc@user/motherfsck) (Ping timeout: 248 seconds) |
| 2023-04-17 17:49:58 +0200 | <carbolymer> | I keep forgetting how this version bound works... x ^>= 0.1.1 means: 0.1.1 =< x =< 0.1.2 right? |
| 2023-04-17 17:50:29 +0200 | <monochrom> | < 0.2 |
| 2023-04-17 17:50:35 +0200 | <carbolymer> | oh right |
| 2023-04-17 17:50:36 +0200 | <carbolymer> | thanks |
| 2023-04-17 17:53:58 +0200 | <yushyin> | carbolymer: https://cabal.readthedocs.io/en/stable/cabal-package.html#pkg-field-build-depends if you scroll down a bit you'll find an explanation |
| 2023-04-17 17:54:28 +0200 | nate1 | (~nate@98.45.169.16) (Ping timeout: 276 seconds) |
| 2023-04-17 17:54:31 +0200 | <carbolymer> | caret operator |
| 2023-04-17 17:54:39 +0200 | <carbolymer> | I wasn't able to find "^>=" in cabal docs |
| 2023-04-17 17:54:43 +0200 | <carbolymer> | yushyin: thanks! |
| 2023-04-17 17:55:20 +0200 | <yushyin> | :) |
| 2023-04-17 17:57:36 +0200 | tzh | (~tzh@c-24-21-73-154.hsd1.or.comcast.net) |
| 2023-04-17 17:57:50 +0200 | barcisz | (~barcisz@79.191.65.29.ipv4.supernova.orange.pl) (Quit: Connection closed) |
| 2023-04-17 17:58:18 +0200 | kenran | (~user@user/kenran) (Remote host closed the connection) |
| 2023-04-17 18:00:04 +0200 | agevelt[m] | (~ageveltmo@2001:470:69fc:105::3:16db) (Quit: You have been kicked for being idle) |
| 2023-04-17 18:00:45 +0200 | <mauke> | ah yes, haskell versions |
| 2023-04-17 18:01:12 +0200 | <mauke> | W.X.Y.Z where W is the major version, X is also the major version, Y is the minor version, and Z the revision |
| 2023-04-17 18:11:23 +0200 | econo | (uid147250@user/econo) |
| 2023-04-17 18:12:18 +0200 | <kaol> | What do you think of function composition going right to left? I've been using Haskell so long that it feels completely natural to me but some newcomers in our team seem to want to reverse that and I'd like to tell them something better besides stop being weird. |
| 2023-04-17 18:12:52 +0200 | <yushyin> | the PVP spec is a tad old, W often denotes the epoch or just doesn't change at all |
| 2023-04-17 18:13:34 +0200 | <Guest17> | I want to review my proposal by my mentor for my summer of haskell. where can I connect with him? |
| 2023-04-17 18:13:37 +0200 | sadmax | (~user@64.130.91.66) (Remote host closed the connection) |
| 2023-04-17 18:15:53 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-04-17 18:15:57 +0200 | <geekosaur> | kaol, you might look at Data.Function.&, which is used a lot in lens |
| 2023-04-17 18:16:13 +0200 | <ski> | kaol : if you can convinve them that function argument should come before function, in function application, go for it |
| 2023-04-17 18:16:29 +0200 | <geekosaur> | but haskell is inspired by math and function composition in math is right to left |
| 2023-04-17 18:16:39 +0200 | <kaol> | I know of & and I don't understand the uses for it. |
| 2023-04-17 18:17:06 +0200 | <ski> | kaol : otherwise, it's easier to refactor inbetween `(foo a b . bar . baz c) x' and `foo a b (bar (baz c x))', if the order isn't changed |
| 2023-04-17 18:17:14 +0200 | <geekosaur> | mostly just to make lens operations look more natural |
| 2023-04-17 18:18:05 +0200 | <ski> | (btw, any idea for *why* function tends to come before argument, in function application ?) |
| 2023-04-17 18:18:40 +0200 | ski | has some theories |
| 2023-04-17 18:18:45 +0200 | <kaol> | I'm thinking that the way you could use `fmap` in place of (.) is a part of why it clicks so well. |
| 2023-04-17 18:19:49 +0200 | <ski> | .. i rarely use `fmap' over `(rho ->)', tbh |
| 2023-04-17 18:20:16 +0200 | <kaol> | I could expand the same to apply to function application: it's natural the way it is because it's just `id` in disguise. |
| 2023-04-17 18:20:33 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) |
| 2023-04-17 18:20:38 +0200 | <ski> | elaborate ? |
| 2023-04-17 18:20:58 +0200 | <kaol> | > (+1) `id` 2 |
| 2023-04-17 18:20:59 +0200 | <lambdabot> | 3 |
| 2023-04-17 18:21:15 +0200 | <ncf> | that just moves the question to the order of arguments to id |
| 2023-04-17 18:21:18 +0200 | <ski> | why wouldn't that work as well, with a reversed order of function application ? |
| 2023-04-17 18:22:28 +0200 | <kaol> | There's no "order of arguments", you all know that id takes only one argument. |
| 2023-04-17 18:22:37 +0200 | <ncf> | i wonder if this order is an artifact of SVO word order |
| 2023-04-17 18:23:03 +0200 | <ncf> | it takes two arguments if you specialise it at a function type |
| 2023-04-17 18:23:30 +0200 | <kaol> | All functions in Haskell take only one argument. Some of them just return more functions. |
| 2023-04-17 18:24:00 +0200 | ski | figures ncf is after the two operands for an infix operator |
| 2023-04-17 18:26:09 +0200 | <ncf> | well, if you accept that a `f` b means f a b if functions come first, or a b f if functions come last, then you've reduced "where's the function in "a `id` b" to "where's the function in "a b" |
| 2023-04-17 18:26:15 +0200 | <kaol> | My intuition says that there's some connection with the order of how (.) and ($) go and how they can be replaced by the more generic `fmap` and `id` and that gives a bias to the functions that makes them more natural the way they are. |
| 2023-04-17 18:26:27 +0200 | Guest17 | (~Guest17@2401:4900:126d:1ed:1569:dad9:4996:db21) (Quit: Client closed) |
| 2023-04-17 18:27:55 +0200 | <ski> | i agree with the former part. not so sure about the latter part |
| 2023-04-17 18:28:37 +0200 | <ski> | ncf : yes, exactly |
| 2023-04-17 18:28:52 +0200 | trev | (~trev@user/trev) (Quit: trev) |
| 2023-04-17 18:31:00 +0200 | trev | (~trev@user/trev) |
| 2023-04-17 18:32:25 +0200 | nain | (~nain@169.150.218.82) (Ping timeout: 240 seconds) |
| 2023-04-17 18:34:46 +0200 | barcisz | (~barcisz@79.191.65.29.ipv4.supernova.orange.pl) |
| 2023-04-17 18:35:34 +0200 | kuribas | (~user@ip-188-118-57-242.reverse.destiny.be) (Ping timeout: 265 seconds) |
| 2023-04-17 18:35:42 +0200 | <ddellacosta> | I will use <&> and & sometimes when the flow feels like it makes more sense that way, but I have also found that it's rare that feels natural |
| 2023-04-17 18:36:01 +0200 | ski | not too seldom uses `=<<' |
| 2023-04-17 18:36:55 +0200 | <ddellacosta> | oh yeah that works a lot inside of subterms in do notation I feel like |
| 2023-04-17 18:37:02 +0200 | jpds1 | (~jpds@gateway/tor-sasl/jpds) (Remote host closed the connection) |
| 2023-04-17 18:37:26 +0200 | jpds1 | (~jpds@gateway/tor-sasl/jpds) |
| 2023-04-17 18:37:33 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) (Ping timeout: 250 seconds) |
| 2023-04-17 18:38:45 +0200 | berberman_ | (~berberman@user/berberman) (Ping timeout: 256 seconds) |
| 2023-04-17 18:40:52 +0200 | um | (68ou5yyswu@jail.mp2.macomnet.net) |
| 2023-04-17 18:41:12 +0200 | um | (68ou5yyswu@jail.mp2.macomnet.net) () |
| 2023-04-17 18:41:31 +0200 | machinedgod | (~machinedg@d198-53-218-113.abhsia.telus.net) (Ping timeout: 240 seconds) |
| 2023-04-17 18:43:41 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 18:43:48 +0200 | barcisz | (~barcisz@79.191.65.29.ipv4.supernova.orange.pl) (Quit: Connection closed) |
| 2023-04-17 18:44:25 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) (Ping timeout: 240 seconds) |
| 2023-04-17 18:44:47 +0200 | <ski> | x <- (foo . bar <=< baz . quux) =<< frob |
| 2023-04-17 18:45:23 +0200 | Guest8 | (~Guest8@27-139-169-39.rev.home.ne.jp) |
| 2023-04-17 18:45:37 +0200 | Guest8 | (~Guest8@27-139-169-39.rev.home.ne.jp) (Client Quit) |
| 2023-04-17 18:46:08 +0200 | flowert | (~flowert@27-139-169-39.rev.home.ne.jp) |
| 2023-04-17 18:46:21 +0200 | flowert | (~flowert@27-139-169-39.rev.home.ne.jp) (Client Quit) |
| 2023-04-17 18:46:44 +0200 | vglfr | (~vglfr@88.155.3.42) |
| 2023-04-17 18:52:54 +0200 | u0_a202 | (~u0_a202@47.60.32.137) |
| 2023-04-17 18:54:11 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Ping timeout: 246 seconds) |
| 2023-04-17 18:57:19 +0200 | u0_a202 | (~u0_a202@47.60.32.137) (Client Quit) |
| 2023-04-17 19:01:10 +0200 | <monochrom> | Just another endian war. :) |
| 2023-04-17 19:08:38 +0200 | eggplantade | (~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection) |
| 2023-04-17 19:11:12 +0200 | mei | (~mei@user/mei) (Quit: mei) |
| 2023-04-17 19:12:41 +0200 | eggplantade | (~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) |
| 2023-04-17 19:13:56 +0200 | dolio | (~dolio@130.44.134.54) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2023-04-17 19:14:08 +0200 | jero98772 | (~jero98772@2800:484:1d84:9000::1) (Ping timeout: 248 seconds) |
| 2023-04-17 19:15:20 +0200 | dolio | (~dolio@130.44.134.54) |
| 2023-04-17 19:21:09 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) |
| 2023-04-17 19:25:54 +0200 | joseemds | (~josee@187.19.227.233) |
| 2023-04-17 19:26:53 +0200 | mbuf | (~Shakthi@49.207.178.186) (Quit: Leaving) |
| 2023-04-17 19:27:32 +0200 | jero98772 | (~jero98772@2800:484:1d84:9000::4) |
| 2023-04-17 19:28:18 +0200 | joseemds | (~josee@187.19.227.233) (Client Quit) |
| 2023-04-17 19:29:43 +0200 | harveypwca | (~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) |
| 2023-04-17 19:30:30 +0200 | eggplantade | (~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection) |
| 2023-04-17 19:30:42 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) |
| 2023-04-17 19:32:50 +0200 | Unicorn_Princess | (~Unicorn_P@user/Unicorn-Princess/x-3540542) |
| 2023-04-17 19:35:36 +0200 | <bwe> | how can I derive Pretty instance for a data record (Pretty class is defined in package prettyprinter)? |
| 2023-04-17 19:40:11 +0200 | <ncf> | bwe: looks like there's a default implementation for types with a Show instance, so `deriving (Show, Pretty)` should be enough? |
| 2023-04-17 19:42:23 +0200 | <ncf> | (might need DeriveAnyClass) |
| 2023-04-17 19:46:05 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) (Quit: oac) |
| 2023-04-17 19:46:20 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) |
| 2023-04-17 19:50:34 +0200 | segfaultfizzbuzz | (~segfaultf@108.211.201.53) (Quit: segfaultfizzbuzz) |
| 2023-04-17 20:01:28 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:944e:aa4f:ecfd:acab) |
| 2023-04-17 20:04:10 +0200 | berberman | (~berberman@user/berberman) |
| 2023-04-17 20:05:30 +0200 | mmynsted[m] | (~mmynstedm@2001:470:69fc:105::3:474b) |
| 2023-04-17 20:05:55 +0200 | kuribas | (~user@ptr-17d51ep0r5c3e7q42xz.18120a2.ip6.access.telenet.be) |
| 2023-04-17 20:08:46 +0200 | alexherbo2 | (~alexherbo@2a02-842a-8180-4601-2596-ec38-9e63-4653.rev.sfr.net) |
| 2023-04-17 20:12:41 +0200 | danrh | (~danrh@199.119.233.150) |
| 2023-04-17 20:15:17 +0200 | <bwe> | ncf: DeriveAnyClass solves it :) - thanks |
| 2023-04-17 20:27:56 +0200 | szkl | (uid110435@id-110435.uxbridge.irccloud.com) |
| 2023-04-17 20:30:03 +0200 | danrh | (~danrh@199.119.233.150) (Read error: Connection reset by peer) |
| 2023-04-17 20:32:49 +0200 | gnalzo | (~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) |
| 2023-04-17 20:45:45 +0200 | kaskal | (~kaskal@213-147-166-209.nat.highway.webapn.at) (Ping timeout: 240 seconds) |
| 2023-04-17 20:46:11 +0200 | jbalint_ | (~jbalint@2600:6c44:117f:e98a:816a:9488:fb1:7b7) (Ping timeout: 246 seconds) |
| 2023-04-17 20:47:04 +0200 | jbalint | (~jbalint@2600:6c44:117f:e98a:816a:9488:fb1:7b7) |
| 2023-04-17 20:51:38 +0200 | waleee | (~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) |
| 2023-04-17 20:52:15 +0200 | raym | (~ray@user/raym) (Quit: leaving) |
| 2023-04-17 20:53:13 +0200 | raym | (~ray@user/raym) |
| 2023-04-17 20:56:03 +0200 | enoq | (~enoq@2a05:1141:1f5:5600:b9c9:721a:599:bfe7) (Quit: enoq) |
| 2023-04-17 20:57:06 +0200 | hochata | (~user@user/hochata) (Remote host closed the connection) |
| 2023-04-17 21:01:43 +0200 | alexherbo2 | (~alexherbo@2a02-842a-8180-4601-2596-ec38-9e63-4653.rev.sfr.net) (Ping timeout: 260 seconds) |
| 2023-04-17 21:01:56 +0200 | alexherbo2 | (~alexherbo@2a02-8440-2140-b0a8-4dcf-c179-4324-b99f.rev.sfr.net) |
| 2023-04-17 21:03:05 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) (Ping timeout: 240 seconds) |
| 2023-04-17 21:07:36 +0200 | bitmapper | (uid464869@id-464869.lymington.irccloud.com) |
| 2023-04-17 21:15:19 +0200 | gurkenglas | (~gurkengla@dynamic-046-114-183-107.46.114.pool.telefonica.de) |
| 2023-04-17 21:16:06 +0200 | shriekingnoise | (~shrieking@186.137.175.87) (Ping timeout: 255 seconds) |
| 2023-04-17 21:16:07 +0200 | shriekingnoise_ | (~shrieking@186.137.175.87) |
| 2023-04-17 21:16:32 +0200 | kaskal | (~kaskal@2001:4bb8:2cc:efb3:2d42:311d:d744:4a5) |
| 2023-04-17 21:17:25 +0200 | Inst | (~Inst@2601:6c4:4081:54f0:71a6:8347:491d:ec1e) |
| 2023-04-17 21:18:12 +0200 | a_coll | (~acoll@45.92.120.189) |
| 2023-04-17 21:21:31 +0200 | dsrt^ | (~dsrt@c-76-105-96-13.hsd1.ga.comcast.net) |
| 2023-04-17 21:21:38 +0200 | trev | (~trev@user/trev) (Quit: trev) |
| 2023-04-17 21:23:14 +0200 | tr_ev | (~trev@user/trev) |
| 2023-04-17 21:23:32 +0200 | tr_ev | trev |
| 2023-04-17 21:25:07 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) |
| 2023-04-17 21:38:17 +0200 | harveypwca | (~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) (Quit: Leaving) |
| 2023-04-17 21:43:24 +0200 | kuribas | (~user@ptr-17d51ep0r5c3e7q42xz.18120a2.ip6.access.telenet.be) (Remote host closed the connection) |
| 2023-04-17 21:50:42 +0200 | nate1 | (~nate@98.45.169.16) |
| 2023-04-17 21:55:44 +0200 | nate1 | (~nate@98.45.169.16) (Ping timeout: 248 seconds) |
| 2023-04-17 21:55:56 +0200 | vulpine | (xfnw@tilde.team) (Quit: Connection reset by purr) |
| 2023-04-17 21:57:05 +0200 | jargon | (~jargon@174-22-213-236.phnx.qwest.net) (Ping timeout: 240 seconds) |
| 2023-04-17 21:58:36 +0200 | vulpine | (xfnw@tilde.team) |
| 2023-04-17 22:00:34 +0200 | johnw | (~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net) (Quit: ZNC - http://znc.in) |
| 2023-04-17 22:00:52 +0200 | johnw | (~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net) |
| 2023-04-17 22:02:22 +0200 | use-value | (~Thunderbi@2a00:23c6:8a03:2f01:4431:9012:1c52:a85d) |
| 2023-04-17 22:03:02 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 22:05:42 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:944e:aa4f:ecfd:acab) (Remote host closed the connection) |
| 2023-04-17 22:05:50 +0200 | _ht | (~Thunderbi@28-52-174-82.ftth.glasoperator.nl) (Quit: _ht) |
| 2023-04-17 22:06:25 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) (Quit: oac) |
| 2023-04-17 22:06:40 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) |
| 2023-04-17 22:06:59 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:944e:aa4f:ecfd:acab) |
| 2023-04-17 22:07:10 +0200 | use-value | (~Thunderbi@2a00:23c6:8a03:2f01:4431:9012:1c52:a85d) (Ping timeout: 260 seconds) |
| 2023-04-17 22:15:52 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:944e:aa4f:ecfd:acab) (Remote host closed the connection) |
| 2023-04-17 22:18:06 +0200 | grnman_ | (~michaelsc@c-66-176-3-51.hsd1.fl.comcast.net) (Quit: Lost terminal) |
| 2023-04-17 22:19:16 +0200 | barak | (~barak@77.125.91.113) |
| 2023-04-17 22:26:39 +0200 | opticblast | (~Thunderbi@172.58.87.218) |
| 2023-04-17 22:36:01 +0200 | vglfr | (~vglfr@88.155.3.42) (Ping timeout: 240 seconds) |
| 2023-04-17 22:38:40 +0200 | trev | (~trev@user/trev) (Quit: trev) |
| 2023-04-17 22:39:51 +0200 | gnalzo | (~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8) |
| 2023-04-17 22:40:59 +0200 | johnw | (~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net) (Quit: ZNC - http://znc.in) |
| 2023-04-17 22:41:19 +0200 | johnw | (~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net) |
| 2023-04-17 22:41:51 +0200 | JScript | (~JScript@45.248.77.204) |
| 2023-04-17 22:45:42 +0200 | zq | (~zq@xorshift.org) () |
| 2023-04-17 22:46:05 +0200 | Ranhir | (~Ranhir@157.97.53.139) (Remote host closed the connection) |
| 2023-04-17 22:46:16 +0200 | cheater_ | (~Username@user/cheater) |
| 2023-04-17 22:48:05 +0200 | cheater | (~Username@user/cheater) (Ping timeout: 240 seconds) |
| 2023-04-17 22:48:11 +0200 | cheater_ | cheater |
| 2023-04-17 22:57:22 +0200 | Ranhir | (~Ranhir@157.97.53.139) |
| 2023-04-17 23:02:02 +0200 | gentauro | (~gentauro@user/gentauro) (Read error: Connection reset by peer) |
| 2023-04-17 23:06:33 +0200 | heraldo | (~heraldo@user/heraldo) |
| 2023-04-17 23:06:45 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) (Quit: oac) |
| 2023-04-17 23:07:01 +0200 | oac | (~oac@50-93-248-155.fttp.usinternet.com) |
| 2023-04-17 23:07:42 +0200 | gentauro | (~gentauro@user/gentauro) |
| 2023-04-17 23:10:06 +0200 | shriekingnoise | (~shrieking@186.137.175.87) |
| 2023-04-17 23:10:24 +0200 | shriekingnoise_ | (~shrieking@186.137.175.87) (Ping timeout: 255 seconds) |
| 2023-04-17 23:10:51 +0200 | slack1256 | (~slack1256@181.42.52.231) |
| 2023-04-17 23:13:49 +0200 | <slack1256> | I am hitting this error when deriving Lift on a Unlifted data type: "Cannot derive well-kinded instance of form ‘Lift (Strict ...)’ Class ‘Lift’ expects an argument of kind ‘*’". Yet if we see the definition of class Lift is: "class Lift (t :: TYPE r) where", allowing Unlifted data types. They even have some definitions on there. |
| 2023-04-17 23:14:18 +0200 | <slack1256> | So what gives? Is DeriveLift only for Lifted Kinds? |
| 2023-04-17 23:16:18 +0200 | Tuplanolla | (~Tuplanoll@91-159-68-236.elisa-laajakaista.fi) |
| 2023-04-17 23:16:20 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:944e:aa4f:ecfd:acab) |
| 2023-04-17 23:17:13 +0200 | a_coll | (~acoll@45.92.120.189) (Remote host closed the connection) |
| 2023-04-17 23:20:07 +0200 | <ncf> | > Representation-polymorphic since template-haskell-2.16.0.0. |
| 2023-04-17 23:20:08 +0200 | <lambdabot> | <hint>:1:60: error: |
| 2023-04-17 23:20:08 +0200 | <lambdabot> | parse error (possibly incorrect indentation or mismatched brackets) |
| 2023-04-17 23:20:21 +0200 | <ncf> | are you using an older version? |
| 2023-04-17 23:21:08 +0200 | <slack1256> | I am using 2.18.0.0 |
| 2023-04-17 23:21:31 +0200 | <slack1256> | I am guessing that 'DeriveLift' is only for Lifted kinds, given the default signature. |
| 2023-04-17 23:21:49 +0200 | eggplantade | (~Eggplanta@2600:1700:38c5:d800:944e:aa4f:ecfd:acab) (Ping timeout: 250 seconds) |
| 2023-04-17 23:27:26 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.) |
| 2023-04-17 23:28:00 +0200 | jero98772 | (~jero98772@2800:484:1d84:9000::4) (Ping timeout: 248 seconds) |
| 2023-04-17 23:29:13 +0200 | sammelweis | (~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) |
| 2023-04-17 23:32:18 +0200 | takuan | (~takuan@178-116-218-225.access.telenet.be) (Remote host closed the connection) |
| 2023-04-17 23:35:47 +0200 | <Inst> | hmmm |
| 2023-04-17 23:36:00 +0200 | <Inst> | is there a market for a GUI wrapper around GHCup and Cabal? |
| 2023-04-17 23:37:25 +0200 | <slack1256> | Inst: There is a TUI wrapper for GHCup |
| 2023-04-17 23:37:53 +0200 | <Inst> | I know, but the TUI doesn't work on Windows (maerwald is working on getting a substitute because it's an issue with bricks / vty) |
| 2023-04-17 23:38:10 +0200 | <geekosaur> | guis are even less portable… |
| 2023-04-17 23:38:18 +0200 | <Inst> | monomer is multi-platform |
| 2023-04-17 23:38:39 +0200 | <slack1256> | Yeah, what is up with monomer? sounds like a dream |
| 2023-04-17 23:38:43 +0200 | <Inst> | what would people think if people used Sarcasm as a project manager for Haskell? |
| 2023-04-17 23:38:49 +0200 | <Inst> | monomer is understaffed |
| 2023-04-17 23:39:12 +0200 | jero98772 | (~jero98772@2800:484:1d84:9000::4) |
| 2023-04-17 23:39:20 +0200 | <Inst> | it works on Windows, seems to be nice in general, but issues with sdl2 installation on windows (you'll have to get into mingw to compile exactly the right binary) |
| 2023-04-17 23:39:47 +0200 | <slack1256> | Inst: When you mean windows, you mean windows without WSLv2 right? |
| 2023-04-17 23:39:53 +0200 | <Inst> | erm, compile exactly the right sdl2, because GHC won't install the most recent sdl2 |
| 2023-04-17 23:39:53 +0200 | <slack1256> | Does it work on WSLv2? |
| 2023-04-17 23:40:01 +0200 | <Inst> | I mean straight windows |
| 2023-04-17 23:40:07 +0200 | <slack1256> | Gotcha |
| 2023-04-17 23:40:33 +0200 | <Inst> | monomer is a great project, wish I were qualified to give it more support |
| 2023-04-17 23:40:56 +0200 | <Inst> | I disagree with elm architecture, but it's not like there's anything better |
| 2023-04-17 23:46:37 +0200 | <monochrom> | There is a demand market, but no supply market. :) |
| 2023-04-17 23:47:11 +0200 | <monochrom> | May I therefore tell you again the relevant Aesop fable. :) |
| 2023-04-17 23:48:12 +0200 | <Inst> | Thanks, I think I'll start by wrapping GHCup, because it's easier, then try Cabal, which'll be harder |
| 2023-04-17 23:48:25 +0200 | <monochrom> | The mice of the world held an international conference on cat evasion. They unanimously passed two resolution: 1. A bell is to be worn on the cat for early warning. 2. Someone else is to do it. |
| 2023-04-17 23:51:38 +0200 | michalz | (~michalz@185.246.207.221) (Remote host closed the connection) |
| 2023-04-17 23:57:03 +0200 | coot | (~coot@213.134.170.228) (Quit: coot) |
| 2023-04-17 23:59:26 +0200 | slack1256 | (~slack1256@181.42.52.231) (Remote host closed the connection) |