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

[DNM] Resharper cleanup #2283

Closed
wants to merge 8 commits into from
Closed

Conversation

nschonni
Copy link
Collaborator

@nschonni nschonni commented Jan 3, 2017

Through the base through ReSharper to see what it could come up with. There is some other stuff, but this was the simplest pieces to see if there is an interest.

@mgreter
Copy link
Contributor

mgreter commented Jan 5, 2017

Looks fine for me. I actually expected some warnings in clang or gcc, but they all seem to agree. Not sure if some older compilers will warn missing return when a throw is in place. But CI seems to agree here!

@nschonni
Copy link
Collaborator Author

nschonni commented Jan 5, 2017

@mgreter I left all the commits discrete if you want to cherrypick parts, or I can fastforward the branch with the latest.
PS: There were more warnings, these where just the simple stuff

@xzyfer
Copy link
Contributor

xzyfer commented Jan 5, 2017 via email

@xzyfer
Copy link
Contributor

xzyfer commented Jan 26, 2017

@nschonni there has been a lot of churn on master. Want to give this another shot?

@nschonni
Copy link
Collaborator Author

@xzyfer you mentioned you wanted to cherry-pick some stuff. I can do specific PRs for the parts if you call them out here

@xzyfer
Copy link
Contributor

xzyfer commented Jan 26, 2017 via email

@am11
Copy link
Contributor

am11 commented Jan 30, 2017

Nice cleanup! 👍

Related to this, would it be a good idea to have .clang-format rules file like this and make TravisCI do the linting based on the clang-format per PR like these guys are doing? Then in our contribution guide, we can say something this effect:

To avoid build failures due to code formatting, make sure to run .clang-format before issuing the pull request. On Windows, you can use Clang-Format extension for VS.

@nschonni
Copy link
Collaborator Author

Rebased, but I'm going to need to go back and redo some stuff because of the switch to using Cast

@nschonni nschonni changed the title Resharper cleanup [DNM] Resharper cleanup Jan 30, 2017
@xzyfer
Copy link
Contributor

xzyfer commented Jan 30, 2017

@am11 omg I've been dreaming about something like .clang-format. I couldn't find docs on a prevailing convention or tool for this stuff.

@@ -9,8 +9,6 @@ namespace Sass {
// throw a runtime error if this happens
// we want a well defined set of possible nodes
throw std::runtime_error("invalid node for to_value");
// mute warning
Copy link
Contributor

Choose a reason for hiding this comment

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

Interestingly there seems to have been a reason for these superflous returns ...

@mgreter
Copy link
Contributor

mgreter commented Feb 4, 2017

Rebased and cherry picked in #2316

@mgreter
Copy link
Contributor

mgreter commented Feb 4, 2017

Closing this as most has been merged with #2316. Thanks @nschonni!

@mgreter mgreter closed this Feb 4, 2017
@nschonni nschonni deleted the resharper-cleanup branch June 2, 2017 05:16
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