giulianobelinassi wrote:
> Maybe you can open a PR against the branch?
Sorry, but I can only do this tomorrow. Feel free to open the PR if you need it
immediately.
> And `final` as well as `override`? (This is why I'm not convinced we should
> be backporting anything -- the problem is with
giulianobelinassi wrote:
We would like this fixed in 18.1 as well. We are expanding to support C++ and
we will hit this bug at some point.
https://github.com/llvm/llvm-project/pull/87281
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
giulianobelinassi wrote:
> > > > > @erichkeane, thank you. What's the process of including this in the
> > > > > next release?
> > > >
> > > >
> > > > After CI is complete, you can click "Squash and Merge" below (if you
> > > > cannot, let us know and someone can do it for you), and it'll be
giulianobelinassi wrote:
I am not sure how I feel about dropping the canPrintOnRight/printOnRight logic.
We use it as a fallback when the SourceRange of a function is unreliable,
otherwise we always copy and paste the code the user wrote.
Regardless of that I will check for fallbacks on
