From b7c28004ca3b178fe1ae505c021c0483ebaac224 Mon Sep 17 00:00:00 2001 From: Ardi <113623122+hardlyardi@users.noreply.github.com> Date: Fri, 7 Mar 2025 02:01:58 -0600 Subject: [PATCH] add line break --- 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 63ab042..dfac69a 100644 --- a/docs/eager-inference-annotations-for-polymorphic-types.md +++ b/docs/eager-inference-annotations-for-polymorphic-types.md @@ -53,4 +53,4 @@ The `T!` syntax would indicate a that the type binding for `T` is monomorphic. - **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. -- **Function-argument-bindings**: Flip the relationship from being declared per-type-parameter to be set per-argument: `function test(a: T, b: T, c: T!)` which provides the user more control, and could allow both instantiation behaviours of polymorphic types under a uniform syntax. +- **Function-argument-bindings**: Flip the relationship from being declared per-type-parameter to be set per-argument:
`function test(a: T, b: T, c: T!)` which provides the user more control, and could allow both instantiation behaviours of polymorphic types under a uniform syntax.