PyO3 / PyO3/pyo3

`DefaultHasher` for `no_std`

Open
#6,329 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no_std
Dominant language
Rust
Stars
16.2k
Forks
1k
Avg merge
2d 6h
Merged PRs (30d)
66

Description

The pyclass macro generates code that uses DefaultHasher from the std library. hashbrown does not include this until 0.16, but pyo3 supports it starting from 0.15.

We can either:

  • drop support for 0.15
  • depend directly on the foldhash crate (this is what hashbrown uses)

Contributor guide

Open the contributing guide

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.

Research direction

Start by tracing the pyclass macro's generated use of DefaultHasher and checking how hashbrown versions 0.15 and 0.16 handle it in no_std builds. Compare the two proposed compatibility paths—dropping 0.15 support or depending on foldhash—and verify the chosen approach across the supported versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.