From 27d8c66b864c7e00ecd7e62fff2477a7a71d4566 Mon Sep 17 00:00:00 2001 From: Ardi <113623122+hardlyardi@users.noreply.github.com> Date: Fri, 7 Mar 2025 08:09:12 -0600 Subject: [PATCH] changes to alternatives --- ...-inference-annotations-for-polymorphic-types.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/eager-inference-annotations-for-polymorphic-types.md b/docs/eager-inference-annotations-for-polymorphic-types.md index 1a0e4e9..9815f03 100644 --- a/docs/eager-inference-annotations-for-polymorphic-types.md +++ b/docs/eager-inference-annotations-for-polymorphic-types.md @@ -39,18 +39,22 @@ test(1, "string") -- Type error: Expected `number`, got `string` ## Alternatives ### Function-argument-bindings -Flip the relationship being declarared per-type-parameter to be per-argument which provides more control in expressing the inference and could allow both instantiation behaviours of polymorphic types under an uniform syntax. +Flip the relationship being declarared per-type-parameter to be per-argument which provides more control in expressing the inference, and could allow both instantiation behaviours of polymorphic types under a uniform syntax. -A polymorphic function has arguments marked with T! will not contribute to the inference of `T`. Instead `T` should be inferred on the arguments without the annotation. +A polymorphic function's arguments marked with type `T!` will not contribute to the instantiation of type `T` in the function. Instead, `T` should be inferred on the arguments without the annotation. ```luau -function test(first: T!, second: T!, third: T): T +function test(first: T, second: T, third: T!): T end -test(1, "string", true) -- Type error: Expected `boolean`, got `number` +test(1, "string", true) -- TypeError: Type `boolean` could not be converted into `number | string` ``` + + ### Type Function Constraint Provide a `types.monomorphic` function in user-defined type functions to enforce monomorphism dynamically. But this would probably require some way to propagate an `*error-type*` to the user. + + ### Keywords -Something like `` or `` should also be considered if we want to reduce symbols. +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!?`