Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standard instant patterns are case-insensitive, unnecessarily #228

GoogleCodeExporter opened this issue Mar 15, 2015 · 1 comment


Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 15, 2015

For some reason we lower-case single-character patterns for Instant,
which means N, G and D work as well as n, g and d.

Only the lower-case versions are documented, and every other pattern uses 
case-sensitive handling, so I *think* we're okay to just kill this behaviour so 
long as we note it in the release notes.

Original issue reported on by jonathan.skeet on 20 Jul 2013 at 6:56

Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 15, 2015

Fixed in revision 6640fdf286b4 which was merged into the default branch in 
revision a4f5290d40d4.

Original comment by jonathan.skeet on 22 Jul 2013 at 2:31

  • Changed state: Fixed
@malcolmr malcolmr added the bug label Mar 15, 2015
@malcolmr malcolmr modified the milestone: 1.2.0 Mar 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.