SafeCall — Call any function with any amount of arguments

[Michaohneel]

SafeCall allows you to safely call any function, regardless of the number of arguments you are passing or the parameters it expects.

This is most useful with callbacks, to which you might want to provide data via arguments.
To do this, either the callback is forced to define corresponding parameters, or the caller has to check how many arguments the callback expects.
This short function makes this easy, by checking the amount of arguments passed against the function's expected parameters.
It's nothing crazy, but it can save you some work sometimes.

GitHub

Note that this does not perform type checking, functions can still throw parameter errors if you pass them arguments of invalid types.

Everyone is free to use this in whatever way they like, as detailed at the bottom of the Read-Me file.

Thank you for reading and have a nice day :)

[swagfag]

ive read the post, ive read the code, ive read the tests, ive read the markdown, and im still not sure what the use-case for this is.

if im gonna be invoking a callback, im invoking it with precisely as many parameters as my library-code intends to provide - nothing less, nothing more. if parameter are being provided, then it stands to reason that theyre supposed to be used for something.
if the client-code doesnt care about some(or all) of the provided parameters(for whatever reason), then they should discard any parameters that they dont care about(ie lone, unnamed variadic * at the end of the parameter list). then the intent is as clear as can be

this seems like its bringing the old v1 call-anything-anytime-withanyparams behavior, so maybe it should have been more aptly named v1GarbageCall instead

essentially, having the library-code make that choice instead-of/for the client-code is inviting more potential for misuse(since ure bypassing whatever parameter checking v2 would have automatically done for u)... idk

[SandyClams]

ive read the post, ive read the code, ive read the tests, ive read the markdown, and im still not sure what the use-case for this is.

I wrote a similar function myself. In my case I have functions which accept callbacks as arguments, and the callbacks are allowed a flexible number of parameters. I found it handy to write this utility function so that I could supply my callbacks willy nilly, then have the calling function just call them with the maximum number of arguments every time, which get truncated based on how many arguments the callback formally expects. (I believe my version is literally called "TruncateArguments")

basically, JavaScript array helper functions. Maybe one callback only needs the value, next one wants the index and the array too, etc.. It's lame to account for the full argument list every time I want to pass a callback. Sometimes sloppy is nice

[Adventurer]

Very useful for a script I'm working on, thank you.