RFC: Allow prev_timer to be set to nothing #131
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The circular self-reference of
prev_timer
field can cause problems in some circumstances.For example, exporting
TimerOutput
usingJLD
causesStackOverflowError
.Workaround for #40
I realise this is an issue for
JLD
rather thanTimerOutputs
, so marking as RFC. However, it seems to provide a workaround with little impact onTimerOutputs
.Change type of
prev_timer
toUnion{TimerOutput,Nothing}
which allows setting it tonothing
, breaking the circularity.It also seems consistent that
prev_timer == nothing
wheneverprev_timer_label == ""
.Before saving to
JLD
, setprev_timer
tonothing
.