Serafean wrote: > I'm not certain this is the correct approach. I think we should expose a > cursor kind for a coroutine statement body so that you can test for this sort > of thing if needed
Ok, I'll see how exposing the body's compound statement would work. > there something broader you're working on where you'd need that kind of > helper function? Within KDevelop we have a code browser information widget that shows information about the "cursor". My broad goal is to extend it for coroutines so that: - It shows that a function is a coroutine - It directly shows the promise's methods, and for `co_await` expressions it exposes the various `await_*` methods. This was a naive attempt to do part 1, as so far I have no idea how to do the rest. Thanks for the comments. https://github.com/llvm/llvm-project/pull/182685 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
