You are not going to have anyway a link<Object>. That makes it fine to
resolve a
link<Block> and a link<Device> according to different rules.
I think we agreed (in IRC) that we can handle this by changing
qdev_resolve_path() to take an optional TYPE argument which will cause
qdev_resolve_path() to only succeed if the resulting object implements
TYPE.
This can be used to disambiguate partial path matches such that a
link<BlockDriverState> property would only attempt to do partial path
resolutions on objects that have BlockDriverState in their parent
hierarchy.