Newest at the top
| 2025-05-16 20:05:45 +0200 | <c_wraith> | length is sufficient |
| 2025-05-16 20:03:38 +0200 | <EvanR> | deepseq |
| 2025-05-16 20:03:26 +0200 | <EvanR> | how do you even do that |
| 2025-05-16 20:03:14 +0200 | <EvanR> | I'm boggling at reading in an entire lazy bytestring and closing the connection immediately xD |
| 2025-05-16 20:02:28 +0200 | <EvanR> | it says immediately closes the connection |
| 2025-05-16 20:02:23 +0200 | <EvanR> | I paraphrased it |
| 2025-05-16 20:00:13 +0200 | <monochrom> | Hell, also for the "read" part. |
| 2025-05-16 19:59:41 +0200 | <monochrom> | You can believe all of it, keeping in mind it never said "right now right away" for the "close" part. |
| 2025-05-16 19:58:29 +0200 | <c_wraith> | I'm not sure which part of the docs to disbelieve |
| 2025-05-16 19:58:13 +0200 | <c_wraith> | It's either not lazy for efficiency or doesn't promptly close the connection |
| 2025-05-16 19:54:55 +0200 | <EvanR> | I'm wondering how lazy that strategy can be |
| 2025-05-16 19:53:51 +0200 | <monochrom> | A Data.ByteString.Lazy of Flesh |
| 2025-05-16 19:51:52 +0200 | dibblego | (~dibblego@haskell/developer/dibblego) dibblego |
| 2025-05-16 19:51:52 +0200 | dibblego | (~dibblego@116.255.1.119) (Changing host) |
| 2025-05-16 19:51:52 +0200 | dibblego | (~dibblego@116.255.1.119) |
| 2025-05-16 19:51:23 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 19:51:02 +0200 | <EvanR> | httpLbs (pronounced http pounds of course), "reads in the entire response and closes the connection. uses lazy bytestring for memory efficiency" o_O |
| 2025-05-16 19:50:00 +0200 | dibblego | (~dibblego@haskell/developer/dibblego) (Ping timeout: 244 seconds) |
| 2025-05-16 19:49:37 +0200 | <monochrom> | When meaningful names go wrong. :) |
| 2025-05-16 19:48:43 +0200 | <EvanR> | or not supposed to be |
| 2025-05-16 19:48:29 +0200 | <EvanR> | oh getResponseBody is not IO |
| 2025-05-16 19:48:04 +0200 | <ski> | wbrawner ^ |
| 2025-05-16 19:47:56 +0200 | <ski> | return (L8.unpack (responseBody response)) |
| 2025-05-16 19:47:40 +0200 | <ski> | oh, and that would make it |
| 2025-05-16 19:47:26 +0200 | <ski> | hm, try replacing `getResponseBody' with `responseBody' ? |
| 2025-05-16 19:46:34 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
| 2025-05-16 19:42:45 +0200 | jespada | (~jespada@r179-25-150-22.dialup.adsl.anteldata.net.uy) (Client Quit) |
| 2025-05-16 19:41:40 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 19:40:58 +0200 | jespada | (~jespada@r179-25-150-22.dialup.adsl.anteldata.net.uy) jespada |
| 2025-05-16 19:39:12 +0200 | <ski> | `(<$>)' is another name for `fmap' |
| 2025-05-16 19:38:47 +0200 | <wbrawner> | That gives me Couldn't match type ‘L8.ByteString’ with ‘IO L8.ByteString’ |
| 2025-05-16 19:38:29 +0200 | <wbrawner> | Haven't seen that before, I'll have to read up on what it is |
| 2025-05-16 19:37:08 +0200 | <ski> | yep |
| 2025-05-16 19:37:06 +0200 | <ski> | L8.unpack <$> getResponseBody response |
| 2025-05-16 19:36:39 +0200 | <EvanR> | try changing $ to <$> on the last line |
| 2025-05-16 19:36:27 +0200 | <wbrawner> | I'll change that to requestStr or something along those lines |
| 2025-05-16 19:36:07 +0200 | <wbrawner> | EvanR yeah, naming is hard :P I have GET prefixed to the URL |
| 2025-05-16 19:35:52 +0200 | <EvanR> | i.e. DELETE /facebook |
| 2025-05-16 19:35:27 +0200 | j1n37- | (~j1n37@user/j1n37) (Ping timeout: 265 seconds) |
| 2025-05-16 19:35:23 +0200 | <EvanR> | "parseRequest" sounds like it would expect a request and not a URL |
| 2025-05-16 19:35:14 +0200 | <ski> | (not being LGPL, iirc ?) |
| 2025-05-16 19:35:04 +0200 | <wbrawner> | Couldn't match type ‘Char’ with ‘[Char]’. Expected IO String, Actual [Char] |
| 2025-05-16 19:34:43 +0200 | <wbrawner> | I updated the type signature, now getting a different error: https://paste.wbrawner.com/upload/monkey-falcon-dove |
| 2025-05-16 19:34:38 +0200 | <ski> | there's some variant/clone, `ledit', written in OCaml |
| 2025-05-16 19:34:28 +0200 | <EvanR> | violating that rule instantly |
| 2025-05-16 19:34:25 +0200 | <wbrawner> | EvanR if that question was for me, I'm using http-client |
| 2025-05-16 19:34:06 +0200 | <EvanR> | do one thing and do it well, then combine with something else which did that |
| 2025-05-16 19:34:04 +0200 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-05-16 19:33:59 +0200 | tromp | (~textual@2001:1c00:3487:1b00:a44a:50e6:3df5:3b66) |
| 2025-05-16 19:33:48 +0200 | <monochrom> | (and that's how I heard of it) |