| Commit message (Collapse) | Author | Age |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
No horde-ad test speedup noticed.
|
| |
|
|
| |
This should allow foldr/build fusion
|
| | |
|
| |
|
|
| |
This speeds up {r,s}generatePrim
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The explicit usage at Int in the non-primed versions of the functions
results in an auto-generated SPEC rule at Int, so even without any
SPECIALIZE pragmas, using sh?Enum' at Int should not (need to) result in
multiple specialisations.
|
| | |
|
| |
|
|
| |
and probably more sound than earlier versions.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This ensures that the argument order consistently puts the main thing
being operated on at the end, and supporting singletons at the start.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|