Skip to content

Conversation

@rrahn
Copy link
Contributor

@rrahn rrahn commented Jul 16, 2024

Further constraints the conversion constructors of the nucleotide and aminoacid base alphabet types to only consider conversion if all requirements are fulfilled. This is now represented by the specific concept convertable_to_through_char_representation.
Through this proxy types will not be converted through their char representation but will be implicitly converted to their underling base alphabet type, e.g. dna4, and then copied/moved using the copy/move constructor of the underlying base alphabet type.

Fixes #3264
Fixes #3267

rrahn added 2 commits July 16, 2024 14:55
… `seqan3::bitpacked_sequence`. seqan#3264

Further constraints the conversion constructors of the nucleotide and aminoacid base alphabet types to only consider conversion if all requirements are fulfilled. This is now represented by the specific concept `convertable_to_through_char_representation`.
Through this proxy types will not be converted through their char representation but will be implicitly converted to their underling base alphabet type, e.g. dna4, and then copied/moved using the copy/move constructor of the underlying base alphabet type.
@vercel
Copy link

vercel bot commented Jul 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
seqan3 ✅ Ready (Inspect) Visit Preview Jul 16, 2024 5:39pm

@rrahn rrahn requested a review from eseiler July 16, 2024 13:10
@seqan-actions seqan-actions added the lint [INTERNAL] signal for linting label Jul 16, 2024
@seqan-actions seqan-actions removed the lint [INTERNAL] signal for linting label Jul 16, 2024
@seqan-actions seqan-actions added lint [INTERNAL] signal for linting and removed lint [INTERNAL] signal for linting labels Jul 16, 2024
Copy link
Member

@eseiler eseiler left a comment

Choose a reason for hiding this comment

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

Do you have an opinion regarding #3267 (comment) ?

Comment on lines +7 to +8
#include <vector>

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
#include <vector>

Needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well, I am using a std::vector. It might be included by the helper.hpp already. Not including it has the potential that if some other code is refactored this test might not compile anymore since vector is not included through some dependent includes. Adding it makes clear, that I need it in the test.
But frankly, I don't care too much. What is the preferred policy here?

Copy link
Member

Choose a reason for hiding this comment

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

Ah, didn't see the result_t. It's fine then

@rrahn
Copy link
Contributor Author

rrahn commented Jul 16, 2024

Do you have an opinion regarding #3267 (comment) ?

I answered on the issue page.

@seqan-actions seqan-actions added lint [INTERNAL] signal for linting and removed lint [INTERNAL] signal for linting labels Jul 16, 2024
@rrahn rrahn requested a review from eseiler July 16, 2024 17:38
@eseiler eseiler merged commit 69284e8 into seqan:main Jul 16, 2024
@rrahn rrahn deleted the fix/issue_3264 branch July 17, 2024 07:11
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.

Alphabet conversion is not properly constrained Question regarding the usage of seqan3::fm_index_cursor using seqan3::bitpacked_sequence.

3 participants