[MISC] Use vector for arguments #239
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
eseiler
force-pushed
the
misc/vector_ctor
branch
from
a885d22 to
c5eefaa
Compare
seqan-actions
added
lint
eseiler
force-pushed
the
misc/vector_ctor
branch
from
c5eefaa to
bb67f43
Compare
seqan-actions
added
lint
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #239 +/- ##
==========================================
+ Coverage 91.90% 91.94% +0.04%
==========================================
Files 17 17
Lines 1618 1627 +9
==========================================
+ Hits 1487 1496 +9
Misses 131 131 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am pretty much making this change in all my PRs. So let's make it a separate PR :)
I will make a follow-up issue after merge with things that need to be decided once we resolved the other PRs: