| /** | |
| @func | |
| log how long it takes to run a block of code | |
| - for a supplied number of times | |
| @warning | |
| the supplied func runs in a loop | |
| - so first make sure there are no log statements in the func | |
| - either comment them out, or replace them with lMock... | |
| - const l = s => undefined; //lMock |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
This section describes the conventions used here to describe type signatures.
A [T] is an array-like value (only ever used read-only in this API), i.e., one with an integer length and whose indexed properties from 0 to length - 1 are of type T.
A type T? should be read as T | undefined -- that is, an optional value that may be undefined.
| ### | |
| Allow the user to download a file or a directory as a _.tar.gz_ | |
| compressed version. | |
| ### | |
| fs = require "fs" | |
| {exec} = require "child_process" | |
| {resolve} = require "path" | |
| # `callback` receives `(tarPath)` |