Development record
The blindness core's fourth condition says items come back unordered and unweighted where the companion's section 2 says items are returned in the order they arise in the object
issueresolvedminoriss-2609021153261145
The blindness core's fourth condition says items come back unordered and unweighted where the companion's section 2 says items are returned in the order they arise in the object
Grounds
- pursued: we expect the definitions to state the companion's ordering rule rather than a contradicting one, so a reading returns items in the order they arise in the object and nothing in the instrument asks it to do otherwise; a definition whose core still says items come back unordered and unweighted, or four cores that have drifted apart, would show it wrong
Frontmatter
| id | iss-2609021153261145 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609021153261145-the-blindness-core-s-fourth-condition.md
open on GitHub ↗ · commit history ↗
mentions2
- itd-2609021003095168The invocation is a position and a target state, and the committed preset for the position supplies what the reading is handed
- spc-2609021004075744The invocation is a position and a target state: the scope operand and the override stamp leave, and the committed preset for the position is applied by the assembler