rust-by-example
rfcs
rust-by-example | rfcs | |
---|---|---|
66 | 666 | |
6,760 | 5,713 | |
1.7% | 1.0% | |
8.5 | 9.8 | |
3 days ago | about 21 hours ago | |
Handlebars | Markdown | |
Apache License 2.0 | 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.
rust-by-example
- Learning Rust for project.
-
A Beginner’s Guide to the Solana Web3 Stack
Rust can feel a bit intimidating at first but once you start getting the hang of it, you will enjoy it a lot. It has a very well articulated documentation, which can be used as a good learning resource too. Some other resources for Rust include Rustlings and Rust-By-Example.
-
Jumping into Rust for the first time. Is the interactive Rust textbook, published by the CS department at Brown University, a good starting point?
Rust by Example
-
How to move to rust from c++?
Rust by Example: Collection of runnable examples, which many find useful to read
-
Rust by Example: read lines - Why is the second example more efficient?
I think something went wrong there, I can find this (merged) PR with https://github.com/rust-lang/rust-by-example/pull/1679/files that has the first example collecting into a string, (which is obv less effective). It was merged 2 weeks ago. I dont know why it isnt online yet.
-
Picking Up Rust Before C With My Goals In Mind?
I more or less went straight from The Book (see also Rust by Example) to Learning Rust With Entirely Too Many Linked Lists and code::dive conference 2014 - Scott Meyers: Cpu Caches and Why You Care and I've often seen PNGme suggested as the next step after that.
-
How do I return a value from match construct?
Context around the "rust by example" discussion from 2015: https://github.com/rust-lang/rust-by-example/issues/390
-
From High-Level to Systems Programming: A Practical Guide to Rust, Part 2
The Rust By Example website is another helpful resource for learning Rust. It provides a series of interactive examples that demonstrate how to use various Rust features and libraries.
-
How to learn Rust (for backend) ?
The book is great and was my original introduction to the language, but rustlings or Rust By Example might be more interesting for an interactive (and more self paced) approach.
-
Learning rust
Rust by Example: Rust by Example is a collection of runnable examples that cover a wide range of Rust concepts and standard libraries. It's a great way to see how Rust code works in practice.
rfcs
-
Ask HN: What April Fools jokes have you noticed this year?
RFC: Add large language models to Rust
https://github.com/rust-lang/rfcs/pull/3603
- Rust to add large language models to the standard library
-
Why does Rust choose not to provide `for` comprehensions?
Man, SO and family has really gone downhill. That top answer is absolutely terrible. In fact, if you care, you can literally look at the RFC discussion here to see the actual debate: https://github.com/rust-lang/rfcs/pull/582
Basically, `for x in y` is kind of redundant, already sorta-kinda supported by itertools, and there's also a ton of macros that sorta-kinda do it already. It would just be language bloat at this point.
Literally has nothing to do with memory management.
- Coroutines in C
-
Uv: Python Packaging in Rust
Congrats!
> Similarly, uv does not yet generate a platform-agnostic lockfile. This matches pip-tools, but differs from Poetry and PDM, making uv a better fit for projects built around the pip and pip-tools workflows.
Do you expect to make the higher level workflow independent of requirements.txt / support a platform-agnostic lockfile? Being attached to Rye makes me think "no".
Without being platform agnostic, to me this is dead-on-arrival and unable to meet the "Cargo for Python" aim.
> uv supports alternate resolution strategies. By default, uv follows the standard Python dependency resolution strategy of preferring the latest compatible version of each package. But by passing --resolution=lowest, library authors can test their packages against the lowest-compatible version of their dependencies. (This is similar to Go's Minimal version selection.)
> uv allows for resolutions against arbitrary target Python versions. While pip and pip-tools always resolve against the currently-installed Python version (generating, e.g., a Python 3.12-compatible resolution when running under Python 3.12), uv accepts a --python-version parameter, enabling you to generate, e.g., Python 3.7-compatible resolutions even when running under newer versions.
This is great to see though!
I can understand it being a flag on these lower level, directly invoked dependency resolution operations.
While you aren't onto the higher level operations yet, I think it'd be useful to see if there is any cross-ecosystem learning we can do for my MSRV RFC: https://github.com/rust-lang/rfcs/pull/3537
How are you handling pre-releases in you resolution? Unsure how much of that is specified in PEPs. Its something that Cargo is weak in today but we're slowly improving.
- RFC: Rust Has Provenance
-
The bane of my existence: Supporting both async and sync code in Rust
In the early days of Rust there was a debate about whether to support "green threads" and in doing that require runtime support. It was actually implemented and included for a time but it creates problems when trying to do library or embedded code. At the time Go for example chose to go that route, and it was both nice (goroutines are nice to write and well supported) and expensive (effectively requires GC etc). I don't remember the details but there is a Rust RFC from when they removed green threads:
https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b...
-
Why stdout is faster than stderr?
I did some more digging. By RFC 899, I believe Alex Crichton meant PR 899 in this repo:
https://github.com/rust-lang/rfcs/pull/899
Still, no real discussion of why unbuffered stderr.
- Go: What We Got Right, What We Got Wrong
-
Ask HN: What's the fastest programming language with a large standard library?
Rust has had a stable SIMD vector API[1] for a long time. But, it's architecture specific. The portable API[2] isn't stable yet, but you probably can't use the portable API for some of the more exotic uses of SIMD anyway. Indeed, that's true in .NET's case too[3].
Rust does all this SIMD too. It just isn't in the standard library. But the regex crate does it. Indeed, this is where .NET got its SIMD approach for multiple substring search from in the first place[4]. ;-)
You're right that Rust's standard library is conservatively vectorized though[5]. The main thing blocking this isn't the lack of SIMD availability. It's more about how the standard library is internally structured, and the fact that things like substring search are not actually defined in `std` directly, but rather, in `core`. There are plans to fix this[6].
[1]: https://doc.rust-lang.org/std/arch/index.html
[2]: https://doc.rust-lang.org/std/simd/index.html
[3]: https://github.com/dotnet/runtime/blob/72fae0073b35a404f03c3...
[4]: https://github.com/dotnet/runtime/pull/88394#issuecomment-16...
[5]: https://github.com/BurntSushi/memchr#why-is-the-standard-lib...
[6]: https://github.com/rust-lang/rfcs/pull/3469
What are some alternatives?
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
rust - Empowering everyone to build reliable and efficient software.
book - The Rust Programming Language
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
zero-to-production - Code for "Zero To Production In Rust", a book on API development using Rust.
crates.io - The Rust package registry
monkey - Monkey patching in Go
polonius - Defines the Rust borrow checker.
RustBooks - List of Rust books
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
easy_rust - Rust explained using easy English
rust-gc - Simple tracing (mark and sweep) garbage collector for Rust