Newest at the top
| 2025-11-14 05:02:07 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-11-14 04:57:56 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-14 04:56:48 +0100 | <jreicher> | monochrom: Oh wait. Are you saying shift/reset might be dynamic in the sense that shift can be substituted into the scope of a reset? |
| 2025-11-14 04:47:25 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-11-14 04:42:33 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-14 04:31:52 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds) |
| 2025-11-14 04:29:49 +0100 | td_ | (~td@i53870933.versanet.de) |
| 2025-11-14 04:28:00 +0100 | td__ | (~td@i53870917.versanet.de) (Ping timeout: 256 seconds) |
| 2025-11-14 04:27:30 +0100 | trickard_ | (~trickard@cpe-62-98-47-163.wireline.com.au) |
| 2025-11-14 04:27:16 +0100 | trickard_ | (~trickard@cpe-62-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-14 04:27:10 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-14 04:24:16 +0100 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2025-11-14 04:23:27 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-11-14 04:23:01 +0100 | jmcantrell | (~weechat@user/jmcantrell) (Quit: WeeChat 4.7.1) |
| 2025-11-14 04:18:36 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-14 04:16:49 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 264 seconds) |
| 2025-11-14 04:11:25 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-11-14 04:07:36 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-11-14 04:06:54 +0100 | annamalai | (~annamalai@157.32.194.69) annamalai |
| 2025-11-14 04:02:18 +0100 | <jreicher> | I meant to say "...and then the continuation is constructed..." |
| 2025-11-14 04:01:45 +0100 | <jreicher> | I think lexically scoped is correct. When shift captures the evaluation context it includes the reset, which is certainly a lexical scoping before anything else is done, and then the continuation is captured with that reset in exactly the same spot, which is effectively the same "spirit" as capture-avoiding substitution for beta-reduction, and so the lexical scoping is preserved. At least that's my take on it. |
| 2025-11-14 04:00:34 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-14 04:00:11 +0100 | <monochrom> | (In the same sense as: If you define "bar = x + 1", and if it is bar's call site that determines what x means, that is dynamic scoping.) |
| 2025-11-14 03:59:03 +0100 | <monochrom> | I may be wrong in saying "lexically scoped". If you define "foo = shift ...", then it is foo's call sites that determines the corresponding reset. That is dynamic rather than static. |
| 2025-11-14 03:56:49 +0100 | deptype_ | (~deptype@124.123.128.236) (Ping timeout: 256 seconds) |
| 2025-11-14 03:56:24 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 244 seconds) |
| 2025-11-14 03:56:19 +0100 | <jreicher> | That's interesting. I couldn't tell for sure from the "theoretical" difference between static and dynamic, but it seemed to me it would be. |
| 2025-11-14 03:55:35 +0100 | <monochrom> | Yes. |
| 2025-11-14 03:55:34 +0100 | <jreicher> | monochrom: ^ |
| 2025-11-14 03:55:13 +0100 | <jreicher> | OK, so the exercises you give there can be done in terms of shift/reset. In your experience is shift/reset "usually" enough for "most" situations? (I realise that's a vague question) |
| 2025-11-14 03:55:08 +0100 | deptype | (~deptype@2406:b400:3a:73c2:d817:93dd:2198:fe22) (Ping timeout: 256 seconds) |
| 2025-11-14 03:53:23 +0100 | deptype__ | (~deptype@124.123.128.236) |
| 2025-11-14 03:52:01 +0100 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2025-11-14 03:51:59 +0100 | deptype_ | (~deptype@124.123.128.236) |
| 2025-11-14 03:51:22 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-11-14 03:50:02 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-11-14 03:50:01 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 256 seconds) |
| 2025-11-14 03:46:55 +0100 | myxos | (~myxos@2001:579:8380:f20:1406:c18d:98b3:27d1) myxokephale |
| 2025-11-14 03:45:10 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-14 03:44:22 +0100 | <monochrom> | jreicher: My https://www.vex.net/~trebla/haskell/cont.xhtml#shift-reset (or the whole thing) |
| 2025-11-14 03:41:28 +0100 | bggd | (~bgg@2a01:e0a:819:1510:761:a174:4d6f:f8ab) (Remote host closed the connection) |
| 2025-11-14 03:37:33 +0100 | ubert1 | ubert |
| 2025-11-14 03:37:33 +0100 | ubert | (~Thunderbi@178.165.182.105.wireless.dyn.drei.com) (Ping timeout: 256 seconds) |
| 2025-11-14 03:34:29 +0100 | ubert1 | (~Thunderbi@178.165.175.248.wireless.dyn.drei.com) ubert |
| 2025-11-14 03:34:07 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds) |
| 2025-11-14 03:29:46 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-14 03:24:55 +0100 | <jreicher> | But I couldn't find her spending much time on shift/reset. It was more about prompt/control and then prompt/control0 |
| 2025-11-14 03:24:37 +0100 | <jreicher> | Yeah I did. That's one of the first introductions to it all I had. |
| 2025-11-14 03:23:55 +0100 | <jackdk> | Maybe look up Alexis King's work on eff? |
| 2025-11-14 03:23:54 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection) |