tailscale / tailscale/depaware
Separate unsafe and cgo
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 459
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
While both might be problematic in terms of GC or race detection, CGO can introduce additional issues for cross-compiling. It would be great if CGO was recognizable on its own. Maybe different bomb types or bombs plus U/C code?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating how depaware currently detects or reports unsafe and cgo dependencies, then determine how CGO should be represented separately; done means CGO is recognizable independently for cross-compilation concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100