Newest at the top
| 2026-02-25 20:22:50 +0100 | uli-fem | (~uli-fem@118.210.1.123) |
| 2026-02-25 20:22:39 +0100 | target_i | (~target_i@user/target-i/x-6023099) target_i |
| 2026-02-25 20:16:57 +0100 | prdak | (~Thunderbi@user/prdak) (Ping timeout: 255 seconds) |
| 2026-02-25 20:16:56 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 20:16:55 +0100 | tjbc | (~tjbc@user/fliife) fliife |
| 2026-02-25 20:14:20 +0100 | Tuplanolla | (~Tuplanoll@88-114-89-88.elisa-laajakaista.fi) Tuplanolla |
| 2026-02-25 20:13:43 +0100 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh |
| 2026-02-25 20:12:15 +0100 | tjbc | (~tjbc@user/fliife) (Ping timeout: 245 seconds) |
| 2026-02-25 20:10:39 +0100 | uli-fem | (~uli-fem@118.210.1.123) (Ping timeout: 255 seconds) |
| 2026-02-25 20:06:50 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-25 20:06:24 +0100 | tjbc | (~tjbc@user/fliife) fliife |
| 2026-02-25 20:05:06 +0100 | tjbc | (~tjbc@user/fliife) (Ping timeout: 268 seconds) |
| 2026-02-25 20:04:07 +0100 | uli-fem | (~uli-fem@118.210.1.123) |
| 2026-02-25 20:03:37 +0100 | tromp | (~textual@2001:1c00:3487:1b00:7955:9591:6018:7ef9) |
| 2026-02-25 20:02:40 +0100 | uli-fem | (~uli-fem@118.210.1.123) (Ping timeout: 245 seconds) |
| 2026-02-25 20:02:36 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 20:00:56 +0100 | <haskellbridge> | <ijouw> I think i messed the fmap up |
| 2026-02-25 19:58:17 +0100 | uli-fem | (~uli-fem@118.210.1.123) |
| 2026-02-25 19:56:45 +0100 | <haskellbridge> | <ijouw> https://paste.tomsmeding.com/OUVh8TUU |
| 2026-02-25 19:56:20 +0100 | <haskellbridge> | <ijouw> Some formatting issue |
| 2026-02-25 19:56:03 +0100 | <haskellbridge> | <ijouw> That prints weiredly |
| 2026-02-25 19:55:45 +0100 | <haskellbridge> | ... long message truncated: https://kf8nh.com/_heisenbridge/media/kf8nh.com/ROHzIHXhlwulEzElCZCROwyR/IEURazvg-wM (5 lines) |
| 2026-02-25 19:55:45 +0100 | <haskellbridge> | <ijouw> Like so |
| 2026-02-25 19:51:18 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds) |
| 2026-02-25 19:47:57 +0100 | <haskellbridge> | <ijouw> i usually use left to right composition |
| 2026-02-25 19:47:45 +0100 | <lambdabot> | Nothing |
| 2026-02-25 19:47:44 +0100 | <probie> | > (\xs -> let y:ys = xs in if null xs then Nothing else Just (y, ys)) [] |
| 2026-02-25 19:47:43 +0100 | <Milan_Vanca> | ijouw do you really find this more readable? |
| 2026-02-25 19:47:05 +0100 | <haskellbridge> | <ijouw> i did not typecheck it |
| 2026-02-25 19:46:48 +0100 | <ski> | hah, ijouw :) |
| 2026-02-25 19:46:10 +0100 | <lambdabot> | *Exception: <interactive>:3:5-21: Non-exhaustive patterns in !Nothing |
| 2026-02-25 19:46:08 +0100 | <ski> | > let !Nothing = Just 3 in () |
| 2026-02-25 19:46:05 +0100 | <lambdabot> | () |
| 2026-02-25 19:46:03 +0100 | <ski> | > let Nothing = Just 3 in () |
| 2026-02-25 19:45:40 +0100 | <lambdabot> | (*Exception: <interactive>:3:5-26: Non-exhaustive patterns in x : xs |
| 2026-02-25 19:45:38 +0100 | <ski> | > let x:xs = [] :: [Integer] in (x,xs) |
| 2026-02-25 19:45:19 +0100 | <haskellbridge> | <ijouw> counter = fmap (((s,v) -> responseLBS s [(hContentType, hvApplicationJson)] v) . ((status400,) . PL.pack ||| (status200,) . encode . increment)) . lazyRequestBody |
| 2026-02-25 19:45:11 +0100 | <ski> | (and on other data constructors. however, a value of tuple type can never fail to match a tuple pattern, but for data types with multiple data constructors, you can get match failure, so it's good to only match on those, in `let'/`where'/toplevel sparingly, when you're sure that they won't actually fail ..) |
| 2026-02-25 19:44:49 +0100 | rncwnd | (~quassel@2a01:4f8:221:27c6::1) |
| 2026-02-25 19:44:33 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 19:44:13 +0100 | rncwnd | (~quassel@2a01:4f8:221:27c6::1) (Quit: Later) |
| 2026-02-25 19:43:41 +0100 | <ski> | you can always match on tuples, in `let' and `where' (and toplevel) |
| 2026-02-25 19:43:22 +0100 | <ski> | Milan_Vanca : yes, it's same rule. `where'-block also starts at whatever column `something' is at, regardless of which column `where' is at |
| 2026-02-25 19:43:08 +0100 | <Milan_Vanca> | ski: Nicer solution.. so tuple is ok ni this case? |
| 2026-02-25 19:42:28 +0100 | <ski> | return (responseLBS status [(hContentType,hvAplicationJSON)] result) |
| 2026-02-25 19:42:15 +0100 | <ski> | Right c -> (status200,encode (increment c)) |
| 2026-02-25 19:42:02 +0100 | <ski> | Left e -> (status400,PL.pack e) |
| 2026-02-25 19:41:59 +0100 | <Milan_Vanca> | I don't think same rules apply for where I can have where\n..something or where\n..................something |
| 2026-02-25 19:41:39 +0100 | <ski> | let (status,result) = case eitherDecode body of |
| 2026-02-25 19:41:03 +0100 | wickedjargon | (~user@208.98.208.115) (Ping timeout: 246 seconds) |