easy_rust
rfcs
Our great sponsors
easy_rust | rfcs | |
---|---|---|
21 | 666 | |
7,815 | 5,700 | |
- | 1.4% | |
0.0 | 9.8 | |
over 1 year ago | 2 days ago | |
Shell | Markdown | |
MIT License | 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.
easy_rust
-
Stuck at 4.3 of the rust book. It's so hard for me.
There's also Easy Rust, an effort in translating the Rust Book into Simple English (limited vocabulary, limited use of idioms), which has now become a Book.
-
Easy Rust has been reborn on Manning as Learn Rust in a Month of Lunches
Up on Manning starting this week is a book I wrote / am writing called Learn Rust in a Month of Lunches, whose origins date back to Easy Rust that people here might be familiar with and which I wrote 2 years ago. The first six chapters are now up on MEAP which is pretty exciting. (The code mlmacleod gives 45% off until February 2 btw)
-
Anything C can do Rust can do Better
Easy Rust - David MacLeod
-
I have returned
Along with the Book, I wrote a book after learning Rust that's for absolute beginners, and doesn't even require installing Rust. It's almost entirely done in the Playground so you can just open up a tab in your browser and follow along. As far as paid books are concerned, my favourite is Programming Rust.
-
So you want to learn Rust?
Easy Rust OR GH Page
-
What is the best course to start learning?
I made a book for absolute complete beginners, after which the Book should be easy to understand. After that I'd recommend Programming Rust (my favourite book on Rust).
-
Newbie here. Just finished reading the book. What now?
https://github.com/Dhghomon/easy_rust The book
-
Rust course
Depends on what language you come from. I found this a decent enough intro for most languages: https://github.com/Dhghomon/easy_rust
-
I have to admit. The free code camp course is a bit more sparing than I would have preferred. How did everyone learn Rust?
This is my favorite: https://github.com/Dhghomon/easy_rust
-
It's been 20 days since I started learning rust as my first language. Terrible experience. Should I move forward?
I put together a book that goes over most of the same content found in The Book but written with easy / straightforward English (partially for English L2 speakers but also for English speakers that just want the info in as straightforward a package as possible).
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?
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
rust - Empowering everyone to build reliable and efficient software.
rust-by-example - Learn Rust with examples (Live code editor included)
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
crates.io - The Rust package registry
Rust-Full-Stack - Rust projects here are easy to use. There are blog posts for them also.
polonius - Defines the Rust borrow checker.
Exercism - website - The codebase for Exercism's website.
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
tour_of_rust - A tour of rust's language features
rust-gc - Simple tracing (mark and sweep) garbage collector for Rust