rust-lang/rfcs on Hacker News

…fits this case, IMO). [1] http://discuss.rust-lang.org/t/if-int-has-the-wrong-size/454... [2] https://github.com/rust-lang/rfcs/pull/464

comment by gioele · 2014-12-03 · in Gangnam Style breaks YouTube viewer count

…in" blog and the RFC's also, to form your own opinion of stability http://this-week-in-rust.org/ https://github.com/rust-lang/rfcs#active-rfc-list __________________________ discussion re: stdlib and 1.0…

comment by gtani · 2014-12-02 · in Go: Planning the 1.5 release

…single driven community member can achieve. [1] https://github.com/rust-lang/rust/issues/18009 [2] https://github.com/rust-lang/rfcs/pull/235 [3] https://github.com/rust-lang/rust/issues/18424

comment by kibwen · 2014-11-19 · in Rust, Lifetimes, and Collections

…support for within-application custom allocators, it looks like this is still under discussion: https://github.com/rust-lang/rfcs/pull/244

comment by rdw · 2014-11-15 · in Allocators in Rust

…seen a way to swap out the memory allocator in various contexts. You mean something like this? https://github.com/rust-lang/rfcs/pull/244 I think part of it was inspired by something similar from C++. D-lang also seems to have something…

comment by Dewie · 2014-11-10 · in Real-Time Garbage Collection Is Real

The motivation doesn't have to do with it looking like comments: https://github.com/rust-lang/rfcs/pull/386

comment by steveklabnik · 2014-10-30 · in A taste of Rust for C/C++ programmers

…much easier. There's still work to be done on this front, but I'm _incredibly_ excited by this RFC: https://github.com/rust-lang/rfcs/pull/403

comment by steveklabnik · 2014-10-19 · in Rust vs. C++ Benchmark Game

That too is being removed: https://github.com/rust-lang/rfcs/pull/230

comment by m0th87 · 2014-10-19 · in Rust vs. C++ Benchmark Game

