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. Note that Rust now also has the ? operator, which can be a bit easier on the eyes than try!: https://github.com/rust-lang/rfcs/blob/master/text/0243-trai... https://blog.rust-lang.org/2016/11/10/Rust-1.13.html
  2. Fair enough! :) Relevant links: https://github.com/erickt/stateful and https://github.com/rust-lang/rfcs/pull/1823
    comment by steveklabnik · 2017-01-08 · in The Piston image library is now pure Rust
  3. …imposed serious overhead elsewhere: http://stackoverflow.com/questions/29428318/why-did-rust-rem... https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b... https://aturon.github.io/blog/2016/08/11/futures/ From the third link: >…
  4. > as best I remember the history of Rust There's an RFC for that! https://github.com/rust-lang/rfcs/blob/master/text/0230-remo... (A reminder that this was written in 2014, so statements are about Rust at that time period) > I think Rust…
    comment by steveklabnik · 2017-01-08 · in The Piston image library is now pure Rust
  5. …Check out https://github.com/dpc/tokio-fiber/ for co-routines being re-envisioned on tokio, and https://github.com/rust-lang/rfcs/issues/613 acknowledges that the actor story is still a work-in-progress. I have seen no indication that…
    comment by tupshin · 2017-01-08 · in The Piston image library is now pure Rust
  6. It's a priority for this year with the ground work already completed last year: https://github.com/rust-lang/rfcs/blob/master/text/1774-road... https://blog.rust-lang.org/2016/09/08/incremental.html
    comment by a_humean · 2017-01-08 · in The Piston image library is now pure Rust
  7. …or Rustup's toolchain management, and their 2017 roadmap is pretty much entirely about tooling: https://github.com/rust-lang/rfcs/blob/master/text/1774-road...
  8. …changes to the language must undergo an RFC process, which is also coordinated via a Github repo: https://github.com/rust-lang/rfcs/ .
  9. …interest of transparency, we have made one or two small fixes so far. Specifically, I'm thinking of https://github.com/rust-lang/rfcs/pull/1214 , which was a soundness fix that went through warnings in 1.4 and became an error in 1.7. Code…
    comment by steveklabnik · 2016-12-29 · in Rust is mostly safety
  10. …with the changes. For more on how this works: https://blog.rust-lang.org/2014/10/30/Stability.html https://github.com/rust-lang/rfcs/blob/master/text/1122-lang... https://github.com/rust-lang/rfcs/blob/master/text/1105-api-... These are…
    comment by steveklabnik · 2016-12-28 · in The Resurgence of C Programming
  11. https://github.com/rust-lang/rfcs/blob/master/text/1522-cons...
    comment by steveklabnik · 2016-12-25 · in Getting Started with Tokio
  12. …nightly/stable split in Rust, but I think a big part of this problem will be solved by macros 1.1: https://github.com/rust-lang/rfcs/blob/master/text/1681-macr...
    comment by hiimnate · 2016-12-24 · in The Rust split: stable vs. nightly
  13. We're in the process of addressing discoverability of the crates.io ecosystem, which led to this RFC: https://github.com/rust-lang/rfcs/pull/1824 A quote from it: > By far, the most common attribute people said they considered in the…
    comment by steveklabnik · 2016-12-23 · in Show HN: Rocket – Web Framework for Rust
  14. …It's a combination of timing + a tiny feature. Let's take a step back. Macros 1.1 is RFC 1681: https://github.com/rust-lang/rfcs/blob/master/text/1681-macr... See the section saying "The initial implementation of librustc_macro is proposed…
    comment by steveklabnik · 2016-12-22 · in Announcing Rust 1.14
  15. …bringing the pattern matching for structs to be consistent with other uses of ".." Relevant RFC: https://github.com/rust-lang/rfcs/blob/master/text/1492-dotd...
    comment by anuragsoni · 2016-12-22 · in Announcing Rust 1.14
  16. Ah, in that case I suppose it's blocked by lack of type parametrization with integers: https://github.com/rust-lang/rfcs/issues/1038 https://github.com/ticki/rfcs/blob/pi-types/text/0000-pi-typ...
  17. In case anyone else is interested in reading it, the relevant RFC is here: https://github.com/rust-lang/rfcs/blob/master/text/1504-int1...
  18. …[1] - https://github.com/BurntSushi/rust-snappy/blob/master/src/de... [2] - https://github.com/rust-lang/rfcs/blob/master/text/1725-unal...
  19. …the effort for efficient code reuse (such as filling the gaps of lack of inheritance)? I.e. this: * https://github.com/rust-lang/rfcs/issues/349 * https://github.com/rust-lang/rust/issues/31844 Is it something coming soon, or it's pretty…
    comment by shmerl · 2016-11-10 · in Announcing Rust 1.13
  20. …(so, failure sides have to match, but success sides are flexible)? EDIT: Answering my own question: https://github.com/rust-lang/rfcs/blob/master/text/0243-trai... makes it pretty clear; the error types must be the same. Which completely…
    comment by tsuraan · 2016-11-10 · in Announcing Rust 1.13
  21. This is a better link, as it will include the discussion: https://github.com/rust-lang/rfcs/pull/1774
    comment by kalmar · 2016-10-22 · in 2017 Rust Roadmap
  22. …merged/adopted as the official 2017 roadmap. The conversation can be followed/joined/whatever here: https://github.com/rust-lang/rfcs/pull/1774
    comment by dikaiosune · 2016-10-22 · in 2017 Rust Roadmap
  23. I've been following https://github.com/rust-lang/rfcs/issues/1061 for a while. It seems that high-level pieces are there, but that certain elements useful in day-to-day software engineering still need some more time.
    comment by wbond · 2016-10-19 · in Introducing Rust Language Server
  24. As for alternate implementations, https://github.com/thepowersgang/mrustc . As for specification, https://github.com/rust-lang/rfcs/pull/1643 is what's currently happening, i.e. specifying exactly how unsafe code behaves (this is more…
    comment by Manishearth · 2016-10-05 · in The cost of forsaking C
  25. …status of any of the discussions: https://internals.rust-lang.org/t/on-native-allocations-poin... https://github.com/rust-lang/rfcs/blob/bdbe73d1be948dd925c6b...
  26. …mention that there are both an RFC [1] on adding DbC as a language feature and a library [2]. [1] https://github.com/rust-lang/rfcs/issues/1077 [2] https://github.com/nrc/libhoare
    comment by wyldfire · 2016-09-30 · in A Hoare Logic for Rust
  27. …that there is an RFC discussion for first-class support optional (or keyworded) arguments here: https://github.com/rust-lang/rfcs/issues/323
    comment by asp2insp · 2016-09-30 · in Optional arguments in Rust 1.12
  28. https://github.com/rust-lang/rfcs/issues/1626 Looks like it's to do something with the top data without the overhead of pop()+push() Edit: ninja'd
    comment by mastax · 2016-09-29 · in Announcing Rust 1.12
  29. There is a postponed issue regarding them here: https://github.com/rust-lang/rfcs/issues/811 (Edited after @steveklabnik corrected me)
    comment by untothebreach · 2016-09-29 · in Announcing Rust 1.12
  30. https://github.com/rust-lang/rfcs/blob/4b4fd5146c04c9c284094...
    comment by steveklabnik · 2016-09-14 · in A Critique of Rust's `std::collections`
  31. …example, it might be possible to split the trait into a public and a private half. (But maybe not: https://github.com/rust-lang/rfcs/blob/master/text/0136-no-p... ) I do question the wisdom of the author's design at a higher level, because…
    comment by solidsnack9000 · 2016-09-12 · in Why I’m dropping Rust
  32. …monads within the language. [1] https://doc.rust-lang.org/std/option/enum.Option.html#method... [2] https://github.com/rust-lang/rfcs/issues/324
  33. …you can read more about in a couple places: - http://aturon.github.io/blog/2015/09/28/impl-trait/ - https://github.com/rust-lang/rfcs/pull/1522 This feature allows you to return any struct that implements the trait, without having to type…
    comment by aturon · 2016-08-11 · in Zero-cost futures in Rust
  34. It's a new feature (hopefully to be merged this week). Here are the gory details: https://github.com/rust-lang/rfcs/blob/master/text/1522-cons...
    comment by pcwalton · 2016-08-11 · in Zero-cost futures in Rust
  35. …way because it's much easier to understand, but is the same thing as it would be in the real code. https://github.com/rust-lang/rfcs/blob/master/text/1522-cons... is an explanation of the feature in detail, but it boils down to "I will…
    comment by steveklabnik · 2016-08-11 · in Zero-cost futures in Rust
  36. …future you'll be able to get around that by using the `impl Trait` syntax mentioned in the post ( https://github.com/rust-lang/rfcs/pull/1522 ).
    comment by Rusky · 2016-08-11 · in Zero-cost futures in Rust
  37. …opinion, you get a /lot/ of opinions. There was still a pretty broad consensus in favor. The RFC: https://github.com/rust-lang/rfcs/pull/243 (note for anyone using 'search in page': the issue page hides hundreds of comments in the middle…
  38. And an RFC for it to become its own type recently got approved: https://github.com/rust-lang/rfcs/pull/1216 (The github thread also has a ton of good discussion about it. I learned a lot). Up until now it's been a big edge case. This makes…
  39. Rust notably has slightly weakened RAII semantics: https://github.com/rust-lang/rfcs/blob/master/text/1066-safe... tldr is that Rust does not guarantee that dtors are run
    comment by zokier · 2016-08-03 · in Rust on BBC micro:bit
  40. …first searched for just "rfc 1133" and the matches didn't really make much sense :] Rust RFC 1133: https://github.com/rust-lang/rfcs/pull/1133
    comment by m_eiman · 2016-08-02 · in Rust on BBC micro:bit
  41. …the language! The standard library metapackage would pull crates from crates.io as needed. [1]: https://github.com/rust-lang/rfcs/pull/1133
    comment by Ericson2314 · 2016-07-28 · in The Rust Platform
  42. …our goals, but we are certainly not opposed to adding support for it if there's demand. [1]: https://github.com/rust-lang/rfcs/pull/1573
    comment by erickt · 2016-07-23 · in Rust: The New LLVM
  43. …a project like this seems like it's just asking for a vulnerability that's not fixable. [1] https://github.com/rust-lang/rfcs/issues/847
  44. …off properly before it'll be treated as a serious competitor to CPP (and equally often, Go). [0]: https://github.com/rust-lang/rfcs/issues/1176
    comment by yarper · 2016-07-08 · in Announcing Rust 1.10
  45. There are two that I know of off the top of my head: Code generators/source maps: https://github.com/rust-lang/rfcs/pull/1573 Procedural macros: https://github.com/rust-lang/rfcs/pull/1566
    comment by dikaiosune · 2016-07-07 · in Announcing Rust 1.10
  46. There's some information about the design in the RFC text: https://github.com/rust-lang/rfcs/blob/master/text/1298-incr... AFAICT, the idea is to track and hash items like function signatures and bodies, map them to the object files…
    comment by dikaiosune · 2016-07-07 · in Announcing Rust 1.10
  47. …(e.g. `unwrap_or`, `try!`, etc.) but in many cases I prefer the longer form for simplicity. [1] https://github.com/rust-lang/rfcs/issues/323
    comment by Perceptes · 2016-07-04 · in Ruma, a Matrix homeserver written in Rust
  48. There's an RFC that could address the lack of type-level integers: https://github.com/rust-lang/rfcs/pull/1657
    comment by yberreby · 2016-06-25 · in Comparison between Rust and D
  49. Huh? Anyone can submit an RFC: https://github.com/rust-lang/rfcs While Mozilla may not be the best organization, the Rust team seems much more willing to listen to their users than the Firefox team.
    comment by PeCaN · 2016-06-14 · in Checked C
  50. Everything requested is already in Rust. For rationale behind current design, read RFC 1199. https://github.com/rust-lang/rfcs/blob/master/text/1199-simd... Rust SIMD support tries to be type safe, so there are some subtleties involved for…