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 compiler warnings #6

Merged
merged 3 commits into from
Jan 4, 2018
Merged

Fix compiler warnings #6

merged 3 commits into from
Jan 4, 2018

Conversation

hmenke
Copy link
Contributor

@hmenke hmenke commented Jan 3, 2018

The code caused several compiler warnings, which I fixed.
I also added more warning levels to the CMake file.
On top of that I specified -Werror to prevent the introduction of new warnings.

The code can be automatically built and tested on Travis CI.
Code coverage is automatically determined and uploaded to CodeCov.

Optionally you can add these badges to your README.
Build status Code coverage report
Those badges of course point to my repo, below is the markdown you'd have to insert for your own.

[![Build status](https://travis-ci.org/valandil/wignerSymbols.svg?branch=master)](https://travis-ci.org/valandil/wignerSymbols)
[![Code coverage report](https://codecov.io/gh/valandil/wignerSymbols/branch/master/graph/badge.svg)](https://codecov.io/gh/valandil/wignerSymbols)

@joeydumont joeydumont merged commit 337dd7e into joeydumont:master Jan 4, 2018
@joeydumont
Copy link
Owner

Thanks for this!

Removing the arrays and exclusively using std::vector is a good idea. I have no clue why I wrote it like that back then.

@hmenke
Copy link
Contributor Author

hmenke commented Jan 4, 2018

To activate Travis CI and CodeCov, just go to https://travis-ci.org/ and https://codecov.io/ and login with your GitHub account. Then on Travis CI you have to activate the wignerSymbols repository but CodeCov will just work out-of-the-box.

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.

None yet

2 participants