Consider the attached typesystem snippet. It contains a number of intentional errors, but nonetheless generates code that can compile successfully.
This illustrates a limitation of container conversions; at least w.r.t. the target-to-native conversions, only the first conversion is processed, and the 'type' and 'check' parameters of the conversion are ignored.
This is a problem for me as I am trying to define a target-to-native conversion for PySet to std::set, but it is not possible to due so as of Shiboken 1.1.2, as the 'set' container type hard-codes only accepting PySequence as input type.