tests inherit from common tests in the root `/tests` directory.
- `/docs`: This contains the documentation for the library, including guides, tutorials, and API references.
## Coding Conventions for Hugging Face Transformers
src/core/tracking.rs`.
For full details see [ARCHITECTURE.md](../docs/contributing/ARCHITECTURE.md) and [docs/contributing/TECHNICAL.md](../docs/contributing/TECHNICAL.md). Module responsibilities are documented in each folder's `README.md` and each file's `//!` doc header.
## Key Conventions
- **Error handling**: `anyhow
pull request, write or fix a test, re-sync a translation, find stale documentation, or make any change to the code (this is what the maintainers use Copilot cloud agent
Ember applications
### General Development
- **[code_comments.instructions.md](instructions/generic/code_comments.instructions.md)**: Guidelines for writing effective code comments and self-documenting code
- **[testing.instructions.md](instructions/generic/testing.instructions.md)**: General testing best practices and guidelines
## How These Instructions Work
GitHub Copilot
from the network, a
proxy header, or another node) or corrects audit-log attribution.
- Documentation changes that describe how existing behavior can be abused by an attacker
unreachableCode, deprecated)`.
- Sample `.py` files use comments like `# This should generate an error` to document expected diagnostics, but the actual assertion is the count passed to `validateResults`.
**Fourslash tests** (`src/tests/fourslash
established best practices and conventions
- Include error handling and edge case considerations
- Provide clear documentation and usage examples
- Explain technical decisions and trade-offs
- Test solutions mentally before presenting them