Ingvar Stepanyan

Sure, I looked into code to see how easy it would be to implement this and came to the same conclusion that it would currently require significant changes, but decided...

> I could alternatively construct a new Matcher with the reduced substring, but that would require me to keep track of the start position and possibly incur other overhead. The...

Starting from Rust 1.51, there is a stable `split_inclusive` method on strings that can work with arbitrary patterns. At least on nightly, you should be able to use `pattern` feature...

Alternatively, it could return an iterator like std library does for [`EscapeDefault`](https://doc.rust-lang.org/std/char/struct.EscapeDefault.html) and [`EscapeDebug`](https://doc.rust-lang.org/std/char/struct.EscapeDebug.html), then you can either `.collect()` to `String` or `.extend` existing `String` (and it will be more...

> Yes, I do want to do this. It looks like I wrote this in the README: I did see that you want to do this in README, but thought...

> Compile RegExp only when it is neccessary Not sure about SpiderMonkey, but in V8 regexps are anyway compiled lazily only on the first use and not when regexp literal...

> > > Cc/ @RReverser, for observability into real world asyncify issues. Thanks for tagging me! I'll take a deeper look at the write-up in the next few days, there's...

Thinking about this a bit more - I see that at ptp2 camlib reports PTP property changes. Could we leverage that by exposing a function that would walk through all...

@msmeissn How stable are those "PTP Property 1234 changed" messages btw? I could for now try parsing them myself to figure out which config fields have changed, but they are...

> that they report the properties that were changed by config name space instead of id That would be nice, yeah - otherwise it makes it hard to match prop...