Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
| No. |
Time |
User |
SHA256 |
| -r1 (spooky-0.1.0.0-r1) |
2021-12-13T06:56:52Z |
fresheyeball |
cfb2e8d844df3ec1fbbe26f8496b1dd6c02609ff38dc5c54586e1c47ecd23249
|
|
Changed synopsis
from Unified api for phantom typed newtypes and type aliases
to Unified API for phantom typed newtypes and type aliases Changed description
from In scenarios where newtypes are not well supported, we may need
to use type aliases instead for various reasons. This means we
give away type safety, and static analysis tooling. We can get this
safety back with Spooky. When we compile with -f typed, we
get a type check using newtypes. When compiled without the flag
we get the same code type checking with type aliases.
to In scenarios where newtypes are not well supported, we may need
to use type aliases instead for various reasons. This means we
give away type safety and static analysis tooling. We can get this
safety back with Spooky. When we compile with -f typed, we
get a type check using newtypes. When compiled without the flag
we get the same code type checking with type aliases.
|
| -r0 (spooky-0.1.0.0-r0) |
2021-12-13T06:36:13Z |
fresheyeball |
64844b2f7a4436c3af61d4a1bcbfe21ee296c82c62240e518e61c05393ac68a9
|
|
|