Re: Proposal: Expose offsets for capturing groups in regular expression matches

Adding a property to the match result is indeed tricky. Not sure if you're already aware that named capture groups are stage 3: https://github.com/tc39/proposal-regexp-named-groups On Thu, Mar 23, 2017 at 8:08 AM, T.J. Crowder < tj.crow...@farsightsoftware.com> wrote: > Excellent idea, and

Re: Proposal: Expose offsets for capturing groups in regular expression matches

Excellent idea, and nice and simple as well. I wouldn't think adding a property to the match result would rattle cages, it'll be interesting to find out. @eric - I prefer the proposal's approach to offsets. If you need to know where the end is, you can always add the length of the captured text,

Re: Proposal: Expose offsets for capturing groups in regular expression matches

This would be great. Can I suggest that both the start and end of each match should be there. So instead of offsets you would have "starts" and "ends". Alternatively, offsets should be twice as long with start-end pairs in it. On Mon, Oct 31, 2016 at 9:53 AM, Sebastian Zartner <

Re: Standardizing conditional try/catch

To be clear I was talking about advanced pattern matching for exception handling. Y(probably)AGNI? On Tue, 21 Mar 2017 at 05:08, Isiah Meadows wrote: > It's possible to add a "[No LineTerminator here]" constraint when > necessary, as was done for async functions. > > As

Re: Strawman: partial application operator

I'll invite you to check out this particular Google search, as function binding has been discussed many different times on this list. https://www.google.com/#safe=active=site:esdiscuss.org+partial+application&* - Isiah Meadows m...@isiahmeadows.com On Wed, Mar 22, 2017 at 5:15 AM, Ben