You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by @etorreborre (thank you!!!), this is an issue where the UCM will re-order forward references even when they are nested inside other terms, leading to a new hash where one might not have been expected. The reordering can also affect the readability of a program.
Describe and demonstrate the bug
Reported by @etorreborre (thank you!!!), this is an issue where the UCM will re-order forward references even when they are nested inside other terms, leading to a new hash where one might not have been expected. The reordering can also affect the readability of a program.
A transcript is attached which reproduces this issue:
forwardReference.md
Environment (please complete the following information):
ucm --version 0.5.27
Additional context
For context, see Discord discussion here
The text was updated successfully, but these errors were encountered: