Newest at the top
| 2026-04-13 13:14:06 +0000 | arandombit | (~arandombi@user/arandombit) arandombit |
| 2026-04-13 13:13:20 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) |
| 2026-04-13 13:11:24 +0000 | arandombit | (~arandombi@user/arandombit) (Remote host closed the connection) |
| 2026-04-13 13:02:03 +0000 | rekahsoft | (~rekahsoft@bras-base-orllon1103w-grc-20-76-67-111-168.dsl.bell.ca) rekahsoft |
| 2026-04-13 13:00:45 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) (Ping timeout: 255 seconds) |
| 2026-04-13 12:58:05 +0000 | xff0x | (~xff0x@2405:6580:b080:900:64fb:89e9:b5c1:12b3) |
| 2026-04-13 12:54:36 +0000 | <fp`> | ancillary knowledge more generally, really. Not just tools. |
| 2026-04-13 12:53:59 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) |
| 2026-04-13 12:53:21 +0000 | <fp`> | merijn: Sure, but I'd rather engage with a community that uses the language, learn the conventions from them, and learn about ancillary tools, like in this I learned about Fennel. The answer's not that important to me, the process is the main thing. |
| 2026-04-13 12:50:44 +0000 | rainbyte | (~rainbyte@181.47.219.3) rainbyte |
| 2026-04-13 12:48:54 +0000 | arandombit | (~arandombi@user/arandombit) arandombit |
| 2026-04-13 12:47:39 +0000 | rainbyte | (~rainbyte@181.47.219.3) (Read error: Connection reset by peer) |
| 2026-04-13 12:40:09 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) (Ping timeout: 248 seconds) |
| 2026-04-13 12:35:20 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) |
| 2026-04-13 12:31:01 +0000 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Quit: = "") |
| 2026-04-13 12:27:40 +0000 | <merijn> | ChatGPT |
| 2026-04-13 12:27:37 +0000 | <merijn> | fp`: You know what's unironically really good at coming up with names from a description like that? |
| 2026-04-13 12:24:17 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) (Ping timeout: 252 seconds) |
| 2026-04-13 12:18:02 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) |
| 2026-04-13 12:04:18 +0000 | arandombit | (~arandombi@user/arandombit) (Ping timeout: 244 seconds) |
| 2026-04-13 12:04:06 +0000 | oats | (~oats@user/oats) oats |
| 2026-04-13 12:03:51 +0000 | oats | (~oats@user/oats) (Read error: Connection reset by peer) |
| 2026-04-13 11:58:13 +0000 | karenw | (~karenw@user/karenw) (Client Quit) |
| 2026-04-13 11:55:45 +0000 | karenw | (~karenw@user/karenw) karenw |
| 2026-04-13 11:50:10 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) (Ping timeout: 248 seconds) |
| 2026-04-13 11:45:31 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) |
| 2026-04-13 11:39:36 +0000 | haritz | (~hrtz@user/haritz) haritz |
| 2026-04-13 11:39:36 +0000 | haritz | (~hrtz@2a01:4b00:bc2e:7000:d5af:a266:ca31:5ef8) (Changing host) |
| 2026-04-13 11:39:36 +0000 | haritz | (~hrtz@2a01:4b00:bc2e:7000:d5af:a266:ca31:5ef8) |
| 2026-04-13 11:34:51 +0000 | <alter2000> | then I'd say it's a safe bet; chances are a good chunk of your potential users are already somewhat familiar with lisp style parameter/argument threading |
| 2026-04-13 11:32:39 +0000 | <fp`> | No, I'm just doing some linear algebra, shouldn't be any concurrency in sight |
| 2026-04-13 11:32:37 +0000 | <lambdabot> | Traversable t => (s -> a -> (s, b)) -> s -> t a -> (s, t b) |
| 2026-04-13 11:32:36 +0000 | <mauke> | :t mapAccumL |
| 2026-04-13 11:32:16 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) (Ping timeout: 244 seconds) |
| 2026-04-13 11:32:13 +0000 | <lambdabot> | (a -> b -> b) -> b -> [a] -> [b] |
| 2026-04-13 11:32:13 +0000 | <mauke> | :t scanr |
| 2026-04-13 11:29:44 +0000 | <alter2000> | hmm fair point, it does but given the context it doesn't sound likely; or are you actually involving threads in your library? |
| 2026-04-13 11:28:39 +0000 | <fp`> | Yeah that seems to be the thing. Fennel calls them threading macros, so would threadedScanr make sense? I'd fear though that that sounds concurrency-related. |
| 2026-04-13 11:28:08 +0000 | CiaoSen | (~Jura@p549cbfb1.dip0.t-ipconnect.de) (Ping timeout: 244 seconds) |
| 2026-04-13 11:27:14 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) |
| 2026-04-13 11:24:33 +0000 | <alter2000> | ctx https://fennel-lang.org/reference#------and---threading-macros |
| 2026-04-13 11:24:16 +0000 | <alter2000> | would it help to take a page out of Fennel's playbook? that sounds like scanr + fennel's (->) |
| 2026-04-13 11:21:36 +0000 | <fp`> | I'd like some help naming a function. It's like scanr in that it yields recursive subresults, but it also puts those subresults into the accumulator of the folding function. I came up with arrayScanr, but I think it doesn't capture that the folding function got a change. |
| 2026-04-13 11:21:26 +0000 | arandombit | (~arandombi@user/arandombit) arandombit |
| 2026-04-13 11:21:26 +0000 | arandombit | (~arandombi@2a02:2455:8656:7100:402b:b9d0:7e1b:e24b) (Changing host) |
| 2026-04-13 11:21:26 +0000 | arandombit | (~arandombi@2a02:2455:8656:7100:402b:b9d0:7e1b:e24b) |
| 2026-04-13 11:20:13 +0000 | fp` | (~user@staff237.kora-dyn.aalto.fi) |
| 2026-04-13 11:14:49 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) (Ping timeout: 248 seconds) |
| 2026-04-13 11:08:20 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) |
| 2026-04-13 10:56:31 +0000 | slomp | (~slomp@47-158-199-90.lsan.ca.frontiernet.net) (Ping timeout: 244 seconds) |