rust-gc
compiler-team
rust-gc | compiler-team | |
---|---|---|
10 | 46 | |
913 | 380 | |
- | 1.8% | |
3.9 | 6.8 | |
7 months ago | 14 days ago | |
Rust | HTML | |
Mozilla Public 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-gc
-
loxcraft: a compiler, language server, and online playground for the Lox programming language
rust-langdev has a lot of libraries for building compilers in Rust. Perhaps you could use these to make your implementation easier, and revisit it later if you want to build things from scratch. I'd suggest logos for lexing, LALRPOP / chumsky for parsing, and rust-gc for garbage collection.
-
What would be your programming language of choice to implement a JIT compiler ?
There's nothing stopping you from doing that in Rust. See rust-gc for an example of a GC implemented in Rust. Another example is mozjs, which is Rust bindings to SpiderMonkey. The GC there is implemented in C++, but it shows how you'd structure wrapper types for GC'd pointers in Rust so that you can use them safely, even with all the "ugliness" of a browser-grade GC.
-
Spotting and Avoiding Heap Fragmentation in Rust Apps
One can have a GC as a library, https://github.com/Manishearth/rust-gc
-
Hey Rustaceans! Got a question? Ask here (7/2023)!
The ones I am aware of are gc and broom. None will be as simple to use as the one in old Rust as userland implementations don't have the benefit of first-class integrated compiler support.
-
Chris Lattner on garbage collection vs. Automatic Reference Counting (2017)
Rust has rust-gc, which is an attempt to add opt-in GC over Rust's more traditional automatic memory management. It's a neat project, but I'm not sure where it's actually being used.
-
I have programming skills! I am good at dealing with programs!
Inb4 "already exists": the question is about making it convenient, not just imlementing the behavior.
-
how hard is rust for a javascript programmer?
There is also a library implementation of garbage collection for Rust, made by someone from the Rust core team.
-
Is this the correct way to think about Rust? Correct me if I am wrong about anything.
Yep! And I'd actually fully agree those are garbage collection, there's also a crate by Manish which does """real""" garbage collection—https://github.com/Manishearth/rust-gc
-
Garbage Collection Question.
I don't know that I'd say it "works" - it's never a technique I've needed to use myself, but it's the approach taken by e.g. https://github.com/Manishearth/rust-gc
-
Microsoft Rust intro says "Rust is known to leak memory"
Anyway, I found something recent that implements "rc" but in terms of tracing: https://github.com/Manishearth/rust-gc/ . Maybe useful for projects involving graphs of objects.
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?
rfcs - RFCs for changes to Rust
libvfio-user - framework for emulating devices in userspace
unsafe-code-guidelines - Forum for discussion about what unsafe code can and can't do
llvm-mos - Port of LLVM to the MOS 6502 and related processors
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
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).
its_rusty - learning rust
namespacing-rfc - RFC for Packages as Optional Namespaces
Primes - Prime Number Projects in C#/C++/Python
cargo-show-asm - cargo subcommand showing the assembly, LLVM-IR and MIR generated for Rust code
ixy-languages - A high-speed network driver written in C, Rust, C++, Go, C#, Java, OCaml, Haskell, Swift, Javascript, and Python
libgccjit-patches - Patches awaiting review for libgccjit