- User Since
- Nov 24 2018, 4:02 AM (188 w, 3 d)
May 24 2022
Apr 6 2022
That's the general approach for clang-tidy use too, rely on clang-format for formatting the fixes.
Mar 15 2022
Hmm just a few curious questions from the sidelines.
Why a "custom system" instead of something -ftime-trace based?
How much overhead does this introduce, esp. for normal use-cases?
What's the gain? The information is very coarse and general-purpose system profiling tools should give you much better information regarding file system perf.
Mar 4 2022
@sammccall pls merge
Feb 23 2022
Feb 22 2022
For a callback like
the inlay hint is displayed after the ).
Which also looks confusingly like a hint for the lambda return type (which isn't implemented yet afaik).
I don't have a good sense for how common the "multiple instantiations, same type" scenario is; perhaps @Trass3r has an opinion on that.
Feb 21 2022
No apparent differences. Is there a way to automatically reduce it?
Looks like this only covers a subset.
I see hints for some generic lambdas but not for others while hovering over auto reveals the type.
Feb 18 2022
Feb 15 2022
Is it intentional that the resolved type is not shown in the variable hover (I guess, looking at the code):
param payload Type: const auto &
Jul 21 2020
Sep 20 2019
Has this ever gotten anywhere?
I think the correct mapping would be something like -fno-ms-compatibility -fno-delayed-template-parsing, not sure about -fms-volatile -fms-extensions. Edit: Actually no, you need the extensions and disabling compat makes it disguise as gcc. So only the template parsing is left.
Dec 26 2018
Simply didn't look for other uses of IntShift :)
I'm currently not working on llvm but I still have a bunch of half-decent visualizers for llvm::Value types and the like.
Dec 8 2018
Is this still in progress?