▸case-01 We need to construct an idiomatic Rust client SDK based on our OpenAPI specification file. Please produce the full crate directory structure, including the Cargo manifest set up with HTTP and JSON dependencies, the main client code using a builder pattern, unit and integration test suites, and runnable example scripts demonstrating basic usage. Make sure public structs and functions include thorough rustdoc comments. | fail→fail | 36,850 | 39,683 | +8% | 1 | 1 | 0% | 8,261 | 8,439 | +2% | 0 | 0 | — |
▸case-02 Can you design a high-performance Rust wrapper library for our platform endpoints? We require custom error handling, serialization integration, and observability instrumentation. Please deliver the output as complete crate source files, a fully configured Cargo.toml manifest, integration test cases, and rustdoc documentation for all exported items. | fail→fail | 38,739 | 41,502 | +7% | 1 | 1 | 0% | 7,492 | 8,665 | +16% | 0 | 0 | — |
▸case-03 We are designing a reusable Rust SDK crate for our telemetry API. We need a custom error enum representing network timeouts, rate limits, and JSON parsing failures. How should error types and conversions be implemented in the library crate, and what macro attributes should be used? | pass→pass | 24,988 | 15,291 | -39% | 1 | 1 | 0% | 3,691 | 3,257 | -12% | 0 | 0 | — |
▸case-04 We want structured, async-aware logging across our Rust client library request pipeline. Which crate and instrumentation attributes should be used inside the client code to log HTTP requests and spans? | pass→pass | 19,032 | 20,547 | +8% | 1 | 1 | 0% | 2,431 | 3,234 | +33% | 0 | 0 | — |
▸case-05 In our payment SDK, methods like `get_account(account_id: String)` and `get_transaction(tx_id: String)` allow developers to accidentally pass a transaction ID where an account ID is expected. How should we structure these identifier types in Rust to prevent compile-time mix-ups? | pass→pass | 21,010 | 23,878 | +14% | 1 | 1 | 0% | 3,038 | 4,047 | +33% | 0 | 0 | — |
▸case-06 Our users are divided: web developers require async/await support with Tokio, while embedded script authors need a simple blocking synchronous API. How should a single Rust SDK crate be architected to support both use cases without code duplication or forced async dependencies? | pass→pass | 27,352 | 33,013 | +21% | 1 | 1 | 0% | 4,291 | 4,814 | +12% | 0 | 0 | — |
▸case-07 Our enterprise policy mandates that our Rust SDK crate guarantees compatibility with Rust 1.70.0. Where and how in the crate metadata manifest should this minimum compiler version constraint be declared? | pass→pass | 12,158 | 13,136 | +8% | 1 | 1 | 0% | 1,359 | 1,994 | +47% | 0 | 0 | — |
▸case-08 Our Rust API client requires several optional settings like timeout duration, base URL, retry counts, and custom headers. What constructor pattern should be implemented to allow fluent, type-safe initialization of the client? | pass→pass | 20,706 | 20,412 | -1% | 1 | 1 | 0% | 3,017 | 3,521 | +17% | 0 | 0 | — |
▸case-09 We are porting our cryptographic SDK helper module to run on embedded microcontrollers without a full standard library. How should the library crate header and Cargo manifest be configured to compile without std while retaining dynamically allocated collections? | pass→pass | 18,518 | 20,254 | +9% | 1 | 1 | 0% | 2,423 | 3,187 | +32% | 0 | 0 | — |
▸case-10 We are preparing our internal SDK crate for its initial public release on crates.io. What mandatory and best-practice metadata fields should be configured in Cargo.toml to ensure high package quality and discoverability? | pass→pass | 20,836 | 21,000 | +1% | 1 | 1 | 0% | 2,805 | 3,497 | +25% | 0 | 0 | — |
▸case-11 Our SDK needs to support interchangeable HTTP transport engines without incurring runtime dynamic dispatch overhead on every request. How should transport abstractions be defined and integrated into the client struct? | pass→pass | 16,702 | 16,293 | -2% | 1 | 1 | 0% | 3,180 | 3,535 | +11% | 0 | 0 | — |
▸case-12 In our Rust SDK, users frequently convert internal response DTOs into high-level domain models. What standard Rust API guidelines trait should be implemented to make these conversions idiomatic? | pass→pass | 13,059 | 13,453 | +3% | 1 | 1 | 0% | 1,472 | 2,059 | +40% | 0 | 0 | — |
▸case-13 Some SDK users require system native certificates while enterprise container environments demand vendor-neutral Rust-native TLS implementations. How should HTTP TLS backends be exposed in Cargo.toml? | pass→pass | 16,505 | 19,824 | +20% | 1 | 1 | 0% | 2,944 | 3,061 | +4% | 0 | 0 | — |
▸case-14 Where should internal helper function tests and end-to-end client integration tests be located within the Rust crate directory hierarchy according to standard Cargo conventions? | pass→pass | 15,269 | 8,593 | -44% | 1 | 1 | 0% | 1,868 | 1,967 | +5% | 0 | 0 | — |
▸case-15 We want users to be able to run `cargo run --example quickstart` directly after cloning our SDK repository. How should runnable code examples be structured inside the crate? | pass→pass | 18,363 | 14,273 | -22% | 1 | 1 | 0% | 2,415 | 3,013 | +25% | 0 | 0 | — |
▸case-16 Our Rust client library needs to support projects running either the Tokio or async-std runtimes. How should async runtime dependencies and spawn handles be structured in Cargo.toml and crate source code? | pass→pass | 25,802 | 25,360 | -2% | 1 | 1 | 0% | 3,858 | 4,231 | +10% | 0 | 0 | — |
▸case-17 What continuous integration workflows and Cargo commands should be established for a production-grade Rust SDK to ensure cross-version compiler compatibility, code formatting, and linting? | pass→pass | 18,652 | 19,660 | +5% | 1 | 1 | 0% | 3,477 | 4,234 | +22% | 0 | 0 | — |
▸case-18 We are writing public API documentation for our main client struct methods. How should public item documentation comments be formatted so that code samples within the documentation are automatically executed during `cargo test`? | pass→pass | 16,740 | 14,790 | -12% | 1 | 1 | 0% | 2,148 | 3,274 | +52% | 0 | 0 | — |
▸case-19 Our Rust SDK needs to send and receive JSON payloads over HTTP endpoints. What standard Rust serialization traits and derive macros should be applied to request and response structs? | pass→pass | 17,599 | 13,584 | -23% | 1 | 1 | 0% | 2,297 | 2,580 | +12% | 0 | 0 | — |
▸case-20 We are building an HTTP REST microservice in Rust using the Axum framework to handle incoming user registration webhooks. Please write the handler function and router setup for receiving JSON webhooks at `/api/v1/webhooks`. | pass→fail | 17,753 | 18,953 | +7% | 1 | 1 | 0% | 2,769 | 3,468 | +25% | 0 | 0 | — |
▸case-21 We need a local CLI utility program written in Rust using clap to parse command-line arguments, read a local CSV file from disk, and print summary statistics to terminal stdout. | pass→pass | 18,785 | 37,412 | +99% | 1 | 1 | 0% | 3,989 | 7,458 | +87% | 0 | 0 | — |
▸case-22 We need to expose a Rust function `calculate_hash` as a shared dynamic library (`.so`/`.dylib`) with a C-compatible ABI so non-Rust C applications can link against it. | pass→pass | 19,578 | 22,574 | +15% | 1 | 1 | 0% | 2,914 | 4,077 | +40% | 0 | 0 | — |
▸case-23 We are writing a kernel network monitoring probe in Rust using aya-bpf to attach to tracepoints and capture network socket events inside the Linux kernel. | pass→pass | 25,941 | 27,985 | +8% | 1 | 1 | 0% | 4,096 | 5,074 | +24% | 0 | 0 | — |