Skip to content

List view

  • 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. 1. Adding a new `impl Replacer for &Replacer`. #83 2. Tweak the return value of `reg_replace` to support more use cases. #151 3. Add "multi regexes". #156 4. Is the `Replacer` trait right? Its `no_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.

    No due date
    14/14 issues closed