News for hackers. Stuff that matters.
Re:Rust's 2017 Roadmap by steveklabnik on Monday February 06, 2017 @04:18PM (#13584104)
> What about the warts part?

I'm not sure enough time has passed to tell what Rust's warts truly are. I always joke String should have been called StrBuf...

I do this, yes. This is one of the reasons I hang out in IRC so often; it's an effective way to collect these kinds of things.

More data is always better, and collecting it across multiple venues. I don't think IRC is inherently going to be a representative sample. It's one of the reasons you'll see me pushing for details in Rust threads here, for example.

Re:Rust's 2017 Roadmap by pjungwir on Tuesday February 07, 2017 @02:01AM (#13587672)
So I'm only a Rust amateur (I mean I don't get paid to use it), but I'm on my third round trying to build something with it, and I feel like I'm finally starting to get it. A couple warts I've encountered:

- No support for default struct fields: https://github.com/rust-lang/rfcs/issues/1594

- Terrible signatures for functions that return iterators: https://www.reddit.com/r/rust/comments/2h26cj/functions_retu...

If the next push is going to be for ease-of-use, those would be two nice things to fix.

Re:Rust's 2017 Roadmap by comex on Tuesday February 07, 2017 @02:20AM (#13587733)
A feature designed as a fix for the second problem is already in nightly:

https://github.com/rust-lang/rust/issues/34511

Who knows when it'll be stabilized, though.

Re:Rust's 2017 Roadmap by steveklabnik on Tuesday February 07, 2017 @12:09PM (#13590771)
"sooner rather than later"
Re:Rust's 2017 Roadmap by rat87 on Tuesday February 07, 2017 @08:14AM (#13589101)
I think if you don't mind the overhead you can box the iterator
Re:Rust's 2017 Roadmap by kibwen on Monday February 06, 2017 @05:58PM (#13585133)
> I always joke String should have been called StrBuf

Agreed, and Vec should just be Buf! Let's fork the language. :)

Re:Rust's 2017 Roadmap by iopq on Tuesday February 07, 2017 @05:12AM (#13588373)
And it should be white-space sensitive!

    1. Writing a tab character introduces the equivalent of {} for blocks, but not other uses of {}.
    2. You can still use {} for blocks if need be
    3. Everyone uses elastic tabstops in their editor
oh yeah, and parens are optional for function application
Re:Rust's 2017 Roadmap by kibwen on Tuesday February 07, 2017 @01:40PM (#13591482)
> parens are optional for function application

I think you've gotten confused somehow... Rust++ is a pure concatenative programming language, function application is wholly unnecessary.

Re:Rust's 2017 Roadmap by iopq on Tuesday February 07, 2017 @04:07PM (#13592814)
Stop, I can only get so hard before an unsafe drop in blood pressure
Re:Rust's 2017 Roadmap by cpeterso on Tuesday February 07, 2017 @02:37PM (#13591990)
Why not rename Vec to Buf everywhere with a Vec = Buf type alias for backwards compatibility?
Re:Rust's 2017 Roadmap by cpeterso on Tuesday February 07, 2017 @02:39PM (#13591999)
Why not rename String to StrBuf everywhere with a String = StrBuf type alias for backwards compatibility, if this would clarify new users' understanding of String/str?
Re:Rust's 2017 Roadmap by steveklabnik on Tuesday February 07, 2017 @07:32PM (#13594490)
It's not clear that there's a ton of benefit, and not everyone agrees with me that StrBuf is a good name.
Re:Rust's 2017 Roadmap by ainar-g on Monday February 06, 2017 @04:20PM (#13584135)
I see. I hope to see more better docs soon. Thank you for answering and for generally being open.
Re:Rust's 2017 Roadmap by steveklabnik on Monday February 06, 2017 @04:36PM (#13584330)
You're welcome, on both counts. I hope we can help you not get stuck if you give it a fourth try :)