Futures/Promises thoughts about ramdascript HOT 3 OPEN

@rockymadden The issue in this case should be to find a straightforward way to deal with method chaining.
Example: obj.method1().method2().method3()

from ramdascript.

The most common pattern to achieve methods chain in Ramda is to combine pipe and invoker
Example in RamdaScript:

(pipe
    (invoker 1 'map' futureProducingFunction)
    (invoker 1 'parallel' 1)
    (invoker 2 'fork' console.error console.log))

http://ramdajs.com/docs/#invoker

from ramdascript.

I think there is a lot of things to discuss in this thread if you are still interested.

The main idea behind RamdaScript is to use Ramda as a Lisp. So, to add another libraries to the core would mean move away from its le motif. You may notice that RamdaScript has some functions which are not part of Ramda, example: import, alter... Those are to provide interop with JS.

The translation from RamdaScript to JS is plain and straightforward because Ramda is very powerful. So, the hard work of the compiler is the semantic checker and the compilation of functions aiming JS interop to take advantage of the JavaScript ecosystem of which Sanctuary and Fluture are first class citizens.

That said, we may conclude that it is possible to take advantage of Sanctuary and/or Fluture libraries in RamdaScript, example:

(import 'sanctuary' [Just])

(console.log (Just 42))

from ramdascript.