3 ms·
Having a tiny bit of APL experience, I thought 2 was already 1 line too many, before I saw that one of the lines was essentially just an import statement. ;-)
by userbinator 4y ago
Having a tiny bit of APL experience, I thought 2 was already 1 line too many, before I saw that one of the lines was essentially just an import statement. ;-)
IMHO the APL-family languages are precisely good at things like this, where there's lots of "array processing" going on; on the other hand, typical branchy business logic or other more "mundane" algorithms tend to be a bit harder to express.
- nine_k 4y agoGPUs are all about array processing. I wonder if APL-like languages (or their variants with more verbose syntax, like numpy) make any inroads in that space.
- userbinator 4y agoYes, this is one of the more well-known ones I know that's specifically GPU-oriented: https://news.ycombinator.com/item?id=13797797 https://news.ycombinator.com/item?id=13797797
- forgotpwd16 4y agoCo-dfns is a compiler for a subset of Dyalog APL that targets GPUs. Also supposedly Futhark, a language with a compiler generating GPU code, is a good candidate to target for an APL compiler. An example APL-to-GPU pipeline is APL->apltail->tail2futhark->futhark->GPU as explained in [1]. [1]: https://futhark-lang.org/blog/2016-06-20-futhark-as-an-apl-compiler-target.html https://futhark-lang.org/blog/2016-06-20-futhark-as-an-apl-c...