Jonathan B. Coe

We're looking at adding a valueless_after_move state which is much easier to get into but invalid to access (other than to destroy/assign/query).

On slicing: Potential slicing by (incorrect) use of the pointer constructor will be picked up at run time and an exception of type `bad_polymorphic_value_construction` thrown. I'd like to better understand...

We need to see if the current design + allocators can do all that your SBO design can. As a perhaps irrelevant aside, Rust's mature and excellent [dyn_clone](https://github.com/dtolnay/dyn-clone) has no...

Re: "It seems more and more a weakness of the entire standardisation process that once a paper has been presented the only changes "allowed" are those called for by that...

Do you have use cases that you can share? Any extra experience/examples would be really useful.

Musing on this, these cast operators are impossible for users to add as they require access to internals of `polymorphic_value`. If there is a good motivating use case, then they...

Closing this issue in the absence of a motivating use case.

This may also be of interest: https://github.com/jbcoe/polymorphic_value polymorphic_value does const-propagation and deep copies. hth

@Twon pure oversight. Please go ahead.

Is this issue still a problem for anyone? If the suggested paths are already checked, I would recommend closing this issue.