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
{{ message }}
This repository has been archived by the owner on Jan 6, 2021. It is now read-only.
In this case, I think I know exactly where the problem is. While we're tokenizing the input and parsing through the characters in a rest, we only consider the rest to be "done" when we encounter a space, newline, EOF, or a digit representing duration, and we throw an exception otherwise. The code for that logic is here.
I was having the same problem for notes, and I fixed it by doing this: when an unknown character (e.g. a ]) is encountered, instead of throwing an error, we just say that the note is "done" and start trying to parse a new token (e.g. a "close event sequence" event).
I think that if we do the same thing in the "else" branch for rests, that will fix this problem.
I'd like to add test cases, too, so we can make sure this stays fixed in the future.
This one is best explained with examples
The text was updated successfully, but these errors were encountered: