News for hackers. Stuff that matters.
Re:From Stacks to Trees: A new aliasing model for Rust by bPspGiJT8Y on Monday June 12, 2023 @05:57AM (#36290897)
I do partial application in Elixir all the time. I have a function `curry/1` which takes any function and gives a curried version of it, and I have a `p` macro which introduces Scala-like "holes" (e.g. `(p Enum.map(list, _))`). The order of arguments still doesn't matter and nothing is broken or impossible because of it. I have also tweaked the (|>) macro (as well as some other operators) to support holes, so that I can "pipe" into whichever position of the call.

I think there are many more severe problems with Elixir which make it not even a remotely functional PL for me (rather, procedural + macros), but arguments order is not one of them.

Re:From Stacks to Trees: A new aliasing model for Rust by fredrikholm on Monday June 12, 2023 @07:52AM (#36292011)
I applaud your efforts, but that is a lot of work against the grain. I've yet to see a curried function in the wild outside of a handful of anonymous functions passed as HoFs.

> I think there are many more severe problems with Elixir ... but arguments order is not one of them.

Cheers, I have no dog in this game, merely expanding on what (I think) OP was alluding to.

Re:From Stacks to Trees: A new aliasing model for Rust by bPspGiJT8Y on Monday June 12, 2023 @08:35AM (#36292419)
It's definitely against the grain but also not really a lot of work. The currying function is ~3-4 lines. The macros are 5-10 lines each. As for examples of such things being used "in the wild", many use Witchcraft library which strives to give a Haskell-like experience to Elixir.

Yep, I have no dogs here either :^)