ada-spark-rfcs
rayon
ada-spark-rfcs | rayon | |
---|---|---|
13 | 67 | |
58 | 10,242 | |
- | 1.6% | |
2.8 | 9.0 | |
9 days ago | 7 days ago | |
Rust | ||
- | Apache License 2.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.
ada-spark-rfcs
-
Ada news digest April 2022
Original discussion was there, I guess you can post your comments to that PR to keep the discussion in one place.
-
Is Maintaining An Ada ISO Standard Worthwhile?
I forgot where I saw it, but I do recall reading somewhere that the ARG had discussed whether a shorter revision cycle would be better or not. I wouldn't be surprised if the creation of this ( https://github.com/AdaCore/ada-spark-rfcs ) was inspired by that discussion.
-
Brett Slatkin: Why am I building a new functional programming language?
Ada might be getting pattern matching soon too:
https://github.com/AdaCore/ada-spark-rfcs/blob/master/protot...
-
Why Rust?
> I did some ADA in the past and yes, it is a nice language, but it lacks the modernity and a dynamic community like Rust. ADA did received some nice update to its specification, but, just like C++, it struggle / cannot really fit the latest innovation in programming language that easily.
I'm still learning both Ada and Rust, nevertheless I humbly disagree. The more I learn it and other "old" languages the more it looks to me like "modern" ones rediscover things that have been present in other languages for years.
The really significant difference I can see for now is that Ada is not focused so strongly on functional programming paradigm. Rust borrow checker is a strong success of course and was another significant difference, but latest SPARK got borrow checking capabilities too, AFAIK.
While Ada's open-source community is smaller, I find it as energetic and devoted to improving the ecosystem as Rust's. I have no idea about closed-source community, but in the past 4 years ArianeGroup [1], Airbus [2] and Nvidia [3] talked about choosing Ada for their high-integrity applications.
> And to be fair, it is fine. ADA is very much a "committee" language (its spec are ISO/IEC) instead of a "community" language (all the spec and rfc of Rust are on github and anyone can easily discuss them).
You can discuss Ada/SPARK RFCs here: https://github.com/AdaCore/ada-spark-rfcs . I think I once saw on Ada forum or chat that someone proposing changes to the language was simply invited to talk to people working on the standard, so it doesn't look like the language is developed in isolation or something.
> This makes it so that ADA doesn't get the attention, and the rapidity of innovation, that a language like Rust does, but ADA is mostly made for program that will need to be maintained in critical operations for decades with the code being maintainable and compilable far into the future.
I think that Ada adopted quiet quickly to standards set by Rust: lower entry barrier toolchain, compelling licensing, library distribution, RFCs, etc. And in terms of language features, in many areas it's not only on par, but ahead of competition. So you're less likely to see lots of changes, but they do happen nevertheless. I'm not saying Ada is perfect, of course. There are parts of it that other languages do better. No shame in that.
IMHO, the reason Ada is unknown to many people is a combination of its past, myths surrounding it, and general trend of people to follow trends. ;) But I currently find Ada/SPARK even more compelling option than Rust, even though I like both.
[1] https://www.facebook.com/ArianeGroup/posts/2872955946126067
- Lessons from Learning Ada in 2021
- RFC on exceptional contracts for SPARK
- [RFC] declare local variables without a declare block
-
Does ada support object methods?
There's a proposal to allow dot syntax for untagged types as well.
-
It's Ada Lovelace Day Learn the Ada Programming Language in 2021
There's also an active discussion about adding format strings to the language here: https://github.com/AdaCore/ada-spark-rfcs/pull/77
- Looking for feedback about the syntax for format strings in Ada
rayon
- Rayon: Data-race free parallelization of sequential computations in Rust
- Too Dangerous for C++
-
Which application/problem would you choose for presenting Rust to newcomers in 1h30min?
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.
-
What Are The Rust Crates You Use In Almost Every Project That They Are Practically An Extension of The Standard Library?
rayon: Async CPU runtime for parallelism.
-
Moving from Typescript and Langchain to Rust and Loops
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.
-
AreWeMegafactoryYet? I just breached simulating 1M buildings @ 60 fps (If I'm not recording, Ryzen 7 1700X 8 Core)
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
-
The Rust I Wanted Had No Future
(see https://github.com/rayon-rs/rayon/tree/master/src/iter/plumbing)
-
Parallel event iterator?
I did some very basic testing with this crate : https://crates.io/crates/rayon and it seems to work :
-
General Recommendations: Should I Use Tree-sitter as the AST for the LSP I am developing?
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.
-
python to rust migration
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.
What are some alternatives?
cortex-gnat-rts - This project contains various GNAT Ada Run Time Systems (RTSs) targeted at Cortex boards: so far, the Arduino Due, the STM32F4-series evaluation boards from STMicroelectronics, and the BBC micro:bit (v1)
crossbeam - Tools for concurrent programming in Rust
Kind - A next-gen functional language
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
falcon.py - A python implementation of the signature scheme Falcon
RxRust - The Reactive Extensions for the Rust Programming Language
ada-spark-rfcs - Platform to submit RFCs for the Ada & SPARK languages
rust-numpy - PyO3-based Rust bindings of the NumPy C-API
tokio-rayon - Mix async code with CPU-heavy thread pools using Tokio + Rayon
coroutine-rs - Coroutine Library in Rust
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
libfringe - a Rust library implementing safe, lightweight context switches, without relying on kernel services