search for: callbaseparent

...ght be nicer, but the confusion with the > *existing* type seems much more problematic. I think that we should take whatever name we like the best. Out-of-tree code will fail to compile after the change either way and will require fixing. That having been said, we already have a CallBase (and a CallBaseParent), they're just not part of the classof hierarchy, and using CallBase seems consistent with our other class names.  -Hal > > > Assuming folks are happy with this direction, are there any > incremental patches that folks would like to see in pre-commit review? > I've only don...

Going to keep this RFC short and to the point: TerminatorInst doesn't pull its weight in the type system. There is essentially a single relevant API -- iterating successors. There is no other interesting aspect shared -- the interface itself just dispatches to specific instructions to be implemented. On the flip side, CallInst and InvokeInst have *massive* amounts of code shared and struggle