SHLL
compiler-team
Our great sponsors
SHLL | compiler-team | |
---|---|---|
3 | 45 | |
26 | 374 | |
- | 1.1% | |
9.1 | 6.5 | |
4 days ago | 13 days ago | |
Rust | HTML | |
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.
SHLL
- Is there comptime reflection in Rust proc-macro?
- Fellow Rust enthusiasts: What "sucks" about Rust?
-
How could one write a "Simple" Rust?
Working on a project with similar idea and compiler optimizations enabled https://github.com/qiujiangkun/SHLL
compiler-team
-
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 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.
-
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
- Arbitrary code execution during compile time - rust
-
Fellow Rust enthusiasts: What "sucks" about Rust?
There's already an accepted but not yet implemented proposal for supporting sandboxed build-time execution.
-
Hey Rustaceans! Got a question? Ask here (7/2023)!
For testing such code on nightly there's -Z randomize-layout flag which will deliberately change the layout of repr(Rust) types so you can notice if you were relying on something it does not guarantee.
-
Stop Comparing Rust to Old C++
...and they've accepted (though not yet implemented) a proposal to allow them to opt into being sandboxed to only consuming and producing token streams so things like #[derive(Serialize, Deserialize)] can be sandboxed and badged as such on crates.io.
-
Rust's Witchcraft
There's an accepted Major Change Proposal to run proc macros in a WebAssembly sandbox with no access to anything but the input tokens.
What are some alternatives?
libvfio-user - framework for emulating devices in userspace
llvm-mos - Port of LLVM to the MOS 6502 and related processors
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).
cargo-show-asm - cargo subcommand showing the assembly, LLVM-IR and MIR generated for Rust code
namespacing-rfc - RFC for Packages as Optional Namespaces
libgccjit-patches - Patches awaiting review for libgccjit
skyline-rs - A Rust library for modding Nintendo Switch games using Skyline
rustc_codegen_gcc - libgccjit AOT codegen for rustc
qrintf - sprintf accelerator for GCC and Clang
rustc_codegen_gcc - libgccjit AOT codegen for rustc
rust-delegate - Rust method delegation with less boilerplate
pollster - A minimal async executor that lets you block on a future