Tweaks to export system that simplify usage in user-defined types
All threads resolved!
All threads resolved!
Merge request reports
Activity
Filter activity
- Resolved by Philip Bittihn
added 1 commit
- 4b9b639b - Fix inconsistent generic definitions of deserialize
- Resolved by Philip Bittihn
added 1 commit
- 802613ee - Define export system constants early, so they can be used everywhere
added 1 commit
- 3877e6aa - first versions of serializetodict and deserializefromdict
added 1 commit
- ff7d1f01 - deserialize: forgot to commit removal of superfluous definition
- Resolved by Lukas Hupe
added 1 commit
- c0678653 - @exportrecursive: Use new dict serialization functions
- Resolved by Philip Bittihn
In principle, after we merge this and tag a new
InPartS
version, we could change the custom distribution serialization in all the particle parameters to@exportrecursive
. @lhupe Where do we want to include the legacy loading, the only difference being that the type is saved in dict["distributionType"] instead of dict["_type"]? We could define a special case fordeserializefromdict
for<:Distribution
inlegacy.jl
or (perhaps better) directly inColonyGrowthModels
, so it doesn't pollute our generic code. Or do you envision a different solution?
added 1 commit
- 7da82f7e - Remove references to "params" from serialization docs (scalar export can be any type).
mentioned in commit 609a4035
Please register or sign in to reply