Newest at the top
| 2025-03-26 14:41:09 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 244 seconds) |
| 2025-03-26 14:36:15 +0100 | j0lol | (~j0lol@132.145.17.236) j0lol |
| 2025-03-26 14:36:01 +0100 | j0lol | (~j0lol@132.145.17.236) (Remote host closed the connection) |
| 2025-03-26 14:35:45 +0100 | haritz | saimazoon |
| 2025-03-26 14:32:18 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-03-26 14:30:48 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 245 seconds) |
| 2025-03-26 14:30:45 +0100 | ethantwardy | (user@user/ethantwardy) ethantwardy |
| 2025-03-26 14:30:20 +0100 | ethantwardy | (user@user/ethantwardy) (Remote host closed the connection) |
| 2025-03-26 14:23:40 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 268 seconds) |
| 2025-03-26 14:18:51 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-26 14:18:03 +0100 | <tomsmeding> | that's helpful, I guess, but indeed orthogonal |
| 2025-03-26 14:17:54 +0100 | <tomsmeding> | ah I see |
| 2025-03-26 14:17:51 +0100 | <Athas> | Yes. |
| 2025-03-26 14:17:39 +0100 | <tomsmeding> | automatic broadcasting, in the style of Futhark AutoMap? |
| 2025-03-26 14:17:23 +0100 | <Athas> | tomsmeding: broadcasting/replication is the *only* thing Naperian functors provide. |
| 2025-03-26 14:14:33 +0100 | <tomsmeding> | s/now/how/ |
| 2025-03-26 14:14:18 +0100 | <tomsmeding> | Because I don't see now those Naperian functors help very much there, per se, but I'm probably missing something |
| 2025-03-26 14:13:57 +0100 | <tomsmeding> | Bowuigi: do you have an example of such "APL-style"? |
| 2025-03-26 14:09:26 +0100 | <haskellbridge> | <Bowuigi> tomsmeding the actually useful generality is being able to operate on matrices/tensors of different dimensions APL-style, but I understand your point |
| 2025-03-26 14:07:40 +0100 | <haskellbridge> | <Bowuigi> I see, those papers are more about the API I guess |
| 2025-03-26 14:05:46 +0100 | jespada | (~jespada@2800:a4:2211:7600:7570:cffe:6554:643e) jespada |
| 2025-03-26 14:04:20 +0100 | ljdarj | (~Thunderbi@user/ljdarj) ljdarj |
| 2025-03-26 14:04:08 +0100 | Square | (~Square@user/square) (Ping timeout: 245 seconds) |
| 2025-03-26 14:02:11 +0100 | j1n37- | (~j1n37@user/j1n37) (Ping timeout: 244 seconds) |
| 2025-03-26 14:02:08 +0100 | yangby | (~secret@115.205.72.232) (Quit: Go out for a walk and buy a drink.) |
| 2025-03-26 14:01:15 +0100 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-03-26 13:59:30 +0100 | Square | (~Square@user/square) Square |
| 2025-03-26 13:56:53 +0100 | akegalj | (~akegalj@89-172-183-68.adsl.net.t-com.hr) (Ping timeout: 248 seconds) |
| 2025-03-26 13:52:09 +0100 | zungi | (~tory@user/andrewchawk) andrewchawk |
| 2025-03-26 13:45:12 +0100 | zungi | (~tory@user/andrewchawk) (Ping timeout: 264 seconds) |
| 2025-03-26 13:44:10 +0100 | tabaqui | (~tabaqui@167.71.80.236) tabaqui |
| 2025-03-26 13:43:02 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-03-26 13:42:33 +0100 | Putonlalla | (~Putonlall@it-cyan.it.jyu.fi) (Ping timeout: 252 seconds) |
| 2025-03-26 13:41:54 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 248 seconds) |
| 2025-03-26 13:41:46 +0100 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) (Client Quit) |
| 2025-03-26 13:40:00 +0100 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) |
| 2025-03-26 13:39:04 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) |
| 2025-03-26 13:38:53 +0100 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) (Quit: Client closed) |
| 2025-03-26 13:37:01 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-03-26 13:36:48 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) (Ping timeout: 268 seconds) |
| 2025-03-26 13:36:48 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 246 seconds) |
| 2025-03-26 13:35:20 +0100 | <Athas> | Bowuigi: not directly, they are an orthogonal issue. And they certainly have somewhat bad error messages, even with the tricks Jeremy pulls in that paper. |
| 2025-03-26 13:34:41 +0100 | <tomsmeding> | note that the Acc-nap.pdf link also cheats with OverloadedLists in section 3 |
| 2025-03-26 13:33:08 +0100 | <tomsmeding> | but as we're talking about a user-facing API here, and I don't think users will ever need to be polymorphic over arrays and tuples in numeric code, I'm not sure that particular generality is very valuable here |
| 2025-03-26 13:32:28 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-26 13:32:05 +0100 | <tomsmeding> | I guess it also allows putting tuples on the same footing as vectors |
| 2025-03-26 13:31:26 +0100 | <tomsmeding> | Bowuigi: looking at that first link, and reading section 1.3 plus the definition of Naperian at the bottom of page 9, it seems to me that this is "just" saying "make your API nested single-dimensional arrays"? |
| 2025-03-26 13:26:39 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 276 seconds) |
| 2025-03-26 13:23:30 +0100 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) |
| 2025-03-26 13:22:13 +0100 | alp | (~alp@2001:861:8ca0:4940:dd1f:b4e6:4fbb:e5d8) (Ping timeout: 248 seconds) |