Files
miner/docs/implementation/readme.md
T
rob thijssen 49efb4ebc5 07: stable toolchain, rust validations
- Switch toolchain to stable with clippy and rustfmt components - Clean
up Clippy warnings with inline format args and hygiene fixes - Add GPU
engine placeholders (gpu-cuda, gpu-opencl) in CLI and service - Return
clear runtime error and exit for unimplemented GPU engines - Format all
TOML files with Taplo and ensure taplo fmt --check passes - Improve
mining nonce partitioning for safe range splits - Update tests to pass
cleanly on stable without warnings
2025-09-09 21:39:01 +08:00

2.7 KiB
Raw Blame History

Implementation docs index

This directory is intended for PR reviewers as the definitive context for evaluating changes. Each entry captures a discrete iteration as a “prompt” (plan/spec) and a matching “response” (implementation and outcomes). Commits and PRs should link to the relevant entry; authoring/process guidance lives in /agents.md.

Conventions

  • Numbering: entries are prefixed with a two‑digit sequence (00, 01, …) to indicate order.
  • Pairing: most entries come as a prompt/response pair. Some early entries may be standalone context docs.
  • Scope: each entry should be narrowly scoped and actionable to ease review and onboarding.

Table of contents

For authors and agents Authoring workflow, conventions, and commit/PR linkage requirements are documented in /agents.md.

Cross‑references

  • Authors and agents: see /agents.md for authoring workflow and process details. The repo README.md also links to review-critical docs.
  • Workspace structure, crate boundaries, and feature gates are described inline in prompt/response docs.
  • Dashboards and metrics: see entries 04–07 for metrics chunking, per‑thread/job gauges, and exporter behavior.

Last updated

  • 07: Stable toolchain, Clippy/Taplo hygiene, GPU engine enum placeholders with user‑friendly errors.