mattn / mattn/go-pointer

possible change?

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

Nobody has claimed this yet.

Dominant language
Go
Stars
133
Forks
32
PR merge metrics
No merged PRs in 30d

Description

With go1.21 on my machine, it is allowed to convert a dangling pointer/address to uintptr then to unsafe.Pointer like so var ptr unsafe.Pointer = unsafe.Pointer(uintptr(1)). And I think it would be a performace boost if avoiding memory allocation.

Contributor guide

No contributing guide indexed for this repository

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

The issue only identifies Go 1.21 and an unsafe.Pointer conversion; no file, test, or entry point is named. Start by inspecting the repository’s public pointer-conversion API and any allocation-related tests or benchmarks. Done would require a decided scope and evidence that the proposed change is safe and provides the intended performance benefit.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.