rust-semverver
wg
rust-semverver | wg | |
---|---|---|
8 | 12 | |
641 | 1,837 | |
- | 1.3% | |
1.7 | 8.1 | |
10 months ago | 11 days ago | |
Rust | ||
BSD 3-clause "New" or "Revised" License | - |
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.
rust-semverver
-
A byte string library for Rust
1) No. I think semver is just fine for its intended purpose. I mean, I'm sure its spec could be improved in various ways, but its fundamental idea seems fine to me. I think it's just important to remember that semver is a means to an end, and not an end itself. It is a tool of communication most useful in a decentralized context.
2) No.
3) See: https://github.com/rust-lang/rust-semverver --- But also, this is only ever going to be a "best effort" sort of thing. Semver isn't just about method additions or deletions, but also behavior.
-
Toward fearless `cargo update`
How does this compare to cargo-semverver?
-
Are crate versions numbers all low because Rust just works?
Found this: https://github.com/rust-lang/rust-semverver but it doesn't seem to act on git log/diffs... just FYI.
-
Implied bounds and perfect derive
Enter rust-semverver!
-
my company refuses to use rust because it changes to much
Rust type system on the other hand does not allow this. Traits are monotonic logic: adding trait-impls / most qualifiers does't influence already existing and compiling code (note: for code that doesn't rely on disambiguation to compile). There's rules that clarify this disambiguations and breaking/non-breaking changes according to the type system. There's SemVerVer to automatically verify those guidelines.
-
Would you want crates.io/cargo publish to enforce strictly correct SemVer conventions?
In my case it wasn't so bad and an easy fix was fast to write, but it got me thinking of how much of a problem this is for the wider ecosystem. Some searching showed me, that of course there is a tool rust-semverver to do exactly that. Sadly it errors on my system (or maybe im just using it wrong). Would've been interesting to see how often this actually happens on crates.io and how much of a problem this really is.
-
Semantic Versioning Will Not Save You
There's been an attempt at this for the Rust ecosystem: https://stackoverflow.com/questions/41185023/what-exactly-is...
There's also a library that attempts to automatically check sermver adherence of a crate: https://github.com/rust-lang/rust-semverver
And there has been quite a bit of effort into preventing semver requirements from fracturing the ecosystem. This revolves around the compiler working with multiple major versions of a single library: https://github.com/dtolnay/semver-trick
-
cargo-incversion, a command line utility to update Cargo.toml version
Turns out it already exists: https://github.com/rust-lang/rust-semverver
wg
-
Embedded Rust Education: 2023 Reflections & 2024 Visions
Inspired by James Munns's call, and as 2023 is coming to an end, I figure it's a good opportunity to reflect and look forward to 2024. It's been a bit over 1.5 years since I embarked on my embedded Rust journey and it's been nothing less than exciting since. So here it goes.
-
In search of Rust projects to contribute
Because you are an embedded guy. There is the https://github.com/rust-embedded/wg working-group. Rust on embedded is really on a got track forward. There are many chips/vendors that are supported both in no std / std rust world, but still there is a lot of niche things where you can actively help to be the first to get it run in Rust.
-
Rust – Are We Game Yet?
To specifically answer your question, here:
* <http://www.areweembeddedyet.com/>
It currently redirects to:
* <https://rust-embedded.org>
Which doesn't really contain anything other than a link to <https://github.com/rust-embedded>.
(via <https://github.com/rust-embedded/wg/issues/15>)
-
Google announce secure Rust-based OS for embedded system
Then the Rust Embedded workgroup provides: - Direction on how to using generics and zero-sized types to achieve functional safety - svd2rust, which provides safe abstractions to peripheral access from SVD files and achieves this functional safety - The embedded HAL spec, which makes porting to different vendors/hardware easy - Peripheral access controllers and HALs for various vendors & hardware
-
What are your guys' thoughts on Rust?
The Rust Embedded Devices Working Group curates a list of useful embedded Rust resources, including Peripheral Access Crates (autogenerated from SVD files), embedded-hal Implementation Crates (hand-written libraries implementing the traits (interfaces) specified by the embedded-hal), and Board Support Crates.
-
Question about Rust's binary size
You should also look at https://github.com/rust-embedded/wg/issues/41 and https://github.com/rust-lang/rust/pull/55011#issuecomment-429336055.
-
Things you can’t do in Rust (and what to do instead)
Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.
- Semantic Versioning Will Not Save You
- Is there a embedded community/website where it is modern?
-
Would it be possible to run Rust on the new Raspberry Pi Pico?
Most of the issues are explained in EWG RFC 419. The TL;DR is that some resources need to implement Send to be usable from interrupts, but they must not be sent across cores.
What are some alternatives?
cargo-semver-checks-action - A GitHub Action for running cargo-semver-checks
pico-examples
cargo-semver-checks - Scan your Rust crate for semver violations.
flip-link - Adds zero-cost stack overflow protection to your embedded programs
blog - My blog.
erdtree - A modern, cross-platform, multi-threaded, and general purpose filesystem and disk-usage utility that is aware of .gitignore and hidden file rules.
imgref-iter - A small crate for iterating over the rows or columns of `imgref` buffers
not-yet-awesome-embedded-rust - A collection of items that are not yet awesome in Embedded Rust
really-small-backpack-example - A really small example of the Backpack module system for Haskell
TX-2-simulator - Simulator for the pioneering TX-2 computer
rust-memchr - Optimized string search routines for Rust.
felix - 🐱 Experimental operating system written in Rust