Mercurial > repos > public > sbplib_julia
changeset 829:1de10f5b2008 operator_storage_array_of_table
Add some notes on the format of operator storage
author | Jonatan Werpers <jonatan@werpers.com> |
---|---|
date | Wed, 12 Jan 2022 13:07:43 +0100 |
parents | ca182cbb8f49 |
children | 21ab60cc0a5c |
files | Notes.md |
diffstat | 1 files changed, 13 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/Notes.md Wed Jan 12 08:39:48 2022 +0100 +++ b/Notes.md Wed Jan 12 13:07:43 2022 +0100 @@ -53,6 +53,19 @@ * Remove order as a table name and put it as a variable. +### Parsing +At the moment the only parsing that can be done at the top level is conversion +from the toml file to a dict of strings. This forces the user to dig through +the dictionary and apply the correct parsing methods for the different parts, +e.g. `parse_stencil` or `parse_tuple`. While very flexible there is a tight +coupling between what is written in the file and what code is run to make data +in the file usable. While this coupling is hard to avoid it should be made +explicit. This could be done by putting a reference to a parsing function in +the operator-storage format or somehow specifying the type of each object. +This mechanism should be extensible without changing the package. Perhaps +there could be a way to register parsing functions or object types for the +toml. + ## Variable second derivative