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 gazillions of ICC warnings. #7253

Merged
merged 1 commit into from Jan 19, 2015
Merged

Conversation

ktf
Copy link
Contributor

@ktf ktf commented Jan 17, 2015

  • const type qualifier on basic return type is meaningless.

- const type qualifier on return type is meaningless.
@cmsbuild cmsbuild added this to the Next CMSSW_7_4_X milestone Jan 17, 2015
@Dr15Jones
Copy link
Contributor

Actually, const on some return values is useful. It keeps one from doing

foo().bar = 3;

and stops

auto & f = foo();
f.bar =3;

Which may help with the semantics of the code to avoid cases where you think you are changing the internals of foo but in reality you are not.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @ktf (Giulio Eulisse) for CMSSW_7_4_X.

Fix gazillions of ICC warnings.

It involves the following packages:

SimG4Core/Application

@cmsbuild, @civanch, @nclopezo, @mdhildreth can you please review it and eventually sign? Thanks.
@makortel this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.

@ktf
Copy link
Contributor Author

ktf commented Jan 17, 2015

I think icc complains only about basic scalar types (and my pr only fixes
those). In that case what you say does not apply (since there are no
internals) . Do you want me to amend the commit message or you still think
my pr (and icc) is wrong?
On Sat 17 Jan 2015 at 17:01 Chris Jones notifications@github.com wrote:

Actually, const on some return values is useful. It keeps one from doing

foo().bar = 3;

and stops

auto & f = foo();
f.bar =3;

Which may help with the semantics of the code to avoid cases where you
think you are changing the internals of foo but in reality you are not.


Reply to this email directly or view it on GitHub
#7253 (comment).

@civanch
Copy link
Contributor

civanch commented Jan 17, 2015

+1
I believe these method signatures are historical...

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes or unless it breaks tests.

@ktf
Copy link
Contributor Author

ktf commented Jan 17, 2015

please test

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes (tests are also fine). This pull request will be automatically merged.

cmsbuild added a commit that referenced this pull request Jan 19, 2015
Fix gazillions of ICC warnings.
@cmsbuild cmsbuild merged commit 0a8fafc into cms-sw:CMSSW_7_4_X Jan 19, 2015
@cmsbuild
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants