bolshakov-a wrote:
No, IWYU has some complex logic to figure out which type components the type
alias author intends to provide, and which should be `#include`d at the use
site. Of course, substituted template type arguments are the user
responsibility, not the alias author's one, hence this i
bolshakov-a wrote:
> One possibility here is that if you have the type, then you will have a
> template specialization type for the template alias, and that gives you the
> template arguments used to specialize the alias. Which should answer this
> need.
This can probably go, thank you!
http
bolshakov-a wrote:
> From past conversations with IWYU maintainer, this was desirable, since IWYU
> rolls its own resugarer, which is faulty and difficult to maintain.
I just want to mention that, actually, IWYU doesn't probably need any resugarer
at all. A type template argument as-written is
bolshakov-a wrote:
@mizvekov, could you clarify please what is the point of traversing the host
type twice? The tests pass if just remove the `if` statement.
https://github.com/llvm/llvm-project/pull/132551
___
cfe-commits mailing list
cfe-commits@lis
bolshakov-a wrote:
Thanks, it becomes now clearer for me. However, I'm still not succeeded in
making this code really working, because the default version of
`TraverseDecltypeType` doesn't traverse the underlying desugared type:
https://github.com/llvm/llvm-project/blob/be6ccc98f38227db02164f17
101 - 105 of 105 matches
Mail list logo
