Clean up compiler warnings #129

New issue

Closed

opened 2018-04-25 22:27:10 +02:00 by shyba · 2 comments

shyba commented

2018-04-25 22:27:10 +02:00

(Migrated from github.com)

During compilation I'm getting a lot of warnings and most of them aren't relevant. We should at some point clean them up so its easier to read.
Another idea was to add a linter, but I'm undecided on which one, so I will leave that open and let us start by cleaning the noise instead.

During compilation I'm getting a lot of warnings and most of them aren't relevant. We should at some point clean them up so its easier to read. Another idea was to add a linter, but I'm undecided on which one, so I will leave that open and let us start by cleaning the noise instead.

BrannonKing commented

2018-08-01 19:34:28 +02:00

(Migrated from github.com)

Waiting on #174

BrannonKing commented

2019-03-09 00:33:07 +01:00

(Migrated from github.com)

I feel like this should be the standard:
-Wall -Wextra -Wno-implicit-fallthrough -Wno-unused-parameter
Right now, that much works on the post-merged code.

I feel like this should be the standard: `-Wall -Wextra -Wno-implicit-fallthrough -Wno-unused-parameter` Right now, that much works on the post-merged code.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#129

No description provided.

Rows
Columns