rebel-readline
scope-capture
Our great sponsors
rebel-readline | scope-capture | |
---|---|---|
4 | 9 | |
670 | 557 | |
- | - | |
0.7 | 0.0 | |
about 1 year ago | over 1 year ago | |
Clojure | Clojure | |
Eclipse Public License 1.0 | MIT License |
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.
rebel-readline
-
Poor documentation?
I use rebel as a REPL which shows docs for the current keyword when pressing Ctrl-X Ctrl-D.
-
REBL
Also, it's not to be confused with an amazing REPL library, rebel.
https://github.com/bhauman/rebel-readline
- Rebel-readline: Terminal readline library for Clojure dialects
-
Is it practical to only work off the CLI and a text editor?
Rebel readline for a nicer CLI editing capabilities, eliminating the need to copy-paste forms from your editor to the REPL.
scope-capture
-
What I Have Changed My Mind About in Software Development
Awesome tools.
Personally I can't imagine coding in clojure without scope capture
https://github.com/vvvvalvalval/scope-capture
- Automatic function argument / return value collection
- Using def within the threading macro. Is there a better way of doing this?
-
Python dataclass equivalent
I haven't tried it myself. I generally just use truss for runtime constraint checking. I use a modified version that integrates scope-capture. And malli validation for more complex cases, but I try to limit that. For me it is better to validate individual attributes as needed, vs validating an entire "type"/collection of attributes. So each function only cares about the attributes that it needs, and validates only as needed.
-
Love Clojure, challenged by discoverability
Use scope-capture to observe the actual data flowing through the system
-
Clojure unique way of debugging
Scope capture library https://github.com/vvvvalvalval/scope-capture automates this approach.
- The Clojure debbugging way with scope capture
-
Let, try and other code blocks in the REPL
Is anyone aware of any prior art along the lines of this? I've seen scope-capture but it's more about instrumenting existing programs than writing new ones interactively.
-
Data-Oriented programming and LISP
I am not advocating against the use of a compiler. I am going to illustrate how to reproduce the scope of a program and replay it in the REPL as it is done for instance in Clojure with scope-capture. In some use cases, I find this approach is simpler than using a debugger. This approach is possible only because the data is immutable.
What are some alternatives?
conjure - Interactive evaluation for Neovim (Clojure, Fennel, Janet, Racket, Hy, MIT Scheme, Guile, Python and more!)
clojure - The Clojure programming language
holy-lambda - The extraordinary simple, performant, and extensible custom AWS Lambda runtime for Clojure.
flow-storm-debugger - A debugger for Clojure and ClojureScript with some unique features.
reveal - Read Eval Visualize Loop for Clojure
hashp - A better "prn" for debugging
nrepl - A Clojure network REPL that provides a server and client, along with some common APIs of use to IDEs and other tools that may need to evaluate Clojure code in remote environments.
truss - Assertions micro-library for Clojure/Script
ClojureBoxNpp - Notepad++ patch for Clojure by "modifying config files of Lisp" or "Clojure userDefineLang".
spec-tools - Clojure(Script) tools for clojure.spec
tools.namespace - Tools for managing namespaces in Clojure
debug-repl - A Clojure debug repl as nrepl middleware