golang/go

cmd/cgo: more expansive test coverage

Open

#39,537 opened on Jun 11, 2020

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsFixcompiler/runtimehelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

cgo is very subtle, yet it's lacking in test coverage. For example, misc/cgo/test doesn't have any tests for C.enum_foo or C.struct_bar, and misc/cgo/testgodefs doesn't have any tests for constants (to be addressed by CL 237558).

/cc @ianlancetaylor

Contributor guide

Research direction
Examine the existing tests in misc/cgo/test and misc/cgo/testgodefs to identify missing test cases for C.enum foo, C.struct bar, and constants. Write new tests following the patterns in those directories.
Tech stack
go
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gocgo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45