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

[MISC] rename align_cfg::scoring to align_cfg::scoring_scheme #2027

Merged
merged 1 commit into from
Aug 19, 2020

Conversation

wvdtoorn
Copy link
Contributor

@wvdtoorn wvdtoorn requested review from a team and joergi-w and removed request for a team August 12, 2020 11:40
Copy link
Member

@joergi-w joergi-w left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work, thank you! I found only some style errors.

And what becomes a bit confusing/unintuitive is the distinction:

  • seqan3::scoring_scheme is a concept
  • seqan3::align_cfg::scoring_scheme is a class template for types that model seqan3::scoring_scheme.

@codecov
Copy link

codecov bot commented Aug 13, 2020

Codecov Report

Merging #2027 into release-3.0.2 will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@              Coverage Diff               @@
##           release-3.0.2    #2027   +/-   ##
==============================================
  Coverage          97.89%   97.89%           
==============================================
  Files                263      263           
  Lines               9879     9879           
==============================================
  Hits                9671     9671           
  Misses               208      208           
Impacted Files Coverage Δ
...e/seqan3/alignment/pairwise/detail/type_traits.hpp 100.00% <ø> (ø)
.../seqan3/alignment/pairwise/alignment_algorithm.hpp 98.50% <100.00%> (ø)
...qan3/alignment/pairwise/alignment_configurator.hpp 100.00% <100.00%> (ø)
...lignment/pairwise/detail/policy_scoring_scheme.hpp 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 89df8c8...856c9f8. Read the comment docs.

@wvdtoorn wvdtoorn requested a review from joergi-w August 13, 2020 19:41
@wvdtoorn
Copy link
Contributor Author

wvdtoorn commented Aug 13, 2020

@joergi-w thank you for pointing all the files out, I'm sorry to have overlooked the indentation shifts.
As for the naming concerns, that is a good observation (@seqan/core).

Copy link
Member

@joergi-w joergi-w left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks 👍

@joergi-w joergi-w requested review from a team and smehringer and removed request for a team August 14, 2020 05:44
@rrahn
Copy link
Contributor

rrahn commented Aug 14, 2020

We need to rename the scoring_scheme concept to scoring_scheme_for in order to reflect the concept naming rules of the standard. The rational is that scoring_scheme_for requires an additional type to check for. So I think we can keep the align_cfg naming as is.

@wvdtoorn
Copy link
Contributor Author

Rebased as requested to avoid some mess with the align_cfg::detail namespace (#2020), and cleaned up the commit history.

Copy link
Member

@smehringer smehringer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

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

Successfully merging this pull request may close these issues.

4 participants