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
If raise will be inlined, tools such as unit test coverage analyzer in Visual Studio will not mark raise calls as partially covered. Methods that use it, such as nullArg, will also benefit from this. Is there a reason whiy raise is not inlined? I can redefine these operators myself, but it requires inline assembly and therefore that annoying red squiggles in Visual Studio.
The text was updated successfully, but these errors were encountered:
Perhaps I am a bit late for the party, but could you please reconsider the exception inlining in the light of the following performance issues (or consider to do compiler generated thow only non-inlining methods when raise/nullarg/failwith/etc are used):
If
raise
will be inlined, tools such as unit test coverage analyzer in Visual Studio will not markraise
calls as partially covered. Methods that use it, such asnullArg
, will also benefit from this. Is there a reason whiyraise
is not inlined? I can redefine these operators myself, but it requires inline assembly and therefore that annoying red squiggles in Visual Studio.The text was updated successfully, but these errors were encountered: