Newest at the top
| 2026-06-17 17:02:25 +0000 | machinedgod | (~machinedg@d108-173-95-19.abhsia.telus.net) machinedgod |
| 2026-06-17 17:00:48 +0000 | machinedgod | (~machinedg@d172-219-48-230.abhsia.telus.net) (Ping timeout: 265 seconds) |
| 2026-06-17 17:00:48 +0000 | puke | (~puke@user/puke) puke |
| 2026-06-17 17:00:34 +0000 | puke | (~puke@user/puke) (Remote host closed the connection) |
| 2026-06-17 16:55:38 +0000 | AlexNoo | (~AlexNoo@178.34.161.132) (Quit: Leaving) |
| 2026-06-17 16:43:34 +0000 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2026-06-17 16:41:43 +0000 | puke | (~puke@user/puke) puke |
| 2026-06-17 16:41:32 +0000 | puke | (~puke@user/puke) (Read error: Connection reset by peer) |
| 2026-06-17 16:39:35 +0000 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) |
| 2026-06-17 16:34:42 +0000 | sord937 | (~sord937@gateway/tor-sasl/sord937) (Quit: sord937) |
| 2026-06-17 16:27:34 +0000 | Vajb | (~Vajb@n722b5iomobz6966sly-1.v6.elisa-mobile.fi) |
| 2026-06-17 16:20:09 +0000 | CryptLab | (~NSA@171.33.191.92) CommanderBond007 |
| 2026-06-17 16:18:28 +0000 | CryptLab | (~NSA@171.33.191.94) (Read error: Connection reset by peer) |
| 2026-06-17 16:18:17 +0000 | Vajb | (~Vajb@n4fsyxesh0a4t8vm6z0-1.v6.elisa-mobile.fi) (Ping timeout: 248 seconds) |
| 2026-06-17 16:17:49 +0000 | polykernel_ | polykernel |
| 2026-06-17 16:17:49 +0000 | polykernel | (~polykerne@user/polykernel) (Ping timeout: 245 seconds) |
| 2026-06-17 16:15:47 +0000 | polykernel_ | (~polykerne@user/polykernel) polykernel |
| 2026-06-17 16:07:07 +0000 | danza | (~danza@user/danza) (Remote host closed the connection) |
| 2026-06-17 16:06:34 +0000 | pavonia | (~user@user/siracusa) (Quit: Bye!) |
| 2026-06-17 16:05:22 +0000 | polykernel_ | polykernel |
| 2026-06-17 16:05:22 +0000 | polykernel | (~polykerne@user/polykernel) (Ping timeout: 276 seconds) |
| 2026-06-17 16:03:25 +0000 | polykernel_ | (~polykerne@user/polykernel) polykernel |
| 2026-06-17 15:59:36 +0000 | AlexNoo | (~AlexNoo@178.34.161.132) |
| 2026-06-17 15:59:29 +0000 | AlexNoo | (~AlexNoo@85.174.182.219) (Ping timeout: 245 seconds) |
| 2026-06-17 15:58:55 +0000 | Alex_delenda_est | (~al_test@85.174.182.219) (Ping timeout: 245 seconds) |
| 2026-06-17 15:58:55 +0000 | AlexZenon | (~alzenon@85.174.182.219) (Ping timeout: 245 seconds) |
| 2026-06-17 15:57:16 +0000 | synchromesh | (~john@2406:5a00:247e:1500:a691:b1ff:0:f9d) synchromesh |
| 2026-06-17 15:55:30 +0000 | merijn | (~merijn@77.242.116.150) (Ping timeout: 248 seconds) |
| 2026-06-17 15:54:54 +0000 | chele | (~chele@user/chele) (Remote host closed the connection) |
| 2026-06-17 15:51:23 +0000 | synchromesh | (~john@2406:5a00:247e:1500:a691:b1ff:0:f9d) (Read error: Connection reset by peer) |
| 2026-06-17 15:39:41 +0000 | chromoblob | (~chromoblo@user/chromob1ot1c) chromoblob\0 |
| 2026-06-17 15:39:22 +0000 | chromoblob | (~chromoblo@user/chromob1ot1c) (Read error: Connection reset by peer) |
| 2026-06-17 15:39:08 +0000 | <danza> | thanks for the additional info merijn |
| 2026-06-17 15:38:25 +0000 | <merijn> | danza: tbh, I basically **always** have -Wall set in my cabal and then set -Werror in cabal.project.local |
| 2026-06-17 15:36:46 +0000 | <merijn> | Yeah, warnings don't invalidate the compile cache unless -Werror is active (unless someone wrecked my hard work) |
| 2026-06-17 15:36:06 +0000 | <danza> | okay found the problem. That works, but it will not retrigger compilation. I just have to run `cabal clean` before |
| 2026-06-17 15:35:26 +0000 | <merijn> | What makes you think some warnings aren't shown? |
| 2026-06-17 15:35:01 +0000 | <merijn> | Yeah, -Weverything is really not intended for real use :p |
| 2026-06-17 15:34:40 +0000 | Axman6 | (~Axman6@user/axman6) (Ping timeout: 245 seconds) |
| 2026-06-17 15:34:03 +0000 | <danza> | yes i just used -Weverything and that's too much |
| 2026-06-17 15:33:58 +0000 | <danza> | cheers |
| 2026-06-17 15:33:42 +0000 | <merijn> | Also note that -Wall is "almost all", there's a number of not recommended warnings not included |
| 2026-06-17 15:33:11 +0000 | <merijn> | danza: That enables them for all transitive dependencies. The best way is presumably to add it to ghc-options in your cabal project |
| 2026-06-17 15:32:28 +0000 | <danza> | i feel like some warnings are not being shown |
| 2026-06-17 15:32:14 +0000 | <danza> | is that the way to enable all warnings with cabal? |
| 2026-06-17 15:32:06 +0000 | <danza> | cabal build --ghc-options "-Wall" |
| 2026-06-17 15:29:58 +0000 | ystael | (~ystael@user/ystael) ystael |
| 2026-06-17 15:28:58 +0000 | polykernel_ | polykernel |
| 2026-06-17 15:28:58 +0000 | polykernel | (~polykerne@user/polykernel) (Ping timeout: 276 seconds) |
| 2026-06-17 15:27:21 +0000 | polykernel_ | (~polykerne@user/polykernel) polykernel |