Closed richelbilderbeek closed 5 years ago
I see in the code:
return; //!OCLINT I don't know an alternative;
i = n; j = n;
OCLint will complain, as the second line is never call. I think the return
can be safely removed...
Remember: all tests should keep passing :+1:
nonononononono, that caused a bug remember. Make sure you don't break anything
Op vr 3 mei 2019 17:58 schreef Richel Bilderbeek notifications@github.com:
I see in the code:
return; //!OCLINT I don't know an alternative; i = n; j = n;
OCLint will complain, as the second line is never call. I think the return can be safely removed...
Remember: all tests should keep passing 👍
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/richelbilderbeek/djog_unos_2018/issues/562#issuecomment-489147985, or mute the thread https://github.com/notifications/unsubscribe-auth/AG7ZHEU4TEH2M7BMKQMNSVDPTROK7ANCNFSM4HG3HBOQ .
Is your feature request related to a problem? Please describe.
Currently, we have:
This can be cleaned up:
Describe the solution you'd like
return
byi = n; j = n;
, which causes ending all for loops. There is an error in my suggestion, find one of the multiple ways to do so. Remove the OCLint//!OCLINT must simplify
iff accepted by OCLintAll tests must pass.
Describe alternatives you've considered
None.
Additional context
None.