FallenSigh
8fdf944555
- sync_rtl/common/: skid_buffer, pipeline_reg, defines (valid/ready) - sync_rtl/mod_add/: modular adder example with Verilator C++ TB - test_framework/: Python-driven Verilator compile/sim/compare pipeline - test_framework/modules/mod_add/: 50-vector test plan, full鏈路 PASS - .trellis/spec/: RTL and test_framework conventions documented
52 lines
796 B
Markdown
52 lines
796 B
Markdown
# State Management
|
|
|
|
> How state is managed in this project.
|
|
|
|
---
|
|
|
|
## Overview
|
|
|
|
<!--
|
|
Document your project's state management conventions here.
|
|
|
|
Questions to answer:
|
|
- What state management solution do you use?
|
|
- How is local vs global state decided?
|
|
- How do you handle server state?
|
|
- What are the patterns for derived state?
|
|
-->
|
|
|
|
(To be filled by the team)
|
|
|
|
---
|
|
|
|
## State Categories
|
|
|
|
<!-- Local state, global state, server state, URL state -->
|
|
|
|
(To be filled by the team)
|
|
|
|
---
|
|
|
|
## When to Use Global State
|
|
|
|
<!-- Criteria for promoting state to global -->
|
|
|
|
(To be filled by the team)
|
|
|
|
---
|
|
|
|
## Server State
|
|
|
|
<!-- How server data is cached and synchronized -->
|
|
|
|
(To be filled by the team)
|
|
|
|
---
|
|
|
|
## Common Mistakes
|
|
|
|
<!-- State management mistakes your team has made -->
|
|
|
|
(To be filled by the team)
|