-
Notifications
You must be signed in to change notification settings - Fork 122
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
Add FSIM and FSIMc #109
Add FSIM and FSIMc #109
Conversation
Codecov Report
@@ Coverage Diff @@
## master #109 +/- ##
==========================================
+ Coverage 88.81% 89.78% +0.96%
==========================================
Files 17 18 +1
Lines 1421 1546 +125
==========================================
+ Hits 1262 1388 +126
+ Misses 159 158 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great PR! From my point of view the quality of your code increased dramatically during the last several months. There are just a few small corrections but overall is seems to be ready unless @denproc has some comments.
I see that you added lots of comments in this PR. In general, it is a very good thing. For the educational purposes I want to point out the following thing.
People always forget to change comments/docs when they change code just because it does not effect functionality and thing work fine, tests pass. At the same time, unchanged comment may be extremely confusing for a newcomer trying to understand your implementation. It is often to better have a code without any comments than with some wrong ones.
So the general rule of thumb is to write your code in a way that it is self-explanatory and understandable without any comments. It is absolutely clear that sometimes things are complicated by their nature and if you explain it you are doing a great job. From the other hand, you should always write comments with caution. Great majority of times when you write a comment it just means that you just failed to create a descriptive variable/class/function name or your fancy one-liner does too much stuff. If the code was less dense it would be easier to understand even without any comments.
No particular actions are required here. Just keep it in mind when you implement some new stuff 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, a lot of new insights.
Kudos, SonarCloud Quality Gate passed!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job @zakajd !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, merging
Closes #104
Proposed Changes
Not ready yet. Tests are still in progress