search for: r247253

...longer-term project. > > I'd like to see us move away from using always_inline in core ADT headers to make debugging easier in the near future. > +1 to everything you said. I happened to remember this wasn't always the case for StringRef, so I did some archeology and found: [llvm] r247253 - [ADT] Apply a large hammer to StringRef functions: attribute always_inline. I'm afraid I missed the commit at the time but there are few remarks I would like to make: 1) The motivation for this change, at least from what I understand, is trying to optimize `check-llvm`. As somebody who spend...

...to see us move away from using always_inline in core ADT headers to make debugging easier in the near future. >> > >> >> +1 to everything you said. I happened to remember this wasn't always >> the case for StringRef, so I did some archeology and found: >> [llvm] r247253 - [ADT] Apply a large hammer to StringRef functions: >> attribute always_inline. >> >> I'm afraid I missed the commit at the time but there are few remarks I >> would like to make: >> 1) The motivation for this change, at least from what I understand, is >> t...

Hello all! I find that using lldb to debug LLVM libraries can be super frustrating, because a lot of LLVM classes, like the constructor for StringRef, are marked LLVM_ATTRIBUTE_ALWAYS_INLINE. So when I attempt to have lldb evaluate an expression that implicitly instantiates a StringRef, I get 'error: Couldn't lookup symbols: __ZN4llvm9StringRefC1EPKc'. As an example, most recently