Curry named functions

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;
}));

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 ;-).

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?

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.

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.

Throw compile-time error if a label is used with a curried function (r…

Navigation Menu

Repository navigation

Curry named functions #751

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Curry named functions #751

Description

Activity

vendethiel commented on Jul 9, 2015

kkirby commented on Jul 9, 2015

waynedpj commented on Sep 18, 2015

igl commented on Sep 19, 2015

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions