mda.js | half edge mesh data structure in js | 3D Animation library

Probably something like the following:

The function persRec is calling itself unconditionally. Here:

It's worth noting that using Array.prototype.slice.call(arr, 0) over arr.slice() doesn't throw an error when arr isn't an array/string and arr doesn't have the slice method.

Perhaps they wanted a more robust implementation, thus using the first approach.

check this code.I hope it helps you

With vanillaJS you can simply use reduce and Map

Ramda.js functions are normal javascript functions so Function.call and Function.apply methods are available.

So the solution to your problem is to use .apply method to apply multiple arguments (that are a list):

example:

One way to do this using for loops and counting:

Native approach

You can sort by id and pick the lowest id as the first element of the desired output, then you can push the next elements by finding the next node using the attribute next_id.

The compose function accepts n parameters, and pass it to the 1st function, the result of the 1st function (which can be a function) is passed to the 2nd function (which should accept only a single param). The 2nd function is invoked with that param, and the result can be a function as well.

In your code, the result of compose (before applying the objs) should be equal to filter(R.pathEq(["test"], 3)). The function would then be applied to objs.

Case 1 - R.compose(R.filter,myPath)(3)

The myPath contains receives 3, and we get R.pathEq(["test"], 3) that is passed to R.filter to become the filter(R.pathEq(["test"], 3)) function.

Case 2 - R.compose(R.filter,myPath(3))(objs)

Calling myPath(3) is like setting R.pathEq(["test"], 3) directly. Now objs is passed to it, and the result is false. The false is passed to filter, which expects two params, and returns the partialy applied function (btw - since the predicate is false would fail).

Case 3 - R.compose(R.filter,R.pathEq)(["test"],3)(objs)

The (["test"],3) is passed to R.pathEq, which results in R.pathEq(["test"],3) which is passed to filter, and you get the same function as case 1, which is applied to objs.

Case 4 - R.compose(R.filter,R.pathEq)(["test"])(3)(objs);

The ["test"] is passed to R.pathEq, which returns a function, which is passed to R.filter(), which returns a function. However, the function now gets the number 3. Filter 3 returns an empty array, which is called on objs, and since an array is not a function, you get the error message.