alanxoc3 / concards

77%

master: 88%

LAST BUILD ON BRANCH 66-by-char

branch: 66-by-char

CHANGE BRANCH

x

Reset

• 66-by-char
• 109-basic-hook
• 114-backend-updates-v0.10.0
• 25-cli-rewrite
• 40-outcome-file
• 43-cloze
• 50-readme
• 51-streak-fix
• 53-no-answer-category
• 55-undo-module
• 57-config-dir
• 61-travis-fix
• 63-fix-narg
• 68-colon-syntax
• 73-file-print-opt
• 78-zero-streak
• 80-stat-cmd
• 91-new-cards-top-priority
• 94-no-yes-prioritized
• GH-16-go-report-a-plus
• GH-17-test-coverage
• GH-21-reverse-syntax
• GH-27-indef-done
• GH-29-at-to-pipe
• GH-30-escape-syntax
• GH-32-semantic-versioning
• GH-5-deploy-file-upload-travis
• GH-5-fix-readme-coverall-badge
• GH-5-travis
• GH-6-two-inputs
• GH-71-readme
• GH-74-hash-delim
• add-periods
• alanxoc3-patch-1
• dev
• gui-no-message
• main
• master
• refs/tags/testing-actions
• refs/tags/v0.10.0-alpha
• testing
• v0.1.0h
• v0.5.0
• v0.6.0
• v0.7.0
• v0.8.0
• v0.9.0
• v2.2

Build # 146

Build Type

push

travis-ci

Committed by alanxoc3

Commit Message

[GH-66] Spaces don't matter for parser.

The escaping strategy is better now too, you can escape any character.
You can also escape the starting `@>` token. What I'm most proud of
about this is the speed. My first solution was slow, because I was doing
string and rune casting in order to keep track of things. This solution
is just as fast, or faster, than the parse words, because it is using
the same SplitFunc interface. It might be slower than parsewords since
there is technically more logic, but it might be faster, because it
parses larger areas of text at a time.

Run Details

701 of 905 relevant lines covered (77.46%)

38.1 hits per line