mal: implement DBGEVAL without assuming that a: is a valid symbol #673
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This does not seem worth a test, but can currently break the self-hosting.
|
Sorry, I am cleaning the backlog in semi-random order. |
|
I don't have a strong opinion. I do tend to lean towards having optional things be marked optional in the tests. That way implementors don't get hung up if those optional tests are hard to do in their target language. In this case it's probably not going to trip up implementations. Although I could be wrong. When I was implementing bash it had a bunch of these types of things that should have been simple but ended up triggering weird behaviors (like "*, "!", etc) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This does not seem worth a test, but can currently break the self-hosting.