Relax memctx closures from Fn to FnOnce #390
Merged
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.
While working on #230 I was trying to use
pgx::memcxt::PgMemoryContexts::exec_in_context
andpgx::memcxt::PgMemoryContexts::switch_to
and realized they usedFn
overFnOnce
.This means that closures using it:
Would get errors like: "cannot move out of
internal
, a captured variable in anFn
closure`"This should not break anything for users, as it's a general relaxation.
FnOnce
: https://doc.rust-lang.org/std/ops/trait.FnOnce.htmlFn
: https://doc.rust-lang.org/std/ops/trait.Fn.htmlNotably: