Add history entry for paraemter order change. #455
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.
Now the history file starts like this:
Breaking updates and feature summaries across releases
Catalyst unreleased (master branch)
ReactionSystem
's.ps
field has been changed (only when created through the@reaction_network
macro). Previously they were ordered acording to the order with which they appeared in the macro. Now they are ordered acoridng the to order with which the appeard after theend
part. E.g. in[p,d]
, which now it is[d, p]
.Catalyst 10.1
@unpack observable_variable = rn
andrn.observable_variable
. This requires a new inner constructor definition forReactionSystem
s, but is not considered breaking as the inner constructor isconsidered private.