rhombus-prototype VS rayon

See related post. The dot operator in Rhombus will allow a function call like expr.map(…) to be statically specialized to Some.map(expr, …) provided that expr carries sufficient static information. This isn’t possible in Racket given the lack of static information in general.

If you want to know more the best starting point is https://github.com/racket/rhombus-prototype They have discussion on the GitHub repo

Racket has the concept of binding space built on top of the scope-set model. The experiment language Rhombus makes heavy use of this for contextual bindings. Note that bindings are used for language extensions among other purposes in Racket.

The notion of “tail sequence” in general doesn’t exist in Lisp’s macro-expansion model, since Lisp macros are strictly local transformations. A “tail sequence” allows a macro to control the expansion of the whole context, which requires wrapping the whole context in another macro in Lisp’s model. This is what leads to proposals like #%local-definition in Racket. However, this notion does exist in the enforestation model, which is what the experiment language Rhombus is based on, although it’s probably not quite a Lisp ;)

Rhombus is: - just another #lang. It is built on top of the existing Racket VM and written in Racket. It interoperates with existing Racket code and uses the Racket expander. - macro extendable. Hygiene and all of the good stuff work. - being developed in the open. We meet biweekly over Zoom, and discussions also occur in GitHub Discussions.

Querying Git references for rhombus-prototype at https://github.com/racket/rhombus-prototype.git Using cached16617263581661726358301 for https://github.com/racket/rhombus-prototype.git DrRacket install: version mismatch for dependency for package: https://github.com/racket/rhombus-prototype.git mismatch packages: base (have 8.6, need 8.6.0.9)

Instead of hoping, you might consider reading the discussions to see what the developers are actually saying. Just a thought.

Do some operations with .iter() then later use rayon to parallelize. So you can show how easy is to add a dependency and how easy is to parallelize.

rayon: Async CPU runtime for parallelism.

In the quest for more efficient solutions, the ONNX runtime emerged as a beacon of performance. The decision to transition from Typescript to Rust was an unconventional yet pivotal one. Driven by Rust's robust parallel processing capabilities using Rayon and seamless integration with ONNX through the ort crate, Repo-Query unlocked a realm of unparalleled efficiency. The result? A transformation from sluggish processing to, I have to say it, blazing-fast performance.

With a lot of rayon, blood, sweat and tears I finally managed to simulate a million buildings at 60fps :) Feel free to AMA, game is Combine And Conquer

(see https://github.com/rayon-rs/rayon/tree/master/src/iter/plumbing)

I did some very basic testing with this crate : https://crates.io/crates/rayon and it seems to work :

Sequentially, generating tree-sitter AST for each file and querying for the links of each file takes around 2.3 seconds. However, I randomly remembered this crate rayon, and I decided to test it. It ended up improving the performance (just by changing 2 lines of code) to 200-300ms by parallelizing the iterators and tree-sitter queries. MAJOR.

Now if you really want to use Rust, you can rewrite only the part that are slowing down your consumer. It's easy by using Py03 and maturin. Maybe also rayon to parallelize.