From 5308d81184b8acceef08f24ff8cb7558863d468d Mon Sep 17 00:00:00 2001 From: Marcus Date: Fri, 7 Mar 2025 14:51:48 +0100 Subject: [PATCH] Update eager-inference-annotations-for-polymorphic-types.md --- docs/eager-inference-annotations-for-polymorphic-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/eager-inference-annotations-for-polymorphic-types.md b/docs/eager-inference-annotations-for-polymorphic-types.md index 7cb7680..fc74aa7 100644 --- a/docs/eager-inference-annotations-for-polymorphic-types.md +++ b/docs/eager-inference-annotations-for-polymorphic-types.md @@ -6,7 +6,7 @@ The RFC introduces a feature to annotate a polymorphic function signature to exp ## Motivation -The purpose of this feature is to prevent polymorphic types from widening into a union (e.g., number | string) when the function is called with different arguments, like in the case of `test(1, "a")`. Without the `!` annotation, the solver would infer `T` to be `number | string`, which is undesirable when the intention is to enforce strict type consistency across the function. +The purpose of this feature is to prevent polymorphic types from widening into (e.g., number | string) when the function is called with different arguments, like in the case of `test(1, "a")`. Without the `!` annotation, the solver would infer `T` to be `number | string`, which is undesirable when the intention is to enforce strict type consistency across the function. ```luau function test(a: T, b: T): T