Overview

#6073 reported that text.find doesn't find Nat literals in pattern matches.

See transcript diff for before and after.

Closes #6073

• What does this change accomplish and why?

  • i.e. How does it change the user experience?
  • i.e. What was the old behavior/API and what is the new behavior/API?

• Include "before and after" examples if appropriate. (You can copy/paste screenshots directly into this editor.)

• List any Github issues that this PR closes, in closing-issues-using-keywords format.

Implementation approach and notes

Changes txtPattern to recognize more that Text cases.

Interesting/controversial decisions

I wasn't sure if show was the right move here or if we needed something more sophisticated, but it's a step in the right direction in any case.

Test coverage

• Have you included tests (which could be a transcript) for this change, or is it somehow covered by existing tests?

• Would you recommend improving the test coverage (either as part of this PR or as a separate issue) or do you think it’s adequate?

adequate

• If you only tested by hand, because that's all that's practical to do for this change, mention that. Include screenshots.
  n/a

Loose ends

It doesn't work to use a negative number to search for a negative number, not sure why yet, but that limitation already existed.

n/a

Final checklist

• Choose your PR title well: Your pull request title is what's used to create release notes, so please make it descriptive of the change itself, which may be different from the initial motivation to make the change.
• Update your PR description if the specifics of the PR have changed over time.
• Include transcripts or screenshots that demonstrate the changed behavior.
• If you changed .cabal files, make sure the package.yaml files are up-to-date instead.