source: doc/generic_types/generic_types.tex @ 5103d7a

Last change on this file since 5103d7a was 5103d7a, checked in by Peter A. Buhr <pabuhr@…>, 5 years ago

small fixups in tuples section

  • Property mode set to 100644
File size: 66.2 KB
1% take off review (for line numbers) and anonymous (for anonymization) on submission
3% \documentclass[format=acmlarge,review]{acmart}
6\usepackage{upquote}                                                                    % switch curled `'" to straight
7\usepackage{listings}                                                                   % format program code
10% parindent is relative, i.e., toggled on/off in environments like itemize, so store the value for
11% use rather than use \parident directly.
15\newlength{\gcolumnposn}                                % temporary hack because lstlisting does handle tabs correctly
22\newcommand{\TODO}[1]{\textbf{TODO}: {\itshape #1}} % TODO included
23%\newcommand{\TODO}[1]{} % TODO elided
24% Latin abbreviation
25\newcommand{\abbrevFont}{\textit}       % set empty for no italics
27        \@ifnextchar{,}{\abbrevFont{e}.\abbrevFont{g}.}%
28                {\@ifnextchar{:}{\abbrevFont{e}.\abbrevFont{g}.}%
29                        {\abbrevFont{e}.\abbrevFont{g}.,\xspace}}%
32        \@ifnextchar{,}{\abbrevFont{i}.\abbrevFont{e}.}%
33                {\@ifnextchar{:}{\abbrevFont{i}.\abbrevFont{e}.}%
34                        {\abbrevFont{i}.\abbrevFont{e}.,\xspace}}%
37        \@ifnextchar{.}{\abbrevFont{etc}}%
38        {\abbrevFont{etc}.\xspace}%
41        \@ifnextchar{.}{\abbrevFont{et~al}}%
42                {\abbrevFont{et al}.\xspace}%
44% \newcommand{\eg}{\textit{e}.\textit{g}.,\xspace}
45% \newcommand{\ie}{\textit{i}.\textit{e}.,\xspace}
46% \newcommand{\etc}{\textit{etc}.,\xspace}
49% Useful macros
50\newcommand{\CFA}{C$\mathbf\forall$\xspace} % Cforall symbolic name
51\newcommand{\CC}{\rm C\kern-.1em\hbox{+\kern-.25em+}\xspace} % C++ symbolic name
52\newcommand{\CCeleven}{\rm C\kern-.1em\hbox{+\kern-.25em+}11\xspace} % C++11 symbolic name
53\newcommand{\CCfourteen}{\rm C\kern-.1em\hbox{+\kern-.25em+}14\xspace} % C++14 symbolic name
54\newcommand{\CCseventeen}{\rm C\kern-.1em\hbox{+\kern-.25em+}17\xspace} % C++17 symbolic name
55\newcommand{\CCtwenty}{\rm C\kern-.1em\hbox{+\kern-.25em+}20\xspace} % C++20 symbolic name
59% CFA programming language, based on ANSI C (with some gcc additions)
61        morekeywords={_Alignas,_Alignof,__alignof,__alignof__,asm,__asm,__asm__,_At,_Atomic,__attribute,__attribute__,auto,
62                _Bool,catch,catchResume,choose,_Complex,__complex,__complex__,__const,__const__,disable,dtype,enable,__extension__,
63                fallthrough,fallthru,finally,forall,ftype,_Generic,_Imaginary,inline,__label__,lvalue,_Noreturn,one_t,otype,restrict,_Static_assert,
64                _Thread_local,throw,throwResume,trait,try,ttype,typeof,__typeof,__typeof__,zero_t},
70basicstyle=\linespread{0.9}\sf,                                                 % reduce line spacing and use sanserif font
71stringstyle=\tt,                                                                                % use typewriter font
72tabsize=4,                                                                                              % 4 space tabbing
73xleftmargin=\parindentlnth,                                                             % indent code to paragraph indentation
74%mathescape=true,                                                                               % LaTeX math escape in CFA code $...$
75escapechar=\$,                                                                                  % LaTeX escape in CFA code
76keepspaces=true,                                                                                %
77showstringspaces=false,                                                                 % do not show spaces with cup
78showlines=true,                                                                                 % show blank lines at end of code
79aboveskip=4pt,                                                                                  % spacing above/below code block
81% replace/adjust listing characters that look bad in sanserif
82literate={-}{\raisebox{-0.15ex}{\texttt{-}}}1 {^}{\raisebox{0.6ex}{$\scriptscriptstyle\land\,$}}1
83        {~}{\raisebox{0.3ex}{$\scriptstyle\sim\,$}}1 {_}{\makebox[1.2ex][c]{\rule{1ex}{0.1ex}}}1 % {`}{\ttfamily\upshape\hspace*{-0.1ex}`}1
84        {<-}{$\leftarrow$}2 {=>}{$\Rightarrow$}2,
86}% lstset
88% inline code @...@
91% ACM Information
96\title{Generic and Tuple Types with Efficient Dynamic Layout in \CFA}
98\author{Aaron Moss}
100\author{Robert Schluntz}
102\author{Peter Buhr}
105        \institution{University of Waterloo}
106        \department{David R. Cheriton School of Computer Science}
107        \streetaddress{Davis Centre, University of Waterloo}
108        \city{Waterloo}
109        \state{ON}
110        \postcode{N2L 3G1}
111        \country{Canada}
114\terms{generic, tuple, variadic, types}
115\keywords{generic types, tuple types, variadic types, polymorphic functions, C, Cforall}
121<concept_desc>Software and its engineering~Polymorphism</concept_desc>
126<concept_desc>Software and its engineering~Data types and structures</concept_desc>
131<concept_desc>Software and its engineering~Source code generation</concept_desc>
137\ccsdesc[500]{Software and its engineering~Polymorphism}
138\ccsdesc[500]{Software and its engineering~Data types and structures}
139\ccsdesc[300]{Software and its engineering~Source code generation}
142The C programming language is a foundational technology for modern computing with millions of lines of code implementing everything from commercial operating-systems to hobby projects. This installation base and the programmers producing it represent a massive software-engineering investment spanning decades and likely to continue for decades more. Nonetheless, C, first standardized over thirty years ago, lacks many features that make programming in more modern languages safer and more productive. The goal of the \CFA project is to create an extension of C that provides modern safety and productivity features while still ensuring strong backwards compatibility with C and its programmers. Prior projects have attempted similar goals but failed to honour C programming-style; for instance, adding object-oriented or functional programming with garbage collection is a non-starter for many C developers. Specifically, \CFA is designed to have an orthogonal feature-set based closely on the C programming paradigm, so that \CFA features can be added \emph{incrementally} to existing C code-bases, and C programmers can learn \CFA extensions on an as-needed basis, preserving investment in existing code and engineers. This paper describes two \CFA extensions, generic and tuple types, details how their design avoids shortcomings of similar features in C and other C-like languages, and presents experimental results validating the design.
149\section{Introduction and Background}
151The C programming language is a foundational technology for modern computing with millions of lines of code implementing everything from commercial operating-systems to hobby projects. This installation base and the programmers producing it represent a massive software-engineering investment spanning decades and likely to continue for decades more.
152The \citet{TIOBE} ranks the top 5 most popular programming languages as: Java 16\%, \Textbf{C 7\%}, \Textbf{\CC 5\%}, \CS 4\%, Python 4\% = 36\%, where the next 50 languages are less than 3\% each with a long tail. The top 3 rankings over the past 30 years are:
157                & 2017  & 2012  & 2007  & 2002  & 1997  & 1992  & 1987          \\
159Java    & 1             & 1             & 1             & 1             & 12    & -             & -                     \\
161\Textbf{C}      & \Textbf{2}& \Textbf{2}& \Textbf{2}& \Textbf{2}& \Textbf{1}& \Textbf{1}& \Textbf{1}    \\
163\CC             & 3             & 3             & 3             & 3             & 2             & 2             & 4                     \\
167Love it or hate it, C is extremely popular, highly used, and one of the few system's languages.
168In many cases, \CC is often used solely as a better C.
169Nonetheless, C, first standardized over thirty years ago, lacks many features that make programming in more modern languages safer and more productive.
171\CFA (pronounced ``C-for-all'', and written \CFA or Cforall) is an evolutionary extension of the C programming language that aims to add modern language features to C while maintaining both source compatibility with C and a familiar programming model for programmers. The four key design goals for \CFA~\citep{Bilson03} are:
172(1) The behaviour of standard C code must remain the same when translated by a \CFA compiler as when translated by a C compiler;
173(2) Standard C code must be as fast and as small when translated by a \CFA compiler as when translated by a C compiler;
174(3) \CFA code must be at least as portable as standard C code;
175(4) Extensions introduced by \CFA must be translated in the most efficient way possible.
176These goals ensure existing C code-bases can be converted to \CFA incrementally with minimal effort, and C programmers can productively generate \CFA code without training beyond the features being used.
177Unfortunately, \CC is actively diverging from C, so incremental additions require significant effort and training, coupled with multiple legacy design-choices that cannot be updated.
179\CFA is currently implemented as a source-to-source translator from \CFA to the GCC-dialect of C~\citep{GCCExtensions}, allowing it to leverage the portability and code optimizations provided by GCC, meeting goals (1)-(3). Ultimately, a compiler is necessary for advanced features and optimal performance.
181This paper identifies shortcomings in existing approaches to generic and variadic data types in C-like languages and presents a design for generic and variadic types avoiding those shortcomings. Specifically, the solution is both reusable and type-checked, as well as conforming to the design goals of \CFA with ergonomic use of existing C abstractions. The new constructs are empirically compared with both standard C and \CC; the results show the new design is comparable in performance.
184\subsection{Polymorphic Functions}
187\CFA's polymorphism was originally formalized by \citet{Ditchfield92}, and first implemented by \citet{Bilson03}. The signature feature of \CFA is parametric-polymorphic functions where functions are generalized using a @forall@ clause (giving the language its name):
189`forall( otype T )` T identity( T val ) { return val; }
190int forty_two = identity( 42 );                         $\C{// T is bound to int, forty\_two == 42}$
192The @identity@ function above can be applied to any complete \emph{object type} (or @otype@). The type variable @T@ is transformed into a set of additional implicit parameters encoding sufficient information about @T@ to create and return a variable of that type. The \CFA implementation passes the size and alignment of the type represented by an @otype@ parameter, as well as an assignment operator, constructor, copy constructor and destructor. If this extra information is not needed, \eg for a pointer, the type parameter can be declared as a \emph{data type} (or @dtype@).
194In \CFA, the polymorphism runtime-cost is spread over each polymorphic call, due to passing more arguments to polymorphic functions; preliminary experiments show this overhead is similar to \CC virtual-function calls. An advantage of this design is that, unlike \CC template-functions, \CFA polymorphic-functions are compatible with C \emph{separate compilation}, preventing compilation and code bloat.
196Since bare polymorphic-types provide only a narrow set of available operations, \CFA provides a \emph{type assertion} mechanism to provide further type information, where type assertions may be variable or function declarations that depend on a polymorphic type-variable. For example, the function @twice@ can be defined using the \CFA syntax for operator overloading:
198forall( otype T `| { T ?+?(T, T); }` ) T twice( T x ) { return x + x; } $\C{// ? denotes operands}$
199int val = twice( twice( 3.7 ) );
201which works for any type @T@ with a matching addition operator. The polymorphism is achieved by creating a wrapper function for calling @+@ with @T@ bound to @double@, then passing this function to the first call of @twice@. There is now the option of using the same @twice@ and converting the result to @int@ on assignment, or creating another @twice@ with type parameter @T@ bound to @int@ because \CFA uses the return type, as in~\cite{Ada}, in its type analysis.
202The first approach has a late conversion from @double@ to @int@ on the final assignment, while the second has an eager conversion to @int@. \CFA minimizes the number of conversions and their potential to lose information, so it selects the first approach, which corresponds with C-programmer intuition.
204Crucial to the design of a new programming language are the libraries to access thousands of external software features.
205Like \CC, \CFA inherits a massive compatible library-base, where other programming languages must rewrite or provide fragile inter-language communication with C.
206A simple example is leveraging the existing type-unsafe (@void *@) C @bsearch@ to binary search a sorted floating-point array:
208void * bsearch( const void * key, const void * base, size_t nmemb, size_t size,
209                                int (* compar)( const void *, const void * ));
210int comp( const void * t1, const void * t2 ) { return *(double *)t1 < *(double *)t2 ? -1 :
211                                *(double *)t2 < *(double *)t1 ? 1 : 0; }
212double vals[10] = { /* 10 floating-point values */ };
213double key = 5.0;
214double * val = (double *)bsearch( &key, vals, 10, sizeof(vals[0]), comp );      $\C{// search sorted array}$
216which can be augmented simply with a generalized, type-safe, \CFA-overloaded wrappers:
218forall( otype T | { int ?<?( T, T ); } ) T * bsearch( T key, const T * arr, size_t size ) {
219        int comp( const void * t1, const void * t2 ) { /* as above with double changed to T */ }
220        return (T *)bsearch( &key, arr, size, sizeof(T), comp ); }
221forall( otype T | { int ?<?( T, T ); } ) unsigned int bsearch( T key, const T * arr, size_t size ) {
222        T *result = bsearch( key, arr, size );  $\C{// call first version}$
223        return result ? result - arr : size; }  $\C{// pointer subtraction includes sizeof(T)}$
224double * val = bsearch( 5.0, vals, 10 );        $\C{// selection based on return type}$
225int posn = bsearch( 5.0, vals, 10 );
227The nested function @comp@ provides the hidden interface from typed \CFA to untyped (@void *@) C, plus the cast of the result.
228Providing a hidden @comp@ function in \CC is awkward as lambdas do not use C calling-conventions and template declarations cannot appear at block scope.
229As well, an alternate kind of return is made available: position versus pointer to found element.
230\CC's type-system cannot disambiguate between the two versions of @bsearch@ because it does not use the return type in overload resolution, nor can \CC separately compile a templated @bsearch@.
232\CFA has replacement libraries condensing hundreds of existing C functions into tens of \CFA overloaded functions, all without rewriting the actual computations.
233For example, it is possible to write a type-safe \CFA wrapper @malloc@ based on the C @malloc@:
235forall( dtype T | sized(T) ) T * malloc( void ) { return (T *)(void *)malloc( (size_t)sizeof(T) ); }
236int * ip = malloc();                                            $\C{// select type and size from left-hand side}$
237double * dp = malloc();
238struct S {...} * sp = malloc();
240where the return type supplies the type/size of the allocation, which is impossible in most type systems.
242Call-site inferencing and nested functions provide a localized form of inheritance. For example, the \CFA @qsort@ only sorts in ascending order using @<@. However, it is trivial to locally change this behaviour:
244forall( otype T | { int ?<?( T, T ); } ) void qsort( const T * arr, size_t size ) { /* use C qsort */ }
245{       int ?<?( double x, double y ) { return x `>` y; }       $\C{// locally override behaviour}$
246        qsort( vals, size );                                    $\C{// descending sort}$
249Within the block, the nested version of @<@ performs @>@ and this local version overrides the built-in @<@ so it is passed to @qsort@.
250Hence, programmers can easily form local environments, adding and modifying appropriate functions, to maximize reuse of other existing functions and types.
252Finally, \CFA allows variable overloading:
257short int MAX = ...;
258int MAX = ...;
259double MAX = ...;
263short int s = MAX;  // select correct MAX
264int i = MAX;
265double d = MAX;
270Hence, the single name @MAX@ replaces all the C type-specific names: @SHRT_MAX@, @INT_MAX@, @DBL_MAX@.
271As well, restricted constant overloading is allowed for the values @0@ and @1@, which have special status in C, \eg the value @0@ is both an integer and a pointer literal, so its meaning depends on context.
272In addition, several operations are defined in terms values @0@ and @1@, \eg:
274int x;
275if (x) x++                                                                      $\C{// if (x != 0) x += 1;}$
277Every if statement in C compares the condition with @0@, and every increment and decrement operator is semantically equivalent to adding or subtracting the value @1@ and storing the result.
278Due to these rewrite rules, the values @0@ and @1@ have the types @zero_t@ and @one_t@ in \CFA, which allows overloading various operations for new types that seamlessly connect to all special @0@ and @1@ contexts.
279The types @zero_t@ and @one_t@ have special built in implicit conversions to the various integral types, and a conversion to pointer types for @0@, which allows standard C code involving @0@ and @1@ to work as normal.
284\CFA provides \emph{traits} to name a group of type assertions, where the trait name allows specifying the same set of assertions in multiple locations, preventing repetition mistakes at each function declaration:
286trait summable( otype T ) {
287        void ?{}( T *, zero_t );                                $\C{// constructor from 0 literal}$
288        T ?+?( T, T );                                                  $\C{// assortment of additions}$
289        T ?+=?( T *, T );
290        T ++?( T * );
291        T ?++( T * ); };
292forall( otype T `| summable( T )` ) T sum( T a[$\,$], size_t size ) {  // use trait
293        `T` total = { `0` };                                    $\C{// instantiate T from 0 by calling its constructor}$
294        for ( unsigned int i = 0; i < size; i += 1 ) total `+=` a[i]; $\C{// select appropriate +}$
295        return total; }
298In fact, the set of trait operators is incomplete, as there is no assignment requirement for type @T@, but @otype@ is syntactic sugar for the following implicit trait:
300trait otype( dtype T | sized(T) ) {  // sized is a pseudo-trait for types with known size and alignment
301        void ?{}( T * );                                                $\C{// default constructor}$
302        void ?{}( T *, T );                                             $\C{// copy constructor}$
303        void ?=?( T *, T );                                             $\C{// assignment operator}$
304        void ^?{}( T * ); };                                    $\C{// destructor}$
306Given the information provided for an @otype@, variables of polymorphic type can be treated as if they were a complete type: stack-allocatable, default or copy-initialized, assigned, and deleted.
307% As an example, the @sum@ function produces generated code something like the following (simplified for clarity and brevity)\TODO{fix example, maybe elide, it's likely too long with the more complicated function}:
308% \begin{lstlisting}
309% void abs( size_t _sizeof_M, size_t _alignof_M,
310%               void (*_ctor_M)(void*), void (*_copy_M)(void*, void*),
311%               void (*_assign_M)(void*, void*), void (*_dtor_M)(void*),
312%               _Bool (*_lt_M)(void*, void*), void (*_neg_M)(void*, void*),
313%       void (*_ctor_M_zero)(void*, int),
314%               void* m, void* _rtn ) {                         $\C{// polymorphic parameter and return passed as void*}$
315%                                                                                       $\C{// M zero = { 0 };}$
316%       void* zero = alloca(_sizeof_M);                 $\C{// stack allocate zero temporary}$
317%       _ctor_M_zero(zero, 0);                                  $\C{// initialize using zero\_t constructor}$
318%                                                                                       $\C{// return m < zero ? -m : m;}$
319%       void *_tmp = alloca(_sizeof_M);
320%       _copy_M( _rtn,                                                  $\C{// copy-initialize return value}$
321%               _lt_M( m, zero ) ?                                      $\C{// check condition}$
322%                (_neg_M(m, _tmp), _tmp) :                      $\C{// negate m}$
323%                m);
324%       _dtor_M(_tmp); _dtor_M(zero);                   $\C{// destroy temporaries}$
325% }
326% \end{lstlisting}
328In summation, the \CFA type-system uses \emph{nominal typing} for concrete types, matching with the C type-system, and \emph{structural typing} for polymorphic types.
329Hence, trait names play no part in type equivalence;
330the names are simply macros for a list of polymorphic assertions, which are expanded at usage sites.
331Nevertheless, trait names form a logical subtype-hierarchy with @dtype@ at the top, where traits often contain overlapping assertions, \eg operator @+@.
332Traits are used like interfaces in Java or abstract base-classes in \CC, but without the nominal inheritance-relationships.
333Instead, each polymorphic function (or generic type) defines the structural type needed for its execution (polymorphic type-key), and this key is fulfilled at each call site from the lexical environment, which is similar to Go~\citep{Go} interfaces.
334Hence, new lexical scopes and nested functions are used extensively to create local subtypes, as in the @qsort@ example, without having to manage a nominal-inheritance hierarchy.
335(Nominal inheritance can be approximated with traits using marker variables or functions, as is done in Go.)
337% Nominal inheritance can be simulated with traits using marker variables or functions:
338% \begin{lstlisting}
339% trait nominal(otype T) {
340%     T is_nominal;
341% };
342% int is_nominal;                                                               $\C{// int now satisfies the nominal trait}$
343% \end{lstlisting}
345% Traits, however, are significantly more powerful than nominal-inheritance interfaces; most notably, traits may be used to declare a relationship \emph{among} multiple types, a property that may be difficult or impossible to represent in nominal-inheritance type systems:
346% \begin{lstlisting}
347% trait pointer_like(otype Ptr, otype El) {
348%     lvalue El *?(Ptr);                                                $\C{// Ptr can be dereferenced into a modifiable value of type El}$
349% }
350% struct list {
351%     int value;
352%     list *next;                                                               $\C{// may omit "struct" on type names as in \CC}$
353% };
354% typedef list *list_iterator;
356% lvalue int *?( list_iterator it ) { return it->value; }
357% \end{lstlisting}
358% In the example above, @(list_iterator, int)@ satisfies @pointer_like@ by the user-defined dereference function, and @(list_iterator, list)@ also satisfies @pointer_like@ by the built-in dereference operator for pointers. Given a declaration @list_iterator it@, @*it@ can be either an @int@ or a @list@, with the meaning disambiguated by context (\eg @int x = *it;@ interprets @*it@ as an @int@, while @(*it).value = 42;@ interprets @*it@ as a @list@).
359% While a nominal-inheritance system with associated types could model one of those two relationships by making @El@ an associated type of @Ptr@ in the @pointer_like@ implementation, few such systems could model both relationships simultaneously.
362\section{Generic Types}
364One of the known shortcomings of standard C is that it does not provide reusable type-safe abstractions for generic data structures and algorithms. Broadly speaking, there are three approaches to create data structures in C. One approach is to write bespoke data structures for each context in which they are needed. While this approach is flexible and supports integration with the C type-checker and tooling, it is also tedious and error-prone, especially for more complex data structures.
365A second approach is to use @void *@--based polymorphism, \eg the C standard-library functions @bsearch@ and @qsort@, and does allow the use of common code for common functionality. However, basing all polymorphism on @void *@ eliminates the type-checker's ability to ensure that argument types are properly matched, often requiring a number of extra function parameters, pointer indirection, and dynamic allocation that would not otherwise be needed.
366A third approach to generic code is to use preprocessor macros, which does allow the generated code to be both generic and type-checked, but errors may be difficult to interpret. Furthermore, writing and using preprocessor macros can be unnatural and inflexible.
368Other languages use \emph{generic types}, \eg \CC and Java, to produce type-safe abstract data-types. \CFA also implements generic types that integrate efficiently and naturally with the existing polymorphic functions, while retaining backwards compatibility with C and providing separate compilation. However, for known concrete parameters, the generic type can be inlined, like \CC templates.
370A generic type can be declared by placing a @forall@ specifier on a @struct@ or @union@ declaration, and instantiated using a parenthesized list of types after the type name:
372forall( otype R, otype S ) struct pair {
373        R first;
374        S second;
376forall( otype T ) T value( pair( const char *, T ) p ) { return p.second; }
377forall( dtype F, otype T ) T value_p( pair( F *, T * ) p ) { return *p.second; }
378pair( const char *, int ) p = { "magic", 42 };
379int magic = value( p );
380pair( void *, int * ) q = { 0, &p.second };
381magic = value_p( q );
382double d = 1.0;
383pair( double *, double * ) r = { &d, &d };
384d = value_p( r );
387\CFA classifies generic types as either \emph{concrete} or \emph{dynamic}. Concrete have a fixed memory layout regardless of type parameters, while dynamic vary in memory layout depending on their type parameters. A type may have polymorphic parameters but still be concrete, called \emph{dtype-static}. Polymorphic pointers are an example of dtype-static types, \eg @forall(dtype T) T *@ is a polymorphic type, but for any @T@, @T *@  is a fixed-sized pointer, and therefore, can be represented by a @void *@ in code generation.
389\CFA generic types also allow checked argument-constraints. For example, the following declaration of a sorted set-type ensures the set key supports equality and relational comparison:
391forall( otype Key | { _Bool ?==?(Key, Key); _Bool ?<?(Key, Key); } ) struct sorted_set;
395\subsection{Concrete Generic-Types}
397The \CFA translator template-expands concrete generic-types into new structure types, affording maximal inlining. To enable inter-operation among equivalent instantiations of a generic type, the translator saves the set of instantiations currently in scope and reuses the generated structure declarations where appropriate. For example, a function declaration that accepts or returns a concrete generic-type produces a declaration for the instantiated struct in the same scope, which all callers may reuse. For example, the concrete instantiation for @pair( const char *, int )@ is:
399struct _pair_conc1 {
400        const char * first;
401        int second;
405A concrete generic-type with dtype-static parameters is also expanded to a structure type, but this type is used for all matching instantiations. In the above example, the @pair( F *, T * )@ parameter to @value_p@ is such a type; its expansion is below and it is used as the type of the variables @q@ and @r@ as well, with casts for member access where appropriate:
407struct _pair_conc0 {
408        void * first;
409        void * second;
414\subsection{Dynamic Generic-Types}
416Though \CFA implements concrete generic-types efficiently, it also has a fully general system for dynamic generic types.
417As mentioned in Section~\ref{sec:poly-fns}, @otype@ function parameters (in fact all @sized@ polymorphic parameters) come with implicit size and alignment parameters provided by the caller.
418Dynamic generic-types also have an \emph{offset array} containing structure member-offsets.
419A dynamic generic-union needs no such offset array, as all members are at offset 0 but size and alignment are still necessary.
420Access to members of a dynamic structure is provided at runtime via base-displacement addressing with the structure pointer and the member offset (similar to the @offsetof@ macro), moving a compile-time offset calculation to runtime.
422The offset arrays are statically generated where possible.
423If a dynamic generic-type is declared to be passed or returned by value from a polymorphic function, the translator can safely assume the generic type is complete (\ie has a known layout) at any call-site, and the offset array is passed from the caller;
424if the generic type is concrete at the call site, the elements of this offset array can even be statically generated using the C @offsetof@ macro.
425As an example, @p.second@ in the @value@ function above is implemented as @*(p + _offsetof_pair[1])@, where @p@ is a @void *@, and @_offsetof_pair@ is the offset array passed into @value@ for @pair( const char *, T )@.
426The offset array @_offsetof_pair@ is generated at the call site as @size_t _offsetof_pair[] = { offsetof(_pair_conc1, first), offsetof(_pair_conc1, second) }@.
428In some cases the offset arrays cannot be statically generated. For instance, modularity is generally provided in C by including an opaque forward-declaration of a structure and associated accessor and mutator functions in a header file, with the actual implementations in a separately-compiled @.c@ file.
429\CFA supports this pattern for generic types, but the caller does not know the actual layout or size of the dynamic generic-type, and only holds it by a pointer.
430The \CFA translator automatically generates \emph{layout functions} for cases where the size, alignment, and offset array of a generic struct cannot be passed into a function from that function's caller.
431These layout functions take as arguments pointers to size and alignment variables and a caller-allocated array of member offsets, as well as the size and alignment of all @sized@ parameters to the generic structure (un@sized@ parameters are forbidden from being used in a context that affects layout).
432Results of these layout functions are cached so that they are only computed once per type per function. %, as in the example below for @pair@.
433% \begin{lstlisting}
434% static inline void _layoutof_pair(size_t* _szeof_pair, size_t* _alignof_pair, size_t* _offsetof_pair,
435%               size_t _szeof_R, size_t _alignof_R, size_t _szeof_S, size_t _alignof_S) {
436%     *_szeof_pair = 0; // default values
437%     *_alignof_pair = 1;
439%       // add offset, size, and alignment of first field
440%     _offsetof_pair[0] = *_szeof_pair;
441%     *_szeof_pair += _szeof_R;
442%     if ( *_alignof_pair < _alignof_R ) *_alignof_pair = _alignof_R;
444%       // padding, offset, size, and alignment of second field
445%     if ( *_szeof_pair & (_alignof_S - 1) )
446%               *_szeof_pair += (_alignof_S - ( *_szeof_pair & (_alignof_S - 1) ) );
447%     _offsetof_pair[1] = *_szeof_pair;
448%     *_szeof_pair += _szeof_S;
449%     if ( *_alignof_pair < _alignof_S ) *_alignof_pair = _alignof_S;
451%       // pad to struct alignment
452%     if ( *_szeof_pair & (*_alignof_pair - 1) )
453%               *_szeof_pair += ( *_alignof_pair - ( *_szeof_pair & (*_alignof_pair - 1) ) );
454% }
455% \end{lstlisting}
456Layout functions also allow generic types to be used in a function definition without reflecting them in the function signature.
457For instance, a function that strips duplicate values from an unsorted @vector(T)@ would likely have a pointer to the vector as its only explicit parameter, but use some sort of @set(T)@ internally to test for duplicate values.
458This function could acquire the layout for @set(T)@ by calling its layout function with the layout of @T@ implicitly passed into the function.
460Whether a type is concrete, dtype-static, or dynamic is decided solely on the type parameters and @forall@ clause on a declaration.
461This design allows opaque forward declarations of generic types, \eg @forall(otype T) struct Box@ -- like in C, all uses of @Box(T)@ can be separately compiled, and callers from other translation units know the proper calling conventions to use.
462If the definition of a structure type is included in deciding whether a generic type is dynamic or concrete, some further types may be recognized as dtype-static (\eg @forall(otype T) struct unique_ptr { T* p }@ does not depend on @T@ for its layout, but the existence of an @otype@ parameter means that it \emph{could}.), but preserving separate compilation (and the associated C compatibility) in the existing design is judged to be an appropriate trade-off.
468The reuse of dtype-static structure instantiations enables useful programming patterns at zero runtime cost. The most important such pattern is using @forall(dtype T) T *@ as a type-checked replacement for @void *@, \eg creating a lexicographic comparison for pairs of pointers used by @bsearch@ or @qsort@:
470forall(dtype T) int lexcmp( pair( T *, T * ) * a, pair( T *, T * ) * b, int (* cmp)( T *, T * ) ) {
471        return cmp( a->first, b->first ) ? : cmp( a->second, b->second );
474%       int c = cmp( a->first, b->first );
475%       if ( c == 0 ) c = cmp( a->second, b->second );
476%       return c;
477Since @pair(T *, T * )@ is a concrete type, there are no implicit parameters passed to @lexcmp@, so the generated code is identical to a function written in standard C using @void *@, yet the \CFA version is type-checked to ensure the fields of both pairs and the arguments to the comparison function match in type.
479Another useful pattern enabled by reused dtype-static type instantiations is zero-cost \emph{tag-structures}.
480Sometimes information is only used for type-checking and can be omitted at runtime, \eg:
482forall(dtype Unit) struct scalar { unsigned long value; };
483struct metres {};
484struct litres {};
486forall(dtype U) scalar(U) ?+?( scalar(U) a, scalar(U) b ) {
487        return (scalar(U)){ a.value + b.value };
489scalar(metres) half_marathon = { 21093 };
490scalar(litres) swimming_pool = { 2500000 };
491scalar(metres) marathon = half_marathon + half_marathon;
492scalar(litres) two_pools = swimming_pool + swimming_pool;
493marathon + swimming_pool;                                       $\C{// compilation ERROR}$
495@scalar@ is a dtype-static type, so all uses have a single structure definition, containing @unsigned long@, and can share the same implementations of common functions like @?+?@.
496These implementations may even be separately compiled, unlike \CC template functions.
497However, the \CFA type-checker ensures matching types are used by all calls to @?+?@, preventing nonsensical computations like adding a length to a volume.
503In many languages, functions can return at most one value;
504however, many operations have multiple outcomes, some exceptional.
505Consider C's @div@ and @remquo@ functions, which return the quotient and remainder for a division of integer and floating-point values, respectively.
507typedef struct { int quo, rem; } div_t;
508div_t div( int num, int den );
509double remquo( double num, double den, int * quo );
510div_t qr = div( 13, 5 );                                        $\C{// return quotient/remainder aggregate}$
511int q;
512double r = remquo( 13.5, 5.2, &q );                     $\C{// return remainder, alias quotient}$
514@div@ aggregates the quotient/remainder in a structure, while @remquo@ aliases a parameter to an argument.
515Both approaches are awkward.
516Alternatively, a programming language can directly support returning multiple values, \eg in \CFA:
518[ int, int ] div( int num, int den );           $\C{// return two integers}$
519[ double, double ] div( double num, double den ); $\C{// return two doubles}$
520int q, r;                                                                       $\C{// overload variable names}$
521double q, r;
522[ q, r ] = div( 13, 5 );                                        $\C{// select appropriate div and q, r}$
523[ q, r ] = div( 13.5, 5.2 );
525Clearly, this approach is straightforward to understand and use;
526therefore, why do few programming languages support this obvious feature or provide it awkwardly?
527The answer is that there are complex consequences that cascade through multiple aspects of the language, especially the type-system.
528This section show these consequences and how \CFA deals with them.
531\subsection{Tuple Expressions}
533The addition of multiple-return-value functions (MRVF) are useless without a syntax for accepting multiple values at the call-site.
534The simplest mechanism for capturing the return values is variable assignment, allowing the values to be retrieved directly.
535As such, \CFA allows assigning multiple values from a function into multiple variables, using a square-bracketed list of lvalue expressions (as above), called a \emph{tuple}.
537However, functions also use \emph{composition} (nested calls), with the direct consequence that MRVFs must also support composition to be orthogonal with single-returning-value functions (SRVF), \eg:
539printf( "%d %d\n", div( 13, 5 ) );                      $\C{// return values seperated into arguments}$
541Here, the values returned by @div@ are composed with the call to @printf@.
542However, the \CFA type-system must support significantly more complex composition:
544[ int, int ] foo$\(_1\)$( int );
545[ double ] foo$\(_2\)$( int );
546void bar( int, double, double );
547bar( foo( 3 ), foo( 3 ) );
549The type-resolver only has the tuple return-types to resolve the call to @bar@ as the @foo@ parameters are identical, which involves unifying the possible @foo@ functions with @bar@'s parameter list.
550No combination of @foo@s are an exact match with @bar@'s parameters, so the resolver applies C conversions.
551The minimal cost is @bar( foo@$_1$@( 3 ), foo@$_2$@( 3 ) )@, giving (@int@, {\color{green}@int@}, @double@) to (@int@, {\color{green}@double@}, @double@) with one {\color{green}safe} (widening) conversion from @int@ to @double@ versus ({\color{red}@double@}, {\color{green}@int@}, {\color{green}@int@}) to ({\color{red}@int@}, {\color{green}@double@}, {\color{green}@double@}) with one {\color{red}unsafe} (narrowing) conversion from @double@ to @int@ and two safe conversions.
554\subsection{Tuple Variables}
556An important observation from function composition is that new variable names are not required to initialize parameters from an MRVF.
557\CFA also allows declaration of tuple variables that can be initialized from an MRVF, since it can be awkward to declare multiple variables of different types.
558As a consequence, \CFA allows declaration of \emph{tuple variables} that can be initialized from an MRVF, \eg:
560[ int, int ] qr = div( 13, 5 );                         $\C{// tuple-variable declaration and initialization}$
561[ double, double ] qr = div( 13.5, 5.2 );
563where the tuple variable-name serves the same purpose as the parameter name(s).
564Tuple variables can be composed of any types, except for array types, since array sizes are generally unknown.
566One way to access the tuple-variable components is with assignment or composition:
568[ q, r ] = qr;                                                          $\C{// access tuple-variable components}$
569printf( "%d %d\n", qr );
571\CFA also supports \emph{tuple indexing} to access single components of a tuple expression:
573[int, int] * p = &qr;                                           $\C{// tuple pointer}$
574int rem = qr.1;                                                         $\C{// access remainder}$
575int quo = div( 13, 5 ).0;                                       $\C{// access quotient}$
576p->0 = 5;                                                                       $\C{// change quotient}$
577bar( qr.1, qr );                                                        $\C{// pass remainder and quotient/remainder}$
578rem = [42, div( 13, 5 )].0.1;                           $\C{// access 2nd component of 1st component of tuple expression}$
582\subsection{Flattening and Restructuring}
584In function call contexts, tuples support implicit flattening and restructuring conversions.
585Tuple flattening recursively expands a tuple into the list of its basic components.
586Tuple structuring packages a list of expressions into a value of tuple type, \eg:
591int f( int, int );
592int g( [int, int] );
593int h( int, [int, int] );
594[int, int] x;
598int y;
599f( x );                 $\C[1in]{// flatten}$
600g( y, 10 );             $\C{// structure}$
601h( x, y );              $\C{// flatten and structure}\CRT{}$
606In the call to @f@, @x@ is implicitly flattened so the components of @x@ are passed as the two arguments.
607In the call to @g@, the values @y@ and @10@ are structured into a single argument of type @[int, int]@ to match the parameter type of @g@.
608Finally, in the call to @h@, @x@ is flattened to yield an argument list of length 3, of which the first component of @x@ is passed as the first parameter of @h@, and the second component of @x@ and @y@ are structured into the second argument of type @[int, int]@.
609The flexible structure of tuples permits a simple and expressive function call syntax to work seamlessly with both SRVF and MRVF, and with any number of arguments of arbitrarily complex structure.
612\subsection{Tuple Assignment}
614An assignment where the left side is a tuple type is called \emph{tuple assignment}.
615There are two kinds of tuple assignment depending on whether the right side of the assignment operator has a tuple type or a non-tuple type, called \emph{multiple} and \emph{mass assignment}, respectively.
620int x = 10;
621double y = 3.5;
622[int, double] z;
627z = [x, y];             $\C[1in]{// multiple assignment}$
628[x, y] = z;             $\C{// multiple assignment}$
629z = 10;                 $\C{// mass assignment}$
630[y, x] = 3.14$\C{// mass assignment}\CRT{}$
635Both kinds of tuple assignment have parallel semantics, so that each value on the left and right side is evaluated before any assignments occur.
636As a result, it is possible to swap the values in two variables without explicitly creating any temporary variables or calling a function, \eg, @[x, y] = [y, x]@.
637This semantics means mass assignment differs from C cascading assignment (\eg @a = b = c@) in that conversions are applied in each individual assignment, which prevents data loss from the chain of conversions that can happen during a cascading assignment.
638For example, @[y, x] = 3.14@ performs the assignments @y = 3.14@ and @x = 3.14@, yielding @y == 3.14@ and @x == 3@;
639whereas C cascading assignment @y = x = 3.14@ performs the assignments @x = 3.14@ and @y = x@, yielding @3@ in @y@ and @x@.
640Finally, tuple assignment is an expression where the result type is the type of the left-hand side of the assignment, just like all other assignment expressions in C.
641This example shows mass, multiple, and cascading assignment used in one expression:
643void f( [int, int] );
644f( [x, y] = z = 1.5 );                                          $\C{// assignments in parameter list}$
648\subsection{Member Access}
650It is also possible to access multiple fields from a single expression using a \emph{member-access}.
651The result is a single tuple-valued expression whose type is the tuple of the types of the members, \eg:
653struct S { int x; double y; char * z; } s;
654s.[x, y, z] = 0;
656Here, the mass assignment sets all members of @s@ to zero.
657Since tuple-index expressions are a form of member-access expression, it is possible to use tuple-index expressions in conjunction with member tuple expressions to manually restructure a tuple (\eg rearrange, drop, and duplicate components).
662[int, int, long, double] x;
663void f( double, long );
668x.[0, 1] = x.[1, 0];    $\C[1in]{// rearrange: [x.0, x.1] = [x.1, x.0]}$
669f( x.[0, 3] );            $\C{// drop: f(x.0, x.3)}\CRT{}$
670[int, int, int] y = x.[2, 0, 2]; // duplicate: [y.0, y.1, y.2] = [x.2, x.0. x.2]
675It is also possible for a member access to contain other member accesses, \eg:
677struct A { double i; int j; };
678struct B { int * k; short l; };
679struct C { int x; A y; B z; } v;
680v.[x, y.[i, j], z.k];                                           $\C{// [v.x, [v.y.i, v.y.j], v.z.k]}$
687In C, the cast operator is used to explicitly convert between types. In \CFA, the cast operator has a secondary use as type ascription. That is, a cast can be used to select the type of an expression when it is ambiguous, as in the call to an overloaded function:
689int f();     // (1)
690double f()// (2)
692f();       // ambiguous - (1),(2) both equally viable
693(int)f()// choose (2)
696Since casting is a fundamental operation in \CFA, casts should be given a meaningful interpretation in the context of tuples. Taking a look at standard C provides some guidance with respect to the way casts should work with tuples:
698int f();
699void g();
701(void)f()// (1)
702(int)g()// (2)
704In C, (1) is a valid cast, which calls @f@ and discards its result. On the other hand, (2) is invalid, because @g@ does not produce a result, so requesting an @int@ to materialize from nothing is nonsensical. Generalizing these principles, any cast wherein the number of components increases as a result of the cast is invalid, while casts that have the same or fewer number of components may be valid.
706Formally, a cast to tuple type is valid when $T_n \leq S_m$, where $T_n$ is the number of components in the target type and $S_m$ is the number of components in the source type, and for each $i$ in $[0, n)$, $S_i$ can be cast to $T_i$. Excess elements ($S_j$ for all $j$ in $[n, m)$) are evaluated, but their values are discarded so that they are not included in the result expression. This approach follows naturally from the way that a cast to @void@ works in C.
708For example, in
710[int, int, int] f();
711[int, [int, int], int] g();
713([int, double])f();           $\C{// (1)}$
714([int, int, int])g();         $\C{// (2)}$
715([void, [int, int]])g();      $\C{// (3)}$
716([int, int, int, int])g();    $\C{// (4)}$
717([int, [int, int, int]])g()$\C{// (5)}$
720(1) discards the last element of the return value and converts the second element to @double@. Since @int@ is effectively a 1-element tuple, (2) discards the second component of the second element of the return value of @g@. If @g@ is free of side effects, this expression is equivalent to @[(int)(g().0), (int)(g().1.0), (int)(g().2)]@.
721Since @void@ is effectively a 0-element tuple, (3) discards the first and third return values, which is effectively equivalent to @[(int)(g().1.0), (int)(g().1.1)]@).
723Note that a cast is not a function call in \CFA, so flattening and structuring conversions do not occur for cast expressions\footnote{User-defined conversions have been considered, but for compatibility with C and the existing use of casts as type ascription, any future design for such conversions would require more precise matching of types than allowed for function arguments and parameters.}. As such, (4) is invalid because the cast target type contains 4 components, while the source type contains only 3. Similarly, (5) is invalid because the cast @([int, int, int])(g().1)@ is invalid. That is, it is invalid to cast @[int, int]@ to @[int, int, int]@.
729Tuples also integrate with \CFA polymorphism as a kind of generic type.
730Due to the implicit flattening and structuring conversions involved in argument passing, @otype@ and @dtype@ parameters are restricted to matching only with non-tuple types, \eg:
732forall(otype T, dtype U) void f( T x, U * y );
733f( [5, "hello"] );
735where @[5, "hello"]@ is flattened, giving argument list @5, "hello"@, and @T@ binds to @int@ and @U@ binds to @const char@.
736Tuples, however, may contain polymorphic components.
737For example, a plus operator can be written to add two triples together.
739forall(otype T | { T ?+?( T, T ); }) [T, T, T] ?+?( [T, T, T] x, [T, T, T] y ) {
740        return [x.0 + y.0, x.1 + y.1, x.2 + y.2];
742[int, int, int] x;
743int i1, i2, i3;
744[i1, i2, i3] = x + ([10, 20, 30]);
747Flattening and restructuring conversions are also applied to tuple types in polymorphic type assertions.
749int f( [int, double], double );
750forall(otype T, otype U | { T f( T, U, U ); })
751void g( T, U );
752g( 5, 10.21 );
754Hence, function parameter and return lists are flattened for the purposes of type unification allowing the example to pass expression resolution.
755This relaxation is possible by extending the thunk scheme described by \citet{Bilson03}.
756Whenever a candidate's parameter structure does not exactly match the formal parameter's structure, a thunk is generated to specialize calls to the actual function:
758int _thunk( int _p0, double _p1, double _p2 ) {
759        return f( [_p0, _p1], _p2 );
762so the thunk provides flattening and structuring conversions to inferred functions, improving the compatibility of tuples and polymorphism.
763These thunks take advantage of GCC C nested-functions to produce closures that have the usual function pointer signature.
766\subsection{Variadic Tuples}
768To define variadic functions, \CFA adds a new kind of type parameter, @ttype@ (tuple type).
769Matching against a @ttype@ parameter consumes all remaining argument components and packages them into a tuple, binding to the resulting tuple of types.
770In a given parameter list, there must be at most one @ttype@ parameter that occurs last, which matches normal variadic semantics, with a strong feeling of similarity to \CCeleven variadic templates.
771As such, @ttype@ variables are also called \emph{argument packs}.
773Like variadic templates, the main way to manipulate @ttype@ polymorphic functions is via recursion.
774Since nothing is known about a parameter pack by default, assertion parameters are key to doing anything meaningful.
775Unlike variadic templates, @ttype@ polymorphic functions can be separately compiled.
776For example, a generalized @sum@ function written using @ttype@:
778int sum$\(_0\)$() { return 0; }
779forall(ttype Params | { int sum( Params ); } ) int sum$\(_1\)$( int x, Params rest ) {
780        return x + sum( rest );
782sum( 10, 20, 30 );
784Since @sum@\(_0\) does not accept any arguments, it is not a valid candidate function for the call @sum(10, 20, 30)@.
785In order to call @sum@\(_1\), @10@ is matched with @x@, and the argument resolution moves on to the argument pack @rest@, which consumes the remainder of the argument list and @Params@ is bound to @[20, 30]@.
786The process continues, @Params@ is bound to @[]@, requiring an assertion @int sum()@, which matches @sum@\(_0\) and terminates the recursion.
787Effectively, this algorithm traces as @sum(10, 20, 30)@ $\rightarrow$ @10 + sum(20, 30)@ $\rightarrow$ @10 + (20 + sum(30))@ $\rightarrow$ @10 + (20 + (30 + sum()))@ $\rightarrow$ @10 + (20 + (30 + 0))@.
789It is reasonable to take the @sum@ function a step further to enforce a minimum number of arguments:
791int sum( int x, int y ) { return x + y; }
792forall(ttype Params | { int sum( int, Params ); } ) int sum( int x, int y, Params rest ) {
793        return sum( x + y, rest );
796One more step permits the summation of any summable type with all arguments of the same type:
798trait summable(otype T) {
799        T ?+?( T, T );
801forall(otype R | summable( R ) ) R sum( R x, R y ) {
802        return x + y;
804forall(otype R, ttype Params | summable(R) | { R sum(R, Params); } ) R sum(R x, R y, Params rest) {
805        return sum( x + y, rest );
808Unlike C variadic functions, it is unnecessary to hard code the number and expected types.
809Furthermore, this code is extendable so any user-defined type with a @?+?@ operator.
810Summing arbitrary heterogeneous lists is possible with similar code by adding the appropriate type variables and addition operators.
812It is also possible to write a type-safe variadic print function to replace @printf@:
814struct S { int x, y; };
815forall(otype T, ttype Params | { void print(T); void print(Params); }) void print(T arg, Params rest) {
816        print(arg);
817        print(rest);
819void print( char * x ) { printf( "%s", x ); }
820void print( int x ) { printf( "%d", x ); }
821void print( S s ) { print( "{ ", s.x, ",", s.y, " }" ); }
822print( "s = ", (S){ 1, 2 }, "\n" );
824This example showcases a variadic-template-like decomposition of the provided argument list.
825The individual @print@ functions allow printing a single element of a type.
826The polymorphic @print@ allows printing any list of types, as long as each individual type has a @print@ function.
827The individual print functions can be used to build up more complicated @print@ functions, such as for @S@, which is something that cannot be done with @printf@ in C.
829Finally, it is possible to use @ttype@ polymorphism to provide arbitrary argument forwarding functions.
830For example, it is possible to write @new@ as a library function:
832struct pair( otype R, otype S );
833forall( otype R, otype S ) void ?{}( pair(R, S) *, R, S );  // (1)
834forall( dtype T, ttype Params | sized(T) | { void ?{}( T *, Params ); } ) T * new( Params p ) {
835        return ((T*)malloc( sizeof(T) )){ p }; // construct into result of malloc
837pair( int, char ) * x = new( 42, '!' );
839The @new@ function provides the combination of type-safe @malloc@ with a \CFA constructor call, making it impossible to forget constructing dynamically allocated objects.
840This function provides the type-safety of @new@ in \CC, without the need to specify the allocated type again, thanks to return-type inference.
842% In the call to @new@, @pair(double, char)@ is selected to match @T@, and @Params@ is expanded to match @[double, char]@. The constructor (1) may be specialized to  satisfy the assertion for a constructor with an interface compatible with @void ?{}(pair(int, char) *, int, char)@.
847Tuples are implemented in the \CFA translator via a transformation into generic types.
848For each $N$, the first time an $N$-tuple is seen in a scope a generic type with $N$ type parameters is generated. \eg:
850[int, int] f() {
851        [double, double] x;
852        [int, double, int] y;
855is transformed into:
857// generated before the first 2-tuple
858forall(dtype T0, dtype T1 | sized(T0) | sized(T1)) struct _tuple2 {
859        T0 field_0;
860        T1 field_1;
862_tuple2(int, int) f() {
863        _tuple2(double, double) x;
864        // generated before the first 3-tuple
865        forall(dtype T0, dtype T1, dtype T2 | sized(T0) | sized(T1) | sized(T2)) struct _tuple3 {
866                T0 field_0;
867                T1 field_1;
868                T2 field_2;
869        };
870        _tuple3(int, double, int) y;
873Tuple expressions are then simply converted directly into compound literals:
875[5, 'x', 1.24];
879(_tuple3(int, char, double)){ 5, 'x', 1.24 };
883Since tuples are essentially structures, tuple indexing expressions are just field accesses:
885void f(int, [double, char]);
886[int, double] x;
889printf("%d %g\n", x);
890f(x, 'z');
892Is transformed into:
894void f(int, _tuple2(double, char));
895_tuple2(int, double) x;
898printf("%d %g\n", x.field_0, x.field_1);
899f(x.field_0, (_tuple2){ x.field_1, 'z' });
901Note that due to flattening, @x@ used in the argument position is converted into the list of its fields. In the call to @f@, the second and third argument components are structured into a tuple argument. Similarly, tuple member expressions are recursively expanded into a list of member access expressions.
903Expressions that may contain side effects are made into \emph{unique expressions} before being expanded by the flattening conversion. Each unique expression is assigned an identifier and is guaranteed to be executed exactly once:
905void g(int, double);
906[int, double] h();
909Internally, this expression is converted to two variables and an expression:
911void g(int, double);
912[int, double] h();
914_Bool _unq0_finished_ = 0;
915[int, double] _unq0;
917        (_unq0_finished_ ? _unq0 : (_unq0 = f(), _unq0_finished_ = 1, _unq0)).0,
918        (_unq0_finished_ ? _unq0 : (_unq0 = f(), _unq0_finished_ = 1, _unq0)).1,
921Since argument evaluation order is not specified by the C programming language, this scheme is built to work regardless of evaluation order. The first time a unique expression is executed, the actual expression is evaluated and the accompanying boolean is set to true. Every subsequent evaluation of the unique expression then results in an access to the stored result of the actual expression. Tuple member expressions also take advantage of unique expressions in the case of possible impurity.
923Currently, the \CFA translator has a very broad, imprecise definition of impurity, where any function call is assumed to be impure. This notion could be made more precise for certain intrinsic, auto-generated, and builtin functions, and could analyze function bodies when they are available to recursively detect impurity, to eliminate some unique expressions.
925The various kinds of tuple assignment, constructors, and destructors generate GNU C statement expressions. A variable is generated to store the value produced by a statement expression, since its fields may need to be constructed with a non-trivial constructor and it may need to be referred to multiple time, \eg in a unique expression. The use of statement expressions allows the translator to arbitrarily generate additional temporary variables as needed, but binds the implementation to a non-standard extension of the C language. However, there are other places where the \CFA translator makes use of GNU C extensions, such as its use of nested functions, so this restriction is not new.
931\TODO{Magnus suggests we need some graphs, it's kind of a done thing that the reviewers will be looking for. Also, we've made some unsubstantiated claims about the runtime performance of \CFA, which some micro-benchmarks could help with. I'm thinking a simple stack push and pop, with an idiomatic \lstinline@void*@, \CFA, \CC template and \CC virtual inheritance versions (the void* and virtual inheritance versions likely need to be linked lists, or clumsy in their API -- possibly both versions) to test generics, and variadic print to test tuples. We measure SLOC, runtime performance, executable size (making sure to include benchmarks for multiple types in the executable), and possibly manually count the number of places where the programmer must provide un-type-checked type information. Appendices don't count against our page limit, so we might want to include the source code for the benchmarks (or at least the relevant implementation details) in one.}
934\section{Related Work}
936\CC is the existing language it is most natural to compare \CFA to, as they are both more modern extensions to C with backwards source compatibility. The most fundamental difference in approach between \CC and \CFA is their approach to this C compatibility. \CC does provide fairly strong source backwards compatibility with C, but is a dramatically more complex language than C, and imposes a steep learning curve to use many of its extension features. For instance, in a break from general C practice, template code is typically written in header files, with a variety of subtle restrictions implied on its use by this choice, while the other polymorphism mechanism made available by \CC, class inheritance, requires programmers to learn an entirely new object-oriented programming paradigm; the interaction between templates and inheritance is also quite complex. \CFA, by contrast, has a single facility for polymorphic code, one which supports separate compilation and the existing procedural paradigm of C code. A major difference between the approaches of \CC and \CFA to polymorphism is that the set of assumed properties for a type is \emph{explicit} in \CFA. One of the major limiting factors of \CC's approach is that templates cannot be separately compiled, and, until concepts~\citep{C++Concepts} are standardized (currently anticipated for \CCtwenty), \CC provides no way to specify the requirements of a generic function in code beyond compilation errors for template expansion failures. By contrast, the explicit nature of assertions in \CFA allows polymorphic functions to be separately compiled, and for their requirements to be checked by the compiler; similarly, \CFA generic types may be opaque, unlike \CC template classes.
938Cyclone also provides capabilities for polymorphic functions and existential types~\citep{Grossman06}, similar in concept to \CFA's @forall@ functions and generic types. Cyclone existential types can include function pointers in a construct similar to a virtual function table, but these pointers must be explicitly initialized at some point in the code, a tedious and potentially error-prone process. Furthermore, Cyclone's polymorphic functions and types are restricted in that they may only abstract over types with the same layout and calling convention as @void*@, in practice only pointer types and @int@ - in \CFA terms, all Cyclone polymorphism must be dtype-static. This design provides the efficiency benefits discussed in Section~\ref{sec:generic-apps} for dtype-static polymorphism, but is more restrictive than \CFA's more general model.
940Apple's Objective-C \citep{obj-c-book} is another industrially successful set of extensions to C. The Objective-C language model is a fairly radical departure from C, adding object-orientation and message-passing. Objective-C implements variadic functions using the C @va_arg@ mechanism, and did not support type-checked generics until recently \citep{xcode7}, historically using less-efficient and more error-prone runtime checking of object types instead. The GObject framework \citep{GObject} also adds object-orientation with runtime type-checking and reference-counting garbage-collection to C; these are much more intrusive feature additions than those provided by \CFA, in addition to the runtime overhead of reference-counting. The Vala programming language \citep{Vala} compiles to GObject-based C, and so adds the burden of learning a separate language syntax to the aforementioned demerits of GObject as a modernization path for existing C code-bases. Java \citep{Java8} has had generic types and variadic functions since Java~5; Java's generic types are type-checked at compilation and type-erased at runtime, similar to \CFA's, though in Java each object carries its own table of method pointers, while \CFA passes the method pointers separately so as to maintain a C-compatible struct layout. Java variadic functions are simply syntactic sugar for an array of a single type, and therefore less useful than \CFA's heterogeneously-typed variadic functions. Java is also a garbage-collected, object-oriented language, with the associated resource usage and C-interoperability burdens.
942D \citep{D}, Go \citep{Go}, and Rust \citep{Rust} are modern, compiled languages with abstraction features similar to \CFA traits, \emph{interfaces} in D and Go and \emph{traits} in Rust. However, each language represents dramatic departures from C in terms of language model, and none has the same level of compatibility with C as \CFA. D and Go are garbage-collected languages, imposing the associated runtime overhead. The necessity of accounting for data transfer between the managed Go runtime and the unmanaged C runtime complicates foreign-function interface between Go and C. Furthermore, while generic types and functions are available in Go, they are limited to a small fixed set provided by the compiler, with no language facility to define more. D restricts garbage collection to its own heap by default, while Rust is not garbage-collected, and thus has a lighter-weight runtime that is more easily interoperable with C. Rust also possesses much more powerful abstraction capabilities for writing generic code than Go. On the other hand, Rust's borrow-checker, while it does provide strong safety guarantees, is complex and difficult to learn, and imposes a distinctly idiomatic programming style on Rust. \CFA, with its more modest safety features, is significantly easier to port C code to, while maintaining the idiomatic style of the original source.
944\section{Conclusion \& Future Work}
946There is ongoing work on a wide range of \CFA feature extensions, including reference types, exceptions, and concurrent programming primitives. In addition to this work, there are some interesting future directions the polymorphism design could take. Notably, \CC template functions trade compile time and code bloat for optimal runtime of individual instantiations of polymorphic functions. \CFA polymorphic functions, by contrast, use an approach that is essentially dynamic virtual dispatch. The runtime overhead of this approach is low, but not as low as \CC template functions, and it may be beneficial to provide a mechanism for particularly performance-sensitive code to close this gap. Further research is needed, but two promising approaches are to allow an annotation on polymorphic function call sites that tells the translator to create a template-specialization of the function (provided the code is visible in the current translation unit) or placing an annotation on polymorphic function definitions that instantiates a version of the polymorphic function specialized to some set of types. These approaches are not mutually exclusive, and would allow these performance optimizations to be applied only where most useful to increase performance, without suffering the code bloat or loss of generality of a template expansion approach where it is unnecessary.
948In conclusion, the authors' design for generic types and tuples, unlike those available in existing work, is both reusable and type-checked, while still supporting a full range of C features, including separately-compiled modules. We have experimentally validated the performance of our design against both \CC and standard C, showing it is \TODO{shiny, cap'n}.
951The authors would like to thank Magnus Madsen for valuable editorial feedback.
953This work is supported in part by a corporate partnership with \grantsponsor{Huawei}{Huawei Ltd.}{}\ and the first author's \grantsponsor{NSERC-PGS}{NSERC PGS D}{} scholarship.
961% Local Variables: %
962% tab-width: 4 %
963% compile-command: "make" %
964% End: %
Note: See TracBrowser for help on using the repository browser.