News for hackers. Stuff that matters.

A comment on Rust's 2017 Roadmap. Parent comment

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. :)

[ Parent | on HN ]
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
[ Parent | on HN ]
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.

[ Parent | on HN ]
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
[ Parent | on HN ]
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?
[ Parent | on HN ]