Proposal: Remove Control.Concurrent{QSem, QSemN, , SampleVar, mergeIO, nmergeIO} from base
Henning Thielemann
lemming at henning-thielemann.de
Thu Jun 7 22:24:51 CEST 2012
- Previous message: Proposal: Remove Control.Concurrent{QSem, QSemN, , SampleVar, mergeIO, nmergeIO} from base
- Next message: Proposal: Remove Control.Concurrent{QSem, QSemN, , SampleVar, mergeIO, nmergeIO} from base
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Thu, 7 Jun 2012, Ganesh Sittampalam wrote:
> As a more general point, a principle of breaking things immediately also
> makes it very hard for people who want to support multiple versions of
> GHC or the platform. Even one release worth of deprecation is quite
> difficult if the replacement is introduced in version x and the obsolete
> version removed completely in version x+1, since there is nothing that
> will work in x-1, x and x+1. If you want your software to build in
> Debian sta[b]le as well as the bleeding edge, supporting three versions
> is often necessary.
+1 for deprecation cycle.
> In this case the replacement is an external library so can in theory be
> adopted immediately, but a maintainer would need to be following this
> list to know about the need to do so.
Is it possible to import a module from a user package that has the same
name as a 'base' module?
- Previous message: Proposal: Remove Control.Concurrent{QSem, QSemN, , SampleVar, mergeIO, nmergeIO} from base
- Next message: Proposal: Remove Control.Concurrent{QSem, QSemN, , SampleVar, mergeIO, nmergeIO} from base
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Libraries
mailing list