From 66818977464b56e282f543b3f86c39807c0149c0 Mon Sep 17 00:00:00 2001 From: Tim Van Baak Date: Thu, 14 Nov 2024 09:02:10 -0800 Subject: [PATCH] fix typo --- src/post/2024/lesser-known-operators-in-cs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/post/2024/lesser-known-operators-in-cs.md b/src/post/2024/lesser-known-operators-in-cs.md index 99bfe42..7a45537 100644 --- a/src/post/2024/lesser-known-operators-in-cs.md +++ b/src/post/2024/lesser-known-operators-in-cs.md @@ -165,4 +165,4 @@ For embedded applications, inlining functions often provides performance benefit Func Square = i -> i * i; 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.