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

Fix explanation of Cargo's behavior #25141

Merged
merged 1 commit into from
May 7, 2015

Conversation

steveklabnik
Copy link
Member

`update`, which says ‘ignore the lock, figure out all the latest versions that
fit what we’ve specified. If that works, write those versions out to the lock
file’.
file’. But, by default, Cargo will only look for versions larger than `0.3.0`
and smaller than `0.4.0`. If we want to move to `0.4.x`, we’d have to update
Copy link
Member

Choose a reason for hiding this comment

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

Worth mentioning semver/breaking changes in here somewhere?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not 100% sure. I'm so used to explaining every detail that this higher-level, ignore-the-details stuff is hard for me. I'm still trying to figure out what belongs and what doesn't.

Let's consider adding this kind of thing once the API evolution RFC lands.

@huonw
Copy link
Member

huonw commented May 6, 2015

r=me once the comment has been considered (doesn't have to be accepted).

@steveklabnik
Copy link
Member Author

@bors: r=huonw rollup

@bors
Copy link
Contributor

bors commented May 6, 2015

📌 Commit fc9bc77 has been approved by huonw

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.

3 participants