Ignore:
Timestamp:
May 12, 2025, 8:33:55 PM (10 months ago)
Author:
Fangren Yu <f37yu@…>
Branches:
master, stuck-waitfor-destruct
Children:
edd11bd
Parents:
98c77b2
Message:

proofreading changes from Gregor

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/theses/fangren_yu_MMath/future.tex

    r98c77b2 r8fe7a85  
    88\section{Closed Trait Types}
    99
    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.
     10Currently, \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.
    1111Locally-declared nested-functions,\footnote{
    1212Nested functions are not a feature in C but supported by \lstinline{gcc} for multiple decades and are used heavily in \CFA.}
     
    1717Library implementers normally do not want users to override certain operations and cause the behaviour of polymorphic invocations to change.
    1818\item
    19 Caching and reusing resolution results in the compiler is effected, as newly introduced declarations can participate in assertion resolution;
     19Caching and reusing resolution results in the compiler is affected, as newly introduced declarations can participate in assertion resolution;
    2020as a result, previously invalid subexpressions suddenly become valid, or alternatively cause ambiguity in assertions.
    2121\end{enumerate}
     
    7070\end{figure}
    7171
    72 A \CFA closed trait type is similar to a Haskell type class requiring an explicit instance declaration.
     72A \CFA closed trait type is planned to be working similarly to a Haskell type class that requires an explicit instance declaration.
    7373The syntax for the closed trait might look like:
    7474\begin{cfa}
     
    9191
    9292\section{Associated Types}
     93\label{s:AssociatedTypes}
    9394
    9495The 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.
     
    159160\section{User-defined Conversions}
    160161
    161 Missing type-system feature is a scheme for user-defined conversions.
     162A missing type-system feature in \CFA is a scheme for user-defined conversions.
    162163Conversion means one type goes through an arbitrary complex process of changing its value to some meaningful value in another type.
    163164Because the conversion process can be arbitrarily complex, it requires the power of a function.
Note: See TracChangeset for help on using the changeset viewer.