Why does Mapster not uses the LangVersion provided by default from the TargetFrameworks then instead 10.0 / 8.0 ?

[DevTKSS]

(See Title)

I recognized that the new Dictionary.Build.props file does specifiy <LangVersion>10.0</LangVersion> and also quite all Projects doing the same but with 10.0/8.0 even the SourceGenerator netstandard2.0 👀

By the way, I don't think using higher LangVersion is recommended for Source Generator Projects and could potentially result in runtime problems 🤔

Could we maybe check if we still need the LangVersion set explicitily and by that are restrict our Projects to benefit from the Lang features of later versions?

@stagep @DocSvartz @andrerav what do you think?
What were your reasons to use them at all? 🤔 Maybe the Source Generators netstandard2.0 limitation?

I locally curioursly tryed to even centralise them to 10.0 in the Directory.Package.props but then the Mapster Project itself (which does already use 10.0 🤔) did suddenly file that types would not be known and net Core App 3.0 would not support Lang version 10.0 (along with whole bunch of other Projects, but this was the first in the list, which is normally the culprit when some problem results in a rat tail of other problems to fix before something works again)

It looks to me a bit ridiculous, that we are using net8.0;net9.0;net10.0, but keeping the Lang Version Features limited to net6.0 🤔 👎