I've wanted something like this for quite a long time. I've spent quite a bit of time trying to grok OCaml, Haskell, and Lisp syntaxes, and I've never gotten to the point where I "see past the syntax". Even if you like these languages and their syntaxes, you should be excited about projects like these which help to bridge the cognitive gap between mainstream imperative languages and functional languages--more people getting exposure to functional ideas is a good thing for you--learning syntax and functional concepts in tandem is more difficult than the sum of the constituent parts.
EDIT: Sadly, this project hasn't been touched in 2 months.
If you like his stuff, I've been working through a book he wrote about implementing scheme, which has been very helpful in understanding the why's of lisp.
I have! Sadly it’s native compilation story was pretty poor last I checked. Mostly it seemed like the primary target was bucklescript. There were other issues as well.
Of particular interest in this language is the "then" and "back" syntax [0]. It looks like a somewhat different take on iterators, which I can see being more "readable" in certain situations. I haven't had a chance to try it out, but it seems like it may allow for some interesting behaviors.
It feels something like a generator that has been hoisted up into the language so that it acts like a single value (which defaults to the first element in the generator).
It is just call/cc from scheme. Here calls a function with the current continuation which means you can either do an early return, like the example where they "replace" the current continuation with the value 3.
In scheme you can save that continuation and return to it as many times as you want, which people from other languages have a hard time to wrap their head around. I'm rather sad that they chose to implement undelimited continuations, since that is almost never what you want.
First class continuations are a fantastic tool in your language. They can be used to implement coroutines, fibers, nondeterminism and so on. Really no surprise that they are a part of scheme, which usually pick a few well thought out primitives that combine into nice high level abstractions.
17 comments
[ 4.9 ms ] story [ 36.4 ms ] threadEDIT: Sadly, this project hasn't been touched in 2 months.
http://billhails.net/Book/front.html
Also interops with JS (and has superb bindings for React) so immediate results/learning are very easy to get.
[1] - https://reasonml.github.io
The messenger people don't know what to do about that either, really.
I really like the language though so it's a shame.
But the real zen of Fable is using fable-elmish, which is a UI library that (like Elm) focuses on message passing. It's super elegant.
Good sample app doing nontrivial stuff: https://github.com/SAFE-Stack/SAFE-Chat
(Bonus is that it's full-stack F# :))
define y = 12;
but the following one does not:
define fn(x) = { ... }
[0]: https://github.com/billhails/PyScheme/wiki/Then-and-Back
The example warped my brain a little.
In scheme you can save that continuation and return to it as many times as you want, which people from other languages have a hard time to wrap their head around. I'm rather sad that they chose to implement undelimited continuations, since that is almost never what you want.
First class continuations are a fantastic tool in your language. They can be used to implement coroutines, fibers, nondeterminism and so on. Really no surprise that they are a part of scheme, which usually pick a few well thought out primitives that combine into nice high level abstractions.