From 7d20d52f3ca3b5d2a79084fd85468cb8521579b3 Mon Sep 17 00:00:00 2001 From: Ardi <113623122+hardlyardi@users.noreply.github.com> Date: Fri, 7 Mar 2025 11:16:52 -0600 Subject: [PATCH] separate noinfer alternative for clarity --- ...er-inference-annotations-for-polymorphic-types.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/eager-inference-annotations-for-polymorphic-types.md b/docs/eager-inference-annotations-for-polymorphic-types.md index 7079b78..dc95b58 100644 --- a/docs/eager-inference-annotations-for-polymorphic-types.md +++ b/docs/eager-inference-annotations-for-polymorphic-types.md @@ -54,8 +54,18 @@ end test(1, "string", true) -- TypeError: Type `boolean` could not be converted into `number | string` ``` -Notably, this behavior would be identical to other languages, such as typescript's `noinfer`. This has the added drawback that the `!` syntax modifier would need to be barred from return types, as the return type holds no relevance to implicit instantiation. +This has the added drawback that the `!` syntax modifier would need to be barred from return types, as the return type holds no relevance to implicit instantiation. +### noinfer\ +Same as above, except we introduce no new syntax into the language. Create a binding similar or equivalent to typescript's noinfer: + +```luau +function test(first: T, second: T, third: noinfer): T + return first +end + +test(1, "string", true) -- TypeError: Type `boolean` could not be converted into `number | string` +``` ### Keywords Something like `` or `` should also be considered if we want to reduce symbols. This idea has merit when considering the potential complexity of type aliases combined with `T!?`