-
Notifications
You must be signed in to change notification settings - Fork 82
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
[FEATURE] Serialise index cursor #2048
Conversation
Header test failed:
(An include is missing for |
96e7e33
to
c762759
Compare
Codecov Report
@@ Coverage Diff @@
## master #2048 +/- ##
==========================================
- Coverage 97.93% 97.89% -0.04%
==========================================
Files 267 263 -4
Lines 9985 9899 -86
==========================================
- Hits 9779 9691 -88
- Misses 206 208 +2
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.
Minor stuff
|
||
/*!\cond DEV | ||
* \brief Serialisation support function. | ||
* \tparam archive_t Type of `archive`; must satisfy seqan3::cereal_archive. |
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.
* \tparam archive_t Type of `archive`; must satisfy seqan3::cereal_archive. | |
* \tparam archive_t Type of `archive`; must model seqan3::cereal_archive. |
💅
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.
We use satifsy
in every serialisation method (~12 times). Can I do this as separated PR?
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.
sure
|
||
/*!\cond DEV | ||
* \brief Serialisation support function. | ||
* \tparam archive_t Type of `archive`; must satisfy seqan3::cereal_archive. |
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.
* \tparam archive_t Type of `archive`; must satisfy seqan3::cereal_archive. | |
* \tparam archive_t Type of `archive`; must model seqan3::cereal_archive. |
|
||
/*!\cond DEV | ||
* \brief Serialisation support function. | ||
* \tparam archive_t Type of `archive`; must satisfy seqan3::cereal_archive. |
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.
* \tparam archive_t Type of `archive`; must satisfy seqan3::cereal_archive. | |
* \tparam archive_t Type of `archive`; must model seqan3::cereal_archive. |
*/ | ||
template <cereal_archive archive_t> | ||
void CEREAL_SERIALIZE_FUNCTION_NAME(archive_t & archive) | ||
{ |
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.
Since this function is not visible to the user, we should mention this in the class documentation. I think we might just used \imlements cerealisable
or something similar.. Can you check other classes?
Also Can you add a changelog entry, since this seems to be of interest to users :)
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.
Yes, but then I would also rebase this against the release branch?
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.
Since this function is not visible to the user, we should mention this in the class documentation. I think we might just used
\imlements cerealisable
or something similar.. Can you check other classes?
Yes, it would be great to see directly in the documentation which classes can be serialized with cereal, I had to study the code to see that neither cerealisation is possible, nor I can access the members on my own. I guess adding something like \implements cerealisable
would be perfectly suitable for this.
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.
Currently the documentation is only reflected in the inheritance diagram as far as I can see, https://docs.seqan.de/seqan/3-master-user/interfaceseqan3_1_1cerealisable.html
We should rework this
c762759
to
8032f8c
Compare
I'll squash and push in the hope that travis notices something |
8032f8c
to
e5bb2bb
Compare
e5bb2bb
to
7f46653
Compare
I forgot about it again 🙈 Sorry |
Resolves #2044