Curry named functions

[kkirby]

If you have a named function that curries (I think that's how you'd name it?), the function isn't scoped properly.

:abc (x,y) --> x + y

Expected:

var abc;
abc = (curry$(function(x, y){
  return x + y;
}));

Actual:

(curry$(function abc(x, y){
  return x + y;
}));

[vendethiel]

it's mostly because "labels" attach to "blocks", nothing else. (a for, a function, etc). You ought to use a = --> or

~function a(b, c)
  b

for curried functions anyway ;-).

[kkirby]

I agree to use a = -->, but is this considered expected functionality? I was just reading the code and saw that you can name a function using the label syntax and saw that currying doesn't work with this. If this is expected, should the parser maybe throw an error when this is occurred?

[waynedpj]

also having an issue with creating a curried named function as suggested above ala

~function named (a, b)
  a + b

which compiles to a bound named function w/ 1.4.0 as expected

var this$ = this;
function named(a, b){
  return a + b;
}

all the other combinations i have tried (e.g. --function named, -function named) are giving compilation errors or not currying the named function.

perhaps it is not possible to create a curried named function as they are constants?

thanks.

[igl]

The problem is that you can't.
Wrapping a function statement in Javascript will make it a function expression.
Same as:

foo = :foo -->

The only fix i can think of would be to wrap the body of the function and not the declaration.