yosbelms / ramdascript Goto Github PK

Hi, ramdascript looks awesome.

I was curious what the correct export form?

Input:

(def x (fn []
  (console.log 'hi')))

(export x)

Expected:

var x = function () {
    return console.log('hi');
}

export default x;

Actual:

var x = function () {
    return console.log('hi');

https://yosbelms.github.io/ramdascript/#link:(def%20x%20(fn%20%5B%5D%0A%20%20(console.log%20'hi')))%0A%0A(export%20x)

It would be nice if there is a keyword for
(def hello fn [] "Hello")
like in clojure
(defn hello [] "hello")

I apologize in advance that this is not an actual issue, but more of a conversation if you are willing to entertain/have the bandwidth. I am curious about your thoughts on how one might approach adding Future (https://github.com/fluture-js/Fluture), Promise, and/or async/await support to the core language. To the novice lisper/ramdascripter, it seems like a few items might be addressed/thought through first:

• Upgrade Ramda to >= 0.24.0 where they introduced better support for Fantasy Land
• As a nice-to-have (requirement?), the ability to add other iteratee-first, data-last, curried functions libraries written in the spirit of Ramda to the core language (e.g. https://github.com/fluture-js/Fluture, https://github.com/char0n/ramda-adjunct, https://github.com/sanctuary-js/sanctuary)

If going the Future route and you added Fluture functions to the core ramdascript language, like fork (https://github.com/fluture-js/Fluture#fork), you could then do it fairly easily in ramdascript right? Something akin to:

pipe(
  map(futureProducingFunction),
  parallel(1),
  fork(console.error, console.log)
)([
  'https://example.com/api0',
  'https://example.com/api1',
  'https://example.com/api2'
]);

When I tried to compile Ramdascript to javascript with the following command:
ram compile -src server/server.ram -format none

It compiled without error however when trying to run the file it throws an error that R is not defined. This is due to the fact that the compiled file never imports the ramda library. A workaround for now is to manually add the line 'R = require('ramda') at the top of each compiled file but it's not ideal.

I think it would be useful for anyone that wants to look at this code and play with it for you to add a license file. Ramda.js itself is under the MIT License https://github.com/ramda/ramda/blob/master/LICENSE.txt so that's an option to consider - but it's your choice, of course.

Perhaps there is a way to accomplish this already that I am not seeing?