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. …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
  2. …, it was nearly 17%. Embedded space != kernel hacking, as I've already pointed out. [1] https://github.com/rust-lang/rfcs/commits/master
  3. 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
  4. …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
  5. …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
  6. 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
  7. 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
  8. …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
  9. …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
  10. …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
  11. …(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
  12. …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
  13. …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
  14. …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
  15. …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++
  16. 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
  17. …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…
  18. …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.
  19. …Please correct me if I'm wrong here (a blog post does not qualify as a specification). Relevant: https://github.com/rust-lang/rfcs/issues/1447
  20. Shamelessly reposting my comment https://github.com/rust-lang/rfcs/pull/2052#issuecomment-312... , but I'm concerned about using semver for the tools, and what is effectively just a major version for the language. This is backwards. Every…
    comment by Ericson2314 · 2017-07-05 · in RFC: Evolving Rust Through Epochs
  21. …of the Rust community would feel the same way, but feel free to file an RFC. > Interesting. Link? https://github.com/rust-lang/rfcs/issues/349
    comment by pcwalton · 2017-06-08 · in Rust Performance Pitfalls
  22. Yes, it is. Generics are universals and impl Trait is extisentials. For more, the RFC gets into it https://github.com/rust-lang/rfcs/blob/master/text/1951-expa...
    comment by steveklabnik · 2017-06-08 · in Announcing Rust 1.18
  23. …an RFC in its final comment period regarding improving the ergonomics of matching references: https://github.com/rust-lang/rfcs/pull/2005
    comment by kibwen · 2017-06-08 · in Announcing Rust 1.18
  24. …before, unless the iterator is manually boxed. With impl Trait that is now fixed. The latest RFC is https://github.com/rust-lang/rfcs/pull/1951 ; it was in several.
    comment by kzrdude · 2017-06-08 · in Announcing Rust 1.18
  25. …support was eventually moved out of Rust core to a library. Here is the proposal and rationale: https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b...
    comment by cpeterso · 2017-05-29 · in Green Threads Explained
  26. …efforts may be affected by some of the conversations around the unsafe code guidelines effort: https://github.com/rust-lang/rfcs/pull/1643 https://github.com/nikomatsakis/rust-memory-model
  27. …the rust community. Eh, maybe in some segments, but I don't think that's the majority culture. See https://github.com/rust-lang/rfcs/pull/1985 for something extremely relevant to the discussion here, heh.
    comment by steveklabnik · 2017-05-16 · in Two years of Rust
  28. …has been always unclear (I personally have no strong opinion against or for that though). [1] https://github.com/rust-lang/rfcs/blob/master/text/1210-impl...
    comment by lifthrasiir · 2017-05-10 · in Making a Game in Rust
  29. https://github.com/rust-lang/rfcs/pull/1937
    comment by steveklabnik · 2017-05-08 · in My Struggles with Rust
  30. See https://github.com/rust-lang/rfcs/pull/1931 and https://internals.rust-lang.org/t/lang-team-minutes-const-ge... > We believe that we can have an RFC accepted and const generics available on nightly by the end of 2017. :tada:
    comment by steveklabnik · 2017-04-27 · in Ada: a C Developer's Perspective
  31. …some degree of support appears present. 0 - http://man7.org/linux/man-pages/man7/signal.7.html 1 - https://github.com/rust-lang/rfcs/issues/1368
    comment by AdieuToLogic · 2017-04-27 · in Linux Programming: Signals the easy way
  32. …an error on releasing a resource. Exceptions in C++, Java, and Javascript are more troublesome. [1] https://github.com/rust-lang/rfcs/blob/master/text/1236-stab...
  33. …successors like Java, Go, and Rust all standardized on it, used by hashing algorithms and more: https://github.com/rust-lang/rfcs/pull/560 > In any case, compiler authors are going to follow the C standards, not you hypothetical…
  34. Found it: https://github.com/rust-lang/rfcs/blob/master/text/0738-vari... It still seems bizarre to me that a purely type-level expression is forced by an effectively non-existent term. That RFC specifically states that the main problem is…
    comment by naasking · 2017-03-28 · in Curl is C
  35. …that can't introduce memory safety is a cost we can't afford to pay. If you want the full details, https://github.com/rust-lang/rfcs/blob/1f5d3a9512ba08390a222... is the RFC, and https://github.com/rust-lang/rfcs/pull/560 was the…
    comment by steveklabnik · 2017-03-27 · in Curl is C
  36. …scala, it is effectively the same as inheriting an abstract class with a constructor parameter. [0] https://github.com/rust-lang/rfcs/pull/1546
  37. > Is there a reason why they can't have fields? The design isn't done yet: https://github.com/rust-lang/rfcs/pull/1546
    comment by steveklabnik · 2017-03-04 · in Rust's language ergonomics initiative
  38. > Any was more powerful https://github.com/rust-lang/rfcs/pull/1849 is relevant to your interests; however, as the comments say there, associated type constructors would be needed before it could possibly be used with Any.
    comment by steveklabnik · 2017-03-03 · in Rust's language ergonomics initiative
  39. …be. I'm really grateful that so much of Rust's development happens in such an open fashion. [1] https://github.com/rust-lang/rfcs
  40. …reference and thus must outlive a struct App instance? There is a Rust issue filed for this: https://github.com/rust-lang/rfcs/issues/1532 struct App<'a> { name: String, config: &'a Config, }
  41. …the implementation isn't done yet. Soon! [1] - https://github.com/azerupi/mdBook/issues/29 [2] - https://github.com/rust-lang/rfcs/blob/master/text/1828-rust...
  42. …see a post exploring these possibilities. It might be worth looking at how #[fundamental] works ( https://github.com/rust-lang/rfcs/blob/1f5d3a9512ba08390a222... ) -- it's a coherence escape hatch put on Box<T> and some other stdlib types…
    comment by Manishearth · 2017-02-11 · in Regex: badly needs fuzzing
  43. …starting to get it. A couple warts I've encountered: - No support for default struct fields: https://github.com/rust-lang/rfcs/issues/1594 - Terrible signatures for functions that return iterators: https://www.reddit.com/r/rust/comments/2h2…
    comment by pjungwir · 2017-02-07 · in Rust's 2017 Roadmap
  44. …favor of a different library, but it would continue to work because Rust is backwards compatible. https://github.com/rust-lang/rfcs/blob/master/text/1242-rust... has some of the motivation behind this.
    comment by Manishearth · 2017-02-06 · in Rust's 2017 Roadmap
  45. https://github.com/rust-lang/rfcs/pull/1657#issuecomment-270...
    comment by steveklabnik · 2017-02-06 · in Rust's 2017 Roadmap
  46. …of room for improvement. [1]: https://internals.rust-lang.org/t/setting-our-vision-for-the... [2]: https://github.com/rust-lang/rfcs/pull/1774
    comment by beefsack · 2017-01-18 · in Rust vs. Go
  47. There's an open RFC for this: https://github.com/rust-lang/rfcs/blob/master/text/0066-bett...
    comment by eridius · 2017-01-16 · in Fighting the Borrow Checker
  48. …of relevant crates [2]. [1] https://aturon.github.io/blog/2016/07/27/rust-platform/ [2] https://github.com/rust-lang/rfcs/pull/1824
    comment by epage · 2017-01-14 · in Rust and the limits of swarm design
  49. …discovery before it becomes a problem. They're making first steps to improve it already, e.g.: https://github.com/rust-lang/rfcs/pull/1824
    comment by pornel · 2017-01-14 · in Rust and the limits of swarm design
  50. …This is still a problem, however, but it's one the community has been aware of for a while. https://github.com/rust-lang/rfcs/pull/1824 is step 1 in fixing it.
    comment by Manishearth · 2017-01-14 · in Rust and the limits of swarm design