Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Why doesn't the `IntMap` and `IntSet` code use pointer equality checks to improve sharing and reduce allocations?

Open
#835 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
haskell
Domain
data

Research direction

Read the existing ptrEq usage in the Map and Set code, then compare the corresponding IntMap and IntSet implementations. Determine whether equivalent pointer-equality checks could improve sharing or reduce allocations, and validate any conclusion with the repository's relevant tests or allocation measurements.

Written by the indexing model from the issue text.

Description

IntMap IntSet performance

There's quite a bit of ptrEq usage in the Map and Set code. Why isn't there anything similar in the corresponding IntMap and IntSet code?

Dominant language
Haskell
Stars
356
Forks
195
Avg merge
3d 42m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from haskell/containers

All issues in haskell/containers

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.