ada-spark-rfcs
rand
ada-spark-rfcs | rand | |
---|---|---|
13 | 29 | |
58 | 1,578 | |
- | 1.1% | |
2.8 | 8.3 | |
9 days ago | 6 days ago | |
Rust | ||
- | GNU General Public License v3.0 or later |
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
rand
-
We have getrandom at home
Making compatibility promises for distributions means they cannot take advantage of potential advancements in the field.
-
Blog Post: On Random Numbers
Defining an error type that is meaningful, portable, and compatible with no-std isn't straightforward. If the std lib's getrandom requires std, then just like that, rand and many other crates won't use it anyway. Using io::Result seems to me to face this challenge.
-
Hey Rustaceans! Got a question? Ask here (52/2022)!
Some wasm targets can’t generate random numbers at all but in the case of the book because you are using wasm in a browser you can use JS to generate random numbers. I believe there’s a way to get the rand crate to use JS as the backend for generating rand but its a bit more convoluted than the easy one-liner that the book suggests.
- Data-driven performance optimization with Rust and Miri
-
What crates are considered as de-facto standard?
rand
- Why Rust?
-
[Media] Nebulabrot rendered with Rust — Explanations in the comments
This uses rand and xcomplex to handle the mathematics, png to write image files, and dialoguer and indicatif for some pretty prompts and progress bars.
-
Do you ever use unsafe { .. } when not implementing custom data structures or interacting with external C code?
You can often achieve this without any unsafe by putting an assert!() on the length before the hot loop. For example, I got rid of some unsafe in rand that way.
-
Original source of `(seed * 9301 and 49297) % 233280` random algorithm?
This is a widely used method to map random integers to floating point numbers, but it has the disadvantage of wasting 1 bit of float mantissa precision.
On modern CPUs, its computational advantage over full-precision mapping methods, such as multiplication by a float, is not always clear [1].
[1] https://github.com/rust-random/rand/issues/416
-
Any plans for built-in support of Vec2/Vec3/Vec4 in Rust?
In fact, there are a lot of crates in Rust where in other programming languages, it would be included in the standard library. Examples are regex, random number generators, additional iterator methods, macros for other collections, num traits, loggers, HTTP libraries, error handling, async runtimes, serialization and deserialization, date and time, and many more.
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)
fastrand - A simple and fast random number generator
Kind - A next-gen functional language
fast-float-rust - Super-fast float parser in Rust (now part of Rust core)
falcon.py - A python implementation of the signature scheme Falcon
winapi-rs - Rust bindings to Windows API
ada-spark-rfcs - Platform to submit RFCs for the Ada & SPARK languages
yew - Rust / Wasm framework for creating reliable and efficient web applications
cargo-fuzz - Command line helpers for fuzzing
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266
log - Logging implementation for Rust
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.