nothing but a Result type
Want to see pretty graphs? Log in now!
npm install result-type
|49||downloads in the last day|
|135||downloads in the last week|
|617||downloads in the last month|
|Last Published By|
|Version||1.0.0 last updated 10 months ago|
|Keywords||result, type, spec|
|Dependents (15)||cp-r, dir-each, fs-equals, packin, read-slice, result, result-co, result-core, resultify, rm-r, serve-js, sourcegraph, untar, when-all, writefile|
Just an empty class to use as a kind of tag. If your implementing something you consider to be a "Result" you can inherit from it and enjoy nice reliable type detection via
instanceof. This would normally be too limited but in the case of Result implementations should be fine. Its probably a bad idea anyway though since module systems like npm can easily duplicate modules but fuck it lets see if it works with better package managers.
This form of type checking relies on identity. That means every module that dependends on it must load the exact same path.
$ component install jkroso/result-type
$ packin install result-type:http://github.com/jkroso/result-type/tarball/1.0.0
$ echo "good luck" && npm install result-type
then in your app: