I have currently worked around the issue by changing the order of conditions in
my code so just testing for DefiniteHOW and SubsetHOW first. But generally it
arose from a need to determine base type of a typed attribute. Because there is
common method for this each particular case must be consid
Vadim wrote:
> BTW, while researching the core sources I discovered a potential problem
with DefiniteHOW and SubsetHOW. They both define their own find_method()
which is re-delegating to their base type HOW.find_method. But they don't
support named parameters. Combined with classes with FALLBACK t
