Newest at the top
| 2025-10-08 14:58:00 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 265 seconds) |
| 2025-10-08 14:57:32 +0200 | <haskellbridge> | <Morj> Lowercase morj is my irc nick, but I only use it from one PC which is not this one |
| 2025-10-08 14:56:58 +0200 | <tomsmeding> | I did that without thinking when Morj didn't autocomplete, but that was because you're over the bridge lol |
| 2025-10-08 14:56:41 +0200 | fp | (~Thunderbi@2001:708:150:10::72df) fp |
| 2025-10-08 14:56:34 +0200 | <haskellbridge> | <Morj> I did think there already exist some that are reasonable, it's an old protocol |
| 2025-10-08 14:56:33 +0200 | <tomsmeding> | that @tell is a lambdabot thing that sends that to you in a private message when you next join on irc |
| 2025-10-08 14:56:19 +0200 | <haskellbridge> | <Morj> Thanks for the info tоmsmeding and mаuke |
| 2025-10-08 14:56:15 +0200 | <tomsmeding> | oh brainfart |
| 2025-10-08 14:56:06 +0200 | <haskellbridge> | <Morj> I really want to know how that at-tell is supposed to look without a bridge |
| 2025-10-08 14:55:02 +0200 | <lambdabot> | Consider it noted. |
| 2025-10-08 14:55:01 +0200 | <tomsmeding> | @tell morj that "join/part only for users that participated recently" is built-in behaviour in weechat in the irc.look.smart_filter* settings |
| 2025-10-08 14:54:30 +0200 | poscat | (~poscat@user/poscat) poscat |
| 2025-10-08 14:54:11 +0200 | poscat | (~poscat@user/poscat) (Remote host closed the connection) |
| 2025-10-08 14:53:38 +0200 | <tomsmeding> | you may need ghc 9.10 or higher to get the lexical profiling backtraces |
| 2025-10-08 14:52:46 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-10-08 14:52:42 +0200 | <tomsmeding> | bwe: what GHC version are you on? |
| 2025-10-08 14:52:14 +0200 | <tomsmeding> | -xc prints backtrace info on EVERY thrown exception though, even if it ends up being caught later -- this is a fun way to find out that the haskell standard library uses quite a bunch of exceptions internally sometimes |
| 2025-10-08 14:51:33 +0200 | <tomsmeding> | bwe: yes, with --enable-profilng, optionally with +RTS -xc, you should get more backtrace info |
| 2025-10-08 14:50:55 +0200 | <tomsmeding> | actually I think this latter thing is already done automatically if you --enable-profiling in cabal |
| 2025-10-08 14:50:27 +0200 | <tomsmeding> | alternatively, you can add additional annotations to your program that explicitly collect lexical call stack info; this slows down the program a little because it now does more work and also inhibits some optimisations |
| 2025-10-08 14:49:56 +0200 | <bwe> | would that automatically show a context (e.g. where the Prelude.last was called)? |
| 2025-10-08 14:49:35 +0200 | <tomsmeding> | (cabal run --enable-profiling yourprogram -- +RTS -xc) |
| 2025-10-08 14:49:23 +0200 | <tomsmeding> | there are two things you can do to get something useful: print the actual haskell evaluation stack (which is in order of forcing, not in order of "calls" in your program); you can get that by compiling in profiling mode and running with +RTS -xc |
| 2025-10-08 14:48:34 +0200 | <tomsmeding> | bwe: haskell, being lazy, does not necessarily execute according to the lexical structure of your program; as a result, in contrast to e.g. C/C++, there is no hardware call stack that you can just read off and get something useful |
| 2025-10-08 14:48:14 +0200 | user363627 | (~user@user/user363627) (Remote host closed the connection) |
| 2025-10-08 14:48:10 +0200 | guest3860 | (~username@2a04:27c0:0:d::e018) yoann |
| 2025-10-08 14:47:04 +0200 | annamalai | (~annamalai@157.32.202.67) annamalai |
| 2025-10-08 14:47:01 +0200 | merijn | (~merijn@77.242.116.146) (Ping timeout: 256 seconds) |
| 2025-10-08 14:45:41 +0200 | Googulator52 | (~Googulato@2a01-036d-0106-03fa-5967-6f2a-1e2d-f05a.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-10-08 14:45:41 +0200 | Googulator53 | (~Googulato@2a01-036d-0106-03fa-5967-6f2a-1e2d-f05a.pool6.digikabel.hu) |
| 2025-10-08 14:44:11 +0200 | comerijn | (~merijn@77.242.116.146) merijn |
| 2025-10-08 14:42:54 +0200 | <bwe> | (and why isn't it default?) |
| 2025-10-08 14:42:43 +0200 | <bwe> | how can I get a little more context? |
| 2025-10-08 14:42:40 +0200 | SlackCoder | (~SlackCode@64-94-63-8.ip.weststar.net.ky) (Quit: Leaving) |
| 2025-10-08 14:42:22 +0200 | <bwe> | *** Exception: Prelude.last: empty list |
| 2025-10-08 14:41:06 +0200 | <mauke> | Morj: sounds like something you could script in irssi |
| 2025-10-08 14:37:59 +0200 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-10-08 14:31:18 +0200 | Googulator90 | (~Googulato@193-226-241-224.pool.digikabel.hu) (Quit: Client closed) |
| 2025-10-08 14:31:03 +0200 | poscat | (~poscat@user/poscat) poscat |
| 2025-10-08 14:30:58 +0200 | Googulator52 | (~Googulato@2a01-036d-0106-03fa-5967-6f2a-1e2d-f05a.pool6.digikabel.hu) |
| 2025-10-08 14:30:27 +0200 | poscat | (~poscat@user/poscat) (Remote host closed the connection) |
| 2025-10-08 14:26:01 +0200 | trickard_ | trickard |
| 2025-10-08 14:24:40 +0200 | merijn | (~merijn@77.242.116.146) (Ping timeout: 255 seconds) |
| 2025-10-08 14:22:35 +0200 | trickard_ | (~trickard@cpe-52-98-47-163.wireline.com.au) |
| 2025-10-08 14:19:53 +0200 | qqe | (~qqq@185.54.23.200) |
| 2025-10-08 14:18:01 +0200 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-10-08 14:17:33 +0200 | trickard_ | (~trickard@cpe-51-98-47-163.wireline.com.au) (Ping timeout: 256 seconds) |
| 2025-10-08 14:15:42 +0200 | Googulator35 | (~Googulato@193-226-241-224.pool.digikabel.hu) (Quit: Client closed) |
| 2025-10-08 14:15:40 +0200 | Googulator90 | (~Googulato@193-226-241-224.pool.digikabel.hu) |
| 2025-10-08 14:15:08 +0200 | fp | (~Thunderbi@wireless-86-50-141-222.open.aalto.fi) (Remote host closed the connection) |