Context Navigation

Changes between Version 44 and Version 45 of DataParallel/VectPragma

v44	v45
47	47	indicates that the type `T` should be automatically vectorised even if it is imported. This is the default for all data types declared in the current module. If the type embeds no parallel arrays, no special vectorised representation will be generated.
48	48
49		The type constructor `T` must be in scope, but it may be imported. ~~'PData' and 'PRepr'~~ instances are automatically generated by the vectoriser.
	49	The type constructor `T` must be in scope, but it may be imported. `PData` and `PRepr` instances are automatically generated by the vectoriser.
50	50
51	51	Examples are the vectorisation of types, such as `Maybe` and `[]`, defined in the `Prelude`.
…	…
59	59	directs the vectoriser to replace `T` by `T'` in vectorised code. Vectorisation of `T` is abstract in that constructors of `T` may not occur in vectorised code.
60	60
61		The type constructor `T` must be in scope, but it may be imported. ~~'PData' and 'PRepr'~~ instances must be explicitly defined — they are not automatically generated.
	61	The type constructor `T` must be in scope, but it may be imported. `PData` and `PRepr` instances must be explicitly defined — they are not automatically generated.
62	62
63	63	An example is the vectorisation of parallel arrays, where `[::]` is replaced by `PArray` during vectorisation, but the vectoriser never looks at the representation of `[::]`.