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

Compile warnings #69

Open
DoumanAsh opened this issue Jan 9, 2018 · 4 comments
Open

Compile warnings #69

DoumanAsh opened this issue Jan 9, 2018 · 4 comments

Comments

@DoumanAsh
Copy link
Contributor

While porting I noticed quite high amount of compile warnings.

What is your stance on it?
Should it be eventually fixed?

@eiennohito
Copy link
Contributor

What kind of warnings?

There could be signed-unsigned conversion/comparison warnings over the place.

g++/clang builds on macos/linux are (mostly) warning-free with -Wall.

One place is the usage of tmpfile in tests, but it is safe and actually should be that way.
Let's setup a windows CI and look around the warnings.

@DoumanAsh
Copy link
Contributor Author

One of these warnings are signed-unsigned conversion yes. It seems to be on by default for Windows.

We can I guess tune warnings for windows too.
And maybe turn of "unsafe" function warnings and then take a look.

@eiennohito
Copy link
Contributor

Ah, unsafe Windows CRT functions. I see.
Need to setup a windows environment and see the warnings for myself as it seems.

@eiennohito
Copy link
Contributor

eiennohito commented Jan 11, 2018

On warnings:

(I will update this list)

Ignore:

  • Everything from jumanpp_rnn_legacy
  • C4141 (inline used more than once)

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

No branches or pull requests

2 participants