A Partial Application is a function where some or all of the arguments are packed inside, ready to go and it’s just waiting for a few more before the main function is invoked. They’re like functions that have default arguments, but are pure functions with a fixed amount of parameters.
The following article and companion video playlist will cover what a partial application is and how it can be used for a more pure function option for default arguments. It’s assumed you know what pure functions are. We’ll cover:
Continue reading “What Are Partial Applications?”
- basic function arguments
- default arguments and how order can make them harder/easier to use
- function arity
- function currying with closures and show how the parameter order is reversed compared to default arguments
- building partial applications to show how to make using default arguments pure
- creating partial applications with no arguments
In our last post, we talked about what Tacit Programming is, how it can help reduce argument count of public API functions using known concrete implementations, and how it can help shrink code size & function count for Array comprehensions and Promise chaining.
In this post, we’ll show some helpful ways to use tacit programming in data validation & composing functions together synchronously as well as an example of taking things way too far.
Continue reading “Real World Uses of Tacit Programming: Part 2 of 2”
Continue reading “Real World Uses of Tacit Programming: Part 1 of 2”
My co-worker, Jason Kaiser, created a way for Promises not to fail, called
sureThing. It has 3 benefits to your code that we’ll illustrate below including prior art in other programming languages so you know this isn’t some made-up concept.
Continue reading “Promises That Don’t Fail”