Commit 5957494
better explanation of structural typing
Co-authored-by: Felicity Chapman <felicitymay@github.com>1 parent c9ecb32 commit 5957494
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -42,7 +42,7 @@ Type signatures | |||
| 42 | 42 | Type signatures declare module parameters that are to be substituted with types at module instantiation. | |
| 43 | 43 | Type signature are the simplest category of signatures, as the only thing they allow is the specification of supertypes. | |
| 44 | 44 | ||
| 45 | - The substitution of type signatures relies on structural typing, i.e. types do not have to be explicitly defined as | ||
| 45 | + The substitution of type signatures relies on structural typing. That is, types do not have to be explicitly defined as | ||
| 46 | 46 | implementing a type signature - they just need to have the specified (transitive) supertypes. | |
| 47 | 47 | ||
| 48 | 48 | In detail, a type signature definition consists of: | |
0 commit comments