Skip to content

merge queue: embarking master (92829a5), #11846 and #11790 together#11893

Closed
mergify[bot] wants to merge 7 commits into
masterfrom
mergify/merge-queue/f8737bedd2
Closed

merge queue: embarking master (92829a5), #11846 and #11790 together#11893
mergify[bot] wants to merge 7 commits into
masterfrom
mergify/merge-queue/f8737bedd2

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 26, 2026

✨ The merge conditions cannot be satisfied due to failing checks. ✨

Branch master (92829a5), #11846 and #11790 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11790.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule squash-merge for merge:

  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Required conditions to stay in the queue:

---
checking_base_sha: dc122f6414b9ecb1f3a0906680b6690e696fc111
previous_failed_batches: []
pull_requests:
  - number: 11790
    scopes: []
scopes: []
...

eyeinsky and others added 7 commits May 5, 2026 21:52
The data type `Distribution.Utils.ShortText` was introduced
in 2016 (993d20a)
to provide a compact representation of UTF-8 strings.
Since then the ecosystem moved forward and converged
to using `Data.Text.Text` for this purpose.
The commit defines `type ShortText = Text` and retains `Distribution.Utils`
as a boring compatibility layer.

An alert reader can object that while `Data.Text.Text` is also UTF-8 encoded,
its memory overhead is a few bytes more than `Distribution.Utils.ShortText`
(because `Text` provides constant-time slicing, while `ShortText` takes linear time).
My experience as a maintainer of `bytestring` and `text` is that this memory overhead
is unlikely to matter for Cabal use case, and reducing mental overhead takes
the priority.
@mergify mergify Bot mentioned this pull request May 26, 2026
2 tasks
@mergify mergify Bot closed this May 26, 2026
@mergify mergify Bot deleted the mergify/merge-queue/f8737bedd2 branch May 26, 2026 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants