Different implementation for PAKCS in Applicative IO - instance
In the version3 Prelude (*>) is defined as seqIO for PAKCS and as m >>= \_ -> k for KICS2.
Is there any reason for this?
Currently this leads to a warning when compiling with KICS2.
It would be nice to just keep the KICS2 Definition and let the PAKCS override the definition internally.
To upload designs, you'll need to enable LFS. More information