[WIP] feat(rust): Let the returned RecordBatchReader outlive & parameters #2693
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.
This is a draft PR showing a problem with the annotations of functions that return
impl RecordBatchReader
and take&
paramemeters.The first commit shows how I work around it. When I try to make a Box'd
RecordBatchReader
, the compiler complains because there is a possibility that theimpl RecordBatchReader
returned might be holding any of&
passed in the parameters:When I'm forced to be explicit about lifetimes, I end up with:
This is not ideal because I don't want to tie the lifetime of
table_name: Option<&'a str>
to the lifetime of the returnedRecordBatchReader
.So I believe the proper solution is to change the
adbc_core
traits to explicitly declare that theRecordBatchReader
can outlive the input references. Like this:allowing a wrapper that boxes the
RecordBatchReader
to be written as