Congrats and thank you guys for all the hard works.
Announcing Rust 1.0 Alpha
181–190 of 255 posts
Re: Announcing Rust 1.0 Alpha
#182Earlier quoted context omitted.
This is a very old post, but you can encode many uses of typestate pretty easily: http://pcwalton.github.io/blog/2012/12/26/typestate-is-dead/ It'd be great for someone to write a more up-to-date version of this post!
Haven't used Rust, but I wonder what you could use in place of the phantom types? Are Traits capable of filling this role? Am I completely misreading what Traits are? Can Rust still do phantom types, and I just can't see them anywhere in the language reference?
You should still be able to use phantom types with empty traits or enums.
Here's an article[0] (admittedly from ~6 months ago), about using phantom types in Servo.
[0] https://blog.mozilla.org/research/2014/06/23/static-checking...
Re: Announcing Rust 1.0 Alpha
#183Stupid question, but how can a web developer relate to Rust? I had to look up 'systems programming' and Wikipedia basically told me it is writing software for certain hardware components.
Will I ever be writing a web application in Rust?
Re: Announcing Rust 1.0 Alpha
#184Stupid question, but how can a web developer relate to Rust? I had to look up 'systems programming' and Wikipedia basically told me it is writing software for certain hardware components. Will I ever be writing a web application in Rust?
Here's a handy guide: http://arewewebyet.com/
Re: Announcing Rust 1.0 Alpha
#185Congrats to everyone involved (and there sure are a lot of you)! The TL;DR of the alpha is basically this: 1. The concept of a six-week release cycle begins today, with the first beta coming in March. 2. Breaking changes will basically cease, with the exception of a list of libraries that are still unstable and features that may be tweaked ( https://github.com/rust-lang/rust/wiki/Anticipated-breaking-... ). 3. Given…
> Breaking changes will basically cease, with the exception of a list of libraries that are still unstable
It's worth noting that this is a significant point; probably 40-50% of the standard library is 'unstable'.
You should expect breaking changes often during the alpha. It's just ridiculous to pretend otherwise.
I'm not really a fan of these 'artificial deadlines'. There was no reason today had to be the alpha, other than it was previously said that it would be. There's been a lot of great work going into this release, but the standard library is not ready; it's going to under going some major changes over the next few weeks.
I don't really see the point in hitting the alpha 1.0 now, with the library in it's current state.
Re: Announcing Rust 1.0 Alpha
#186Congrats to everyone involved (and there sure are a lot of you)! The TL;DR of the alpha is basically this: 1. The concept of a six-week release cycle begins today, with the first beta coming in March. 2. Breaking changes will basically cease, with the exception of a list of libraries that are still unstable and features that may be tweaked ( https://github.com/rust-lang/rust/wiki/Anticipated-breaking-... ). 3. Given…
> Breaking changes will basically cease, with the exception of a list of libraries that are still unstable It's worth noting that this is a significant point; probably 40-50% of the standard library is 'unstable'. You should expect breaking changes often during the alpha. It's just ridiculous to pretend otherwise. I'm not really a fan of these 'artificial deadlines'. There was no reason today had to be the alpha, oth…
The 45% number is misleading, because that's a per-item count. The majority of almost every module is stable, just some of the internals haven't been marked as such yet. In addition, the three modules which will see changes have RFCS that are in their final stages, so they will also stabilize soon.
The alpha was always about language items, and an initial commitment to some degree of stability. Beta is the release where things are expected to be in their final form.
Re: Announcing Rust 1.0 Alpha
#187Earlier quoted context omitted.
I think the stdlib is not the way to go. Give me an example of any ecosystem where the standard library is the defacto best solution? But would agree that the only thing Rust might need are officially supported crates, while keeping the language itself fully separate. The language is then completely free of the hastles of maintaining a stdlib that probably isn't used by most people anyway. But at the same time offici…
> I think the stdlib is not the way to go. Give me an example of any ecosystem where the standard library is the defacto best solution? Python, Go, C++'s STL, Java SDK, to name a few. They might not be 100% perfect, but they are good and reliable, and always there for you. Hunting the latest "best" library that gets abandoned after a year (like in Javascript and Ruby often happens, and also Go too) gets old quickly.…
I love Python and Python's standard lib but it's hardly the defacto best solution.
urllib gets trumped by requests, ujson is much much better than the stdlib json module, hardly anyone still uses distutils over setuptools for example.
Re: Announcing Rust 1.0 Alpha
#188Earlier quoted context omitted.
I think you're kind of missing the point. The point isn't to have a "house" style, it's to have an "everything" style. Making it optional or configurable defeats the purpose.
That depends on your purpose and the problem you are trying to solve. If the problem is style bikeshedding, that can easily be solved through autoformatting and configurations for the standard for that project, company, etc. Write however you want, run it through the auto-formatter with the right config before commit (or add it to commit hooks). Problem solved. If you want to solve the problem that people are writing…
You then bikeshed what should go in the configuration file, which is almost as bad.
And gofmt is generally less bound to the style than, say, PEP8 since everyone could trivially mechanically update their source to the new standard.
Re: Announcing Rust 1.0 Alpha
#189Wow. Anyone remembers Rust pre-0.1? When it had typestate, ML syntax, garbage collection, etc.? So nice to see how the language slowly evolved and was molded to fit as best as possible the problem they were trying to solve.
Deeply second that.
Re: Announcing Rust 1.0 Alpha
#190Is the Book up-to-date? http://doc.rust-lang.org/1.0.0-alpha/book/