We already have the exported [save|load]NodeBlob[!] api functions. saveDFG loadDFG should be renamed to match the current design and clear up what they do. The new saveDFG loadDFG will be julia only and therefore likely marked as public and not exported. Therefore, it should be dispatched based (so we can save a variable without getting the API confused with saveVariableBlob!).
We can go with:
- julia Base
read and write (read needs the type, so not that convenient)
- FileIO
save and load (this will need a *.dfg extension)
- New verbs such as
export|import, save|load (will need DFG.)
- Keep
saveDFG|loadDFG
- Other options?
Short term, I think they can be demoted to unstable functions for v0.29.
We already have the exported
[save|load]NodeBlob[!]api functions.saveDFGloadDFGshould be renamed to match the current design and clear up what they do. The newsaveDFGloadDFGwill be julia only and therefore likely marked aspublicand not exported. Therefore, it should be dispatched based (so we cansavea variable without getting the API confused withsaveVariableBlob!).We can go with:
readandwrite(read needs the type, so not that convenient)saveandload(this will need a*.dfgextension)export|import,save|load(will needDFG.)saveDFG|loadDFGShort term, I think they can be demoted to unstable functions for v0.29.