▸case-01 I need a complete Go client library for our internal file service based on the spec at `./specs/fileservice.yaml`. The module path should be `github.com/corp/fileservice-go` targeting Go version 1.21. Please deliver the standard SDK layout including the Go source code, go.mod/go.sum project files, unit test suites, a dedicated examples folder showing basic initialization, and a README detailing installation steps. | fail→fail | 52,284 | 47,300 | -10% | 1 | 1 | 0% | 8,281 | 8,684 | +5% | 0 | 0 | — |
▸case-02 We are constructing a Go SDK for our payment gateway API using the definition at `./api/pay-v1.json`. Please construct the SDK package for `github.com/paycorp/pay-go` using Go 1.22, handling high concurrency and timeout scenarios. Produce all implementation source files, test files, module setup manifests, sample runnable code under an examples directory, and package documentation. | fail→fail | 40,754 | 36,830 | -10% | 1 | 1 | 0% | 8,272 | 8,675 | +5% | 0 | 0 | — |
▸case-03 Can you generate a Go SDK module based on our OpenAPI document located at `./spec.yaml`? The repository target is `github.com/platform/metrics-go` requiring Go 1.20 or newer. Output the Go package code, unit tests in *_test.go files, project configuration files, usage scripts in an examples folder, and a README containing GoDoc-formatted package documentation. | fail→pass | 40,371 | 52,427 | +30% | 1 | 1 | 0% | 8,271 | 8,506 | +3% | 0 | 0 | — |
▸case-04 I am designing a Go client library configuration for `github.com/acme/storage-go` where users need to set custom HTTP timeouts, retry counts, and custom loggers. A developer suggested passing a 15-field Config struct directly or passing 8 individual parameters into `NewClient()`. Show how client configuration should be structured. | pass→pass | 24,367 | 21,123 | -13% | 1 | 1 | 0% | 2,963 | 3,448 | +16% | 0 | 0 | — |
▸case-05 In our Go SDK for `github.com/acme/db-go`, developers are arguing over constructor signatures. Some want `func NewClient(c *http.Client) ClientInterface` returning an interface and taking concrete pointers. What is the idiomatic Go parameter and return pattern for client constructors? | pass→pass | 23,046 | 20,513 | -11% | 1 | 1 | 0% | 2,578 | 2,927 | +14% | 0 | 0 | — |
▸case-06 When an HTTP request fails inside an SDK method for `github.com/acme/api-go`, a developer proposed returning raw string errors like `errors.New(err.Error())` so callers get simple text. How should low-level HTTP and JSON unmarshaling errors be returned to callers? | pass→pass | 15,171 | 20,899 | +38% | 1 | 1 | 0% | 2,861 | 3,306 | +16% | 0 | 0 | — |
▸case-07 We are designing network methods for our Go SDK like `GetUser(id string)` and `CreateOrder(order Order)`. A teammate wants to omit `context.Context` from method signatures to keep the API clean, relying instead on internal fixed HTTP client timeouts. How should network method signatures be designed? | pass→pass | 22,102 | 21,245 | -4% | 1 | 1 | 0% | 2,343 | 3,101 | +32% | 0 | 0 | — |
▸case-08 We have a `Buffer` struct in our Go SDK package. A contributor wants to make calling methods on `Buffer{}` panic with uninitialized map errors unless users call `NewBuffer()`. How should struct types be designed regarding zero values in Go? | pass→pass | 13,479 | 23,662 | +76% | 1 | 1 | 0% | 2,237 | 2,611 | +17% | 0 | 0 | — |
▸case-09 Provide the exact initial file manifest content for a new Go SDK repository `github.com/acme/cloud-go` specifying Go 1.21 as the minimum engine version. | pass→pass | 4,221 | 33,523 | +694% | 1 | 1 | 0% | 770 | 6,075 | +689% | 0 | 0 | — |
▸case-10 We are writing unit test suites in `client_test.go` for our Go SDK. Should we write verbose `if got != want { t.Errorf(...) }` blocks for every assertion or use a standard assertion helper library for Go tests? | pass→pass | 14,594 | 20,241 | +39% | 1 | 1 | 0% | 2,596 | 3,267 | +26% | 0 | 0 | — |
▸case-11 We want to set up automated releases, version tagging, and multi-platform distribution for our Go SDK project binaries and archives. Which tool standardly handles Go release automation? | pass→pass | 15,068 | 16,112 | +7% | 1 | 1 | 0% | 1,884 | 2,479 | +32% | 0 | 0 | — |
▸case-12 Where should GoDoc documentation comments be placed in Go SDK files so `pkg.go.dev` renders them correctly? | pass→pass | 17,666 | 20,307 | +15% | 1 | 1 | 0% | 2,166 | 3,183 | +47% | 0 | 0 | — |
▸case-13 Our Go SDK client caches access tokens that will be read and refreshed concurrently across multiple goroutines. A junior developer used a standard map without locks. How should concurrent access to shared client state be handled? | pass→pass | 14,867 | 20,400 | +37% | 1 | 1 | 0% | 2,679 | 3,394 | +27% | 0 | 0 | — |
▸case-14 Our Go SDK needs internal logging for request tracing. Should we use raw `fmt.Printf` lines or structured logging output for SDK diagnostics? | pass→pass | 19,936 | 14,864 | -25% | 1 | 1 | 0% | 2,634 | 3,055 | +16% | 0 | 0 | — |
▸case-15 We want to run automated static analysis and linter checks in continuous integration for our Go SDK repository. Which unified linter runner should be configured? | pass→pass | 11,220 | 14,590 | +30% | 1 | 1 | 0% | 1,883 | 2,054 | +9% | 0 | 0 | — |
▸case-16 Our Go SDK `github.com/acme/service-go` at version `v1.8.0` is refactoring core interfaces in a breaking manner. How should the module path in `go.mod` be updated according to Go semver rules? | pass→pass | 14,449 | 10,682 | -26% | 1 | 1 | 0% | 1,459 | 2,054 | +41% | 0 | 0 | — |
▸case-17 We are building an SDK that handles Auth, Users, Billing, and Webhooks. Should we dump all 80 Go source files into a single root `package sdk` folder or split them into subpackages? | pass→pass | 23,452 | 24,044 | +3% | 1 | 1 | 0% | 3,004 | 3,696 | +23% | 0 | 0 | — |
▸case-18 In our Go SDK constructor `New(opts ...Option)`, if the user passes no custom HTTP client option, how should the internal HTTP transport be handled? | pass→pass | 17,168 | 18,626 | +8% | 1 | 1 | 0% | 2,307 | 2,696 | +17% | 0 | 0 | — |
▸case-19 We are designing a REST API from scratch and need to write an OpenAPI 3.0 YAML specification for an employee management service, defining the `/employees` endpoint and schema models. Please write the complete OpenAPI 3.0 YAML definition. | pass→pass | 38,569 | 26,689 | -31% | 1 | 1 | 0% | 5,898 | 7,033 | +19% | 0 | 0 | — |
▸case-20 We need a Python SDK client library for our storage service using `requests` and `pydantic`. Please construct the Python package with `setup.py`, `pyproject.toml`, and Python client code. | pass→pass | 29,713 | 21,998 | -26% | 1 | 1 | 0% | 5,854 | 5,535 | -5% | 0 | 0 | — |
▸case-21 Write a GitHub Actions workflow YAML file (`.github/workflows/ci.yml`) to run `go test ./...` on pull requests to the main branch. | pass→pass | 11,199 | 10,171 | -9% | 1 | 1 | 0% | 1,159 | 1,437 | +24% | 0 | 0 | — |
▸case-22 We need a CSS stylesheet to render our API documentation website in dark mode with responsive flexbox layout for the sidebar. | pass→pass | 30,904 | 19,698 | -36% | 1 | 1 | 0% | 5,683 | 3,552 | -37% | 0 | 0 | — |