Parametric TLS for read transactions #300
Open
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 PR introduces a breaking change to the
RoTxn
type, allowing it to be eitherSend
or!Send
without toggling a feature flag. This is useful when using both sendable and non-sendableRoTxn
s in the same application. Non-sendableRoTxn
s are known to be faster as they require less to no allocation.To Do
EncryptedEnv
.WithTls
andWithoutTls
type parameters.WithoutTls
makesRoTxn
Send andWithTls
makes them!Send
.Env
and that it follows the following rules.RoTxn
by using themdb_txn_reset
function.