typical
crater
typical | crater | |
---|---|---|
13 | 23 | |
552 | 615 | |
- | 2.3% | |
7.3 | 7.8 | |
26 days ago | about 1 month ago | |
Rust | 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.
typical
-
Typical: Data interchange with algebraic data types
Yes! We have comprehensive integration tests that run in the browser to ensure the generated code only uses browser-compatible APIs. Also, the generated code never uses reflection or dynamic code evaluation, so it works in Content Security Policy-restricted environments.
See this section of the README for more info: https://github.com/stepchowfun/typical#javascript-and-typesc...
- GitHub - stepchowfun/typical: Data interchange with algebraic data types. "can be compared to Protocol Buffers and Apache Thrift. ... emphasizing a safer programming style with non-nullable types and exhaustive pattern matching."
-
Universal type language!
Protocol Buffers is the most popular one, but there are many others such as Apache Thrift and my own Typical.
-
Syntax for defining algebraic data types
Typical uses the terms "struct" and "choice" for products and sums, respectively, although it's not a programming language.
-
Download source for all crates that depend on a specific crate?
Yeah fair. I was thinking you could scrape that page with something like scraper.
- Typical Rusty: data interchange with algebraic data types
crater
-
Semver violations are common, better tooling is the answer
yup, they reference it as an inspiration: https://github.com/rust-lang/crater
it's probably impossible to automate an entire ecosystem, and there is value to enabling a tighter integration within a project ecosystem (a subset of the language ecosystem).
-
Trip Summer ISO C++ standards meeting (Varna, Bulgaria)
Rather than hypothesising about an imagined tool you could look at the actual tool which of course is in Rust's source code repo: https://github.com/rust-lang/crater
> new proposed C++ changes - are checked against only easily and "well-known" accessible package.
Now that I have, so to say, shown you mine, lets see yours. Where is the tool to perform these checks in C++?
-
GCC 13 and the state of gccrs
The "break things" part of "move fast" is not essential, Rust cares so much about breakage they literally compile and run the tests for every crate on crates.io and github using a tool called Crater. They do this just to test changes, even for stuff thats documented to be unstable, because thats just courtesy. And tooling makes it trivial to switch between Rust versions.
-
Do one thing, and do it well, or not.
The bot's named Crater if you want to look into it more.
-
Improving Rust compile times to enable adoption of memory safety
See https://github.com/rust-lang/crater
-
Discussion about the state of neovim's plugin ecosystem
Rust compiler developers use a tool called Crater to test potentially breaking compiler changes on all crates (Rust's name for libraries) uploaded to the official repository. If plugin stability is the issue, maybe a solution along these lines would be better than merging these plugins to Neovim's core?
-
Experienced C++ users: what do you like about Rust? How would you sell it to other C++ users?
https://github.com/rust-lang/crater is the bot they use to test proposed compiler/stdlib changes against slices of the crates.io library up to and including "all of it".
-
Data-driven performance optimization with Rust and Miri
The tool you're referring to is called Crater: https://github.com/rust-lang/crater.
- GHC 9.4.2 regresses being able to do math on aarch64
-
Rust for Linux officially merged
I'm pretty certain this isn't actually true. You should look at the editions, etc. Rust also has an insane guarantee which I am certain C/C++ don't offer: It rebuilds its entire library ecosystem each time it ships to make sure nothing breaks (https://crater.rust-lang.org). I've never seen an instance were old code didn't compile on a new compiler. Rust isn't forwards compatible (new code compiles on an old compiler) of course, but what is?
What are some alternatives?
Killed by Google - Part guillotine, part graveyard for Google's doomed apps, services, and hardware.
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
rkyv - Zero-copy deserialization framework for Rust
actix-net - A collection of lower-level libraries for composable network services.
website - Official dahliaOS website
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
dhall-lang - Maintainable configuration files
AutoMapper - A convention-based object-object mapper in .NET.
rust-protobuf - Rust implementation of Google protocol buffers
rust-prehistory - historical archive of rust pre-publication development
dimensioned - Compile-time dimensional analysis for various unit systems using Rust's type system.
NUnit - NUnit Framework