I think you could use fn(Size) -> Size in the added variant to avoid the Arc, since Position::SpecificWith also just uses a function pointer (which is Send, Sync and Copy)

I think you could use fn(Size) -> Size in the added variant to avoid the Arc, since Position::SpecificWith also just uses a function pointer (which is Send, Sync and Copy)

I did in the original PR, but for the tester I need to support closures, since I need to make the window wider than it would otherwise be:

The only other solution I could think of, would be to ignore the variable window size when the tester is used.
Maybe you have a better idea?

Hmm

You could add an extra field to the variant which contains extra size, but that could make it a bit confusing to use, or just plain ugly.

Hmm

You could add an extra field to the variant which contains extra size, but that could make it a bit confusing to use, or just plain ugly.

The current API isn't really all user friendly either.
I added a helper function, but the enum variant is still there and requires a manual Arc.
It's not obvious you should use the helper.

@pml68 What do you think about creating a wrapper struct to hide the enum variants?
Then I'd just expose helper functions and nothing else.
That way I wouldn't expose any weird enum variants.

pub struct Size( pub(crate) SizeVariant)

Not sure these enum in struct types fir with the iced style.

@pml68 What do you think about creating a wrapper struct to hide the enum variants? Then I'd just expose helper functions and nothing else. That way I wouldn't expose any weird enum variants.

pub struct Size( pub(crate) SizeVariant)

Hmm not sure honestly. I can't really think of a better way, but I wonder what Héctor would think about the proposed solutions (user has to Arc / hidden enum / some other solution to the test recorder-size adding problem)