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. …an experimental RFC [1]. There is also a working implementation using procedural macros [2]. [1] https://github.com/rust-lang/rfcs/pull/2033 [2] https://github.com/alexcrichton/futures-await
    comment by tmzt · 2018-03-09 · in Writing a Microservice in Rust
  2. …with my suggestions regarding that one with particular focus on the fallible vs infallible nature: https://github.com/rust-lang/rfcs/issues/2143
  3. …the whole mess with strings. 0: https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is... 1: https://github.com/rust-lang/rfcs/issues?utf8=%E2%9C%93&q=is... 2: https://crates.io/search?q=neosmart
  4. ▲ 2
    Rust 2018 roadmap
    story by kiliancs · 2018-03-06 · 0 comments
  5. Optional parameters are tricky because of type inference. See this tracking issue: https://github.com/rust-lang/rfcs/issues/323
    comment by whyever · 2018-02-19 · in Rust things I miss in C
  6. …objectives for the language. This RFC was one of the most discussed at its time. 160 comments! https://github.com/rust-lang/rfcs/pull/560 We would have loved to say that it's always on, but that's just life. Nothing is ever perfect. Rust…
    comment by steveklabnik · 2018-02-19 · in Rust things I miss in C
  7. …most excited about the prospect of using SIMD on stable Rust, which looks to be coming this year: https://github.com/rust-lang/rfcs/pull/2325 EDIT: Also worth mentioning is that Rayon (an official Rust library providing easy data…
    comment by kibwen · 2018-02-15 · in Rust 1.24
  8. ▲ 4
    Rust RFC: Stabilize SIMD
    story by steveklabnik · 2018-02-07 · 0 comments
  9. ▲ 2
    The Rust 2018 Roadmap RFC
    story by nachtigall · 2018-01-30 · 0 comments
  10. ▲ 5
    RFC: Rust 2018 Roadmap
    story by steveklabnik · 2018-01-30 · 0 comments
  11. …to catch more classes of errors. (This is, after all, the very logic that gave us Rust.) [1]: https://github.com/rust-lang/rfcs/pull/1909 [2]: https://github.com/rust-lang/rust/issues/18806
    comment by deathanatos · 2018-01-25 · in Unsafe Zig Is Safer Than Unsafe Rust
  12. …most unfortunate. Happily there's already an accepted RFC for the design of macro modularization ( https://github.com/rust-lang/rfcs/blob/master/text/1561-macr... ) that simply makes all macros operate under the same namespacing rules as…
    comment by kibwen · 2018-01-08 · in Go’s hidden pragmas
  13. …of a rabbit-hole, but I think the whole thing is a very interesting read. It continues on here ( https://github.com/rust-lang/rfcs/issues/1447 ), and then to a repo for a Rust Memory Model specification here (…
    comment by DSMan195276 · 2017-11-25 · in Announcing Rust 1.22
  14. https://github.com/rust-lang/rfcs/blob/master/text/1598-gene... has all the gory details, reading that is probably best!
    comment by steveklabnik · 2017-11-23 · in Announcing Rust 1.22
  15. …use in the compiler [3]. [1]: http://smallcultfollowing.com/babysteps/blog/2016/11/02/asso... [2]: https://github.com/rust-lang/rfcs/pull/1598 [3]: http://smallcultfollowing.com/babysteps/blog/2017/01/26/lowe...
    comment by killercup · 2017-11-23 · in Announcing Rust 1.22
  16. …Dependent types are meant to solve exactly this class of problem. Rust has an RFC for adding these: https://github.com/rust-lang/rfcs/issues/1930
  17. …to recognize that this also has a merged RFC [3] and implementation is actively worked on[2]. [1] https://github.com/rust-lang/rfcs/pull/2133 [2] https://github.com/rust-lang/rust/pull/43690 [3] https://github.com/rust-lang/rfcs/pull/2000…
    comment by weinzierl · 2017-10-29 · in Why Rust fails hard at scientific computing
  18. …generic-array [1], built on top of typenum [2], which you could think of as a sort of polyfill. [0] https://github.com/rust-lang/rfcs/blob/master/text/2000-cons... [1] https://github.com/fizyk20/generic-array [2]…
    comment by mintplant · 2017-10-29 · in Why Rust fails hard at scientific computing
  19. Re: (3), this one: https://github.com/rust-lang/rfcs/pull/2000
  20. Re: (2), this RFC was merged: https://github.com/rust-lang/rfcs/pull/2133
  21. …of support for this in the language itself. Doesn't seem to be a lot of focus on it right now. [1]: https://github.com/rust-lang/rfcs/issues/819
    comment by dljsjr · 2017-10-20 · in Rust for real time audio analysis
  22. The box keyword isn't in stable Rust yet, and isn't even "the box keyword" anymore. https://github.com/rust-lang/rfcs/blob/master/text/1228-plac... is the latest RFC I believe, but even that I believe is changing since the latest allocator…
  23. Rust with https://github.com/rust-lang/rfcs/blob/master/text/2000-cons... should be better positioned to pay physicists real dividends than C++. Fingers crossed!
    comment by Ericson2314 · 2017-10-16 · in Why physicists still use Fortran (2015)
  24. …RFC for fallible collection allocations is now in final comment period [0]. Edit: fix link [0] https://github.com/rust-lang/rfcs/pull/2116
  25. …into the compiler and bootstrap for the first time. https://github.com/rust-lang/rust/pull/45002 https://github.com/rust-lang/rfcs/blob/1f5d3a9512ba08390a222... is the relevant historic RFC; still not yet stable. This work is what will…
  26. …find it just reassuring that people aren't rushing things. (For reference: The original impl Trait: https://github.com/rust-lang/rfcs/pull/1522 The refinement, readying it for stabilisation: https://github.com/rust-lang/rfcs/pull/1951 The…
    comment by GolDDranks · 2017-10-12 · in Rust 1.21
  27. …efforts underway to make it saner: https://withoutboats.github.io/blog/rust/2017/01/04/the-rust... https://github.com/rust-lang/rfcs/pull/2126
  28. …which generated a good argument in their favour (see also the longer comment 5 replies later): https://github.com/rust-lang/rfcs/pull/1373#issuecomment-205... Essentially it's very annoying (slash slash) for blind programmers (slash slash)…
    comment by KwanEsq · 2017-10-11 · in Block Comments Are a Bad Idea
  29. hey david, you can omit the 'static lifetime in the root directory string declarations if you want! https://github.com/rust-lang/rfcs/pull/1623
  30. They're probably referring to https://github.com/rust-lang/rfcs/issues/600 It's absolutely true that we have no plans for ABI stability in the near term.
    comment by steveklabnik · 2017-10-03 · in The Curious Case of the Longevity of C
  31. …2. Coroutines. This is the supporting technology for async/await. https://github.com/rust-lang/rfcs/blob/master/text/2033-expe... 3. 'impl Trait'. This provides a way to say, "Look, my return type implements 'Trait', but the
    comment by ekidd · 2017-09-22 · in Introduction to WebRender
  32. …, it was nearly 17%. Embedded space != kernel hacking, as I've already pointed out. [1] https://github.com/rust-lang/rfcs/commits/master
  33. ▲ 4
    A better Scala? Rust higher-kinded types RFC approved
    story by AheadOfTime295 · 2017-09-09 · 2 comments
  34. Looks like this is moving now: https://github.com/rust-lang/rfcs/pull/1615 because of recently added $XDG_BIN_HOME.
    comment by shmerl · 2017-08-31 · in Announcing Rust 1.20
  35. …years ago; it doesn't work. Well, it didn't work for Rust at least. The RFC that made this change https://github.com/rust-lang/rfcs/blob/master/text/0230-remo...
    comment by steveklabnik · 2017-08-29 · in Rust – Coroutines support merged
  36. …in the eRFC (which admittedly isn't what is linked here, but is the first link in the description, https://github.com/rust-lang/rfcs/pull/2033 ) and various threads on internals before it. > writing your own runtime. This is not a cost…
    comment by steveklabnik · 2017-08-29 · in Rust – Coroutines support merged
  37. Relevant RFC: https://github.com/rust-lang/rfcs/blob/master/text/2033-expe... This looks like a huge win for Rust. The syntax seems to follow the C# and ES async/await syntaxes. With stuff like this, I can see Rust-based webdev becoming…
    comment by pitaj · 2017-08-28 · in Rust – Coroutines support merged
  38. This is experimental so far: https://github.com/rust-lang/rfcs/pull/2033#issuecomment-309... > The key point then is that the experimental RFC is not enough to stabilize something. For that, we need a proper RFC that lays out the plan.…
    comment by computerphage · 2017-08-28 · in Rust – Coroutines support merged
  39. …of RFCs in the pipeline to help with lifetimes, including more elision. In no particular order: https://github.com/rust-lang/rfcs/pull/2115 https://github.com/rust-lang/rfcs/pull/2094 https://github.com/rust-lang/rfcs/pull/2093
    comment by steveklabnik · 2017-08-23 · in D as a Better C
  40. …Plus having nil/null as a a value of the bottom type violates some aspects of bottomness. [0] https://github.com/rust-lang/rfcs/blob/master/text/1216-bang...
    comment by the8472 · 2017-08-11 · in Typed nils in Go 2
  41. …comments about its foundations. (And for a bit more about Coq to Rust, Program extraction from Coq https://github.com/rust-lang/rfcs/issues/667 )
    comment by tanmitch · 2017-08-05 · in A formalization of category theory in Coq
  42. ▲ 156
    Rust RFC 2094: non-lexical lifetimes
    story by JoshTriplett · 2017-08-02 · 66 comments
  43. …(cf. open RFC #1935 [1]). (There was a PR on Diesel to use HLists but it's no longer pursuit.) [1]: https://github.com/rust-lang/rfcs/pull/1935
    comment by killercup · 2017-08-02 · in Grokking Diesel, Rust's ORM
  44. …There's currently an open RFC that would allow the kind of nested calls described in the blog post: https://github.com/rust-lang/rfcs/pull/2025
    comment by Aaron1011 · 2017-08-02 · in Rust: Not So Great For Codec Implementing
  45. …as your error type (as any error can be wrapped in that). And there's an RFC that's been accepted ( https://github.com/rust-lang/rfcs/blob/master/text/1937-ques... ) to allow main to return a Result, so you can use the ? operator in main,…
    comment by eridius · 2017-08-01 · in Rust: Not So Great For Codec Implementing
  46. …but it's not entirely a no-brainer as to how to implement it while keeping Rust's grammar LL(k): https://github.com/rust-lang/rfcs/issues/372
    comment by andolanra · 2017-08-01 · in Rust: Not So Great For Codec Implementing
  47. …a model of language change after the C++ model, but people are concerned that it breaks too much. https://github.com/rust-lang/rfcs/pull/2052
    comment by steveklabnik · 2017-07-28 · in Metaclasses: Thoughts on generative C++
  48. https://github.com/rust-lang/rfcs/blob/master/text/1444-unio... TL;DR: FFI with C is much harder without unions. There are smaller reasons as well.
    comment by steveklabnik · 2017-07-20 · in Announcing Rust 1.19
  49. …so there isn't much distros can do. It seems they have no intention of adding one any time soon: https://github.com/rust-lang/rfcs/issues/600 This is why system libraries are nearly always in c and not c++. The ones that aren't (Qt) have a…
  50. …ever be 100% without support from Microsoft, and a lot of work has been done, but some items on https://github.com/rust-lang/rfcs/issues/1061 feel important enough to give me pause before spending much time with Rust.