Hacker GitHub

← All repos

rust-lang/rfcs

View on GitHub ↗ ★ 6,631 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 RFC on what would need to be done to the region system for nonlexical borrows a while back: https://github.com/rust-lang/rfcs/pull/396 .
    comment by cwzwarich · 2016-05-02 · in Non-Lexical Lifetimes in Rust
  2. …that it can optimize the tail call (and is a compile-time error if it can't). See this comment: https://github.com/rust-lang/rfcs/issues/271#issuecomment-18... Nobody's tried implementing it recently, though.
    comment by geofft · 2016-04-27 · in Introducing MIR
  3. …self.routing_table.insert(origin); } edit: upon digging into the details, it looks like it may: https://github.com/rust-lang/rfcs/blob/db66dd2039b10b7590840...
    comment by eloisius · 2016-04-27 · in Introducing MIR
  4. …https://github.com/rust-lang/rust/issues/26179 Prefetch intrinsic: Looks like a rejected rfc https://github.com/rust-lang/rfcs/pull/125 Inlining: As far as I understand the attributes are #[inline(always)] and #[inline(never)] respectively.
    comment by alkonaut · 2016-04-15 · in Announcing Rust 1.8
  5. Ooops yeah forgot about https://github.com/rust-lang/rfcs/blob/master/text/0320-nonz... . [To be perfectly pendantic, one could trade the drop flags for code bloat and have only a finite blow up and statically known everywhere, so its a…
    comment by Ericson2314 · 2016-04-15 · in Announcing Rust 1.8
  6. Not an exact timeline, but it's something that's being actively worked on. There's even an RFC: https://github.com/rust-lang/rfcs/pull/1566
    comment by steveklabnik · 2016-04-15 · in Announcing Rust 1.8
  7. …when/if we will see support for higher-kinded types in Rust? There is the RFC thread on Github ( https://github.com/rust-lang/rfcs/issues/324 ), but I haven't been following the trajectory very closely, and a quick synopsis would be…
    comment by harveywi · 2016-04-14 · in Announcing Rust 1.8
  8. ▲ 5
    C unions coming to Rust
    story by Jonhoo · 2016-04-08 · 0 comments
  9. …functions that have changed. The code to build and persist the dependency graph has already landed. https://github.com/rust-lang/rfcs/blob/master/text/1298-incr...
  10. ▲ 3
    Rust: Innovative new way for clean error handling
    story by rnestler · 2016-04-01 · 0 comments
  11. …yeah analysis-type tasks is precisely where the REPL is most essential, not going to lie. I hope https://github.com/rust-lang/rfcs/blob/master/text/1298-incr... will help bridge the gap. And perhaps help with writing a REPL too...
    comment by Ericson2314 · 2016-03-27 · in OCaml Language Sucks (2007)
  12. …Take a look at the RFC for std::panic::recover- it definitely takes exception safety into account: https://github.com/rust-lang/rfcs/blob/master/text/1236-stab... Also take a look at things like the design of the Drain iterator- the stdlib…
    comment by Rusky · 2016-03-27 · in Concurrency in Rust
  13. …here: https://doc.rust-lang.org/book/custom-allocators.html And the second is still in RFCs: https://github.com/rust-lang/rfcs/pull/1398 Both of these things are not yet stable. The second does, in fact, give you the ability to return an…
    comment by steveklabnik · 2016-03-27 · in Concurrency in Rust
  14. …//doc.rust-lang.org/std/result/enum.Result.html [1] http://doc.rust-lang.org/core/macro.try!.html [2] https://github.com/rust-lang/rfcs/pull/243
  15. Implementations will do that, e.g. https://github.com/rust-lang/rfcs/pull/1513 .
  16. "ridiculously easy": https://github.com/rust-lang/rfcs/issues/604
    comment by jfbastien · 2016-03-15 · in Experimental support for WebAssembly in V8
  17. …types whose logical invariants are preserved in case of panic). There's an example in the rfc: https://github.com/rust-lang/rfcs/blob/master/text/1236-stab... In Rust logical invariants are used to enforce memory safety. If the destructor…
    comment by Manishearth · 2016-03-07 · in Ill-Advised C++ Rant, Part 2
  18. …but it will be a bumpy road if the compiler simultaneously is going to be made more incremental. https://github.com/rust-lang/rfcs/pull/1317 Nim does a good job with their IDE support http://nim-lang.org/docs/idetools.html
    comment by alkonaut · 2016-03-04 · in Announcing Rust 1.7
  19. …way. That's one of the reasons why adding a defaulted method to a trait is a minor change. See https://github.com/rust-lang/rfcs/blob/master/text/1105-api-... for more.
    comment by steveklabnik · 2016-03-03 · in Announcing Rust 1.7
  20. …and VS Code. We're also working on ways to improve the compiler to better support the IDE use case: https://github.com/rust-lang/rfcs/pull/1317
    comment by kibwen · 2016-03-03 · in Announcing Rust 1.7
  21. …supposed to do with Semver: lay out what 'compatible' means. The primary documents for this are https://github.com/rust-lang/rfcs/blob/master/text/1122-lang... and https://github.com/rust-lang/rfcs/blob/master/text/1105-api-... I quote: >…
    comment by steveklabnik · 2016-03-03 · in Announcing Rust 1.7
  22. …impacted can easily fix them unless they are exploiting the existing "bug" to do something unsound. https://github.com/rust-lang/rfcs/blob/8e2d3a3341da533f846f6...
    comment by tatterdemalion · 2016-03-03 · in Announcing Rust 1.7
  23. …catch_panic", found on Rust's issue tracker, illustrate some unsettled questions I had in mind ( https://github.com/rust-lang/rfcs/pull/1236 ). For example, kentonv wrote: All code can fail, because all code can have bugs. Obviously, we…
    comment by ngrilly · 2016-03-03 · in Visual Studio Code for Go
  24. …forward there were two major features whose RFCs were accepted this cycle: impl specialization ( https://github.com/rust-lang/rfcs/pull/1210#issuecomment-187... ) and the `?` operator ( https://github.com/rust-lang/rfcs/pull/243#issuecommen…
    comment by kibwen · 2016-03-03 · in Announcing Rust 1.7
  25. There is an RFC[1] for making enum variants first-class types. [1]: https://github.com/rust-lang/rfcs/pull/1450
    comment by da4c30ff · 2016-02-29 · in Comparing Rust and Java
  26. Incidentally, the specialization RFC was just accepted https://github.com/rust-lang/rfcs/pull/1210#issuecomment-187...
    comment by steveklabnik · 2016-02-23 · in Rewrite Everything in Rust
  27. …C++ beats Rust in that. For instance Rust is still missing something like virtual structs. See https://github.com/rust-lang/rfcs/issues/349
    comment by shmerl · 2016-02-23 · in Rewrite Everything in Rust
  28. …of the traits you would like to be able to use aren't expressible without "higher kinded types" ( https://github.com/rust-lang/rfcs/issues/324 ), so there are still some big features that everyone kind of hopes will happen soon but there's…
  29. …now. What's important is what happens next. A public issue tracker? A rust style RFC process? ( https://github.com/rust-lang/rfcs ) Just please, whatever you do, do it fast, and stop people from doing what babel did and migrating to…
    comment by shadowmint · 2016-02-12 · in GitHub responds to Dear GitHub letter
  30. …mechanisms to prevent people from treating `recover` as a general error-handling mechanism: https://github.com/rust-lang/rfcs/pull/1323
    comment by kibwen · 2016-02-08 · in The Error Model in Midori
  31. I read it the same way. There's an open issue for it: https://github.com/rust-lang/rfcs/issues/372 I think one of the main reasons this isn't done is because of the grammar issue. I dimly remember that one of the goals of Rust was to be…
  32. …that everything is still well-defined. There does not seem to be real answer to this question yet: https://github.com/rust-lang/rfcs/issues/1447 What does Rust guarantee with respect to lifetimes? In fact it guarantees much less than what…
    comment by wuch · 2016-02-01 · in Why I'm Choosing C++
  33. …question ;-) > Xbox Nope. [1]: https://twitter.com/wickerwaka/status/479842553831776257 [2]: https://github.com/rust-lang/rfcs/blob/master/text/0131-targ...
    comment by tomjakubowski · 2016-02-01 · in Why I'm Choosing C++
  34. I wrote a comment a while ago that has some code examples: https://github.com/rust-lang/rfcs/pull/243#issuecomment-8220... (and the following two comments)
    comment by dbaupp · 2016-01-23 · in Rust and the Blub Paradox
  35. Have you seen https://github.com/rust-lang/rfcs/pull/243 ? What do you think of it?
    comment by steveklabnik · 2016-01-23 · in Rust and the Blub Paradox
  36. …tp://doc.rust-lang.org/std/marker/trait.Copy.html [1] http://doc.rust-lang.org/std/ops/index.html [2] https://github.com/rust-lang/rfcs/pull/953
    comment by masklinn · 2016-01-22 · in Announcing Rust 1.6
  37. …of LLVM we've let pollute into the language in the meantime and where it's feasible to diverge. https://github.com/rust-lang/rfcs/issues/1447 is a good thread if you care about this topic.
    comment by steveklabnik · 2016-01-21 · in Announcing Rust 1.6
  38. EDIT: I realized the post was written before Rust's governance was diversified ( https://github.com/rust-lang/rfcs/blob/master/text/1068-rust... ). Rust at that time was "Mozilla led", but this isn't really true now. > Rust is pushed by…
    comment by Manishearth · 2016-01-21 · in I missed Nim (2014)
  39. …based on a merge I saw recently. The "Trait Based Exception Handling" RFC is in final comments: https://github.com/rust-lang/rfcs/pull/243
    comment by grayrest · 2016-01-21 · in I missed Nim (2014)
  40. …and expect there will be something to make it slow in practice. I could be wrong though. [1] https://github.com/rust-lang/rfcs/blob/master/text/1298-incr...
    comment by comex · 2016-01-18 · in C or C++ for my game engine?
  41. As far as try goes, see https://github.com/rust-lang/rfcs/pull/243#issuecomment-1720... . It's reached final comment period so probably will happen soonish?
  42. Here's a summary: https://news.ycombinator.com/item?id=10713301 Here are the two RFCs: https://github.com/rust-lang/rfcs/blob/master/text/1191-hir.... https://github.com/rust-lang/rfcs/blob/master/text/1211-mir.... And thanks! I'm hoping…
    comment by steveklabnik · 2016-01-12 · in Two Weeks of Rust
  43. …https://www.reddit.com/r/rust/comments/2h26cj/functions_retu... https://github.com/rust-lang/rfcs/pull/105 https://github.com/rust-lang/rfcs/pull/1305 Reading those RFCs can be frustrating, where a discussion goes on for o
    comment by pjungwir · 2016-01-12 · in Two Weeks of Rust
  44. Redefining well-known terms gives nothing except confusion. And https://github.com/rust-lang/rfcs/pull/243 is another step in this direction (beside "?" idea). If usual errors handling will be called "exceptions", then we will have full…
    comment by EugeneOZ · 2016-01-12 · in Two Weeks of Rust
  45. …good support for custom GCs for pure Rust code, but it's definitely being thought about. [0]: https://github.com/rust-lang/rfcs/pull/1398 [1]: http://blog.pnkfx.org/blog/2015/11/10/gc-and-rust-part-1-spe... [2]:…
    comment by bjz_ · 2016-01-12 · in Two Weeks of Rust
  46. The "return function as result" is being worked on: https://github.com/rust-lang/rfcs/pull/1305
    comment by heinrich5991 · 2016-01-12 · in Two Weeks of Rust
  47. …on why the Rust people nevertheless decided against checked arithmetic? The current RFC seems to be https://github.com/rust-lang/rfcs/blob/master/text/0560-inte... which seems to avoid taking a stand on the performance issue.
  48. …they don't feel comfortable with the performance penalty of default integer overflow checks: https://github.com/rust-lang/rfcs/pull/146
  49. …Rust being a panacea: here are the areas of the language which are currently a bit under-specified https://github.com/rust-lang/rfcs/blob/master/text/1122-lang... Surprise: Rust is not a panacea :) There is, however, a lot of work being…
  50. Yes, on the RFC: https://github.com/rust-lang/rfcs/pull/243#issuecomment-1633...
    comment by dbaupp · 2015-12-10 · in Rust 1.5