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
AllStoriesComments NewestTopOldest
  1. …reduce the amount of work that gets unnecessarily repeated with each compilation cycle ( https://github.com/rust-lang/rfcs/pull/594 ). In the even longer run there are plans to fully parallelize the compiler phases and also to pre-optimize…
    comment by kibwen · 2015-06-06 · in Crystal Language
  2. …I linked to an active rfc about constraints that cannot currently be expressed in where clauses ( https://github.com/rust-lang/rfcs/blob/master/text/0135-wher... ), including the example you gave. In cases where a function takes two…
    comment by jamii · 2015-06-05 · in Three months of Rust
  3. Would you not call this uncomfortably explicit: https://github.com/rust-lang/rfcs/pull/105#issuecomment-6410... ? Type inference does make such things easy inside function bodies, but there are a lot of functions so it's not a complete…
    comment by Veedrac · 2015-05-16 · in Announcing Rust 1.0
  4. …don't have destructors. This happens because borrow scopes are always lexical. This is a bug, see https://github.com/rust-lang/rfcs/issues/811 .
    comment by Veedrac · 2015-05-15 · in Announcing Rust 1.0
  5. …Rc issue was moved to RFC because any such change would require one per the guidelines at [1] [1] https://github.com/rust-lang/rfcs
    comment by mastax · 2015-05-03 · in Death to C
  6. In Rust, integer overflow is defined behavior, though: https://github.com/rust-lang/rfcs/blob/master/text/0560-inte...
    comment by steveklabnik · 2015-05-02 · in Integer Overflow Bug in Boeing 787 Dreamliner
  7. …you can't restrict their use on a project. [1] https://github.com/rust-lang/rust/issues/24456 [2] https://github.com/rust-lang/rfcs/pull/1066 [3] http://smallcultfollowing.com/babysteps/blog/2015/04/29/on-r...
    comment by Animats · 2015-05-02 · in Death to C
  8. …new? I swear you had to do &* if you had a String and & if you had a &String. Edit: Ah, here: https://github.com/rust-lang/rfcs/blob/master/text/0241-dere...
    comment by cornstalks · 2015-05-02 · in Death to C
  9. …desire for a `yield` construct to simplify the creation of iterators (inspired by C#). See https://github.com/rust-lang/rfcs/issues/388
    comment by kibwen · 2015-04-30 · in Nim Programming Language 0.11.0 released
  10. …code was using this pattern. Gankro talks about one in the post; you can see a proposal here ( https://github.com/rust-lang/rfcs/pull/1084 ) for the `scoped` API. The basic issue here is about a tension between a couple of different APIs,…
    comment by aturon · 2015-04-27 · in Pre-Pooping Your Pants with Rust
  11. Making mem::forget safe makes that point moot. https://github.com/rust-lang/rfcs/pull/1066
    comment by mcguire · 2015-04-27 · in Pre-Pooping Your Pants with Rust
  12. …all warnings into hard errors; a plan to keep this from happening in the future is being formed at https://github.com/rust-lang/rfcs/issues/1029 ). For this week, the big breaking change will be the deprecation of thread::scoped due to its…
    comment by kibwen · 2015-04-17 · in Rust Priorities after 1.0
  13. …you want to get a bit more of a feel for how this works. The details about the shorthand are here: https://github.com/rust-lang/rfcs/pull/141
    comment by aturon · 2015-04-11 · in Fearless concurrency with Rust
  14. …blunt instrument of inheritance. Here's an example from last year of such an attempt, in RFC form: https://github.com/rust-lang/rfcs/pull/250
    comment by tomjakubowski · 2015-04-10 · in Fearless concurrency with Rust
  15. We may end up adding linear types, not just affine, to Rust as well: https://github.com/rust-lang/rfcs/issues/814
    comment by steveklabnik · 2015-04-10 · in Fearless concurrency with Rust
  16. …people using the language in the community, which eventually turned into the current RFC process ( https://github.com/rust-lang/rfcs ) and which is a bit like Python's PEP process. > Usability involves more than syntax --package >…
    comment by kibwen · 2015-04-03 · in Announcing Rust 1.0 Beta
  17. …the type system ensuring safety. In this instance, `Path` is actually fairly complex. From the RFC: https://github.com/rust-lang/rfcs/blob/master/text/0474-path... > The design of a path abstraction is surprisingly hard. Paths work >…
    comment by steveklabnik · 2015-04-03 · in Announcing Rust 1.0 Beta
  18. https://github.com/rust-lang/rfcs/issues/538 is where we're tracking the discussion, basically :) And thanks!
    comment by steveklabnik · 2015-03-12 · in OpenSSL Audit
  19. …here, and I thought they did a good job of detailing the consequences and their reasoning; see https://github.com/rust-lang/rfcs/blob/master/text/0560-inte... .
    comment by deathanatos · 2015-03-04 · in Swift: Madness of Generic Integer
  20. …a little nervous about this when reading the performance-related objections of @thestinger here: https://github.com/rust-lang/rfcs/pull/560 At least optimized builds aren't affected, but it sounds like lots of code (including Rust…
    comment by haberman · 2015-02-13 · in Rust 1.0: Status report and final timeline
  21. …It also links to the list of RFCs that have been postponed until post-1.0: https://github.com/rust-lang/rfcs/issues?q=is%3Aopen+is%3Ais...
    comment by mbrubeck · 2015-02-13 · in Rust 1.0: Status report and final timeline
  22. …on the direction of the language and libraries. Proposed changes go through a public RFC process ( https://github.com/rust-lang/rfcs#what-the-process-is ), including those proposed by members of the core team -- which are frequently…
    comment by aturon · 2015-02-13 · in Rust 1.0: Status report and final timeline
  23. …and long discussions is "Efficient code reuse" (a.k.a some kind of inheritance), summarized here: https://github.com/rust-lang/rfcs/issues/349 It was explicitly postponed until after 1.0.
    comment by kzrdude · 2015-02-13 · in Rust 1.0: Status report and final timeline
  24. Funny you should ask: https://github.com/rust-lang/rfcs/labels/A-wishlist We have not done any scheduling for what comes after 1.0. I've been doing a huge amount of triage to move over issues that used to be in rust-lang/rust to be under…
    comment by steveklabnik · 2015-02-13 · in Rust 1.0: Status report and final timeline
  25. …variables) one after the other. See the Rust RFC on the subject for motivations and comparisons: https://github.com/rust-lang/rfcs/blob/master/text/0160-if-l...
    comment by masklinn · 2015-02-10 · in Swift 1.2 and Xcode 6.3 beta
  26. "The if let construct is based on the precedent set by Swift," https://github.com/rust-lang/rfcs/blob/master/text/0160-if-l...
    comment by CUViper · 2015-02-09 · in Swift 1.2 and Xcode 6.3 beta
  27. Found it! https://github.com/rust-lang/rfcs/pull/452
    comment by steveklabnik · 2015-02-02 · in Some notes on Rust
  28. The default types for bare literals is described in RFC #212 ( https://github.com/rust-lang/rfcs/pull/212 ) To summarize: bare FP literals default to f64, bare integral literals default to isize. (NOTE: isize is recently renamed from int.…
    comment by drbawb · 2015-02-01 · in Some notes on Rust
  29. The entire api for the IO module is actually being overhauled right now (see https://github.com/rust-lang/rfcs/blob/efb783a79c9987e678ed8... ). I'm sure this stabilization is priority for the team before actual optimizations can be done.
    comment by cbriones · 2015-01-29 · in Testing Rust's IO Speed
  30. …contrast Rust stdlib does depend on glibc. It does not even work on musl, that is on the wishlist: https://github.com/rust-lang/rfcs/issues/625 Of course you can use Rust without stdlib, but that leaves you with fairly barebones language.
    comment by zokier · 2015-01-28 · in C Runtime Overhead
  31. ▲ 1
    Rust RFC 517: Reform the “std::io” and “std::os” libraries
    story by mbrubeck · 2015-01-26 · 0 comments
  32. The discussion about reforming IO has been going on since December 12: https://github.com/rust-lang/rfcs/pull/517 Furthermore, consider that many programming languages have gotten popular post-1.0, so if anything, they had _even less_…
    comment by steveklabnik · 2015-01-24 · in Graydon Hoare on Rust 1.0.0-alpha
  33. …library is designed to support it, the only missing piece is changing one piece of the type system, https://github.com/rust-lang/rfcs/pull/458 , to be able to guarantee safety.)
    comment by dbaupp · 2015-01-24 · in What makes Nim practical?
  34. …The RFC describing the changes is [^1] and the actual commit that finalized them is [^2]. [^1]: https://github.com/rust-lang/rfcs/pull/230 [^2]: https://github.com/rust-lang/rust/commit/0efafac398ff7f28c5f...
    comment by andolanra · 2015-01-11 · in 151-byte static Linux binary in Rust
  35. …read up here: http://doc.rust-lang.org/book/generics.html , as well about "output" generics here: https://github.com/rust-lang/rfcs/blob/master/text/0195-asso... , and explore usage in collections here:…
    comment by nercury · 2015-01-09 · in Announcing Rust 1.0 Alpha
  36. …so sharing data will no longer require reference counting for threads with bounded lifetime: https://github.com/rust-lang/rfcs/pull/458 (the RFC hasn't been officially accepted but it's been referenced as a foregone conclusion several…
    comment by Jweb_Guru · 2014-12-23 · in Clojure: Creating a reducible repeat
  37. …language (I believe C#'s async/await is an example), but Rust doesn't do it... yet: https://github.com/rust-lang/rfcs/issues/388
    comment by thristian · 2014-12-22 · in Rust, an Anti-Sloppy Programming Language
  38. …out, of course, but the language itself is making great strides in usability as it matures. [1] https://github.com/rust-lang/rfcs/blob/704f0060176418659698e...
    comment by portmanteaufu · 2014-12-22 · in Rust, an Anti-Sloppy Programming Language
  39. …much of the most useful parts of the stdlib stable (at least the core functionality). More info: - https://github.com/rust-lang/rfcs/pull/507 - http://blog.rust-lang.org/2014/12/12/1.0-Timeline.html
    comment by dbaupp · 2014-12-19 · in Narrowing the notion of a runtime in Rust
  40. and to the RFC: https://github.com/rust-lang/rfcs/blob/master/text/0230-remo...
    comment by sciurus · 2014-12-19 · in Narrowing the notion of a runtime in Rust
  41. …in particular, you can read a very recent RFC that proposes the final set of API changes for 1.0: https://github.com/rust-lang/rfcs/pull/517 Hope that helps!
    comment by aturon · 2014-12-13 · in Rust 1.0: Scheduling the trains
  42. …closed pending writing an RFC and I haven't had time to figure that out yet. Edit: I added the RFC: https://github.com/rust-lang/rfcs/pull/519
    comment by MichaelGG · 2014-12-13 · in Rust 1.0: Scheduling the trains
  43. It appears that (at least with my searching) we don't have an issue on the RFC repo, so I opened one. https://github.com/rust-lang/rfcs/issues/518
    comment by steveklabnik · 2014-12-12 · in Rust 1.0: Scheduling the trains
  44. …new one for abstract / anonymous return types? This was the previous one for abstract return types: https://github.com/rust-lang/rfcs/pull/105
    comment by scanr · 2014-12-12 · in Rust 1.0: Scheduling the trains
  45. …languages, and we've looked at their pitfalls to make sure we can avoid them. For example, see https://github.com/rust-lang/rfcs/pull/213#issuecomment-6575...
    comment by aturon · 2014-12-12 · in Rust 1.0: Scheduling the trains
  46. Language changes are proposed through our RFC process, which is at this repository: https://github.com/rust-lang/rfcs Open issues start a discussion, and then morph to a more formal proposal.
    comment by steveklabnik · 2014-12-12 · in Rust 1.0: Scheduling the trains
  47. …Rust program written, and people may be surprised if 'the best way' to do this changes after 1.0. https://github.com/rust-lang/rfcs/pull/243
    comment by asb · 2014-12-12 · in Rust 1.0: Scheduling the trains
  48. …change for a future release: https://stackoverflow.com/questions/26329231/returning-a-sim... https://github.com/rust-lang/rfcs/pull/105
    comment by scanr · 2014-12-12 · in Rust 1.0: Scheduling the trains
  49. …moment it may be enlightening to read the recently-implemented Flexible Target Specification RFC ( https://github.com/rust-lang/rfcs/blob/master/text/0131-targ... ), which you may have seen in action via Rust on the PSP (…
    comment by kibwen · 2014-12-11 · in Bootstrapping Rust
  50. …than enums (and change the keyword correspondingly). :) Here's the most recent one that I know of: https://github.com/rust-lang/rfcs/pull/27 Swift seems to have followed Rust's example with its terminology here, so this issue is hardly…
    comment by kibwen · 2014-12-10 · in Elm 0.14 – Simpler Core, Better Tools