…iterators (but it might not be relevant to your question at all, I haven't had my tea yet...). https://github.com/rust-lang/rfcs/pull/105/files > when is Rust going to compile to Javascript Never officially , but that doesn't mean an…

comment by kibwen · 2014-10-17 · in On Error Handling in Rust

…to be constrained too much to get either model where it should be. The decision was made around https://github.com/rust-lang/rfcs/pull/230 but I'm not sure whether there's any important prior discussion not linked from there, the topic has…

comment by ben0x539 · 2014-10-15 · in Rustful – A RESTful web framework for Rust

Unfortunately I don't think higher-kinded types are planned for Rust 1.0. See the rfc: https://github.com/rust-lang/rfcs/issues/324 and this HN thread: https://news.ycombinator.com/item?id=7997926

comment by mhaymo · 2014-10-13 · in Why your first Rust FizzBuzz implementation may not work

Does the RFC230 ( https://github.com/rust-lang/rfcs/pull/230 ) removal of green threads give me out of box 1:1 threading or just that std::io uses native threads and the rest has to use green threads only now as an additional outside…

comment by blinkingled · 2014-10-09 · in Rust 0.12.0 released

…fn get_mut(&mut self) -> &mut T; fn print(s: &str); This is a pretty huge readability win. 1: https://github.com/rust-lang/rfcs/blob/master/active/0039-li...

comment by steveklabnik · 2014-10-09 · in Rust 0.12.0 released

…about them to determine if they should be dropped This is in the process of being eliminated (see https://github.com/rust-lang/rfcs/pull/320 ). I didn't mention it because it's runtime overhead that will not be present shortly, and…

comment by wycats · 2014-10-08 · in Rust means never having to close a socket

…current options. Fear not however as post 1.0, optional GC will be most likely added to Rust. See https://github.com/rust-lang/rfcs/pull/244 .

comment by Ericson2314 · 2014-10-07 · in Rust means never having to close a socket

There is ongoing discussion about this, eg here: https://github.com/rust-lang/rfcs/pull/239 (related reddit thread: http://www.reddit.com/r/rust/comments/2gs85u/rfc_allow_compi... )

comment by zokier · 2014-10-07 · in Rust means never having to close a socket

…to allow statics to have the same sort of very simple inference scheme that C++ and Go have: https://github.com/rust-lang/rfcs/issues/296

comment by kibwen · 2014-10-02 · in A Fresh Look at Rust

…discussion[1] about Rust possibly moving to a static model, for the highest performance. [1]: https://github.com/rust-lang/rfcs/pull/210

comment by dbaupp · 2014-09-20 · in Rust lifetimes: Getting away with things that would be reckless in C++

…(there's no guarantee that it will be implemented though, just that the idea is mostly sound). [1]: https://github.com/rust-lang/rfcs/blob/master/active/0031-be...

comment by dbaupp · 2014-09-20 · in Rust lifetimes: Getting away with things that would be reckless in C++

https://github.com/rust-lang/rfcs/pull/230 It's "just" an RFC, but the notion that has some momentum built up already.

comment by ben0x539 · 2014-09-13 · in Hidden text inside every compiled Rust program

…the way to advocate a change is to write an RFC. To do so, you fork the rfcs repo on GitHub ( https://github.com/rust-lang/rfcs ), and write a document describing your proposal and its pros and cons. Then the community can discuss it, and…

comment by lambda · 2014-09-13 · in Rust Guide

▲ 3

RFC for overhauling Rust's runtime system / IO libraries

story by nham · 2014-09-10 · 0 comments

▲ 3

This RFC proposes a simplification to the I/O stack distributed with Rust

story by hamidr · 2014-08-29 · 0 comments

…pretty darn convenient! [0]: https://developer.apple.com/library/prerelease/ios/documenta... [1]: https://github.com/rust-lang/rfcs/pull/204

comment by sanderjd · 2014-08-18 · in Java 9 features announced

There was an RFC: https://github.com/rust-lang/rfcs/pull/148 The author closed it after finding that there were no non-subjective reasons. Moving to []s causes other ambiguities.

comment by steveklabnik · 2014-08-15 · in A Rust curiosity: pointers to zero-sized types

Here's a recent RFC closed by its author on the subject: https://github.com/rust-lang/rfcs/pull/148 (a big issue with []-generics is that they're easy to confuse with indexing/slicing to a human. <> may look noisy, but it's harder to…

comment by masklinn · 2014-07-02 · in Rust 0.11.0 Released

While this is true, that doesn't mean precedent is irrelevant. While what kiwiben said is true, https://github.com/rust-lang/rfcs/pull/148#issuecomment-4771...

comment by steveklabnik · 2014-07-02 · in Rust 0.11.0 Released

…for use by the time 0.12 rolls around. We also have some very exciting RFCs in the pipe, such as https://github.com/rust-lang/rfcs/pull/141 , which would make it possible to remove 90% of the lifetime parameters from our function…

comment by kibwen · 2014-07-02 · in Rust 0.11.0 Released

▲ 2

Rust RFC: rename 'unsafe' to 'trusted.'

story by steveklabnik · 2014-06-12 · 0 comments

…organization, get a newsfeed of their latest releases and announcement, and highlight commits (ex: https://github.com/rust-lang/rfcs/pull/59 ) ! I don't have time to implement this as an idea, but I think Github has that resource to…

comment by yeukhon · 2014-05-03 · in A Chinese copy of GitHub.com

▲ 126

‘~’ is being removed from Rust

story by steveklabnik · 2014-05-02 · 115 comments

▲ 2

Remove `~` in favor of `box` and `Box`

story by mikeleeorg · 2014-05-01 · 0 comments

…and corner cases, rather than just some syntax/use-cases) would need to go through the RFC process: https://github.com/rust-lang/rfcs/blob/master/active/0001-rf... ((Unfortunately?) I imagine such an RFC would spend a month or two (or…

comment by dbaupp · 2014-04-27 · in Rust by Example

…a lot of effort to be as transparent and participatory as possible in designing the system. [1]: https://github.com/rust-lang/rfcs/

comment by pcwalton · 2014-04-18 · in Rust for C++ programmers – part 1: Hello world

…without losing all of the other goodies. Here's the most recent RFC for doing so, filed yesterday: https://github.com/rust-lang/rfcs/pull/40/files

comment by kibwen · 2014-04-09 · in TLS/SSL implementation in Haskell