I suspect this is because GHC will not specialise functions when used
in other modules unless they are marked INLINABLE.
Matt
On Fri, Mar 3, 2017 at 11:40 AM, Joachim Breitner
Hi,
Am Donnerstag, den 02.03.2017, 18:18 +0300 schrieb David Sorokin:
I offer to define the functions of the Control.Category module inlinable:
-- | Right-to-left composition (<<<) :: Category cat => cat b c -> cat a b -> cat a c {-# INLINABLE (<<<) #-} (<<<) = (.)
-- | Left-to-right composition (>>>) :: Category cat => cat a b -> cat b c -> cat a c {-# INLINABLE (>>>) #-} f >>> g = g . f
Perhaps all functions from this module should be marked by this pragma as possible.
I am surprised that GHC does not consider these inlineable automatically. Maybe it should? Would be worth investigating, if someone is interested in some entry-level GHC hacking, why GHC does not treat them as `INLINEABLE` in the first place. They are certainly small enough, I would say…
Joachim
-- Joachim “nomeata” Breitner mail@joachim-breitner.de • https://www.joachim-breitner.de/ XMPP: nomeata@joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.