search for: pureconstantvector

...> I wonder if the constant class hierarchy should not be revisited in light of this? > For instance you identified that some are local to a module while others are “context-wide”. > > I haven’t given too much thoughts about this, but I'm curious if you did? You mean something like PureConstantVector (which cannot transitively reference GlobalValue) vs ConstantVectorWithGlobalRef (which can/must transitively reference GlobalValue), right? (And also for ConstantStruct, ConstantArray, and ConstantExpr, etc.) I hadn't considered that, and it seems worth thinking about. I'm unsure whethe...

r261464 added a type called ConstantData to the Value hierarchy. This is a parent type for constants with no operands, such as i32 0 and null. Since then, I've removed most instances of iterating through the use-lists of an instance of ConstantData. I'd like to make this illegal. Since the users of ConstantData are spread across an LLVMContext, most code that looks at the users is