27 Nov
2013
27 Nov
'13
3:20 p.m.
On 26 November 2013 09:24, DeadMG
Enabling this variety of any_cast would substantially improve the composability of boost::any. For example, it's arguable that std::function is merely boost::any but with additional interface requirements.
Well, they both use type erasure. I don't see how this exception trick helps, though.
With such an any_cast enhancement, it would be quite trivial to compose std::function implementations or similar concepts on top of boost::any.
Do you have a prototype implementation somewhere that we can look at? -- Nevin ":-)" Liber mailto:nevin@eviloverlord.com (847) 691-1404