Skip to content
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

Rust 1.17.0 #41

Merged
merged 3 commits into from
Jun 22, 2017
Merged

Rust 1.17.0 #41

merged 3 commits into from
Jun 22, 2017

Conversation

rillian
Copy link
Contributor

@rillian rillian commented Jun 21, 2017

Firefox bumped their minimum so workarounds can be dropped.

https://bugzilla.mozilla.org/show_bug.cgi?id=1374807


This change is Reviewable

rillian added 3 commits June 21, 2017 16:24
Firefox has raised their minimum-required version, so we can
allow newer language features now.
Now that our minimum is 1.17 we can simplify some initizers.
Rust 1.17.0 and later will infer this for us.
@Manishearth
Copy link
Member

@bors-servo r+

@bors-servo
Copy link
Contributor

📌 Commit 5256549 has been approved by Manishearth

@bors-servo
Copy link
Contributor

⌛ Testing commit 5256549 with merge c6bd9cb...

bors-servo pushed a commit that referenced this pull request Jun 21, 2017
Rust 1.17.0

Firefox bumped their minimum so workarounds can be dropped.

https://bugzilla.mozilla.org/show_bug.cgi?id=1374807

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/unicode-bidi/41)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

☀️ Test successful - status-travis
Approved by: Manishearth
Pushing c6bd9cb to master...

@bors-servo bors-servo merged commit 5256549 into servo:master Jun 22, 2017
@mbrubeck
Copy link
Contributor

mbrubeck commented Jun 26, 2017

Since this crate has a lot of downstream users besides Firefox, we should document some expectations about when it can break for users of older Rust toolchains. One option is to treat changes like this as a semver-breaking change, so that a minor update will never break an existing build. Another option is to document a support policy like "current stable release and previous 2 stable releases."

@rillian
Copy link
Contributor Author

rillian commented Jun 29, 2017

Gecko will probably move closer to requiring current stable or previous stable, but documenting that requirement is a good idea.

@rillian rillian deleted the rust-1.17.0 branch June 29, 2017 22:19
@behnam
Copy link
Contributor

behnam commented Jun 29, 2017

I think the idea is that "minimum rustc/rust-lang version required" is a package matter, and should be defined somewhere in the package metadata, versus the implicit annotation in travis.yml, or somewhere in a dependent package (Firefox, in this case).

Here's the Cargo discussion: rust-lang/cargo#2751

@mbrubeck
Copy link
Contributor

My point is that we should consider consumers besides Gecko, too.

@rillian
Copy link
Contributor Author

rillian commented Jun 30, 2017

Sorry, I didn't mean to say Gecko was the only driver. Of course crates should consider the needs of everyone who depends on them. I just wanted to say we're planning to update Gecko's minimum more frequently, so that doesn't have the a limiting factor.

@behnam
Copy link
Contributor

behnam commented Jun 30, 2017

(I'm new to Rust-Gecko and related projects, so it may be obvious, so asking anyway.)

Based on this fact that Gecko is not the only driver, I assume these libraries can move at their own pace and only increase the minimum-rustc-version as needed. Then, if so, was there any need for this diff in the Rust-Gecko build process?

@mbrubeck
Copy link
Contributor

mbrubeck commented Jul 1, 2017

No, this was just a cleanup. It removed code that was previously necessary to support the version of Rust used in Gecko.

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.

5 participants