Single-level call rule and generics - Revision history

Bmeyer: /* Monomorphic formal generics */

2007-11-05T18:25:05Z

‎Monomorphic formal generics

2007-11-05T18:18:57Z

‎Monomorphic formal generics

2007-11-05T18:11:53Z

‎Monomorphic formal generics

@@ Line 37: / Line 37: @@
 The first idea is to be able to mark a formal generic as monomorphic:
 <e>
-class X [monomorphic G -> NUMERIC]
+class X [monomorphic G -> NUMERIC] feature
    f (g1, g2: G): G

← Older revision		Revision as of 18:18, 5 November 2007
Line 48:		Line 48:

	The class can then only be generically derived with monomorphic types, i.e. using [[interval types]] <e>X [INTEGER..INTEGER]</e> or <e>X [REAL..REAL]</e>.		The class can then only be generically derived with monomorphic types, i.e. using [[interval types]] <e>X [INTEGER..INTEGER]</e> or <e>X [REAL..REAL]</e>.
		+
		+	[Comment by BM 5 Nov 2007: this does not seem desirable as there is nothing
		+	wrong with the class, only with the feature.]

	For the check we can now assume that <e>G</e> will be monomorphic. This helps a little bit further: For every feature argument which is <e>like Current</e> we can assume that the exact type will be given. But this works only for covariant features which have <e>like Current</e> arguments which are never redefined into something else. Take the following classes for an example:		For the check we can now assume that <e>G</e> will be monomorphic. This helps a little bit further: For every feature argument which is <e>like Current</e> we can assume that the exact type will be given. But this works only for covariant features which have <e>like Current</e> arguments which are never redefined into something else. Take the following classes for an example:

@@ Line 47: / Line 47: @@
 </e>
-The generic class can then only be generically derived with monomorphic types, i.e. using [[interval types]] <e>X [INTEGER..INTEGER]</e> or <e>X [REAL..REAL]</e>.
+The class can then only be generically derived with monomorphic types, i.e. using [[interval types]] <e>X [INTEGER..INTEGER]</e> or <e>X [REAL..REAL]</e>.
 For the check we can now assume that <e>G</e> will be monomorphic. This helps a little bit further: For every feature argument which is <e>like Current</e> we can assume that the exact type will be given. But this works only for covariant features which have <e>like Current</e> arguments which are never redefined into something else. Take the following classes for an example: