# Where is Flambda being developed?

**URL:** <https://discuss.ocaml.org/t/where-is-flambda-being-developed/532>\
**Category:** Ecosystem\
**Tags:** flambda\
**Created:** [July 11, 2017, 11:48pm UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532 "2017-07-11T23:48:12Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![bluddy](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/bluddy/32/104_2.png) [@bluddy](https://discuss.ocaml.org/u/bluddy)\
**Post date:** [July 11, 2017, 11:48pm UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532/1 "2017-07-11T23:48:12Z")

</div>

I’m following up on this comment:

> [@New category idea: Proposals](https://discuss.ocaml.org/t/new-category-idea-proposals/522/6):
>
> For example, everyone has idea on how wonderful flambda could be if only it optimized X better, and almost no one is available to invest work in actually improving flambda.

As far as I know, the Flambda development work is hidden away, or at least I haven’t been able to locate it. Last I inquired, Flambda is also being completely rewritten, making it useless to try to contribute.

Anyone know where the development is taking place?

---

<div class="post-metadata">

**Author:** ![dinosaure](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/dinosaure/32/16_2.png) [@dinosaure](https://discuss.ocaml.org/u/dinosaure)\
**Post date:** [July 12, 2017, 6:05am UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532/2 "2017-07-12T06:05:40Z")

</div>

`flambda` was actively developped by @Pierre Chambart (OCamlPro), @Mark Shinwell (Jane Street) and Damien Doligez (for the integration in the OCaml distribution). I heared too about a new version of `flambda`. If you want to follow the developpement, may be the best is to ask to @Pierre Chambart.

Then, about the choice to hidden the developpement of this part, I don’t have any opinion and information about that but may be somebody (in OCamlPro) can explain why.

---

<div class="post-metadata">

**Author:** ![lpw25](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/lpw25/32/144_2.png) [@lpw25](https://discuss.ocaml.org/u/lpw25)\
**Post date:** [July 12, 2017, 7:05am UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532/3 "2017-07-12T07:05:57Z")

</div>

I don’t normally like to do this, since it doesn’t really matter, but it keeps happening (for flambda and other OCaml projects I’ve been involved with) and it starts to grate after a while: you’ve missed me off of that list. I did less than Mark and Pierre but still more than two months of full-time work on it.

---

<div class="post-metadata">

**Author:** ![dinosaure](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/dinosaure/32/16_2.png) [@dinosaure](https://discuss.ocaml.org/u/dinosaure)\
**Post date:** [July 12, 2017, 8:00am UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532/4 "2017-07-12T08:00:46Z")

</div>

I’m apologize for this missing 🙂, I’m not close to the project and you know this project better than me - honestly, I seen Pierre, Damien and Mark worked on flambda 1 years ago, and it’s why I missed you. Again, sorry.

---

<div class="post-metadata">

**Author:** ![lpw25](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/lpw25/32/144_2.png) [@lpw25](https://discuss.ocaml.org/u/lpw25)\
**Post date:** [July 12, 2017, 9:16am UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532/5 "2017-07-12T09:16:15Z")

</div>

No worries. I just wanted to set the record straight.

---

<div class="post-metadata">

**Author:** ![bluddy](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/bluddy/32/104_2.png) [@bluddy](https://discuss.ocaml.org/u/bluddy)\
**Post date:** [July 12, 2017, 10:35pm UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532/6 "2017-07-12T22:35:32Z")

</div>

Leo, do you have any info about where the next version of Flambda can be found online?

---

<div class="post-metadata">

**Author:** ![lpw25](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/lpw25/32/144_2.png) [@lpw25](https://discuss.ocaml.org/u/lpw25)\
**Post date:** [July 13, 2017, 6:24am UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532/7 "2017-07-13T06:24:14Z")

</div>

Most of it’s probably on Mark’s github somewhere, and some of it might be on Pierre’s. But I doubt they’re pushing the work very often since there hasn’t been much need to share it.

---

<div class="post-metadata">

**Author:** ![mshinwell](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/mshinwell/32/585_2.png) [@mshinwell](https://discuss.ocaml.org/u/mshinwell)\
**Post date:** [July 13, 2017, 3:30pm UTC](https://discuss.ocaml.org/t/where-is-flambda-being-developed/532/8 "2017-07-13T15:30:33Z")

</div>

The most complete up-to-date branch for the next Flambda is the cps\_types branch here:

> **[mshinwell/ocaml](https://github.com/mshinwell/ocaml/tree/cps_types)**
>
> Read-only mirror of INRIA SVN. Contribute to mshinwell/ocaml development by creating an account on GitHub.

This is still very much a work in progress mainly by Pierre Chambart, myself and Leo White. We also have on board a couple of new developers who are being funded to work on the project: Xavier Clerc at Jane Street and Vincent Laviron at OCamlPro.

There will be efforts made going forward, from later in the summer when people are back from vacation, to be more proactive about providing information to the community as to the planned features.

The amount of design work required and current state of the project mean that we’re not really in a place where casual hacking will be productive. Once things settle down that will change. However, in the meantime, if someone suitably qualified is capable of devoting substantial time to the project, they should please get in touch with either myself or Pierre Chambart.

Everyone’s patience with this project, which is not going to make OCaml 4.06, is much appreciated. Early indications are that it will provide a step change in the optimization capabilities of the compiler.
