Closure #323

albertnetymk · 2016-01-26T16:13:14Z

A prerequisite for migrating to new ponyrt.

EliasC · 2016-01-26T22:21:08Z

Could you quickly clarify why this is necessary for the new ponyrt?

Can I still write programs that use functions in a higher-order fashion?

def bump(x : int) : int
  x + 1

def apply(f : int -> int, x : int) : int
  f(x)

def foo() : int
  apply(bump, 42)

albertnetymk · 2016-01-27T03:45:14Z

I believe you can. print foo(); gives me 43.

EliasC · 2016-02-04T09:50:28Z

src/runtime/closure/closure.h

+  closure_fun call;
+  void *env;
+  pony_trace_fn trace;
+};


Why does this need to be exposed to the outside?

I think I see it now. Is it to be able to make static initializations of closures?

EliasC · 2016-02-04T10:01:10Z

I like this PR, and will merge it later today!

albertnetymk · 2016-02-04T10:06:46Z

Is it to be able to make static initializations of closures?

Yes.

Closure

TobiasWrigstad added the ready for review label Jan 26, 2016

albertnetymk added 2 commits January 29, 2016 17:29

Dont use closure for global function

93db416

Use pony_alloc for closures

ad09c4f

EliasC reviewed Feb 4, 2016
View reviewed changes

EliasC added a commit that referenced this pull request Feb 4, 2016

Merge pull request #323 from albertnetymk/closure

8268742

Closure

EliasC merged commit 8268742 into parapluu:development Feb 4, 2016

EliasC removed the ready for review label Feb 4, 2016

albertnetymk deleted the closure branch February 4, 2016 14:21

Provide feedback