1.0
The path to 1.0 should including reaching some kind of finality on the API. The current API has changed very little since inception, and I mostly expect that to be true for 1.0. However, there are some things to consider that might affect the API.
- Adding a new
impl Replacer for &Replacer
. #83 - Tweak the return value of
reg_replace
to support more use cases.
The path to 1.0 should including reaching some kind of finality on the API. The current API has changed very little since inception, and I mostly expect that to be true for 1.0. However, there are some things to consider that might affect the API.
- Adding a new
impl Replacer for &Replacer
. #83 - Tweak the return value of
reg_replace
to support more use cases. #151 - Add "multi regexes". #156
- Is the
Replacer
trait right? Itsno_expand
method seems a little kludgy, and it might be possible to remove it entirely.
Additionally, performance is important, so I think #66 (and consequently, #146) should be included as well.
I've left out #85 (exposing an API for matching on &[u8]
) for now. Maybe it should be part of 1.0, but it seems like something that probably ought to be bolted on via a sub-module.
There are no open issues in this milestone.
Add issues to milestones to help organize your work for a particular release or project.
Create new issueOr find and add issues with no milestone in this repo.