| 2024-04-18 00:03:22 +0200 | <monochrom> | My students are smarter than all of the above. They just click the close-window button. :) |
| 2024-04-18 00:07:33 +0200 | Square2 | (~Square4@user/square) |
| 2024-04-18 00:08:18 +0200 | <int-e> | monochrom: Why would anyone type out '"' 'e' '"' ' ' '"' 'x' '"' ' ' '"' 'i' '"' ' ' '"' 't' '"'? Do they hate themselves? |
| 2024-04-18 00:08:21 +0200 | target_i | (~target_i@user/target-i/x-6023099) (Quit: leaving) |
| 2024-04-18 00:08:28 +0200 | CATS | (apic@brezn3.muc.ccc.de) |
| 2024-04-18 00:08:33 +0200 | <monochrom> | haha |
| 2024-04-18 00:08:54 +0200 | <dolio> | monochrom probably wrote a Haskell program to generate the text. |
| 2024-04-18 00:09:19 +0200 | gooba | (~gooba@90-231-13-185-no3430.tbcn.telia.com) (Ping timeout: 256 seconds) |
| 2024-04-18 00:09:35 +0200 | wroathe | (~wroathe@user/wroathe) (Ping timeout: 264 seconds) |
| 2024-04-18 00:09:45 +0200 | malte | (~malte@mal.tc) (Ping timeout: 255 seconds) |
| 2024-04-18 00:10:13 +0200 | <ncf> | > fix (unwords . map show) |
| 2024-04-18 00:10:15 +0200 | <lambdabot> | "*Exception: <<loop>> |
| 2024-04-18 00:10:39 +0200 | Square | (~Square@user/square) (Ping timeout: 260 seconds) |
| 2024-04-18 00:11:05 +0200 | <int-e> | > text . unwords . map show . unwords . map (show . (:[])) $ "exit" |
| 2024-04-18 00:11:06 +0200 | <lambdabot> | '"' 'e' '"' ' ' '"' 'x' '"' ' ' '"' 'i' '"' ' ' '"' 't' '"' |
| 2024-04-18 00:11:33 +0200 | <ncf> | :t text |
| 2024-04-18 00:11:34 +0200 | <lambdabot> | String -> Doc |
| 2024-04-18 00:12:13 +0200 | <monochrom> | It means using the fact that the Show instance of Doc does not add quoting or escaping. |
| 2024-04-18 00:12:29 +0200 | malte | (~malte@mal.tc) |
| 2024-04-18 00:12:33 +0200 | <monochrom> | putStrLn : ghci :: text : lambdabot |
| 2024-04-18 00:12:53 +0200 | <int-e> | > var "silly fancy version" |
| 2024-04-18 00:12:54 +0200 | <lambdabot> | silly fancy version |
| 2024-04-18 00:13:16 +0200 | <monochrom> | Ugh now that's fancy and silly, yeah :) |
| 2024-04-18 00:13:36 +0200 | gmg | (~user@user/gehmehgeh) (Quit: Leaving) |
| 2024-04-18 00:15:05 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 00:15:23 +0200 | <ncf> | sometimes i wonder about like, "fixed points with initial value" |
| 2024-04-18 00:15:48 +0200 | <ncf> | it feels like i should be able to apply that function to "exit" repeatedly and take some sort of colimit to get an infinite string instead of a <<loop>> |
| 2024-04-18 00:16:05 +0200 | <monochrom> | Does that mean "iterate f x0" and hope that something stabilizes down the road? |
| 2024-04-18 00:16:15 +0200 | <ncf> | would have to somehow add the information that the input string is a substring of the output string |
| 2024-04-18 00:16:19 +0200 | <ncf> | as in subsequence |
| 2024-04-18 00:17:17 +0200 | <ncf> | i guess one way would be to say "the nth character of the fixed point only depends on the first m applications" |
| 2024-04-18 00:17:37 +0200 | <int-e> | > fix (('\'' :) . tail . unwords . map show) |
| 2024-04-18 00:17:38 +0200 | <lambdabot> | "'\\'' '\\\\' '\\'' '\\'' ' ' '\\'' '\\\\' '\\\\' '\\'' ' ' '\\'' '\\\\' '\\... |
| 2024-04-18 00:17:54 +0200 | <monochrom> | iterate show "exit" may get you started. |
| 2024-04-18 00:18:00 +0200 | gooba | (~gooba@90-231-13-185-no3430.tbcn.telia.com) |
| 2024-04-18 00:21:01 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 00:21:12 +0200 | Sgeo | (~Sgeo@user/sgeo) |
| 2024-04-18 00:21:20 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 00:24:33 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 00:24:55 +0200 | <ncf> | so like formally the space of strings on a given alphabet has the structure of a category for the "is subsequence of" relation, and if your quoting function is nice enough there is a ω-diagram that starts at "exit" and then repeatedly applies quoting; what kind of strings do we need to add for this diagram to have a sequential colimit? |
| 2024-04-18 00:24:58 +0200 | peterbecich | (~Thunderbi@47.229.123.186) |
| 2024-04-18 00:26:14 +0200 | <EvanR> | so you want to exit the program immediately, first let me introduce you to some category theory |
| 2024-04-18 00:27:03 +0200 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.) |
| 2024-04-18 00:27:04 +0200 | <ncf> | i guess the colimit would look like "^ωe"^ω"^ωx"^ω... |
| 2024-04-18 00:28:25 +0200 | acidjnk | (~acidjnk@p200300d6e714dc694defcfab5eaaea04.dip0.t-ipconnect.de) (Ping timeout: 272 seconds) |
| 2024-04-18 00:28:46 +0200 | redcedar0 | (~redcedar@97-113-208-43.tukw.qwest.net) |
| 2024-04-18 00:29:30 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 00:29:38 +0200 | <ncf> | https://en.wikipedia.org/wiki/Omega_language 👀 |
| 2024-04-18 00:30:12 +0200 | <ncf> | hm those are just functions from ℕ, so that wouldn't work |
| 2024-04-18 00:30:26 +0200 | <ncf> | i seem to recall there was a notion of infinite words based on trees or something |
| 2024-04-18 00:31:25 +0200 | <Inst> | hummm, i'm trying to reach the maintainer of hackage's TinyFileDialogs wrapper on Github |
| 2024-04-18 00:31:38 +0200 | <Inst> | if he doesn't respond, do I have justification to fork it and upload a derivative? |
| 2024-04-18 00:31:46 +0200 | <EvanR> | is it called omega language because as soon as you speak an infinite word it's the last word you'll ever say |
| 2024-04-18 00:31:49 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 00:31:50 +0200 | <Inst> | Not sure if anyone else uses the package, since tfd imo is pretty fundamental as a capability |
| 2024-04-18 00:32:15 +0200 | <ncf> | you could supertask your way out of it |
| 2024-04-18 00:32:24 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 00:32:35 +0200 | <Inst> | *attempt to say |
| 2024-04-18 00:34:14 +0200 | itscaleb | (~itscaleb@user/itscaleb) |
| 2024-04-18 00:40:07 +0200 | <ncf> | (ah, i was thinking of "generalised words" in "Isomorphism of regular trees and words") |
| 2024-04-18 00:40:15 +0200 | redcedar0 | rdcdr |
| 2024-04-18 00:40:33 +0200 | rdcdr | walker |
| 2024-04-18 00:40:56 +0200 | walker | rdcdr |
| 2024-04-18 00:41:22 +0200 | <ncf> | (and "An algorithm for the solution of fixed-point equations for infinite words") |
| 2024-04-18 00:41:32 +0200 | dunj3 | (~dunj3@kingdread.de) (Read error: Connection reset by peer) |
| 2024-04-18 00:43:54 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 00:43:56 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 00:44:19 +0200 | <geekosaur> | Inst, you always have approval to upload a derivative. you need approval to take over a package |
| 2024-04-18 00:45:09 +0200 | <Inst> | no, but courtesy |
| 2024-04-18 00:45:24 +0200 | <Inst> | i'm actually unsure when TFD developed security holes, it was something that came up like 2 years ago |
| 2024-04-18 00:45:37 +0200 | <Inst> | or even if it did |
| 2024-04-18 00:45:38 +0200 | <Inst> | :( |
| 2024-04-18 00:45:39 +0200 | peterbecich | (~Thunderbi@47.229.123.186) (Ping timeout: 260 seconds) |
| 2024-04-18 00:46:21 +0200 | zetef | (~quassel@5.2.182.98) (Remote host closed the connection) |
| 2024-04-18 00:48:03 +0200 | malte | (~malte@mal.tc) (Ping timeout: 272 seconds) |
| 2024-04-18 00:48:37 +0200 | malte | (~malte@mal.tc) |
| 2024-04-18 00:49:22 +0200 | rdcdr | (~redcedar@97-113-208-43.tukw.qwest.net) (Quit: The Lounge - https://thelounge.chat) |
| 2024-04-18 00:50:50 +0200 | <Inst> | thanks :) |
| 2024-04-18 00:56:51 +0200 | Batzy_ | Batzy |
| 2024-04-18 01:00:44 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 01:02:16 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 01:02:49 +0200 | tri | (~tri@ool-18bc2e74.dyn.optonline.net) |
| 2024-04-18 01:09:21 +0200 | ncf | . o O ( quoting is a well-pointed endofunctor ) |
| 2024-04-18 01:13:23 +0200 | sawilagar | (~sawilagar@user/sawilagar) (Ping timeout: 268 seconds) |
| 2024-04-18 01:23:39 +0200 | <masaeedu> | maralorn: it might be worth considering not keeping the log in memory at all (the term "log" suggests you're not reading it to decide what to do subsequently) |
| 2024-04-18 01:25:37 +0200 | <haskellbridge> | <maralorn> Well I want to display the log or parts of it. |
| 2024-04-18 01:26:44 +0200 | FinnElija | (~finn_elij@user/finn-elija/x-0085643) (Remote host closed the connection) |
| 2024-04-18 01:27:16 +0200 | FinnElija | (~finn_elij@user/finn-elija/x-0085643) |
| 2024-04-18 01:27:58 +0200 | mud | (~mud@user/kadoban) |
| 2024-04-18 01:29:49 +0200 | <masaeedu> | I see. I imagined you don't access the log within whatever computation is logging: instead something else reads the log after the computation is complete. |
| 2024-04-18 01:31:35 +0200 | mima | (~mmh@aftr-62-216-211-54.dynamic.mnet-online.de) (Ping timeout: 268 seconds) |
| 2024-04-18 01:51:10 +0200 | <monochrom> | ncf: What is the well-pointed part? Does it just mean I have both fmap and pure? |
| 2024-04-18 02:00:56 +0200 | <Inst> | data.text can't convert to CString directly? ;_; |
| 2024-04-18 02:01:14 +0200 | <Inst> | here we go, Data.Text.Foreign |
| 2024-04-18 02:02:05 +0200 | <geekosaur> | you're not supposed to make assumptions about the internal encoding, and you have to specify an encoding to use when going to CString |
| 2024-04-18 02:03:18 +0200 | noumenon | (~noumenon@113.51-175-156.customer.lyse.net) (Quit: Leaving) |
| 2024-04-18 02:04:29 +0200 | <monochrom> | Yeah what would "convert" mean? For example convert λ to what C string? |
| 2024-04-18 02:04:36 +0200 | <Inst> | ah i see |
| 2024-04-18 02:06:01 +0200 | <monochrom> | Non-programmers and generally non-tech-savvy people can be understood to think in terms of DWIM and generally lack technical imagination. |
| 2024-04-18 02:06:20 +0200 | <monochrom> | But programmers, of all people, are not supposed to afford to be that sloppy. |
| 2024-04-18 02:08:31 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 02:09:47 +0200 | tri | (~tri@ool-18bc2e74.dyn.optonline.net) (Remote host closed the connection) |
| 2024-04-18 02:10:44 +0200 | tri | (~tri@ool-18bc2e74.dyn.optonline.net) |
| 2024-04-18 02:10:47 +0200 | euleritian | (~euleritia@77.22.252.56) (Ping timeout: 264 seconds) |
| 2024-04-18 02:10:53 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 02:10:55 +0200 | euleritian | (~euleritia@dynamic-176-006-177-197.176.6.pool.telefonica.de) |
| 2024-04-18 02:11:54 +0200 | <Inst> | bytestring doesn't even come with a Foreign interface |
| 2024-04-18 02:12:27 +0200 | <monochrom> | Should it? |
| 2024-04-18 02:13:09 +0200 | <Inst> | "Represents sequences of bytes or 8 bit characters" |
| 2024-04-18 02:13:35 +0200 | <Inst> | C string type is just a null-terminated array and it's platform specific as to its encoding |
| 2024-04-18 02:13:35 +0200 | <monochrom> | packCString useAsCString etc covers most cases. |
| 2024-04-18 02:13:36 +0200 | <geekosaur> | ByteString is best thought of as raw binary |
| 2024-04-18 02:14:14 +0200 | <geekosaur> | any encoding is specified by whatever you're feeding it to/from, and may be specified by a protocol or out of band or etc. |
| 2024-04-18 02:14:15 +0200 | <monochrom> | There are unsafe ones in Data.ByteString.Unsafe if you want fast and you code correctly. |
| 2024-04-18 02:14:37 +0200 | <Inst> | it's just annoying because Foreign.C.String has a very pleasant interface, except that strings aren't supposed to be good for performance due to being a linked list of chars |
| 2024-04-18 02:15:53 +0200 | <monochrom> | I'm beginning to wonder if you are just complaining that the word "Foreign" does not appear in the function names. |
| 2024-04-18 02:17:08 +0200 | <masaeedu> | It's a bit elitist to assume non-programmers lack technical imagination... |
| 2024-04-18 02:17:38 +0200 | <monochrom> | I did not mean assume. I meant understandable if some of them don't. |
| 2024-04-18 02:18:07 +0200 | <masaeedu> | Oh, I see |
| 2024-04-18 02:18:07 +0200 | <Inst> | no, in this case, i simply wasn't familiar with C encoding of strings |
| 2024-04-18 02:18:34 +0200 | <geekosaur> | neither is C 😛 |
| 2024-04-18 02:19:02 +0200 | <Inst> | C doesn't even have a true array type, just a pointer, an increment based on type, and some sugar |
| 2024-04-18 02:19:21 +0200 | <monochrom> | That's actually wrong. |
| 2024-04-18 02:20:15 +0200 | <monochrom> | inb4 "in this case, I simply wasn't familiar with the C standard" |
| 2024-04-18 02:20:31 +0200 | <geekosaur> | is anyone really? |
| 2024-04-18 02:21:01 +0200 | <monochrom> | Well, sure, no, but I happened to read that section about how "int foo[4]" and "int foo[5]" are different types. |
| 2024-04-18 02:22:16 +0200 | <Inst> | i like monochrom being appropriately harsh |
| 2024-04-18 02:22:17 +0200 | <monochrom> | If you accept laziness, I can legitimately claim that I am familiar with it, because I will read the relevant sections on demand! >:) |
| 2024-04-18 02:22:49 +0200 | <geekosaur> | …which leaves "comprehens"… |
| 2024-04-18 02:22:53 +0200 | <geekosaur> | -s+d |
| 2024-04-18 02:23:15 +0200 | <monochrom> | https://ro-che.info/ccc/11 |
| 2024-04-18 02:24:44 +0200 | philopsos | (~caecilius@user/philopsos) (Ping timeout: 252 seconds) |
| 2024-04-18 02:24:57 +0200 | oo_miguel | (~Thunderbi@78-11-181-16.static.ip.netia.com.pl) (Ping timeout: 272 seconds) |
| 2024-04-18 02:25:30 +0200 | peterbecich | (~Thunderbi@47.229.123.186) |
| 2024-04-18 02:33:25 +0200 | <Inst> | what's wrong with reading the C standards? |
| 2024-04-18 02:35:00 +0200 | <geekosaur> | not comprehensible by mortals |
| 2024-04-18 02:36:18 +0200 | <Inst> | i'm skimming through it now, it's only 757 pages, which, while long, is still manageable |
| 2024-04-18 02:36:40 +0200 | <geekosaur> | also, Apr 16 20:54:53 <c_wraith> "Developers who manage to figure out what the standard actually means are frequently appalled." truer words never spoken of C |
| 2024-04-18 02:39:01 +0200 | <Inst> | tho core is only 186 pages |
| 2024-04-18 02:39:04 +0200 | <Inst> | rest is library documentation |
| 2024-04-18 02:39:28 +0200 | <monochrom> | Yeah I was appalled that it does not let me examine the 4 bytes of a 32-bit int by union { int i; char b[4]; } |
| 2024-04-18 02:39:41 +0200 | madeleine-sydney | (~madeleine@c-76-155-235-153.hsd1.co.comcast.net) |
| 2024-04-18 02:39:44 +0200 | euleritian | (~euleritia@dynamic-176-006-177-197.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
| 2024-04-18 02:40:12 +0200 | <geekosaur> | that one doesn't surprise me; it's a hack that happens to work on many common architectures |
| 2024-04-18 02:40:24 +0200 | <geekosaur> | and always was |
| 2024-04-18 02:41:08 +0200 | <monochrom> | There was one year when I taught that hack to students. Subsequently I saw you guys here mentioning that it is not kosher, so I retracted it. |
| 2024-04-18 02:42:52 +0200 | <monochrom> | Subsequently I only taught fwrite to a file and then just examining the bytes in the file. >:) |
| 2024-04-18 02:43:27 +0200 | <Inst> | by the way, why are people using c2hs instead of just capi? |
| 2024-04-18 02:44:07 +0200 | <monochrom> | I think they are orthogonal? You could use both? They solve two unrelated problems? |
| 2024-04-18 02:44:08 +0200 | <geekosaur> | because with capi you still have to write the bindings; c2hs does that for you, when it works |
| 2024-04-18 02:45:07 +0200 | <yushyin> | "when it works" I really feel that |
| 2024-04-18 02:45:31 +0200 | <geekosaur> | capi deals with making function calls via C instead of directly via asm. c2hs writes bindings for you; those might be via capi or via asm |
| 2024-04-18 02:46:20 +0200 | <Inst> | in terms of space and time, which is better? |
| 2024-04-18 02:47:48 +0200 | <geekosaur> | asm is faster when it works but most functions expect to be called via C, and as such often make use of preprocessor macros and the like which asm won't know about |
| 2024-04-18 02:48:09 +0200 | <jackdk> | There are important correctness benefits to using CApiFFI, particularly around things like variadic functions and exotic calling conventions, see https://www.haskell.org/ghc/blog/20210709-capi-usage.html |
| 2024-04-18 02:49:03 +0200 | xff0x | (~xff0x@2405:6580:b080:900:7a5b:fae6:85e7:e330) (Ping timeout: 255 seconds) |
| 2024-04-18 02:49:11 +0200 | <geekosaur> | capi pretty much only exists because moving to generating asm directly instead of compiling via C broke the original ffi spec in important ways |
| 2024-04-18 02:49:46 +0200 | <geekosaur> | so capi brings back how it used to work (and arguably how the spec expects it to work, although it's not documented as such) |
| 2024-04-18 02:51:48 +0200 | dcoutts | (~duncan@cpc69400-oxfd27-2-0-cust750.4-3.cable.virginm.net) (Remote host closed the connection) |
| 2024-04-18 02:52:10 +0200 | dcoutts | (~duncan@cpc69400-oxfd27-2-0-cust750.4-3.cable.virginm.net) |
| 2024-04-18 02:53:54 +0200 | peterbecich | (~Thunderbi@47.229.123.186) (Ping timeout: 252 seconds) |
| 2024-04-18 02:55:55 +0200 | mud | (~mud@user/kadoban) (Quit: quit) |
| 2024-04-18 02:57:43 +0200 | dcoutts | (~duncan@cpc69400-oxfd27-2-0-cust750.4-3.cable.virginm.net) (Ping timeout: 260 seconds) |
| 2024-04-18 02:58:37 +0200 | euleritian | (~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) |
| 2024-04-18 03:08:41 +0200 | wroathe | (~wroathe@23.162.40.122) |
| 2024-04-18 03:08:42 +0200 | wroathe | (~wroathe@23.162.40.122) (Changing host) |
| 2024-04-18 03:08:42 +0200 | wroathe | (~wroathe@user/wroathe) |
| 2024-04-18 03:15:29 +0200 | ridcully | (~ridcully@p508accab.dip0.t-ipconnect.de) (Ping timeout: 268 seconds) |
| 2024-04-18 03:16:02 +0200 | <Inst> | with regards to bytestring, it seems that the unsafe functions will create data that's not garbage collected? So how should bytestring-generated data be GCed? |
| 2024-04-18 03:16:35 +0200 | ridcully | (~ridcully@p508acfbb.dip0.t-ipconnect.de) |
| 2024-04-18 03:17:10 +0200 | <Inst> | and actually in the standard bytestring interface, there are provisions for converting bytestring to cstring and vice versa |
| 2024-04-18 03:19:36 +0200 | mei | (~mei@user/mei) (Remote host closed the connection) |
| 2024-04-18 03:22:02 +0200 | <geekosaur> | if you mean unsafePackCString, the point is that there is no way to automatically know how to dispose of it, and indeed it may be a pointer to a C `static` buffer which can't be freed at all |
| 2024-04-18 03:22:37 +0200 | <geekosaur> | if you know that it came from C malloc, use unsafePackMallocCString |
| 2024-04-18 03:23:59 +0200 | beka | (~beka@2607:f598:bd4a:6e0:c0ad:38f8:7650:7d75) (Remote host closed the connection) |
| 2024-04-18 03:24:12 +0200 | <Inst> | thanks for your patience |
| 2024-04-18 03:24:16 +0200 | <geekosaur> | you would normally use unsafePackCString when receiving a C string as part of some data from a C library, where its lifetime is controlled by calling some deinitialization function |
| 2024-04-18 03:24:47 +0200 | mei | (~mei@user/mei) |
| 2024-04-18 03:24:51 +0200 | <geekosaur> | (and you probably don't want to assign that function as a finalizer because it would tear down more than just that string) |
| 2024-04-18 03:26:29 +0200 | tri | (~tri@ool-18bc2e74.dyn.optonline.net) (Remote host closed the connection) |
| 2024-04-18 03:26:36 +0200 | <geekosaur> | so it's your duty to play along with what the C API requires |
| 2024-04-18 03:26:56 +0200 | beka | (~beka@2607:f598:bd4a:6e0:c0ad:38f8:7650:7d75) |
| 2024-04-18 03:28:16 +0200 | beka | (~beka@2607:f598:bd4a:6e0:c0ad:38f8:7650:7d75) (Remote host closed the connection) |
| 2024-04-18 03:33:59 +0200 | madeleine-sydney | (~madeleine@c-76-155-235-153.hsd1.co.comcast.net) (Quit: Konversation terminated!) |
| 2024-04-18 03:42:36 +0200 | xff0x | (~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp) |
| 2024-04-18 03:43:35 +0200 | todi | (~todi@p57803331.dip0.t-ipconnect.de) (Remote host closed the connection) |
| 2024-04-18 03:43:51 +0200 | todi | (~todi@p57803331.dip0.t-ipconnect.de) |
| 2024-04-18 03:44:23 +0200 | otto_s | (~user@p4ff27d2e.dip0.t-ipconnect.de) (Ping timeout: 260 seconds) |
| 2024-04-18 03:46:06 +0200 | otto_s | (~user@p4ff271d1.dip0.t-ipconnect.de) |
| 2024-04-18 03:47:49 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 03:49:36 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 03:55:52 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 03:58:03 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 04:00:23 +0200 | califax | (~califax@user/califx) (Remote host closed the connection) |
| 2024-04-18 04:00:32 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 04:01:07 +0200 | xff0x | (~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp) (Ping timeout: 268 seconds) |
| 2024-04-18 04:01:27 +0200 | califax | (~califax@user/califx) |
| 2024-04-18 04:02:54 +0200 | xff0x | (~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp) |
| 2024-04-18 04:10:52 +0200 | axioms | (~gnu-user@2a00:23c7:c32c:b101:b454:be36:7ae4:3bb6) |
| 2024-04-18 04:12:52 +0200 | tri | (~tri@ool-18bc2e74.dyn.optonline.net) |
| 2024-04-18 04:13:07 +0200 | kritzefitz | (~kritzefit@debian/kritzefitz) (Ping timeout: 256 seconds) |
| 2024-04-18 04:14:35 +0200 | sroso | (~sroso@user/SrOso) |
| 2024-04-18 04:22:37 +0200 | kritzefitz | (~kritzefit@debian/kritzefitz) |
| 2024-04-18 04:26:04 +0200 | notzmv | (~daniel@user/notzmv) |
| 2024-04-18 04:30:33 +0200 | dcpagan | (~dcpagan@gateway/tor-sasl/dcpagan) |
| 2024-04-18 04:36:21 +0200 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) |
| 2024-04-18 04:38:07 +0200 | wroathe | (~wroathe@user/wroathe) (Ping timeout: 268 seconds) |
| 2024-04-18 04:39:48 +0200 | wroathe | (~wroathe@207-153-38-140.fttp.usinternet.com) |
| 2024-04-18 04:39:48 +0200 | wroathe | (~wroathe@207-153-38-140.fttp.usinternet.com) (Changing host) |
| 2024-04-18 04:39:48 +0200 | wroathe | (~wroathe@user/wroathe) |
| 2024-04-18 04:40:03 +0200 | mei | (~mei@user/mei) (Ping timeout: 252 seconds) |
| 2024-04-18 04:41:02 +0200 | mei | (~mei@user/mei) |
| 2024-04-18 04:42:29 +0200 | phma | (phma@2001:5b0:210f:3f8:8fc8:ef37:29ba:76ce) (Read error: Connection reset by peer) |
| 2024-04-18 04:43:04 +0200 | td_ | (~td@i53870905.versanet.de) (Ping timeout: 256 seconds) |
| 2024-04-18 04:43:09 +0200 | phma | (~phma@host-67-44-208-76.hnremote.net) |
| 2024-04-18 04:44:47 +0200 | td_ | (~td@i53870914.versanet.de) |
| 2024-04-18 04:46:27 +0200 | igemnace | (~ian@user/igemnace) |
| 2024-04-18 04:52:42 +0200 | ski | (~ski@ext-1-033.eduroam.chalmers.se) (Ping timeout: 252 seconds) |
| 2024-04-18 04:53:16 +0200 | ddellacosta | (~ddellacos@ool-44c73d29.dyn.optonline.net) (Ping timeout: 256 seconds) |
| 2024-04-18 05:03:01 +0200 | ski | (~ski@ext-1-033.eduroam.chalmers.se) |
| 2024-04-18 05:05:24 +0200 | <Inst> | huh, was never aware of this |
| 2024-04-18 05:05:25 +0200 | <Inst> | https://ghc.gitlab.haskell.org/ghc/doc/users_guide/exts/package_qualified_imports.html |
| 2024-04-18 05:09:42 +0200 | ddellacosta | (~ddellacos@ool-44c73d29.dyn.optonline.net) |
| 2024-04-18 05:13:06 +0200 | nullobject | (~josh@user/nullobject) |
| 2024-04-18 05:22:15 +0200 | danza | (~francesco@ge-19-109-232.service.infuturo.it) |
| 2024-04-18 05:32:15 +0200 | causal | (~eric@50.35.88.207) |
| 2024-04-18 05:48:51 +0200 | peterbecich | (~Thunderbi@47.229.123.186) |
| 2024-04-18 05:53:51 +0200 | machinedgod | (~machinedg@d173-183-246-216.abhsia.telus.net) (Ping timeout: 256 seconds) |
| 2024-04-18 05:57:49 +0200 | aforemny | (~aforemny@2001:9e8:6ccd:f100:e17c:113d:7:744f) |
| 2024-04-18 05:59:05 +0200 | aforemny_ | (~aforemny@2001:9e8:6ce7:3b00:8038:4ef8:85b4:e05b) (Ping timeout: 256 seconds) |
| 2024-04-18 06:07:26 +0200 | _ht | (~Thunderbi@28-52-174-82.ftth.glasoperator.nl) |
| 2024-04-18 06:08:13 +0200 | michalz | (~michalz@185.246.207.221) |
| 2024-04-18 06:13:28 +0200 | wroathe | (~wroathe@user/wroathe) (Ping timeout: 260 seconds) |
| 2024-04-18 06:16:27 +0200 | chiselfuse | (~chiselfus@user/chiselfuse) (Remote host closed the connection) |
| 2024-04-18 06:24:07 +0200 | chiselfuse | (~chiselfus@user/chiselfuse) |
| 2024-04-18 06:31:35 +0200 | peterbecich | (~Thunderbi@47.229.123.186) (Ping timeout: 268 seconds) |
| 2024-04-18 06:34:42 +0200 | it_ | (~quassel@v2202212189510211193.supersrv.de) (Quit: No Ping reply in 210 seconds.) |
| 2024-04-18 06:41:56 +0200 | Philonous | (~Philonous@user/philonous) (Ping timeout: 260 seconds) |
| 2024-04-18 06:42:26 +0200 | it_ | (~quassel@v2202212189510211193.supersrv.de) |
| 2024-04-18 06:42:28 +0200 | Philonous | (~Philonous@user/philonous) |
| 2024-04-18 06:42:52 +0200 | sshine | (~simon@zhen.mechanicus.xyz) (Ping timeout: 260 seconds) |
| 2024-04-18 06:42:52 +0200 | s4msung | (aynWsNEo99@user/s4msung) (Ping timeout: 260 seconds) |
| 2024-04-18 06:42:59 +0200 | sshine | (~simon@zhen.mechanicus.xyz) |
| 2024-04-18 06:43:55 +0200 | s4msung | (~s4msung@user/s4msung) |
| 2024-04-18 06:48:51 +0200 | waleee | (~waleee@h-176-10-144-38.NA.cust.bahnhof.se) (Ping timeout: 268 seconds) |
| 2024-04-18 06:56:52 +0200 | peterbecich | (~Thunderbi@47.229.123.186) |
| 2024-04-18 07:02:15 +0200 | itscaleb | (~itscaleb@user/itscaleb) (Quit: away) |
| 2024-04-18 07:05:13 +0200 | itscaleb | (~itscaleb@user/itscaleb) |
| 2024-04-18 07:05:15 +0200 | mei | (~mei@user/mei) (Ping timeout: 256 seconds) |
| 2024-04-18 07:10:31 +0200 | axioms | (~gnu-user@2a00:23c7:c32c:b101:b454:be36:7ae4:3bb6) (Ping timeout: 255 seconds) |
| 2024-04-18 07:12:35 +0200 | monochrom | (trebla@216.138.220.146) (Ping timeout: 264 seconds) |
| 2024-04-18 07:14:00 +0200 | it_ | (~quassel@v2202212189510211193.supersrv.de) (Quit: No Ping reply in 180 seconds.) |
| 2024-04-18 07:15:43 +0200 | it_ | (~quassel@v2202212189510211193.supersrv.de) |
| 2024-04-18 07:18:27 +0200 | takuan | (~takuan@178-116-218-225.access.telenet.be) |
| 2024-04-18 07:19:08 +0200 | tri | (~tri@ool-18bc2e74.dyn.optonline.net) (Remote host closed the connection) |
| 2024-04-18 07:19:24 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) |
| 2024-04-18 07:19:32 +0200 | danza | (~francesco@ge-19-109-232.service.infuturo.it) (Read error: Connection reset by peer) |
| 2024-04-18 07:20:06 +0200 | danza | (~francesco@ge-19-98-47.service.infuturo.it) |
| 2024-04-18 07:23:40 +0200 | monochrom | (trebla@216.138.220.146) |
| 2024-04-18 07:23:44 +0200 | zetef | (~quassel@5.2.182.99) |
| 2024-04-18 07:25:57 +0200 | myxos | (~myxos@65.28.251.121) (Remote host closed the connection) |
| 2024-04-18 07:26:13 +0200 | danza | (~francesco@ge-19-98-47.service.infuturo.it) (Remote host closed the connection) |
| 2024-04-18 07:26:36 +0200 | danza | (~francesco@ge-19-98-47.service.infuturo.it) |
| 2024-04-18 07:26:41 +0200 | myxos | (~myxos@65.28.251.121) |
| 2024-04-18 07:29:59 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2024-04-18 07:30:02 +0200 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2024-04-18 07:31:27 +0200 | danza | (~francesco@ge-19-98-47.service.infuturo.it) (Ping timeout: 256 seconds) |
| 2024-04-18 07:31:46 +0200 | philopsos | (~caecilius@user/philopsos) |
| 2024-04-18 07:33:19 +0200 | it_ | (~quassel@v2202212189510211193.supersrv.de) (Quit: No Ping reply in 180 seconds.) |
| 2024-04-18 07:34:59 +0200 | mei | (~mei@user/mei) |
| 2024-04-18 07:36:03 +0200 | bilegeek | (~bilegeek@2600:1008:b082:b7f1:2f0e:c3ab:9fc1:67e7) |
| 2024-04-18 07:36:33 +0200 | _ht | (~Thunderbi@28-52-174-82.ftth.glasoperator.nl) (Remote host closed the connection) |
| 2024-04-18 07:40:31 +0200 | euleritian | (~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) (Ping timeout: 260 seconds) |
| 2024-04-18 07:40:41 +0200 | euleritian | (~euleritia@dynamic-176-006-184-220.176.6.pool.telefonica.de) |
| 2024-04-18 07:41:31 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 07:42:32 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 07:43:19 +0200 | peterbecich | (~Thunderbi@47.229.123.186) (Ping timeout: 260 seconds) |
| 2024-04-18 07:44:44 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 07:44:48 +0200 | axioms | (~gnu-user@2a00:23c7:c32c:b101:b454:be36:7ae4:3bb6) |
| 2024-04-18 07:48:50 +0200 | it_ | (~quassel@v2202212189510211193.supersrv.de) |
| 2024-04-18 07:57:55 +0200 | mei | (~mei@user/mei) (Ping timeout: 268 seconds) |
| 2024-04-18 08:00:38 +0200 | reki | (~halloy490@broadband-5-228-80-43.ip.moscow.rt.ru) |
| 2024-04-18 08:00:43 +0200 | danse-nr3 | (~danse-nr3@ge-19-98-47.service.infuturo.it) |
| 2024-04-18 08:07:20 +0200 | igemnace | (~ian@user/igemnace) (Read error: Connection reset by peer) |
| 2024-04-18 08:13:50 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) |
| 2024-04-18 08:17:23 +0200 | JeremyB99 | (~JeremyB99@2600:1702:21b0:a500:a430:c3a5:5a62:375c) (Read error: Connection reset by peer) |
| 2024-04-18 08:17:29 +0200 | it_ | (~quassel@v2202212189510211193.supersrv.de) (Quit: No Ping reply in 180 seconds.) |