Shouldn't Environment.NewLine be an intrinsic instead? Like BitConverter.IsLittleEndian or string.Empty?

UPD: ah, I guess JIT is not able to concat const strings yet (but would be nice to be able to fold CNS_STR nodes, I think it's not difficult to implement: #26000 (comment))

I guess JIT is not able to concat const strings yet (but would be nice to be able to fold CNS_STR nodes, I think it's not difficult to implement

It of course could be done, but it'd be more than just handling constant strings... the JIT would need to unwind decisions the C# compiler makes about what overloads of string.Concat to use.

I guess JIT is not able to concat const strings yet (but would be nice to be able to fold CNS_STR nodes, I think it's not difficult to implement

It of course could be done, but it'd be more than just handling constant strings... the JIT would need to unwind decisions the C# compiler makes about what overloads of string.Concat to use.

I mean at least simple cases, e.g. (from your changes):

text.Append(Environment.NewLine + InnerExceptionPrefix);

So JIT in runtime should replace Environment.NewLine with CNS_STR (const string) because its value never changes. Environment.NewLine + InnerExceptionPrefix is:

\--*  CALL      ref    String.Concat
   +--*  CALL      ref    Environment.get_NewLine
   \--*  CNS_STR   ref   <string constant>

then is converted into:

\--*  CALL      ref    String.Concat
   +--*  CNS_STR   ref   <string constant>   ;; it's now a const
   \--*  CNS_STR   ref   <string constant>

then JIT should fold it into just

\--*  CNS_STR   ref   <string constant>