Newest at the top
| 2025-11-02 23:04:42 +0100 | <EvanR> | where did the third star come from |
| 2025-11-02 23:04:32 +0100 | <EvanR> | an array of pointers, double** |
| 2025-11-02 23:04:17 +0100 | <EvanR> | if it was an array of double, you could pass that around using double* |
| 2025-11-02 23:03:29 +0100 | <monochrom> | It was C! What box? :) |
| 2025-11-02 23:03:17 +0100 | <EvanR> | and* |
| 2025-11-02 23:03:13 +0100 | <EvanR> | any each individual double was boxed? |
| 2025-11-02 23:01:46 +0100 | <monochrom> | Basically just because I had 2D arrays, fully dynamically allocated, and back then "double[m][n]" was not allowed for variable m,n, and I needed to pass such matrices by reference. |
| 2025-11-02 23:00:33 +0100 | <EvanR> | impressive |
| 2025-11-02 23:00:28 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-02 23:00:11 +0100 | <monochrom> | I used double*** in C a long time ago. |
| 2025-11-02 22:59:41 +0100 | <EvanR> | lol |
| 2025-11-02 22:59:29 +0100 | <darkling> | Is that what's known as a snake case variable? :) |
| 2025-11-02 22:58:55 +0100 | <EvanR> | if you find yourself using an xsss, you're now a three S haskell programmer |
| 2025-11-02 22:58:16 +0100 | <monochrom> | Yeah it's a very common convention. |
| 2025-11-02 22:57:03 +0100 | <mwnaylor> | I'd gravitated toward xss. I like getting others' opinions. |
| 2025-11-02 22:55:57 +0100 | <monochrom> | OK you already know. :) |
| 2025-11-02 22:55:39 +0100 | <monochrom> | You can use "xss" for [[a]] |
| 2025-11-02 22:54:55 +0100 | <mwnaylor> | It is an abstraction, as mapcat is a higher order function. As least for this discussion. |
| 2025-11-02 22:53:04 +0100 | jreicher | (~user@user/jreicher) jreicher |
| 2025-11-02 22:52:45 +0100 | <EvanR> | but abstract operations on any list don't get this luxury |
| 2025-11-02 22:52:30 +0100 | <EvanR> | page:pages |
| 2025-11-02 22:52:21 +0100 | <EvanR> | person:persons |
| 2025-11-02 22:52:06 +0100 | <EvanR> | if you're managing a real list of concrete things, maybe use another name |
| 2025-11-02 22:51:43 +0100 | <mwnaylor> | I wasn't planning on much Haskell code. I like some of the clean names. |
| 2025-11-02 22:51:41 +0100 | <Anarchos> | OCaml uses xss too (in seq.ml[i] files of stdlib) |
| 2025-11-02 22:51:38 +0100 | <EvanR> | xss |
| 2025-11-02 22:51:33 +0100 | <EvanR> | if you have many xs's |
| 2025-11-02 22:51:28 +0100 | <EvanR> | x is something, if you have many x's, the short name is xs |
| 2025-11-02 22:50:58 +0100 | <EvanR> | xsxs misses the point of this name |
| 2025-11-02 22:50:47 +0100 | <mwnaylor> | xss is one option I'd considered. xsxs was the other, but I think xss reads better. |
| 2025-11-02 22:50:28 +0100 | <EvanR> | though xs is already doing that |
| 2025-11-02 22:50:20 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-11-02 22:49:54 +0100 | <EvanR> | but is sure to infuriate non-haskell people reading the code |
| 2025-11-02 22:49:49 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-11-02 22:49:24 +0100 | <EvanR> | xss, indicates it's a list of lists |
| 2025-11-02 22:48:57 +0100 | <jackdk> | mwnaylor: I have seen people write example implementations of e.g. `concat :: [[a]] -> [a]` with a pattern `xs:xss`. But I haven't seen this sort of function come up in enough industrial code to notice a pattern |
| 2025-11-02 22:46:37 +0100 | AlexZenon_2 | AlexZenon |
| 2025-11-02 22:46:33 +0100 | <mwnaylor> | Don't know about Haskell, but have seen it a bit in Clojure. For practice, writing the Clojure mapcat in elisp and Common Lisp. |
| 2025-11-02 22:44:40 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-02 22:44:30 +0100 | <haskellbridge> | <loonycyborg> Does it happen often enough to have a convention? :P |
| 2025-11-02 22:44:18 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer) |
| 2025-11-02 22:44:17 +0100 | <haskellbridge> | <loonycyborg> Unless you deal with all 3 layers at the same place |
| 2025-11-02 22:43:41 +0100 | <haskellbridge> | <loonycyborg> I'd expect list of lists to mostly arise in context where x is a list, therefore list of lists would be xs |
| 2025-11-02 22:42:07 +0100 | <mwnaylor> | s/and item/an item/ |
| 2025-11-02 22:41:51 +0100 | <mwnaylor> | Been a while since I tinkered with Haskell. I remember that `x' in a generic name for and item, while `xs' names a lists. Is there a convention for list of lists? |
| 2025-11-02 22:38:35 +0100 | mwnaylor | (~user@2601:5cf:837e:2bb0:8f48:1249:bca4:3647) mwnaylor |
| 2025-11-02 22:36:00 +0100 | op_4 | (~tslil@user/op-4/x-9116473) op_4 |
| 2025-11-02 22:35:43 +0100 | ttybitnik | (~ttybitnik@user/wolper) (Quit: Fading out...) |
| 2025-11-02 22:33:47 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-11-02 22:32:43 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |