cargo-script-mvs
farolero
cargo-script-mvs | farolero | |
---|---|---|
9 | 16 | |
35 | 358 | |
- | - | |
5.3 | 2.4 | |
21 days ago | 13 days ago | |
Rust | Clojure | |
GNU General Public License v3.0 or later | Eclipse Public License 1.0 |
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.
cargo-script-mvs
-
This Week in Rust #497
The eRFC was intentionally light on details so the Pre-RFC / IRLO thread and the demo best reflect what we hope to accomplish which are pretty detailed as-is.
-
Rust went from side project to world’s fastest growing language
> A) is easy to write one off scripts that do a job fast, with minimal thinking and effort. I am thinking of Python and Ruby. For me I can write code with high velocity in these languages.
Once I wrap up some other projects, I plan to explore this space a little bit within Rust.
imo the biggest bang for the buck is just having good `#!` support. Probably mid-year I expect to have a Pre-RFC up for single-file cargo packages. See https://github.com/epage/cargo-script-mvs/discussions/15.
A bigger effort is a batteries included, non-zero cost stdlib. I've started writing up my thoughts at https://github.com/ergo-rs/ergo.
For more background on why I think these are important, see https://epage.github.io/blog/2021/09/learning-rust/.
Would love feedback on these ideas and other ways to make Rust easy to use without sacrificing what makes Rust it is.
-
Rust as bash scripting replacement?
This is something I'm interested. Every time I write a bash or Python script, I think "why didn't I do this in Rust?". The first barrier is in the same line as your thoughts which is why I've been investigating the various cargo-script spin-offs and working towards an MVP for a Pre-RFC.
-
Val on Programming: What makes a good REPL?
Something I've been thinking a lot about for Rust is what can and should a REPL experience be for a compiled language (ie what are reasonable compromises).
There seem to be two repls that haven't gotten much traction:
- https://github.com/google/evcxr/blob/main/evcxr_repl/README....
- https://github.com/sigmaSd/IRust
There have been little and big nits that have held me back from wanting to push these further, including
- Bad defaults (having to opt-in to panic handling)
- Command syntax feeling out of place and likely not beginner friendly
- Limits on variable preservation
- Lack of introspection (at least irust as `:type`)
So far I've been punting on wanting to improve this area by instead focusing on polishing up a rust script solution in the hopes of getting it merged: https://github.com/epage/cargo-script-mvs
-
Quick Tip: You don't need to create a new cargo project if you want to test if something works in rust
rust-script is the most up-to-date version I could find. See https://github.com/epage/cargo-script-mvs/discussions/15
-
Creating an Easy Mode for Rust
cargo-script has been forked or reimplemented several times.
-
clap with Ed Page :: Rustacean Station
cargo-script: I've done some initial analysis and recorded my thoughts on what cargo-script in Rust should look like. If people are interested in this or other individual / company on-boarding improvements, I'd love to talk!
-
When not to use Rust?
Fully agree with this though I also feel there is room for experimentation and improvement in this area. I've previously blogged on this and have started researching cargo-script. Hopefully later I'll get to my standard-adjacent library.
farolero
-
clojure from common lisp
You can use this library to get CL-style conditions and restarts in Clojure: https://github.com/IGJoshua/farolero
-
Val on Programming: What makes a good REPL?
True, the CL REPL is more useful than the Clojure REPL, but CL has a 20-30 year head start in development. Plus, Clojure was developed as a hosted language, and runs on .NET, Javascript, JVM, and even Dart (in-progress).
Since exceptions are quite deeply integrated into those platforms (as opposed to conditions), it has "bled through" to the Clojure APIs, and, in turn, REPL.
Folks have written a CL-style condition/restart library for Clojure (https://github.com/IGJoshua/farolero) too.
- IGJoshua/farolero: Thread-safe Common Lisp style conditions and restarts for Clojure(Script).
- Opinions of "brothers and sisters"...
-
How to handle errors or failed computations in clojure?
conditions/restarts are also a possibility https://github.com/IGJoshua/farolero
-
ClojureRS – Clojure interpreter implemented in Rust
Someone added conditions/restarts to Clojure: https://github.com/IGJoshua/farolero
It does allow errors to be caught by the Repl and just.hkw to handle them.
-
What are the advantages of Hy/Hissp over python bindings for CL/Clojure?
farolero
-
Clojure REPL vs. CLI: IDE Wars
This is interesting tool[1] that allows much the same with Clojure
[1]: https://github.com/IGJoshua/farolero
-
Do we have good use case based examples of usage of derive based hierarchies and multi-methods?
https://github.com/IGJoshua/farolero This uses derive hierarchies to enable general error handling.
- Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
What are some alternatives?
cargo-script - Cargo script subcommand
cloroutine - Coroutine support for clojure
rust-script - Run Rust files and expressions as scripts without any setup or compilation step.
ex - In which we deal with exceptions the clojure way
gcpp - Experimental deferred and unordered destruction library for C++
wingman - Restartable exception handling for Clojure, allowing you to recover from exceptions without unwinding the stack.
evcxr
clojure-scheme - Clojure to Scheme to C to the bare metal.
IRust - Cross Platform Rust Repl
cloture - Clojure in Common Lisp
team - CLI working group
py4cl2 - Call python from Common Lisp