search for: aliasrelationship

...}; > > I find the "Alias" suffix redundant, but "No", "Maybe", "Partial", and "Must" also seem awkward. Is there a better enum name than "AliasKind"? These aren't *just* results, so I don't like the current name. > > AliasRelationship? None, May/PossiblyAliased/Unknown, Aliased, PartiallyAliased? > > (tense could use some tweaking and I suppose this still has the suffix problem in all except the "None" case... ) I like this colour: enum class AliasKind /* or AliasCategory? */ { Null, Unknown,...

...sistent anyway, then PartialAlias isn't all bad.) > That leaves the question of the enumeration name. I think "AliasResult" is my new found favorite. Danny gave me a reason: these are really results of a particular query, not just abstract kinds of aliasing... And its shorter than AliasRelationship. =] > > Thoughts? I don't really see how it's better than AliasKind, but I don't see anything wrong with it either.

Greetings all, I'm working on refactoring the alias analysis layers to remove the usage of analysis groups and make the logic sharable between old and new pass managers, and I have a couple of questions below. As background, the overall plan that I've discussed with Hal and a few others previously is as follows: - Create an AliasAnalysisManager which is provided by a normal analysis