As part of my Core Libraries Committee (CLC) involvement, I committed to writing monthly CLC updates, and this is the 3rd update.
Previous update:
All CLC work is done by volunteers in their free time.
Featured discussion
Currently, the main and the longest discussion in CLC is about a base
split, GHC internal modules in base
, and how to move forward from the status quo.
All relevant discussions:
- PVP#46 | Formalize “.Internal” module convention
- HF#47 | Standard library reform: Split base
- CLC#145 | Buy-in for Technical Proposal #47
- CLC#146 | GHC-internal modules in
base
- CLC#162 | base API changes introduced by GHC proposal 475
New
List of newly opened proposals since the last update.
- #156: Expose sized integer types from Prelude
- #157: Add instances for StablePtr
- #158: Make the type of
(&)
analogous to the one of($)
- #160: Derive instance {Enum, Bounded, Num, Real, Integral} Compose f g a
Approved
List of approved proposals since the last update.
- #117: Export
fromThreadId
from GHC.Conc.Sync - #150: Port ghcjs-base.GHCJS.Foreign.Callback as base.GHC.JS.Foreign.Callback for the GHC JavaScript Backend
- #152: Generalize the type of keepAlive#, touch#
Declined
List of rejected proposals since the last update.
It was decided not to subject issues in the array
library to the CLC process:
As a consequence, a few array
-related issues were closed as out-of-scope:
Withdrawn
List of proposals withdrawn voluntarily by their authors.
-
#159: Automatic conversion of fixed-point representations in
Data.Fixed
- The author proposed the addition of a conversion function but an alternative already existing conversion function was suggested in replies (and the proposal itself received some pushback overall)
Abandoned or Dormant
List of abandoned proposals due to lack of progress from the proposal author.
None
Meta
List of CLC process updates and meta improvements.
-
#155: head/tail warnings: update migration entry
- Updated migration guide for the
head/tail
functions warnings
- Updated migration guide for the
-
#161: Add issue templates
- The CLC proposal issue template was added (mostly to remind authors that they’re responsible for actually implementing the proposal)
Feel free to share any feedback on these updates! Do you like the format? Do you like the granularity? Anything else