Hello Joaquín,

I would like to make a proposal for additional feature of optionaly making multi-index container non-copyable (via copying policy class). The same way as a user can decide which indicies to use she/he could specify whether the new data-structure should be copyable or not. In my case I was assuming to pass container by reference, but it was copied by some function object. Which produced despite the performane issue wrong results. Using the non-copyable policy I would simply get a compiler error.


With Kind Regards,
Ovanes