You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How hard would it be to extend this library to support matching on arbitrary streams, instead of strings? I'm looking for an equivalent of TRE's tre_reguexec.
The basic idea is that the caller can pass the equivalent of an iterator over something that may not be a string. This would make it possible to match over gap buffers, ropes, piece tables, and other string implementations that do not rely on a contiguous char array.
Thanks!
The text was updated successfully, but these errors were encountered:
Do you think it would be easier to add a limited form of this which supports passing the subject string as an array of strings? Onigmo would consider that as just one string, ignoring the fact that it's split up. This should provide reasonable efficiently, while being a bit simpler to implement, maybe?
Even simpler, how hard would it be to support just two such strings? This would allow Onigmo to work for gap buffers.
Hi there,
Thanks for the cool work on Onigmo!
How hard would it be to extend this library to support matching on arbitrary streams, instead of strings? I'm looking for an equivalent of TRE's
tre_reguexec
.The basic idea is that the caller can pass the equivalent of an iterator over something that may not be a string. This would make it possible to match over gap buffers, ropes, piece tables, and other string implementations that do not rely on a contiguous char array.
Thanks!
The text was updated successfully, but these errors were encountered: