# CLC Update (August 2023)

**URL:** <https://discourse.haskell.org/t/clc-update-august-2023/7210>\
**Category:** Core Libraries Committee\
**Created:** [August 4, 2023, 1:29pm UTC](https://discourse.haskell.org/t/clc-update-august-2023/7210 "2023-08-04T13:29:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChShersh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/chshersh/32/2551_2.png) [@ChShersh](https://discourse.haskell.org/u/ChShersh)\
**Post date:** [August 4, 2023, 1:29pm UTC](https://discourse.haskell.org/t/clc-update-august-2023/7210/1 "2023-08-04T13:29:01Z")

</div>

As part of my [Core Libraries Committee (CLC)](https://github.com/haskell/core-libraries-committee) involvement, I committed to writing monthly CLC updates.

Previous update:

- [CLC Update (July 2023)](http://discourse.haskell.org/t/clc-update-july-2023/6905)

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

### 💎 Featured discussions

CLC also maintains [PVP](https://pvp.haskell.org/) (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](https://github.com/haskell/pvp/pull/46) 🚫
- [#50: Add a FAQ entry about multiple public libraries](https://github.com/haskell/pvp/pull/50) 🆕 ✅
- [#51: Drop the requirement of specifying upper bounds](https://github.com/haskell/pvp/pull/51) 🆕 🔥
- [#52: Make clear the tree doesn’t precisely represent the spec](https://github.com/haskell/pvp/pull/52)🆕 ✅
- [#53: Make clear .Internal convention does not adhere to the spec](https://github.com/haskell/pvp/pull/53) 🆕 ✅
- [#54: [RFC] Make PVP ecosystem/language agnostic)](https://github.com/haskell/pvp/issues/54) 🆕🔥

### 🆕 New

> List of **newly opened** proposals since the last update.

- [#190: Adding Fix to base](https://github.com/haskell/core-libraries-committee/issues/190) 🔥
- [#192: `numberToRangedRational`: fix edge cases for exp ≈ `(maxBound :: Int)`](https://github.com/haskell/core-libraries-committee/issues/192)
- [#193: Expose Type from Prelude](https://github.com/haskell/core-libraries-committee/issues/193) 🔥

### ✅ Approved

> List of **approved** proposals since the last update.

- [#175: Allow `lookup` to fuse](https://github.com/haskell/core-libraries-committee/issues/175)
- [#179: Add INLINE[1] to compareInt / compareWord](https://github.com/haskell/core-libraries-committee/issues/179)
- [#186: Export List from GHC.List](https://github.com/haskell/core-libraries-committee/issues/186) 🆕
- [#187: Use native operations for `Enum Int64` and `Enum Word64` on 32-bit platforms](https://github.com/haskell/core-libraries-committee/issues/187) 🆕
- [#188: Add a few primops for `memcpy`, `memmove`, and `memset`](https://github.com/haskell/core-libraries-committee/issues/188) 🆕

### 🚫 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](https://github.com/haskell/core-libraries-committee/issues/162)
  - 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`](https://github.com/haskell/core-libraries-committee/issues/191) 💤 🆕
  - 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`](https://github.com/haskell/core-libraries-committee/issues/189)
  - 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 🙂