When saving a capture, some could find JSON more familiar than RON. Or, perhaps, a non-default PrettyConfig is desired (e.g. one that includes struct names). One could even think of using bincode to have compact output.
We can easily have a configuration type passed over to save_capture. It's not entirely obvious how load_capture is supposed to discover the description files, given they can have different extensions.
A somewhat good thing is - having the config would technically make ron a non-required feature.
When such a configuration is implemented, it should also have switches for other pieces of logic, like the PNG saving ability of #2234.
When saving a capture, some could find JSON more familiar than RON. Or, perhaps, a non-default PrettyConfig is desired (e.g. one that includes struct names). One could even think of using
bincodeto have compact output.We can easily have a configuration type passed over to
save_capture. It's not entirely obvious howload_captureis supposed to discover the description files, given they can have different extensions.A somewhat good thing is - having the config would technically make
rona non-required feature.When such a configuration is implemented, it should also have switches for other pieces of logic, like the PNG saving ability of #2234.