You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling clone is not a problem for types that implement copy, but for types that don't. Like TransactionSignature, it means that a clone operation always occurs, even when the caller has no need for ownership of the value and could have used a reference.
This has a performance cost and is overall a bad design for an API: the method should not assume anything about the caller intentions
The text was updated successfully, but these errors were encountered:
Calling clone is not a problem for types that implement copy, but for types that don't. Like
TransactionSignature
, it means that a clone operation always occurs, even when the caller has no need for ownership of the value and could have used a reference.This has a performance cost and is overall a bad design for an API: the method should not assume anything about the caller intentions
The text was updated successfully, but these errors were encountered: