Pull requests are welcomed, but please follow our code style guide below:
- Use actual tab character instead of spaces
- Please use Java or Kotlin as a development language
- Functional collection APIs are prefered.
- Results of functions should be lazy evaluation.
- Use symbols like
-\>,?to representto,orNot. It's clearer. - Use Lisp-style function names.
Example:
; good
(int->str 1)
; bad
(intToStr 1)
; good
(null? ())
; bad
(nullOrNot ())