Closed dionhaefner closed 2 years ago
Hi, I agree, and I think changing it is a good Idea, since the bugfix is trivial for the API is remaining unchanged otherwise. This is currently implemented in PR as part of a code cleanup effort and waiting for approval. https://github.com/delve-team/delve/pull/63
I wonder if
CheckLayerSat
is really the best name for your main tracker object. The imperative sounds more like a function name to me, andSat
is so overloaded that it's not obvious what it stands for. I would probably use something likeSaturationTracker
or so.But I understand that changing names in the public API can be a pain, so if you insist to keep it that's fine with me.
(This is a part of the ongoing review at openjournals/joss-reviews#3992)