Hacker GitHub

← All repos

rust-lang/rfcs

View on GitHub ↗ ★ 6,628 Markdown

RFCs for changes to Rust

685 mentions on Hacker News by 352 people: 46 stories, 639 comments · first 2014-04-09 · latest 2026-08-22

Mentions per year 685 mentions · busiest year 2016 (105)
20082026
  1. …reason to convert to Rust to target WebAssembly when neither of them were actually released. [1]: https://github.com/rust-lang/rfcs/blob/master/text/0230-remo... [2]: https://en.wikipedia.org/wiki/WebAssembly#History
  2. …or not by the vulnerability because you don't have the exact resolved versions stored anywhere ( https://github.com/rust-lang/rfcs/pull/2801 ).
    comment by frankjr · 2024-06-11 · in Swift Static Linux SDK
  3. …exact issue. https://github.com/denoland/deno_core/blob/98b09fa4f77db1131... Anxiously waiting on https://github.com/rust-lang/rfcs/pull/3467
    comment by mmastrac · 2024-05-02 · in Rust: Box Is a Unique Type
  4. …be good to have more supported options for this tradeoff in Rust, including but not limited to https://github.com/rust-lang/rfcs/pull/3470
    comment by fl0ki · 2024-04-18 · in The Rust calling convention we deserve
  5. RFC: Add large language models to Rust https://github.com/rust-lang/rfcs/pull/3603
  6. …with a heavy runtime. Java has already a heavy runtime, so what is a smidgen more flab? Source: https://github.com/rust-lang/rfcs/blob/master/text/0230-remo...
    comment by Ygg2 · 2024-03-25 · in Why choose async/await over threads?
  7. …RFC[1] for coroutines in rust: https://doc.rust-lang.org/beta/unstable-book/language-featur... [1]: https://github.com/rust-lang/rfcs/pull/2033
    comment by Levitating · 2024-02-27 · in Coroutines in C (2000)
  8. …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…
    comment by epage · 2024-02-15 · in Uv: Python packaging in Rust
  9. ▲ 55
    RFC: Rust Has Provenance
    story by killcoder · 2024-02-01 · 18 comments
  10. …are routed through the green scheduler and/or underlying event loop and nonblocking I/O. [0]: https://github.com/rust-lang/rfcs/blob/master/text/0230-remo...
  11. …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...
  12. 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.
    comment by loeg · 2024-01-11 · in Why is stdout faster than stderr?
  13. …the green thread runtime [1] more than two years after Go had hit 1.0 [2], yet is still fine? [1]: https://github.com/rust-lang/rfcs/blob/master/text/0230-remo... [2]: https://go.dev/blog/go1
  14. …but there are two major cases that were specifically enumerated as reasons to add this API: https://github.com/rust-lang/rfcs/blob/master/text/1236-stab... > It is currently defined as undefined behavior to have a Rust program panic across…
    comment by steveklabnik · 2024-01-04 · in Go: What we got right, what we got wrong
  15. Interestingly, in Rust, we thought about doing this. "early drop" was the term folks talked about https://github.com/rust-lang/rfcs/pull/239 One big concern was that there's a lot of pre-existing unsafe code that could rely on the drop…
  16. …[5]: https://github.com/BurntSushi/memchr#why-is-the-standard-lib... [6]: https://github.com/rust-lang/rfcs/pull/3469 [7]: https://github.com/BurntSushi/rebar#summary
  17. …describes the benefits of standardizing Rust. Since she created the RFC for standardizing Rust ( https://github.com/rust-lang/rfcs/pull/3355 ) and is also on the team that is working on Rust standardization (…
    comment by thesuperbigfrog · 2023-12-18 · in Progress toward a GCC-based Rust compiler
  18. …standard: https://blog.m-ou.se/rust-standard/ https://rust-lang.github.io/rfcs/3355-rust-spec.html https://github.com/rust-lang/rfcs/pull/3355 There are many organizations and industries that will not adopt Rust until it has a standard. C,…
    comment by thesuperbigfrog · 2023-12-18 · in Progress toward a GCC-based Rust compiler
  19. …enough people wanting the value form and other pairs of method names were considered better. [1] https://github.com/rust-lang/rfcs/pull/2757 [2] https://github.com/rust-lang/rust/issues/64260
  20. …(which most Rust binaries an end-user uses should be compiled with) it just wraps [1] [2] [1] https://github.com/rust-lang/rfcs/blob/26197104b7bb9a5a35db2... [2] https://stackoverflow.com/a/60238510
    comment by abound · 2023-12-12 · in OpenBSD – pinning all system calls
  21. …people that felt frustrated by this arguably implementation-centric view that kind of lost steam: https://github.com/rust-lang/rfcs/issues/391 Intuitively, the bottom lifetime should the one that is uninhabited, which would be a lifetime…
    comment by cwzwarich · 2023-12-05 · in Common Rust Lifetime Misconceptions (2020)
  22. …that has fairly broad support that I just need to bug some people some more so we can approve it. https://github.com/rust-lang/rfcs/pull/3243
    comment by epage · 2023-10-26 · in Was Rust Worth It?
  23. …a parent crate that has sub-crates that only exist within itself. We do have an RFC for this: https://github.com/rust-lang/rfcs/pull/3452 The most complex part is the Index, figuring out how to represent it in the metadata tables we…
    comment by epage · 2023-10-26 · in Was Rust Worth It?
  24. …breaking up `std` and listing which new libraries one wants in the regular [depenencies] section. https://github.com/rust-lang/rfcs/pull/1133 Yeah definitely I haven't been wanting this for years...
  25. …(& how that's communicated out & tracked is another complaint). For example & relevant to this: https://github.com/rust-lang/rfcs/issues/816 redirected to https://github.com/rust-lang/rfcs/pull/2318 https://github.com/rust-lang/rfcs/pull/23…
    comment by vlovich123 · 2023-10-05 · in Divan: Fast and Simple Benchmarking for Rust
  26. The recently-formed testing subteam is looking to solve your exact complaint: https://github.com/rust-lang/rfcs/pull/3455
    comment by jeffparsons · 2023-10-05 · in Divan: Fast and Simple Benchmarking for Rust
  27. …to do some more thinking. [1] https://www.adaic.org/resources/add_content/standards/05rm/h... [2] https://github.com/rust-lang/rfcs/issues/671 [3] https://github.com/rust-lang/rust/pull/107606
    comment by naruhodo · 2023-10-01 · in AdaCore Announces Gnat Pro for Rust
  28. …and a web app, even if I do get frustrated with mind-numbing Async issues from time to time. 1. https://github.com/rust-lang/rfcs/pull/230 2. https://embassy.dev/
  29. See for example https://github.com/rust-lang/rust/issues/63818 and https://github.com/rust-lang/rfcs/pull/3467 Basically the problem is that async blocks/fns/generators need to create a struct that holds all the local variables within them…
  30. …going on since 2014. Note that even your link is not an accepted RFC; it's still being reviewed ( https://github.com/rust-lang/rfcs/pull/3463 )
  31. …some unergonomic workarounds. Rust is making some promising progress on unified coroutines ( https://github.com/rust-lang/rfcs/pull/2781 ), but the generator types are opaque so you can't encapsulate them in a Sized struct or allocate an…
    comment by 10000truths · 2023-07-11 · in Storing Data in Control Flow
  32. …have green threads before 1.0. You can read about the proposal and reasoning for it's removal here https://github.com/rust-lang/rfcs/blob/master/text/0230-remo... . If you'd like more info on the story around the adoption of async/await in…
    comment by tbillington · 2023-07-05 · in How to think about async/await in Rust
  33. Did you get a look at https://github.com/rust-lang/rfcs/pull/3446 at all?
  34. this forgets https://github.com/rust-lang/rfcs/pull/3127 and https://github.com/rust-lang/rust/issues/111540
    comment by transportheap · 2023-06-15 · in This Week in Rust 499
  35. …out. But there's apparently many gotchas and no one has clearly written a way around them (2). (1) https://github.com/rust-lang/rfcs/issues/493 (although the comment section is kind of unhinged and goes off on distant tangents to modular…
  36. …-lang.org/cargo/reference/workspaces.html#th... [1] https://github.com/rust-lang/cargo/pull/12069 [2] https://github.com/rust-lang/rfcs/pull/3424
  37. …a feasible design for this, but I do wish we could specify what modules are cyclic vs acyclic. [0] https://github.com/rust-lang/rfcs/pull/3424
  38. …to support them. (Note that while I'm the author, this RFC is definitely a community effort.) [1] https://github.com/rust-lang/rfcs/pull/3407
    comment by phi-go · 2023-06-05 · in The Rust I wanted had no future
  39. …in building a specification for the rust language in the project itself - here's the relevant RFC https://github.com/rust-lang/rfcs/pull/3355 (1) I am one of the managing directors of Ferrous
    comment by Xylakant · 2023-05-31 · in Rust has been forked to the Crab Language
  40. …is nice. Wish I had this in Rust. Looks like it was asked for ( https://github.com/rust-lang/rfcs/issues/1756 ) but went nowhere.
    comment by cmrdporcupine · 2023-05-29 · in C++17’s useful features for embedded systems
  41. …[1] https://blog.rust-lang.org/inside-rust/2022/10/06/governance... [2] https://github.com/rust-lang/rfcs/pull/3392
    comment by lolinder · 2023-05-28 · in Why I Left Rust
  42. …relieved that they are apparently making a significant effort at reforming their governance ( https://github.com/rust-lang/rfcs/pull/3392 ) were it not for the fact that one of the authors of that PR is the author of the post we're…
    comment by veidr · 2023-05-28 · in Why I Left Rust
  43. > Everything is done openly on https://github.com/rust-lang/rfcs But the RFCs are written and reviewed by people. And they need to have the feeling that the work they do isn't useless because the one who actually decides is somebody else…
    comment by ReleaseCandidat · 2023-05-28 · in Why I Left Rust
  44. How? Everything is done openly on https://github.com/rust-lang/rfcs I mean, I hear you. I understand what you're saying, I just don't understand how you (or others) think this is related to the technical aspects of the language.
    comment by wokwokwok · 2023-05-28 · in Why I Left Rust
  45. It is completely the answer to your question. Note that Rust does not have green threads (RFC 230: https://github.com/rust-lang/rfcs/blob/master/text/0230-remo... ), so without using the coroutine crate (which most developers don’t know…
    comment by halostatue · 2023-04-16 · in Elixir and Rust is a good mix
  46. Nitpick: Rust doesn't do tail call optimization (unless llvm decides to unprompted, iirc). https://github.com/rust-lang/rfcs/issues/2691
    comment by iudqnolq · 2023-04-07 · in WebAssembly Tail Calls
  47. …that there are different tradeoffs at play. There's an old but good discussion of the issue here https://github.com/rust-lang/rfcs/blob/master/text/1183-swap...
  48. …like auto-propagation, but it would be way better than the current state of async Rust. https://github.com/rust-lang/rfcs/issues/2327
    comment by yazaddaruvala · 2023-03-27 · in Rust's Golden Rule
  49. …WASM doesn't support guaranteed TCE yet (it's a proposal), and that's an important target for Rust. https://github.com/rust-lang/rfcs/issues/2691
  50. Rust postponed this feature in the RFC process. https://github.com/rust-lang/rfcs/pull/1615 So it's been through some official channels.
    comment by kzrdude · 2023-03-25 · in Use the XDG Base Directory Specification