rustlings-solutions-5
compiler-team
Our great sponsors
rustlings-solutions-5 | compiler-team | |
---|---|---|
26 | 46 | |
22 | 377 | |
- | 1.9% | |
0.0 | 6.5 | |
about 1 year ago | 8 days ago | |
Rust | HTML | |
- | 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.
rustlings-solutions-5
-
Give me the best Resources to learn Rust
https://doc.rust-lang.org/book/ https://github.com/rust-lang/rustlings https://doc.rust-lang.org/rust-by-example/
-
Learn WebAssembly by writing small programs
i think you've found what i'm looking for! https://github.com/rust-lang/rustlings
-
Managed to land a junior role need help!
I would recommend rustlings as a way to get used to semantics. It starts from absolute basics but it gave me a more intuitive understanding of the language.
-
Suggestions for rust beginner
go along with Rustlings https://github.com/rust-lang/rustlings
-
The Rust Programming Language has recently made it possible to compile your code to the PS Vita! This potentially mean an increase in projects released as Rust is to a certain extent easier than the C programming language. Iām excited about this!
rustlings ā Small exercises to get you used to reading & writing Rust code!
-
Testing Vlang, Rust and Zig and more!
I had finished this Udemy course, which was a bit too fast towards the end but still enjoyable, I read THE BOOK and done the Rustlings (here are my old solutions and here the new ones).
-
Fellow Rust enthusiasts: What "sucks" about Rust?
You will get used to it when you write more Rust code. Read the book, implement some exercises and watch some tutorial YT videos, everything will make sense eventually.
-
THE BOOK IS AMAZING.
Check out rustlings. Simple exercises with writing rust code, introducing new concepts along the way.
-
You don't say
There's an official "book" that you can look up online. It goes through Rust step by step, like a tutorial. Alternatively there's the rustling's course where you learn Rust by doing small exercises. I have only ever looked at the book, which is fantastic. But if you know a bit of C and some sort of class-system like in OOP or Haskell's typeclasses you can just look up the syntax when you need to, it is really easy. Also, the compiler warnings/errors usually tell you what you need to do in order to fix your error (especially for simple stuff in the beginning) so often you don't even need to google the issue.
-
I am trying to learn rust. can you give me 10 challenges please?
Rustlings might be useful to you: https://github.com/rust-lang/rustlings
compiler-team
-
The Rust Calling Convention We Deserve
> Also, why aren't we size-sorting fields already?
We are for struct/enum fields. https://camlorn.net/posts/April%202017/rust-struct-field-reo...
There's even an unstable flag to help catch incorrect assumptions about struct layout. https://github.com/rust-lang/compiler-team/issues/457
- Rust proposal for ABI for higher-level languages
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
Are you talking about https://github.com/rust-lang/compiler-team/issues/688 ? I think that issue provides a lot of interesting context for this specific improvement.
-
Progress toward a GCC-based Rust compiler
And mips64, which rustc recently dumped support for after their attempt to extort funding/resources from Loongson failed:
https://github.com/rust-lang/compiler-team/issues/648
This is the biggest problem with the LLVM mentality: they use architecture support as a means to extract support (i.e. salaried dev positions) from hardware companies.
GNU may have annoyingly-higher standards for merging changes, but once it's in there and supported they will keep it for the long haul.
-
Cargo has never frustrated me like npm or pip has. Does Cargo ever get frustrating? Does anyone ever find themselves in dependency hell?
See https://github.com/rust-lang/compiler-team/issues/688
- Rust: Drop MIPS to Tier 3
-
There is now a proposal to switch Rustc Nightly to use a parallel frontend
The work has been going on for some time now and it seems we are quite close to it being enabled as a default for nightly builds, I am super thrilled upwards of 20% faster clean builds and possibly more are on the horizon. Hope everything works out without triggering some unseen ICE. https://github.com/rust-lang/compiler-team/issues/681 Edit: If you want to discuss this feature reach out on Zulip
-
Rust 1.72.0
I'd recommend reading the MCP[1] they linked regarding the decision as well as their target tier policy [2].
They are dropping tier 1 support for Win 7 and Win 8. That means they are no longer going to guarantee that the project builds on those platforms and passes all tests via CI.
As long as it is feasible they will probably keep CI runs for those platforms and if interested parties step up and provide sufficient maintenance support, it will remain tier 2. i.e a guarantee that it builds on those platforms via CI but not necessarily that all features are supported and guaranteed via passing tests.
If interested parties can provide sufficient maintenance that all tests continue passing, it will be tier 1 in all but name. However the rest of the development community won't waste their time with issues like Win 7 and 8's partial support for UTF-8.
And once CI stops being feasible for the compiler team to host, it'll drop down to tier 3. If there's sufficient interest from the community towards maintaining these targets, in practice you should see comparable support to with tiers 1 or 2 however now any CI will be managed externally by the community and the compiler team will stop worrying about changes that could break compilation on those targets.
TLDR: They aren't saying "it'll no longer work" but rather "if you want it to stay maintained for these targets, you have to pitch in dev hours to maintain it and eventually support the infrastructure to do this because we don't see a reason to continue doing this". So if you care for these targets, you'll have to contribute to keep it maintained.
[1]: https://github.com/rust-lang/compiler-team/issues/651
- Experimental feature gate for `extern "crabi"` ABI
-
Prerequisites for a Windows XP 3D game engine
(The already broken) XP support was removed almost 3 years ago: https://github.com/rust-lang/compiler-team/issues/378
What are some alternatives?
gopherlings - šļø Learn Go by fixing tiny incorrect programs
libvfio-user - framework for emulating devices in userspace
proposals - Tracking WebAssembly proposals
llvm-mos - Port of LLVM to the MOS 6502 and related processors
linux - Linux kernel source tree
ua-parser-js - UAParser.js - Free & open-source JavaScript library to detect user's Browser, Engine, OS, CPU, and Device type/model. Runs either in browser (client-side) or node.js (server-side).
rust-typed-builder - Compile-time type-checked builder derive
namespacing-rfc - RFC for Packages as Optional Namespaces
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
cargo-show-asm - cargo subcommand showing the assembly, LLVM-IR and MIR generated for Rust code
wasmtime - A fast and secure runtime for WebAssembly
libgccjit-patches - Patches awaiting review for libgccjit