Opened 12 years ago

Closed 10 years ago

#2254 closed proposal (fixed)

have Control.Arrow re-export (>>>) and (<<<)

Reported by: ross Owned by:
Priority: normal Milestone: Not GHC
Component: libraries/base Version: 6.8.2
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:


#1773 split the Arrow class, making (>>>) and (<<<) functions in Control.Category. This breaks programs that use Control.Arrow.

To avoid some of the breakage, the proposal is that Control.Arrow should re-export (>>>) and (<<<), imported from Control.Category.

Change History (5)

comment:1 Changed 12 years ago by ganesh

I support this; I think it's unnecessarily burdensome on users to have to import Control.Category when using arrows.

comment:2 Changed 12 years ago by igloo

difficulty: Unknown
Milestone: Not GHC

comment:3 Changed 11 years ago by simonmar

Architecture: UnknownUnknown/Multiple

comment:4 Changed 11 years ago by simonmar

Operating System: UnknownUnknown/Multiple

comment:5 Changed 10 years ago by ross

Resolution: fixed
Status: newclosed

fait accompli

Note: See TracTickets for help on using tickets.