Newest at the top
| 2024-04-28 00:49:22 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) |
| 2024-04-28 00:48:41 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) (Remote host closed the connection) |
| 2024-04-28 00:45:16 +0200 | <geekosaur> | unprincipled coroutines |
| 2024-04-28 00:42:12 +0200 | <yin> | got it |
| 2024-04-28 00:41:47 +0200 | <dolio> | When you need something, your thread gets interrupted and the one that was supposed to calculate it runs instead. |
| 2024-04-28 00:41:05 +0200 | <dolio> | You can think of it as concurrency where the scheduling gets informed by the lazy evaluation. |
| 2024-04-28 00:38:48 +0200 | <yin> | is it just concurrent output or something else? |
| 2024-04-28 00:38:41 +0200 | peterbecich | (~Thunderbi@47.229.123.186) (Ping timeout: 252 seconds) |
| 2024-04-28 00:38:06 +0200 | <yin> | what is that list? |
| 2024-04-28 00:37:52 +0200 | <yin> | huh? |
| 2024-04-28 00:37:39 +0200 | yin | (~yin@user/zero) |
| 2024-04-28 00:36:07 +0200 | gmg | (~user@user/gehmehgeh) (Quit: Leaving) |
| 2024-04-28 00:27:47 +0200 | orcus- | (~orcus@host-78-146-88-32.as13285.net) (Remote host closed the connection) |
| 2024-04-28 00:27:17 +0200 | orcus- | (~orcus@host-78-146-88-32.as13285.net) |
| 2024-04-28 00:25:10 +0200 | <dolio> | ski gave the right answer. :þ |
| 2024-04-28 00:23:11 +0200 | yin | (~yin@user/zero) (Ping timeout: 256 seconds) |
| 2024-04-28 00:21:58 +0200 | dispater- | (~dispater@host-78-146-88-32.as13285.net) (Remote host closed the connection) |
| 2024-04-28 00:21:42 +0200 | dispater- | (~dispater@host-78-146-88-32.as13285.net) |
| 2024-04-28 00:18:11 +0200 | orcus- | (~orcus@host-78-146-88-32.as13285.net) (Remote host closed the connection) |
| 2024-04-28 00:18:10 +0200 | dispater- | (~dispater@host-78-146-88-32.as13285.net) (Remote host closed the connection) |
| 2024-04-28 00:17:59 +0200 | orcus- | (~orcus@host-78-146-88-32.as13285.net) |
| 2024-04-28 00:17:28 +0200 | dispater- | (~dispater@host-78-146-88-32.as13285.net) |
| 2024-04-28 00:13:51 +0200 | sam113101 | (~sam@24.157.253.231) |
| 2024-04-28 00:13:18 +0200 | sam113101 | (~sam@24.157.253.231) (Client Quit) |
| 2024-04-28 00:13:08 +0200 | __monty__ | (~toonn@user/toonn) (Quit: leaving) |
| 2024-04-28 00:11:39 +0200 | sam113101 | (~sam@24.157.253.231) |
| 2024-04-28 00:11:06 +0200 | sam113101 | (~sam@24.157.253.231) (Quit: WeeChat 4.2.2) |
| 2024-04-28 00:08:40 +0200 | pavonia | (~user@user/siracusa) |
| 2024-04-28 00:01:22 +0200 | sam113101 | (~sam@24.157.253.231) |
| 2024-04-28 00:01:02 +0200 | sam113101 | (~sam@24.157.253.231) (Quit: WeeChat 4.2.2) |
| 2024-04-27 23:58:04 +0200 | phma | (~phma@2001:5b0:2172:cfd8:e2ba:31ce:8b83:bc5) |
| 2024-04-27 23:57:48 +0200 | pavonia | (~user@user/siracusa) (Read error: Connection reset by peer) |
| 2024-04-27 23:57:03 +0200 | phma | (phma@2001:5b0:210d:77f8:690d:ee85:cd6a:7031) (Read error: Connection reset by peer) |
| 2024-04-27 23:49:55 +0200 | Square | (~Square@user/square) (Ping timeout: 245 seconds) |
| 2024-04-27 23:46:51 +0200 | target_i | (~target_i@user/target-i/x-6023099) (Quit: leaving) |
| 2024-04-27 23:45:36 +0200 | sam113101 | (~sam@24.157.253.231) |
| 2024-04-27 23:41:13 +0200 | sam113101 | (~sam@24.157.253.231) (Client Quit) |
| 2024-04-27 23:40:21 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2024-04-27 23:40:06 +0200 | sam113101 | (~sam@24.157.253.231) |
| 2024-04-27 23:39:49 +0200 | <EvanR> | it's possible to think yourself out of the side effects and claim what it's doing makes sense, but normally you don't have to do that in haskell. So extra brain cycles required |
| 2024-04-27 23:38:56 +0200 | <yahb2> | [h(),e(),l(),l(),o(), (),w(),o(),r(),l(),d()] |
| 2024-04-27 23:38:56 +0200 | <[Leary]> | % traverse (unsafeInterleaveIO . putChar) "hello world" >>= print |
| 2024-04-27 23:38:52 +0200 | <[Leary]> | Here, we're printing a list of units, so the `void` is redundant and should be removed. |
| 2024-04-27 23:38:24 +0200 | <yahb2> | [(),(),(),(),(),(),(),(),(),(),()] |
| 2024-04-27 23:38:24 +0200 | <[Leary]> | % traverse (unsafeInterleaveIO . putChar) "hello world" >>= print . void |
| 2024-04-27 23:38:10 +0200 | <[Leary]> | Jade: It's akin to `pure . unsafePerformIO`; the former does not actually cancel the danger of the latter. In particular, it violates referential transparency: when `unsafeInterleaveIO` is in use, you cannot replace one expression with another equal expression blindly, as one may produce observable side effects when forced, hence the substitution changes the meaning of your program. |
| 2024-04-27 23:37:39 +0200 | sam113102 | (~sam@24.157.253.231) (Client Quit) |
| 2024-04-27 23:36:00 +0200 | sam113102 | (~sam@24.157.253.231) |
| 2024-04-27 23:34:53 +0200 | dispater- | (~dispater@host-78-146-88-32.as13285.net) (Remote host closed the connection) |
| 2024-04-27 23:33:48 +0200 | dispater- | (~dispater@host-78-146-88-32.as13285.net) |