Skip to content

1.0.0-alpha release notes #20620

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 7, 2015
Merged

1.0.0-alpha release notes #20620

merged 3 commits into from
Jan 7, 2015

Conversation

brson
Copy link
Contributor

@brson brson commented Jan 6, 2015

A whole lot happened this cycle. I tried to highlight the best stuff. Please review and note important stuff I'm missing or foolish mistakes.

@rust-highfive
Copy link
Contributor

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@brson brson changed the title Relnotes 1.0.0-alpha release notes Jan 6, 2015
not terminated by a semicolon are [parsed as
expressions][macros], which makes expressions like `vec![1i32,
2, 3].len()` work as expected.
* Trait objects now implement their traits automatically.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might want to mention trait object safety here as well.

@jroesch
Copy link
Member

jroesch commented Jan 6, 2015

It might be interesting to reference progress on experimental/feature-gated parts of the language for those who don't follow the GitHub and IRC chatter closely. For example a ton of work was done on associated types since 0.12.0 and without closely following the community I would have no idea that they are much much more stable then they were and ready to be experimented with and hammered on.

* [`where` clauses][where] provide a more versatile and attractive
syntax for specifying generic bounds, though the previous syntax
remains valid.
* Rust again picks a [fallback] (either i32 or f64) for uninferred
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link to fallback RFC doesn't parse as intended.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be [fallback][fallback] so the (either i32 or f64) part isn't parsed as the link's URL.

@brson
Copy link
Contributor Author

brson commented Jan 6, 2015

Current feedback has been addressed.

though there is a significant amount of cleanup and bugfixes
remaining.
* Nearly 50% of the public API surface of the standard library has
been declared 'stable'. Those interfaces will not change.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should "will not" this be softened slightly? It seems to me we still want some room for tweaks and adjustments based on feedback.

even though the internals do not (e.g. structs containing unsafe
pointers like `Arc`). These changes are intended to prevent some
footguns and are collectively known as [opt-in built-in
traits][oibit] (though `Sync` and `Share` will soon become pure
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be Sync and Send?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch.

brson and others added 2 commits January 6, 2015 22:15
bors added a commit that referenced this pull request Jan 7, 2015
A whole lot happened this cycle. I tried to highlight the best stuff. Please review and note important stuff I'm missing or foolish mistakes.
@bors bors merged commit 9d8de1f into rust-lang:master Jan 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.