Provide better string operations in *SL
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 112
- Forks
- 73
- Avg merge
- 9h 41m
- Merged PRs (30d)
- 1
Description
*SL includes string-lower-case? and string-upper-case?, but no functions for actually downcasing or upcasing strings. OTOH, it includes char-upper-case? and char-upcase, char-lower-case? and char-downcase.
It includes string=? and string-ci=?, and string<? and string-ci<? etc, but then it includes string-contains? but not string-contains-ci?.
This mishmash means that students can't use string-contains-ci? until they've learned about lists and map and characters, and can implement it themselves....
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names existing *SL operations such as string-lower-case?, string-upcase?, string-contains?, and their character counterparts, but names no files, tests, or implementation entry point. Start by locating the *SL string primitive definitions and tests; done means the string API consistently supports case conversion and case-insensitive containment for students.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100