search for: gettypelocclass

...ev: what should we do to fix this? I don't think it's helpful > >>> to add machinery to llvm::cast to handle concrete type conversion, so > >>> I think we should consider a non-llvm::cast solution for this > >>> hierarchy. Replace the llvm::isa calls with getTypeLocClass calls (or > >>> a separate wrapper for that) & add a SpecificTypeLoc(const TypeLoc&) > >>> ctor for every specific TypeLoc that has an appropriate assert & calls > >>> up through to the base copy ctor. It'll be a fair bit of code to add > >&...

...uld we do to fix this? I don't think it's helpful >> >>> to add machinery to llvm::cast to handle concrete type conversion, so >> >>> I think we should consider a non-llvm::cast solution for this >> >>> hierarchy. Replace the llvm::isa calls with getTypeLocClass calls (or >> >>> a separate wrapper for that) & add a SpecificTypeLoc(const TypeLoc&) >> >>> ctor for every specific TypeLoc that has an appropriate assert & calls >> >>> up through to the base copy ctor. It'll be a fair bit of code to ad...

...) >> >> Clang Dev: what should we do to fix this? I don't think it's helpful >> to add machinery to llvm::cast to handle concrete type conversion, so >> I think we should consider a non-llvm::cast solution for this >> hierarchy. Replace the llvm::isa calls with getTypeLocClass calls (or >> a separate wrapper for that) & add a SpecificTypeLoc(const TypeLoc&) >> ctor for every specific TypeLoc that has an appropriate assert & calls >> up through to the base copy ctor. It'll be a fair bit of code to add >> to TypeLoc, but nothing comp...

...gt;> Clang Dev: what should we do to fix this? I don't think it's helpful >>> to add machinery to llvm::cast to handle concrete type conversion, so >>> I think we should consider a non-llvm::cast solution for this >>> hierarchy. Replace the llvm::isa calls with getTypeLocClass calls (or >>> a separate wrapper for that) & add a SpecificTypeLoc(const TypeLoc&) >>> ctor for every specific TypeLoc that has an appropriate assert & calls >>> up through to the base copy ctor. It'll be a fair bit of code to add >>> to TypeLoc,...

...fix this? I don't think it's helpful >>> >>> to add machinery to llvm::cast to handle concrete type conversion, so >>> >>> I think we should consider a non-llvm::cast solution for this >>> >>> hierarchy. Replace the llvm::isa calls with getTypeLocClass calls (or >>> >>> a separate wrapper for that) & add a SpecificTypeLoc(const TypeLoc&) >>> >>> ctor for every specific TypeLoc that has an appropriate assert & calls >>> >>> up through to the base copy ctor. It'll be a fair bit o...