-
Notifications
You must be signed in to change notification settings - Fork 168
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
RUST-2097 Migrate from derivative
to derive-where
#1245
Conversation
crypt: Crypt, | ||
exec: CryptExecutor, | ||
internal_client: Option<Client>, | ||
_internal_client: Option<Client>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got a dead code lint error for this field when I switched the Debug
impl on the struct, but deleting it caused errors 🤔 I think something else is holding a weak reference to it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CryptExecutor
holds a WeakClient
, so that's probably it. I vaguely recall that it's weak because whether it's using internal_client
or a user-supplied Client
depends on whether the context is implicit or explicit encryption, and if it's user-supplied we don't want to hold a strong reference and keep it alive longer than the user expects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
crypt: Crypt, | ||
exec: CryptExecutor, | ||
internal_client: Option<Client>, | ||
_internal_client: Option<Client>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CryptExecutor
holds a WeakClient
, so that's probably it. I vaguely recall that it's weak because whether it's using internal_client
or a user-supplied Client
depends on whether the context is implicit or explicit encryption, and if it's user-supplied we don't want to hold a strong reference and keep it alive longer than the user expects.
Can you file a ticket so we remember to do this? |
derivative
to derive-where
derivative
to derive-where
Can we make a minor release of this |
@TroyKomodo 3.1.1 was just released! |
Migrates from
derivative
toderive-where
. In the long term, I'd like to switch over toderive_more
, which we already depend on for someDisplay
-related utilities.derive_more
has the largest feature set of crates of its ilk; however, its MSRV for the features we'd need is 1.75 (compared to our current 1.67), and it does not yet supportPartialEq
. We can make the swap once those concerns are resolved. This is tracked in RUST-2102.