Adding a `regexp-replaces' leads to the question of where to add it:
`racket/string' makes sense more than `racket/private/string' since
it's really not something that should be considered core. But to make
it correspond to `regexp-replace*' it should deal with both strings
and bytes, so `racket/string' is not a good place for it.
Maybe there should be a new `racket/regexp'? In addition to the new
function, some functions from `racket/private/string' could move there
too.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________
Racket Developers list:
http://lists.racket-lang.org/dev
