fix typo
This commit is contained in:
parent
6678f4c082
commit
6681897746
|
@ -165,4 +165,4 @@ For embedded applications, inlining functions often provides performance benefit
|
||||||
Func<int, int> Square = i -> i * i;
|
Func<int, int> Square = i -> i * i;
|
||||||
Console.WriteLine(Square.Apply(9)); // prints "81", but efficiently
|
Console.WriteLine(Square.Apply(9)); // prints "81", but efficiently
|
||||||
|
|
||||||
Inlining is not always possible or beneficial. Dynamic functions may not be able to be inlined at compile time and inlining marge methods may adversely affect assembly size. For these cases, C# 13 also provides the **thick lambda operator**, `≡>`. Thick lambdas are marked for JIT compilation by the CLR. This allows you to get performance benefits even when dynamically defining functions or loading assemblies.
|
Inlining is not always possible or beneficial. Dynamic functions may not be able to be inlined at compile time and inlining large methods may adversely affect assembly size. For these cases, C# 13 also provides the **thick lambda operator**, `≡>`. Thick lambdas are marked for JIT compilation by the CLR. This allows you to get performance benefits even when dynamically defining functions or loading assemblies.
|
||||||
|
|
Loading…
Reference in New Issue