|Yes, that could be a problem.|
OTOH it's what we developers work with every day. So I expect many people to care and that they appreciate a more detailed survey.
We could try to strip the number of compiler checks down by doing a first survey on this list.
Fwiw, I would not recommend this approach for a survey. If you get too detailed people start to either 1) not complete the survey or 2) make up their answers.
Yes, I would do that if we agree we want to go this way.
What if we do a dedicated survey only for the compiler checks, where we list the ones currently ignored (I counted 31) and let the community state what severity they would prefer for which check?
I’m not convinced we’ll get enough data from this. Seems pretty specific and takes some time to answer. But who knows. Do you volunteer to create the questions for such a survey? :)
ide-dev mailing listide-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/ide-dev