This repository was archived by the owner on Sep 16, 2021. It is now read-only.
Revise expectation syntax, fix regular expression bug, refactor implementation #30
Conversation
This file contains hidden or 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
Add test for Scanner
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resolves #13
Fixes #25
This PR changes the syntax for DocTest expectations in source code. Currently
=>matches the expected REPL output. With this change,=>instead matches the value literal in the REPL output.The following table documents all of the available expectations:
1 + 2 // -> String1 + 2 // => 31 + 2 // ~> String = \d1 / 0 // !! error: division by zeroIn addition, this PR also refactors the use of regular expression into a new
Scannertype and fixes a bug in the regex pattern that caused DocTest annotations to be missed.