Changeset 8fe7a85 for doc/theses/fangren_yu_MMath/future.tex
- Timestamp:
- May 12, 2025, 8:33:55 PM (10 months ago)
- Branches:
- master, stuck-waitfor-destruct
- Children:
- edd11bd
- Parents:
- 98c77b2
- File:
-
- 1 edited
-
doc/theses/fangren_yu_MMath/future.tex (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
doc/theses/fangren_yu_MMath/future.tex
r98c77b2 r8fe7a85 8 8 \section{Closed Trait Types} 9 9 10 Currently, \CFA does not have any closed types, as open type are the basis of its unique type-system, allowing new functions to be added at any time to override existing ones for trait satisfaction.10 Currently, \CFA does not have any closed types, as open types are the basis of its unique type-system, allowing new functions to be added at any time to override existing ones for trait satisfaction. 11 11 Locally-declared nested-functions,\footnote{ 12 12 Nested functions are not a feature in C but supported by \lstinline{gcc} for multiple decades and are used heavily in \CFA.} … … 17 17 Library implementers normally do not want users to override certain operations and cause the behaviour of polymorphic invocations to change. 18 18 \item 19 Caching and reusing resolution results in the compiler is effected, as newly introduced declarations can participate in assertion resolution;19 Caching and reusing resolution results in the compiler is affected, as newly introduced declarations can participate in assertion resolution; 20 20 as a result, previously invalid subexpressions suddenly become valid, or alternatively cause ambiguity in assertions. 21 21 \end{enumerate} … … 70 70 \end{figure} 71 71 72 A \CFA closed trait type is similar to a Haskell type class requiringan explicit instance declaration.72 A \CFA closed trait type is planned to be working similarly to a Haskell type class that requires an explicit instance declaration. 73 73 The syntax for the closed trait might look like: 74 74 \begin{cfa} … … 91 91 92 92 \section{Associated Types} 93 \label{s:AssociatedTypes} 93 94 94 95 The analysis presented in \VRef{s:AssertionSatisfaction} shows if all type parameters have to be bound before assertion resolution, the complexity of resolving assertions becomes much lower as every assertion parameter can be resolved independently. … … 159 160 \section{User-defined Conversions} 160 161 161 Missing type-system featureis a scheme for user-defined conversions.162 A missing type-system feature in \CFA is a scheme for user-defined conversions. 162 163 Conversion means one type goes through an arbitrary complex process of changing its value to some meaningful value in another type. 163 164 Because the conversion process can be arbitrarily complex, it requires the power of a function.
Note:
See TracChangeset
for help on using the changeset viewer.