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
{{ message }}
This repository has been archived by the owner on Jun 8, 2021. It is now read-only.
Now that closures implement Copy and Clone
Does this mean we should be able to get rid of builder.clone() calls?
Would it be as simple as adding #[derive(Clone, Copy)] to the Builder struct?
The text was updated successfully, but these errors were encountered:
I didn't have one exactly. What I was wanting to do was be able to have the Builder struct implement the Clone trait, so we don't have to use a clone! macro or do .clone() calls on it.
I couldn't track down exactly where the Builder struct was in the gtk-rs source code, but the pseudo-code would look something like this:
gtk::Builder is already implementing Clone. It can't possibly implement Copy as that is only possible to derive and is limited to basic types and combinations of them.
Now that closures implement Copy and Clone
Does this mean we should be able to get rid of
builder.clone()
calls?Would it be as simple as adding
#[derive(Clone, Copy)]
to the Builder struct?The text was updated successfully, but these errors were encountered: