Clarify result value lookup semantics
This commit is contained in:
@@ -75,7 +75,15 @@ unsupported-navigation behavior must remain unchanged.
|
||||
|
||||
## 2. The exported Value documentation omits essential settled semantics
|
||||
|
||||
**Priority:** P3. **Status:** Open. **Plan stage:** 9.
|
||||
**Priority:** P3. **Status:** Complete. **Plan stage:** 9.
|
||||
|
||||
**Completion:** expanded Value's declaration documentation for root selection,
|
||||
manual results, presence versus availability, intermediate navigation, present
|
||||
nil interfaces and typed nil values, preserved terminal types, scalar leaves,
|
||||
no conversion/revalidation or codec calls, and ordinary assignment ownership.
|
||||
Referenced the shared schema binding contract and Path semantics. Reviewed
|
||||
`go doc Result.Value`; formatting and whitespace checks passed. No runtime
|
||||
behavior changed in this unit.
|
||||
|
||||
**Relevant documentation:** the declaration comment in
|
||||
[result_value.go](../../result_value.go), with the existing
|
||||
|
||||
Reference in New Issue
Block a user