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

Update compiler error 0034 to use new format. #35959 modified #36009

Closed
wants to merge 3 commits into from
Closed

Update compiler error 0034 to use new format. #35959 modified #36009

wants to merge 3 commits into from

Conversation

athulappadan
Copy link
Contributor

Part of #35233
Addresses #35205

I have updated the unit test to check for the labels and also removed the tab characters. As I am relatively new to contributing to open source projects, please make suggestions if I am not using git in the correct way.

r? @jonathandturner

@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jonathandturner (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@@ -241,7 +241,8 @@ impl<'a, 'gcx, 'tcx> FnCtxt<'a, 'gcx, 'tcx> {

MethodError::Ambiguity(sources) => {
let mut err = struct_span_err!(self.sess(), span, E0034,
"multiple applicable items in scope");
"multiple applicable items in scope");
Copy link
Member

@GuillaumeGomez GuillaumeGomez Aug 26, 2016

Choose a reason for hiding this comment

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

Why changing the indent?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh!, I did that unintentionally. Will recommit it.

Copy link
Member

Choose a reason for hiding this comment

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

You can commit then squash. It'll be faster. If you don't know how to squash, take a look here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry, that blog link is not loading.

Copy link
Member

Choose a reason for hiding this comment

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

Works fine for me. :-/

@athulappadan
Copy link
Contributor Author

Any more changes to be done..?

r? @jonathandturner

@sophiajt
Copy link
Contributor

@athulappadan - looks pretty close. Can you squash your git commits down from 3 commits to 1? You can read how with articles like http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html

@athulappadan
Copy link
Contributor Author

I am getting all kinds of errors while trying to squash and I am not able to figure it out myself. Seems like I have messed it up with my commits and merges. If possible, shall I open a fresh PR and finish the thing in one commit? (I think I need to spend some time to get a fix on how to use git properly)

r? @jonathandturner

@GuillaumeGomez
Copy link
Member

:-/

Go ask on IRC if possible. We can't merge like this.

@sophiajt
Copy link
Contributor

@athulappadan - yes, you can close this PR and open a new one if you need to. Getting used to squashing can take a little practice.

Something I like to do is to always use a branch for a specific PR. That way, if I ever need to update something, I can switch back to master, git pull in master, and then rebase into my branch. Since I rebase regularly, my changes are always at the top. When I want to squash, I can git log to get first commit in the list that isn't mine, git reset to that commit number, and then add everything back all at once.

Not sure if that helps you. It took me a while to get use to git and the techniques they use here, but after a while it gets easier.

@athulappadan
Copy link
Contributor Author

Earlier itself I thought of making a new branch but then I saw the line saying push against master branch. Now I will make a new branch and push the changes.

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.

4 participants