|
|
|
|
|
|
|
Eric Mertens kindly offered to scribe meeting minutes from our most recent meeting. Here they are:
|
|
Eric Mertens kindly offered to scribe meeting minutes from our most recent meeting. Here they are:
|
|
|
|
|
|
|
|
|
|
|
|
## Meeting Notes
|
|
## Meeting Notes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This meeting was held Thursday, November 5, 2015 at 20:00 UTC
|
|
This meeting was held Thursday, November 5, 2015 at 20:00 UTC
|
|
|
|
|
|
|
|
## Discussion around `Semigroup.sconcat`
|
|
|
|
|
|
## Discussion around Semigroup.sconcat
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The committee decided to keep sconcat in the Semigroup class when merging it into base.
|
|
|
|
|
|
|
|
|
|
|
|
|
The committee decided to keep sconcat in the Semigroup class when merging it into base. [Proposals/SemigroupMonoid](libraries/proposals/semigroup-monoid)
|
|
## Timeline for MonadFail? transition
|
|
|
|
|
|
|
|
## Timeline for `MonadFail` transition
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The committee decided that the `MonadFail` class should appear in Prelude in GHC 8.4, the same time as fail switches over to the new class. [Proposals/MonadFail](libraries/proposals/monad-fail)
|
|
The committee decided that the MonadFail? class should appear in Prelude in GHC 8.4, the same time as fail switches over to the new class.
|
|
|
|
|
|
|
|
|
|
|
|
## Adding floating-point operators
|
|
## Adding floating-point operators
|
|
|
|
|
|
|
|
|
|
|
|
|
The committee decided to introduce the new operators to the class with suitable default implementations. The new methods would not be exported in Prelude. Decisions about removing the default implementations in the future are deferred to a future committee. [Proposals/ExpandFloating](libraries/proposals/expand-floating)
|
|
|
|
|
|
The committee decided to introduce the new operators to the class with suitable default implementations. The new methods would not be exported in Prelude. Decisions about removing the default implementations in the future are deferred to a future committee.
|
|
|
|
|
|
|
|
|
|
|
|
## Documenting the “Three Release Policy"
|
|
## Documenting the “Three Release Policy"
|
|
|
|
|
|
|
|
|
|
|
|
|
The committee Joachim offered to take on the task of preparing a wiki page for the [ policy](https://groups.google.com/forum/#!msg/haskell-core-libraries/qXYMfV8JZ6k/tTuFrBMdDgAJ).
|
|
|
|
|
|
The committee Joachim offered to take on the task of preparing a wiki page for the policy.
|
|
|
|
|
|
|
|
|
|
|
|
## Working with Mike Meyer on change process
|
|
## Working with Mike Meyer on change process
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Edward is going to chat with Mike to see if he’d be interested in the editorial aspects of change management
|
|
Edward is going to chat with Mike to see if he’d be interested in the editorial aspects of change management
|
|
|
|
|
|
|
|
|
|
|
|
## Trac-ing proposals
|
|
## Trac-ing proposals
|
|
|
|
|
|
|
|
|
|
|
|
|
The committee agreed that proposals should be tracked on the Haskell Prime Trac instance. [https://prime.haskell.org/wiki/Libraries/Proposals](https://prime.haskell.org/wiki/Libraries/Proposals)
|
|
|
|
|
|
The committee agreed that proposals should be tracked on the Haskell Prime Trac instance.
|
|
|
|
|
|
|
|
|
|
|
|
## Updating committee membership
|
|
## Updating committee membership
|
|
|
|
|
|
|
|
|
|
|
|
|
We discussed replacing the HP ex-officio committee membership with three new slots. The goal of the expansion would be to incorporate more diverse views in order to strengthen the mandate of the committee to guide the libraries. Edward expects to reopen the chair position next year. [ https://mail.haskell.org/pipermail/libraries/2015-November/026497.html](https://mail.haskell.org/pipermail/libraries/2015-November/026497.html)
|
|
|
|
|
|
We discussed replacing the HP ex-officio committee membership with three new slots. The goal of the expansion would be to incorporate more diverse views in order to strengthen the mandate of the committee to guide the libraries. Edward expects to reopen the chair position next year.
|
|
|
|
|
|
|
|
|
|
|
|
## Recurring meetings
|
|
## Recurring meetings
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The committee agreed that regularly scheduled, bi-monthly meetings would be useful for coordinating committee actions.
|
|
The committee agreed that regularly scheduled, bi-monthly meetings would be useful for coordinating committee actions.
|
|
|
|
|
|
|
|
|
|
|
|
## Removing return from Monad
|
|
## Removing return from Monad
|
|
|
|
|
|
|
|
|
|
|
|
|
The committee agreed to leave return in the Monad class at this point. With the default implementation available in GHC 7.10, this question can be revisited at a future release. There was agreement, however, on resolving to work toward removing (\>\>) from the class while preserving performance across a window of versions. [ https://mail.haskell.org/pipermail/libraries/2015-September/026121.html](https://mail.haskell.org/pipermail/libraries/2015-September/026121.html) |
|
|
|
\ No newline at end of file |
|
The committee agreed to leave return in the Monad class at this point. With the default implementation available in GHC 7.10, this question can be revisited at a future release. There was agreement, however, on resolving to work toward removing (\>\>) from the class while preserving performance across a window of versions.
|
|
|
|
|
|
|
|
|