whirlisp
excoptional
whirlisp | excoptional | |
---|---|---|
5 | 5 | |
17 | 11 | |
- | - | |
4.9 | 0.0 | |
about 3 years ago | over 2 years ago | |
Common Lisp | HTML | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
whirlisp
-
Understanding the Power of Lisp (2020)
I wrote this to try and show how that could happen in a realistic enough way to make sense:
https://github.com/codr7/whirlisp
- Why Lisp?
- Show HN: A Whirlwind Lisp Adventure
excoptional
-
From ES6 to Scala: Basics
> I mean Scala because I guess it actually has it, but worth pointing out it's like 30 LOC to define one for JS, depending on how many convenience methods you want.
Here's one I wrote: https://github.com/sbernheim4/excoptional
I fully believe it to be one of the best Option implementations in JS/TS
- Understanding the Power of Lisp (2020)
-
[AskJS] How often do you use the ES6+(ES7, ES8, ES9 and ES10) syntax? Do you like it? Does it help?
https://github.com/sbernheim4/excoptional is an option object for js/ts
-
Functors, Applicatives, and Monads in Pictures
One benefit to keeping your value wrapped in a Maybe is that as you transform and manipulate the value and pass it around in your system, you leave it up to the last place in your system that uses the value to define the fallback value in the case of a None rather than defining a fallback value part way through and establish a convention that the fallback value means nothing was found at some other part of your system.
Another benefit to using Maybes is that you avoid the rigamarole of null checks at every call site where you want to use the value. If you have a function that returns null or a value, whenever you call that function you'll always have to add an if guard to validate it's not null. If it is, that function itself may return null, and callers to it will again have to implement the same check.
I wrote a JS implementation of the Option object and the readme has lots of specific examples about these benefits: https://github.com/sbernheim4/excoptional
- Show HN: An Option Object for JavaScript and TypeScript
What are some alternatives?
SICL - A fresh implementation of Common Lisp
sicp - HTML5/EPUB3 version of SICP
cafe-latte - An implementation of Common Lisp dynamic variables, control flow operators, and condition system in plain Java.
Chimney - Scala library for boilerplate-free, type-safe data transformations
diode - Scala library for managing immutable application model
gophernotes - The Go kernel for Jupyter notebooks and nteract.
mostly-adequate-guide - Mostly adequate guide to FP (in javascript)
oh - A new Unix shell.
tyrian - Elm-inspired Scala UI library.
circle - The compiler is available for download. Get it!
Converter - Typescript to Scala.js converter