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

Revision as of 00:25, 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

Clade structure:

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 20: / Line 20: @@
 ** {{l/ver/clade|Sys\Data\Things\Array\ifaces|Series}}
 ** {{l/ver/clade|Sys\Data\Things\Array\ifaces|Whole}}
+* {{l/ver/clade|Sys\Data\Things\Array\ifaces|ARoot}}: tentatively, this stuff should all be in {{l/ver/clade|Sys/Data/Things|Array}}.
+* To be explained:
+** {{l/ver/clade|Sys\Data\Things\Array|DStor}} stuff:
+*** interfaces:
+**** {{l/ver/clade|Sys\Data\Things\Array\ifaces\D|Keyed}}
+**** {{l/ver/clade|Sys\Data\Things\Array\ifaces\D|Series}}
+**** {{l/ver/clade|Sys\Data\Things\Array\ifaces\D|Whole}}
+*** podlings:
+**** {{l/ver/clade|Sys\Data\Things\Array\DStor|AStr}}
+**** {{l/ver/clade|Sys\Data\Things\Array\DStor|Pieces}}
+***** {{l/ver/clade|Sys\Data\Things\Array\DStor\AStr|Row}}
+** {{l/ver/clade|Sys\Data\Things\Array|QStor}} stuff:
+*** interfaces:
+**** {{l/ver/clade|Sys\Data\Things\Array\ifaces\Q|Keyed}}
+**** {{l/ver/clade|Sys\Data\Things\Array\ifaces\Q|Series}}
+**** {{l/ver/clade|Sys\Data\Things\Array\ifaces\Q|Whole}}
+*** podlings:
+**** {{l/ver/clade|Sys\Data\Things\Array\DStor|AObj}}
+**** {{l/ver/clade|Sys\Data\Things\Array\DStor|Fields}}
 ==History==
 * '''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.