Haojian Wu

Regarding the original request for `#pragma region` folding, it could be supported by the C++ language server clangd, but it is not implemented yet. Instead of relying on individual language...

> I think the basic_string_view and span recognition in Clang is probably going too far. For the other functions, we want to recognize them as builtins anyway for other reasons...

> By the way - I keep getting [this confusing error](https://github.com/llvm/llvm-project/actions/runs/11472747270/job/31925816201?pr=112751#step:3:4068) in CI, and I'm not sure if I'm decorating something incorrectly. If anyone has an idea, please let me...

> > By the way - I keep getting [this confusing error](https://github.com/llvm/llvm-project/actions/runs/11472747270/job/31925816201?pr=112751#step:3:4068) in CI, and I'm not sure if I'm decorating something incorrectly. If anyone has an idea, please let...

> There is also another failure in the lifetimebound.verify.cpp: This seems to be caused by missing the `` and `` include headers.

> I seem to be encountering a strange situation where this code gives a dangling reference error when I annotate `std::vector::operator[]` with `[[clang::lifetimebound]]`: > > ```c++ > #include > #include...

Taking a closer look, it seems there's a bug in how the analyzer processes GSL pointers: - When encountering a constructor for a `gsl::pointer`, the analyzer continues traversing the constructor...

#114044 is a draft fix.

> Ah wow, thanks for isolating that. It feels like the ` [[gsl::Pointer]]`/` [[gsl::Owner]]` analyzer strips off a layer of references/pointers when it shouldn't. This would be a blocker for...

> Yeah, I think that, since the only reason we had our own type hierarchy view to begin with was that there wasn't a standard one at the time, we...