CLC Update (August 2023)

[ChShersh]

As part of my Core Libraries Committee (CLC) involvement, I committed to writing monthly CLC updates.

Previous update:

• CLC Update (July 2023)

All CLC work is done by volunteers in their free time.

Featured discussions

CLC also maintains PVP (a versioning policy, popular in the Haskell ecosystem and closest to what is supported by Hackage).

Last month was fruitful on various discussions, changes and improvements to PVP:

• #46: Formalize “.Internal” module convention
• #50: Add a FAQ entry about multiple public libraries
• #51: Drop the requirement of specifying upper bounds
• #52: Make clear the tree doesn’t precisely represent the spec
• #53: Make clear .Internal convention does not adhere to the spec
• #54: [RFC] Make PVP ecosystem/language agnostic)

New

List of newly opened proposals since the last update.

• #190: Adding Fix to base
• #192: numberToRangedRational: fix edge cases for exp ≈ (maxBound :: Int)
• #193: Expose Type from Prelude

Approved

List of approved proposals since the last update.

• #175: Allow lookup to fuse
• #179: Add INLINE[1] to compareInt / compareWord
• #186: Export List from GHC.List
• #187: Use native operations for Enum Int64 and Enum Word64 on 32-bit platforms
• #188: Add a few primops for memcpy, memmove, and memset

Declined

List of rejected proposals since the last update.

None

Withdrawn

List of proposals withdrawn voluntarily by their authors.

• #162: base API changes introduced by GHC proposal 475
  • Recently, HF accepted the GHC+CLC proposal about implementing all experimental features in the yet-to-be-created package ghc-experimental. So this CLC proposal was withdrawn with the idea to implement requested features in ghc-experimental instead of base.

Abandoned or Dormant

List of abandoned proposals due to lack of progress from the proposal author.

• #191: HasField for Maybe
  • The proposed feature received some pushback as being too experimental, and the proposal author decided to gather more usage data on the feature first

Meta

List of CLC process updates and meta improvements.

• #189: [Question] purpose and encoding of ioe_filename
  • An attempt to gather more feedback on the meaning of the field in question to understand what can be done to improve the situation

---

Feel free to share any feedback on these updates! Do you like the format? Do you like the granularity? Anything else