| | 1 | === Idea of refactoring Key PMC === |
| | 2 | |
| | 3 | Current Keys are messy and incomprehensible. So there is idea of refactoring them into something more sane. |
| | 4 | |
| | 5 | Keys currently serve only one purpose: navigate in nested containers. Iteration over containers was removed as part of key_revamp branch. |
| | 6 | To support this functionality more implicit and in clean way we will: |
| | 7 | |
| | 8 | 1. Add {{{KeyItem}}} interface class to represent single abstract step. |
| | 9 | |
| | 10 | 2. Implement {{{StringKeyItem}}}, {{{IntegerKeyItem}}} and {{{PMCKeyItem}}} to store concrete value for each step. |
| | 11 | Such {{{FooKeyItem}}} will implement {{{get_foo}}} vtable methods, freeze/thaw and nothing else. We don't need FloatKeyItem because float keys are meaningless. |
| | 12 | |
| | 13 | 3. Re-implement Key as: |
| | 14 | |
| | 15 | a. RPA for storing *KeyItem. |
| | 16 | |
| | 17 | b. Various {{{push_foo}}} vtables to create specific FooKeyItem and append it to path. |
| | 18 | |
