Ferreteria/v0.6/clade/Sys/Data/Things/Array: Difference between revisions

Revision as of 16:40, 16 August 2025

clade: Sys\Data\Things\Array

Clade Family
StandardBase (c,i) Keyed (i,t) Series (i,t) Whole (i,t)	→ Array	→ DStor → QStor

An Array is always a Series (i.e. it retains order), but a Series is not necessarily an Array. (It could be more like a stream.)
An Array always has a key, but sometimes the key is just a sequential number. A Keyed array is an Array with assigned key-values.

subject to revision while I think through the concepts (2025-08-16)

Array: clade which consolidates all the array-type interfaces and code
Array-type interfaces & code (traits) which go into Array:
- Keyed
- Series
- Whole
ARoot: tentatively, this stuff should all be in Array.
To be explained:
- DStor stuff:
  - interfaces:
    - Keyed
    - Series
    - Whole
  - podlings:
    - AStr
    - Pieces
      - Row
- QStor stuff:
  - interfaces:
    - Keyed
    - Series
    - Whole
  - podlings:
    - AObj
    - Fields

2025-08-15 I keep getting muddled about how this is supposed to work, and therefore writing problematic code -- so, finally mapping it out conceptually.

@@ Line 14: / Line 14: @@
 |}
 ==About==
-Clade structure:
+===Concepts===
+* An Array is always a Series (i.e. it retains order), but a Series is not necessarily an Array. (It could be more like a stream.)
+* An Array always has a key, but sometimes the key is just a sequential number. A Keyed array is an Array with assigned key-values.
+===Clade structure===
+''subject to revision while I think through the concepts (2025-08-16)''
 * {{l/ver/clade|Sys/Data/Things|Array}}: clade which consolidates all the array-type interfaces and code
 * Array-type interfaces & code (traits) which go into {{l/ver/clade|Sys/Data/Things|Array}}: