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. 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?
  2. 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
  3. …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
  4. 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
  5. …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
  6. 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
  7. …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.
  8. …they don't feel comfortable with the performance penalty of default integer overflow checks: https://github.com/rust-lang/rfcs/pull/146
  9. …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…
  10. Yes, on the RFC: https://github.com/rust-lang/rfcs/pull/243#issuecomment-1633...
    comment by dbaupp · 2015-12-10 · in Rust 1.5
  11. No problem. To be more specific, https://github.com/rust-lang/rfcs/pull/243#issuecomment-1633... and https://github.com/rust-lang/rfcs/pull/243#issuecomment-1633... TL;DR: we're still adjusting process a bit, but the idea is that this is…
    comment by steveklabnik · 2015-12-10 · in Rust 1.5
  12. …Member of said moderation team (and partially behind its design) We have due process. See https://github.com/rust-lang/rfcs/blob/master/text/1068-rust... Yes, the code of conduct is a bit subjective. That is why there is an entire…
  13. …nor any oversight of significance. The oversight for the moderation team is documented here: https://github.com/rust-lang/rfcs/blob/master/text/1068-rust... > It's also quite common to see any comment here (and at certain other discussion…
  14. Rust automatically chooses the "best" strategy based on how you're building the source, per https://github.com/rust-lang/rfcs/blob/master/text/1183-swap... If you're building a dynamic or static library, we use the system allocator because…
  15. …the ability to catch exceptions exists, people like me are going to write exceptional code. [1] https://github.com/rust-lang/rfcs/pull/1236#issuecomment-127... [2] https://github.com/rust-lang/rfcs/pull/1236#issuecomment-128... > > the…
  16. …and see that the majority of them revolve around various ways of deliberately handicapping the API: https://github.com/rust-lang/rfcs/pull/1236 It even inspired a followup RFC for the purpose of codifying these restrictions in a brand-new…
  17. …for the same reasons as this presentation, basically. It looks like SIL is closer to MIR. HIR: https://github.com/rust-lang/rfcs/blob/master/text/1191-hir.... MIR: https://github.com/rust-lang/rfcs/blob/master/text/1211-mir....
  18. …case is still too verbose. That said, the reason it wasn't included in the original elision RFC ( https://github.com/rust-lang/rfcs/pull/141 ) is that the design space here is a little bit more subtle than some of the cases that did make…
    comment by wycats · 2015-11-01 · in Rust Lifetimes
  19. It makes it easier to have assurances about the behaviour of the program, even in error cases, https://github.com/rust-lang/rfcs/pull/560#issuecomment-6999...
  20. …mode, and that the result needs to be computed as per two's complement, i.e. not unspecified. [0]: https://github.com/rust-lang/rfcs/blob/master/text/0560-inte...
  21. …Here's an overview of how the compiler devs expect rustc to operate once this work is complete: https://github.com/rust-lang/rfcs/pull/1211#issuecomment-128... and here's a comment expanding on this overview:…
    comment by kibwen · 2015-10-24 · in LLVM Code Generation in HHVM
  22. …only works on nightly. [0] an RFC was created then retracted[4] for discussions on internals[5] [1] https://github.com/rust-lang/rfcs/pull/129/files [2] http://rust-dev.1092773.n5.nabble.com/Rust-crypto-highlights... [3]…
    comment by masklinn · 2015-10-20 · in BoringSSL
  23. …analysis passes, as well as laying the groundwork for goodies like incremental compilation ( https://github.com/rust-lang/rfcs/pull/1298 ).
    comment by kibwen · 2015-10-04 · in Rust Faster
  24. The relevant search terms are "SEME regions" and "non-lexical borrows". The tracking issue is here: https://github.com/rust-lang/rfcs/issues/811 and https://github.com/rust-lang/rust/issues/6393 is the older issue it superseded, with…
    comment by steveklabnik · 2015-10-01 · in Trying Rust for web services
  25. You can't go evangelizing about compile times without even mentioning incremental recompilation. :P https://github.com/rust-lang/rfcs/pull/1298
    comment by kibwen · 2015-10-01 · in Trying Rust for web services
  26. …wants to get involved, this RFC was the one that got merged, but hasn't been made stable yet: https://github.com/rust-lang/rfcs/blob/master/text/0809-box-... And this is the active, in-final-comment-period one which modifies it:…
    comment by steveklabnik · 2015-09-29 · in Redox: A Rust Operating System
  27. …to send over a channel). Some more detail can be found in the RFC[1] that implemented them. [1] https://github.com/rust-lang/rfcs/blob/master/text/0019-opt-...
    comment by bbatha · 2015-09-29 · in Resurrecting impl Trait
  28. I love Bitstring Syntax in Elixir and Erlang. Similar feature is coming for Rust[1]. [1] https://github.com/rust-lang/rfcs/issues/346
    comment by namelezz · 2015-09-25 · in Elixir v1.1.0 Released
  29. …using a version of Rust that's pre-1.0.0. Progress is being made on making this first class though: https://github.com/rust-lang/rfcs/issues/604
    comment by timcameronryan · 2015-09-23 · in TodoMVC in Rust
  30. …called outside the protocol Traits that are being defined. Which lead to discussions like this one: https://github.com/rust-lang/rfcs/pull/1236#issuecomment-136...
  31. https://github.com/rust-lang/rfcs/pull/1183
    comment by Manishearth · 2015-09-22 · in Asynchronous IO in Rust
  32. "it" being --target? https://github.com/rust-lang/rfcs/blob/master/text/0131-targ... is the original RFC. Off the top of my head, I think that's it for now. Since cross compilation is getting easier in the future, I haven't invested a lot…
    comment by steveklabnik · 2015-09-20 · in Rust bare metal on ARM microcontroller
  33. …`let x = Box::new(make_inner())`, which may be a move of `make_inner()`) Placer is a part of this ( https://github.com/rust-lang/rfcs/blob/master/text/0809-box-... is the whole design). from_raw isn't, that's just a useful API for FFI. >…
    comment by Manishearth · 2015-09-19 · in Asynchronous IO in Rust
  34. …and so would require duplicating most of the API, however there may be some tricks that work. https://github.com/rust-lang/rfcs/issues/538 covers the allocator stuff.
    comment by dbaupp · 2015-09-18 · in Asynchronous IO in Rust
  35. We have a ticket open: https://github.com/rust-lang/rfcs/issues/388
    comment by steveklabnik · 2015-09-17 · in Asynchronous IO in Rust
  36. …abstract green and native threads into a single API, which lead to a lot of unnecessary overhead: https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b... Sadly, that proposal also removed concurrent IO from the standard library,…
    comment by acconsta · 2015-09-16 · in Asynchronous IO in Rust
  37. …(all the state is stored inline, no need to allocate a separate stack). Relevant issues: - https://github.com/rust-lang/rfcs/issues/388 - https://github.com/rust-lang/rfcs/issues/1081 I'm pretty sure this is quite non-trivial to implement…
    comment by dbaupp · 2015-09-11 · in Why Rust? [pdf]
  38. …quixotic decision. Most of the problems identified in the RFC stem from the unified API issue: https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b... I also understand Rust's implementation was backed by libuv, which, being…
    comment by acconsta · 2015-09-10 · in Why Rust? [pdf]
  39. …trying to mitigate this by adopting officially blessed libraries into the `rust-lang` organization: https://github.com/rust-lang/rfcs/blob/master/text/1242-rust... --- This allows us to avoid the problems with a big standard library (too…
    comment by burntsushi · 2015-09-10 · in Why Rust? [pdf]
  40. …trying to mitigate this by adopting officially blessed libraries into the `rust-lang` organization: https://github.com/rust-lang/rfcs/blob/master/text/1242-rust... --- This allows us to avoid the problems with a big standard library (too…
    comment by burntsushi · 2015-09-09 · in Why Rust? [pdf]
  41. …altering Rust's concurrency support in order to better support fork-join parallelism in the future: https://github.com/rust-lang/rfcs/blob/master/text/0458-send... I'm also confused about your perception that the rhetoric gets ahead of the…
    comment by kibwen · 2015-09-09 · in Why Rust? [pdf]
  42. …contains the full proposal, as well as a motivations section that hopefully makes it more clear: https://github.com/rust-lang/rfcs/pull/1210 TL;DR: specialization lets you also implement a more specific version of something that's generic.…
    comment by steveklabnik · 2015-08-14 · in Rust in 2016
  43. …on a design, such a feature can be easily implemented. I'd love to see an RFC on the topic ( https://github.com/rust-lang/rfcs )!
    comment by aturon · 2015-08-14 · in Rust in 2016
  44. …and eventually did decide to make overflows panic -- but they are checked only in debug builds. https://github.com/rust-lang/rfcs/blob/master/text/0560-inte...
    comment by CUViper · 2015-08-13 · in Android libstagefright still exploitable
  45. …syntax and idiom issues. We _will_ be adding some sort of thing kind of like inheritance to Rust. https://github.com/rust-lang/rfcs/issues/349 is the RFC issue, and it outlines: * cheap field access from internal methods; * cheap dynamic…
    comment by steveklabnik · 2015-08-10 · in Go and Rust – objects without class (2013)
  46. …so far. I think I've found a way, but it would depend on negative trait bounds, as discussed here: https://github.com/rust-lang/rfcs/issues/1053 Ideally, I'd like to be able to do something like this: let a: Scalar<Joules> =…
    comment by jarrettc · 2015-08-08 · in Type-checked matrix operations in Rust
  47. …the trade-offs seem pretty tough and the path to an optimal solution is not at all obvious. [0]: https://github.com/rust-lang/rfcs/blob/master/text/0560-inte... [1]: https://internals.rust-lang.org/t/on-casts-and-checked-overf...
  48. It's a bit more subtle than that, see https://github.com/rust-lang/rfcs/blob/master/text/1122-lang...
    comment by steveklabnik · 2015-07-04 · in Things Rust shipped without
  49. They've been proposed: https://github.com/rust-lang/rfcs/pull/724 If you really need them, you can implement them in a library by declaring a suitably sized byte array and having methods that return casted pointers to it. This would be…
    comment by comex · 2015-07-04 · in Things Rust shipped without
  50. I would add Ropes: https://github.com/rust-lang/rfcs/issues/653 Given the frequency of manipulating large bodies of text in contemporary programming I do not agree it is best left to a library implementation. Without ropes as core std…
    comment by shawn-butler · 2015-07-03 · in Things Rust shipped without