I try to bring it up whenever I can :smile:
Also I just wanna do a shout out. I've been using Ramda for a few months now and it is just glorious. Thanks to the developers/maintainers so much :pray:
For a direct function to function comparison, see: https://github.com/sanctuary-js/sanctuary/wiki/Ramda-to-Sanctuary
As you can see, sanctuary is more focused, and embraces further some of the concepts of functional programming, whereas ramda has a lot more utility functions and relaxes some of the constraints traditional FP enforces, making ramda somewhat more user friendly to folks from imperitive backgrounds
Hello all, really dumb question. How would you handle something like a socket in a composition chain. For instance, how would I do something like this but using functional composition.
Url = “localhost:8080”
connection = open_connection(url)
result = Send_data(connection, data)
raw_response = Get_response(connection)
response = parse(response)
const sendData = R.curry(send_data)(R.__,data)
const result = R.pipe(
open_connection
, sendData
, get_response
,parse
)(url);
sorry I missed some of the cases, get_response refers to Get_response and send_data refers to Send_data
I'm curious how people here generally approach debugging their Ramda code? I've found the easiest/most fluid way to be putting a breakpoint at the top of a pipe call and playing around with the code in the debug console in vscode. I've wondered if I should try Emacs since it seems to support more repl based development that I'm trying to replicate here...
I've been wondering how feasible it might be to write a little VSCode extension that would put the outputs of each line inline in faded text when you're on a breakpoint. It seems to me like it would be pretty difficult
@chughes87 I sometimes use something like this:
const log = x => (console.log(x), x)
const pipeLog = (...fns) =>
pipe(log, ...intersperse(log, fns), log)
pipeLog(inc, inc, inc)(0) // logs 0, 1, 2, 3
// also
pipe(dec, dec, log, dec)(100) // logs 98REPL: https://bit.ly/2QKz2P1
var b = pipe(add(1), tap(console.log), add(1));
b(1); // = 3 (and prints 2)
const DEBUG_MODE = true;
let debugTimestamps: { [label: string]: number }[] = [];
const debugPipe = (label: string) => <T>(input: T) => {
if (DEBUG_MODE) {
debugTimestamps = [
...debugTimestamps,
{
[label]: performance.now(),
},
];
console.log({ [label]: input });
}
return input;
}
it's basically the same thing, but allows for some recording of timestamps, and then I have a
startDebug or endDebug that basically just grabs the debugTimestamps and prints the performance numbers
The
C combinator I believe it is called
flip is very useful when you have to use other libs/apis that are not set up for easy composition with the data last format (or in cases where your data is the key name). But very handy tool in your belt, none the less
so
const fn = R.prop(R._, x) I believe?
for being easy to curry the function returned by other functions ?such as compose and pipe
how can i write this in ramda?
ramda isn't really a language, but more of a utility belt
and in that example, I don't see anything that could take advantage of ramda without seeing more context
What if we could do this:
const appendLeft = (arr) => {}