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. 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...
  2. 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...
  3. …[1] - https://github.com/BurntSushi/rust-snappy/blob/master/src/de... [2] - https://github.com/rust-lang/rfcs/blob/master/text/1725-unal...
  4. ▲ 5
    128-bit Primitives for Rust (RFC 1504)
    story by miqkt · 2016-11-27 · 0 comments
  5. …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
  6. …(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
  7. 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
  8. …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
  9. 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
  10. 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
  11. …status of any of the discussions: https://internals.rust-lang.org/t/on-native-allocations-poin... https://github.com/rust-lang/rfcs/blob/bdbe73d1be948dd925c6b...
  12. …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
  13. …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
  14. 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
  15. 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
  16. https://github.com/rust-lang/rfcs/blob/4b4fd5146c04c9c284094...
    comment by steveklabnik · 2016-09-14 · in A Critique of Rust's `std::collections`
  17. …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
  18. …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
  19. …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
  20. 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
  21. …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
  22. …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
  23. …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…
  24. 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…
  25. 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
  26. …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
  27. …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
  28. …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
  29. …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
  30. …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
  31. 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
  32. 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
  33. …(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
  34. 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
  35. 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
  36. 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…
  37. ▲ 17
    Requesting C like SIMD intrinsics for Rust lang
    story by siavashserver · 2016-06-05 · 17 comments
  38. …bound) * Rust doesn't currently support dynamic stack allocation so DSTs can't be stack-allocated ( https://github.com/rust-lang/rfcs/issues/618 )
  39. https://github.com/rust-lang/rfcs/blob/master/text/0230-remo... and the PR/issue linked there. There are also old mailing list discussions on rust-dev somewhere which discuss this IIRC.
    comment by Manishearth · 2016-05-30 · in Writing an OS in Rust: Catching CPU Exceptions
  40. …but it's not really that big of a problem. For partial borrows, there has been some work on it ( https://github.com/rust-lang/rfcs/issues/1215 ), but I agree that this is something that's missing. That said, I very rarely run into this,…
    comment by Jonhoo · 2016-05-29 · in The Path to Rust
  41. …into Rust, without any assembly file (see [3], especially the `common.ld` linker script). [1]: https://github.com/rust-lang/rfcs/pull/1201 [2]: http://wiki.osdev.org/Bare_Bones [3]: https://github.com/japaric/cu
  42. …feature for consideration. It's one of relatively few areas where D is superior to Rust IMO. [1] https://github.com/rust-lang/rfcs/issues/1077
    comment by wyldfire · 2016-05-26 · in Announcing Rust 1.9
  43. This is also a pending issue: https://github.com/rust-lang/rfcs/issues/349
    comment by shmerl · 2016-05-26 · in The Path to Rust
  44. …the time it does make sense and the borrow checker just isn't clever enough to know. For example: https://github.com/rust-lang/rfcs/issues/811
    comment by IshKebab · 2016-05-26 · in The Path to Rust
  45. Others don't consider languages which do not handle OS signals a "systems" language: https://github.com/rust-lang/rfcs/issues/1368
    comment by ustolemyname · 2016-05-26 · in The Path to Rust
  46. …primitive. I have an long-open RFC that I hope will get cross-compilation working the right way https://github.com/rust-lang/rfcs/pull/1133 . That said RustUP is still a fine easy way to get compilers builds as opposed to standard library…
    comment by Ericson2314 · 2016-05-14 · in Taking Rust everywhere with rustup
  47. ▲ 2
    Rust RFC: native C-compatible unions via contextually recognized keyword union
    story by JoshTriplett · 2016-05-12 · 0 comments
  48. …a long-term experiment to implement KVM in Rust. Adding union support to Rust was the first step: https://github.com/rust-lang/rfcs/pull/1444
    comment by JoshTriplett · 2016-05-12 · in QEMU: out-of-bounds memory access issue
  49. …the special case of Result, the new ? operator is going to subsume try! and offer more flexibility: https://github.com/rust-lang/rfcs/pull/243 (note that what was actually accepted differs from the text of the RFC, you need to scroll to…
    comment by comex · 2016-05-03 · in Rewrite Tor in Rust
  50. What will be interesting is when rust gets its own ABI. There is an rfc for it even: https://github.com/rust-lang/rfcs/issues/600 Hopefully if such a thing exists you could link directly to a rust library from other high level languages…
    comment by robohamburger · 2016-05-03 · in Go bindings to Rust's regex engine