Newest at the top
2025-03-19 21:38:23 +0100 | <[exa]> | this above is the first attempt because I want a few computers to talk to each other about what they compute and I don't see myself debugging this without usable types |
2025-03-19 21:38:03 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
2025-03-19 21:37:49 +0100 | <[exa]> | like, for numerical things I still just go to julia |
2025-03-19 21:37:24 +0100 | <[exa]> | that would be great tbh |
2025-03-19 21:35:20 +0100 | <tomsmeding> | I'm hacking on something that can be seen as a competitor to hmatrix, but it's not stable enough yet |
2025-03-19 21:35:05 +0100 | wootehfoot | (~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer) |
2025-03-19 21:34:32 +0100 | <tomsmeding> | to get around the fact that GHC is not good at compiling fast numerical code |
2025-03-19 21:34:24 +0100 | euleritian | (~euleritia@95.90.214.149) |
2025-03-19 21:33:53 +0100 | <tomsmeding> | accelerate retains the higher-order array operations (SOACs, in the lingo in the field) but ceases being a "normal" library, being a deeply embedded DSL instead |
2025-03-19 21:33:12 +0100 | <tomsmeding> | hmatrix does that |
2025-03-19 21:33:05 +0100 | <tomsmeding> | first-order operations like sum, add-two-arrays-elementwise, multiply-two-arrays-elementwise, etc. can be fast just fine by writing and FFI'ing in some C code |
2025-03-19 21:32:35 +0100 | <tomsmeding> | any array library in haskell with higher-order operations like map/fold/scan/etc. will not be super-fast |
2025-03-19 21:31:40 +0100 | <tomsmeding> | those remarks about vectorisation apply just as well to massiv |
2025-03-19 21:31:10 +0100 | <[exa]> | yes they're on this trac thing, not github |
2025-03-19 21:31:08 +0100 | <tomsmeding> | with 3.4 being the main branch |
2025-03-19 21:30:58 +0100 | <tomsmeding> | that 4.1.0.1 release on github was an experiment, apparently |
2025-03-19 21:30:48 +0100 | <tomsmeding> | it seems maintained with a new release just a few months ago |
2025-03-19 21:30:36 +0100 | <tomsmeding> | I don't think this is a reason to move from repa though, however many others there may be |
2025-03-19 21:30:16 +0100 | <[exa]> | I'm confused all the way to massiv now |
2025-03-19 21:30:08 +0100 | <tomsmeding> | right |
2025-03-19 21:29:27 +0100 | <tomsmeding> | ok those github releases just make no sense, perhaps? |
2025-03-19 21:29:17 +0100 | <[exa]> | https://groups.google.com/g/haskell-repa/c/ULjCQC8nJL8 |
2025-03-19 21:29:15 +0100 | <[exa]> | well |
2025-03-19 21:28:47 +0100 | <tomsmeding> | this is highly confusing |
2025-03-19 21:28:46 +0100 | <[exa]> | didn't look to me like that but maybe 3.4 is newer than 4.1 because of some versioning LTS strategy or what |
2025-03-19 21:28:38 +0100 | <tomsmeding> | wait |
2025-03-19 21:28:36 +0100 | <tomsmeding> | oh |
2025-03-19 21:28:12 +0100 | <tomsmeding> | isn't it hackage that has the new versions? |
2025-03-19 21:28:06 +0100 | <tomsmeding> | uh |
2025-03-19 21:27:58 +0100 | <[exa]> | nah more like they didn't release on hackage |
2025-03-19 21:27:41 +0100 | <tomsmeding> | perhaps they didn't create github tags for the releases? |
2025-03-19 21:27:37 +0100 | [exa] | confused |
2025-03-19 21:27:06 +0100 | <[exa]> | tomsmeding: looks a bit weird there, github says last release 4.1.0.1 in 2015, hackage has 3.4.2.0 as latest |
2025-03-19 21:23:45 +0100 | euleritian | (~euleritia@ip5f5ad695.dynamic.kabel-deutschland.de) (Ping timeout: 248 seconds) |
2025-03-19 21:21:36 +0100 | dhil | (~dhil@2a0c:b381:52e:3600:e6af:ac8c:7aa:72f4) (Ping timeout: 246 seconds) |
2025-03-19 21:20:51 +0100 | <tomsmeding> | wait a sec repa has updates? TIL |
2025-03-19 21:20:06 +0100 | <tomsmeding> | not sure it _matters_ so much if it works |
2025-03-19 21:19:55 +0100 | <tomsmeding> | repa is definitely not being actively maintained |
2025-03-19 21:18:47 +0100 | <[exa]> | ok good, sold, thanks! |
2025-03-19 21:18:39 +0100 | <[exa]> | yeah all searches basically say "a little richer and more maintained" |
2025-03-19 21:17:28 +0100 | TheCoffeMaker_ | (~TheCoffeM@186.136.173.70) (Ping timeout: 245 seconds) |
2025-03-19 21:17:15 +0100 | <tomsmeding> | [exa]: massiv seems to have a few more representation types? |
2025-03-19 21:17:06 +0100 | <EvanR> | I see, it's not any old type |
2025-03-19 21:16:45 +0100 | <tomsmeding> | probably in the details there are differences |
2025-03-19 21:16:40 +0100 | <tomsmeding> | they look similar to me too |
2025-03-19 21:16:32 +0100 | <[exa]> | tomsmeding: ok I rechecked the massiv guide just now and now I can't really tell whats the main difference between the packages :D |
2025-03-19 21:16:10 +0100 | <tomsmeding> | [exa]: I see! |
2025-03-19 21:15:44 +0100 | <tomsmeding> | that b is the type of variable references |
2025-03-19 21:15:35 +0100 | <tomsmeding> | EvanR: look at `type CoreExpr = Expr CoreBndr` |
2025-03-19 21:07:37 +0100 | sprotte24 | (~sprotte24@p200300d16f414f00d95fa8d2f58ba4f5.dip0.t-ipconnect.de) |