-
Notifications
You must be signed in to change notification settings - Fork 79
Add options flags to string setters #1990
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
Add options flags to string setters #1990
Conversation
|
Ah, I'd forgotten about the update case where we want to pass ownership of a large string to the table. This is easy to do, and definitely requires the options flag, so it's a done-deal that we need this. I'll update later. |
|
Adding options to |
|
I was thinking the same thing... |
a14abb4 to
26babdb
Compare
|
OK, I think this is ready to go - might was well get the messy stuff out of the way before starting on #2006. |
|
Oops, needs a CHANGELOG entry... |
26babdb to
959a028
Compare
Codecov Report
@@ Coverage Diff @@
## main #1990 +/- ##
=======================================
Coverage 93.35% 93.35%
=======================================
Files 27 27
Lines 25521 25522 +1
Branches 1111 1111
=======================================
+ Hits 23826 23827 +1
Misses 1660 1660
Partials 35 35
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
d2b08a2 to
959a028
Compare
|
Ugh, maybe we don't want to do this. As noted in #2006 (comment) we'll have to drop all the const qualifiers in the signatures if we do it this way, which is particularly annoying when dealing with literal strings. Maybe we should have a separate set of methods instead? |
|
Closed in favour of "takeset" methods, #2016 |
Closes #1979
The idea of this was to open the ground for #1977, but I'm having second thoughts now because the
x_table_set_columnsdoesn't have an options value (which I forgot).I guess we could add an option to
tsk_x_table_init(table, options)which is likeTSK_EXTERNAL_MEMORYor something, which flicks a switch were we store pointers inset_columnsandset_metadata_schema,set_reference_sequence_dataetc. So then, we don't need these options values.I guess the alternative is to add
optionsto all thex_tables_set_columns.Any thoughts @benjeffery?