As Rog says - I need to support arbitrary expressions, and the only case 
that's really causing grief is /^/.  

The path of least resistance looks like re-implementing/forking a piece of 
regexp to manipulate EmptyOp.  I'll give it a shot in-place and see what 
upstreaming brings.

Thanks for the lead, Rog.


On Monday, April 9, 2018 at 4:40:27 AM UTC-4, rog wrote:
> On 9 April 2018 at 09:31, Jan Mercl < <javascript:>> 
> wrote: 
> > On Mon, Apr 9, 2018 at 6:47 AM Paul Lalonde < 
> <javascript:>> 
> > wrote: 
> > 
> >> Any advice? 
> > 
> > If regexp cannot solve your task don't use regexp. Write the tiny state 
> > machine by yourself, it should be not too much code. 
> Surely that depends whether Paul needs support for arbitrary regular 
> expressions. 

You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to