Language level constraint

[MaorBM]

Hi all,

I recently started using Mapperly and I have noticed that Mapperly requires c# language level 9.The problem is even if I pack my code as a nuget package, the users of my package also required for c# language 9 which causes a problem. Is there any way to avoid this? I don't want to cause this kind of constraint over my users.

Thank you.

[latonz]

Do you keep the mapperly reference after compilation (see docs)?

[latonz]

Yeah but without it, there will be no reference to Mapperly for the consumers of the library. You could probably suppress RMG046, but all your consumer projects would probably need to do that too.

[latonz]

Alternatively, we need a new csproj option to disable this check.

[MaorBM]

Thank you.
In the case I can avoid carrying the reference to Mapperly with my package the error will not pop, but will they have any problems with the generated code using new language features (even if its already compiled)?
Shouldn't this error only pop for compilation time? Is it still important for someone that uses the compiled output (mine or Mapperly)?

[latonz]

The pops up at compilation time, doesn't it?
The generated code needs these language features, however consumers of your library only consume the compiled code of your library and therefore it may work if the language features involved don't need runtime features.

[MaorBM]

It pops up during compilation time, but compilation of the consuming projects (against the compiled code).
So currently I cannot use it if I don't want to impose language level 9 constraints on my consumers (because of possible needed runtime features), right?