You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While bringing the features/param-nullchecking branch up to date, I found the following build error:
CSC : error CS8103: Combined length of user strings used by the program exceeds allowed limit. Try to decrease use of string literals. [C:\Users\rikki\src\roslyn\src\Compilers\CSharp\Test\Emit\Microsoft.CodeAnalysis.CSharp.Emit.UnitTests.csproj]
I think the 1400~ lines of emit tests in the feature branch pushed us over an edge. We probably need to factor another test project out of the current 'Emit' test project.
Any strategies/suggestions for how to do this split would be welcome. I will try soon to write up a script to count up the sizes of string constants in different source files. Maybe a logical split will become apparent then.
cc @dotnet/roslyn-compiler
The text was updated successfully, but these errors were encountered:
Any strategies/suggestions for how to do this split would be welcome. I will try soon to write up a script to count up the sizes of string constants in different source files. Maybe a logical split will become apparent then.
I think this is the best approach here and I'm hopeful a logical split becomes apparent.
Do we know what the limit is here that we're working against? I forget the exact size here.
While bringing the features/param-nullchecking branch up to date, I found the following build error:
CSC : error CS8103: Combined length of user strings used by the program exceeds allowed limit. Try to decrease use of string literals. [C:\Users\rikki\src\roslyn\src\Compilers\CSharp\Test\Emit\Microsoft.CodeAnalysis.CSharp.Emit.UnitTests.csproj]
I think the 1400~ lines of emit tests in the feature branch pushed us over an edge. We probably need to factor another test project out of the current 'Emit' test project.
Any strategies/suggestions for how to do this split would be welcome. I will try soon to write up a script to count up the sizes of string constants in different source files. Maybe a logical split will become apparent then.
cc @dotnet/roslyn-compiler
The text was updated successfully, but these errors were encountered: