Re: Time to merge scratch/correct-warning-pos into master, perhaps?

[Eli Zaretskii]

> From: chad <yandros@mit.edu>
> Date: Wed, 26 Jan 2022 11:56:30 -0500
> 
> There is an outstanding question of whether or not to merge the capability 
> into the development head, to get
> more people involved in testing and refinement. Again, this is a question for 
> the maintainers. I will hazard a
> guess that they would like to see a bit more forward motion of how to measure 
> the costs first, but I could be
> wrong. In either case, it seems like there is enough interest that if someone 
> were to put together some
> candidate benchmarks, and there were reasonable buy-in that the candidates 
> were solid, we could probably
> get people to run some tests from the branch. That would probably (I'm 
> guessing here) be enough to make a
> clear call between "needs more baking" and "we can try this on git master".

You may have missed the fact that the feature was already merged, and
is now on master.