-
Notifications
You must be signed in to change notification settings - Fork 467
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
[DNM] Resharper cleanup #2283
Conversation
2625e33
to
633649c
Compare
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! |
@mgreter I left all the commits discrete if you want to cherrypick parts, or I can fastforward the branch with the latest. |
There are bits and pieces I'll cherry-pick onto to master. I'll take care
of it this weekend. Thanks Nick.
Regards,
Michael
…On Fri, Jan 6, 2017 at 10:43 AM, Nick Schonning ***@***.***> wrote:
@mgreter <https://github.com/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
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2283 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWIpWJiuiKyPnYindMGpSaVsY4zmPks5rPYAQgaJpZM4LaIxy>
.
|
@nschonni there has been a lot of churn on master. Want to give this another shot? |
@xzyfer you mentioned you wanted to cherry-pick some stuff. I can do specific PRs for the parts if you call them out here |
On my phone now. Iirc my main gripe was with renaming variables like lhs
and rhs with have a semantic meaning and make the code easier to reason
about.
On 26 Jan. 2017 2:27 pm, "Nick Schonning" <[email protected]> wrote:
@xzyfer <https://github.com/xzyfer> you mentioned you wanted to cherry-pick
some stuff. I can do specific PRs for the parts if you call them out here
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2283 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWEf3TO93X7vtYPiHAdHyl3QE5kk2ks5rWBKNgaJpZM4LaIxy>
.
|
Nice cleanup! 👍 Related to this, would it be a good idea to have
|
Primarily "break" after a return statement that might be intended for style reasons.
633649c
to
b05491b
Compare
Rebased, but I'm going to need to go back and redo some stuff because of the switch to using |
@am11 omg I've been dreaming about something like |
@@ -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 |
There was a problem hiding this comment.
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 ...
Rebased and cherry picked in #2316 |
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.