bug#36444: [PATCH] Improved regexp-opt KEEP-ORDER check

[Mattias Engdegård]

4 juli 2019 kl. 16.18 skrev Noam Postavsky <npostavs@gmail.com>:
> 
>> Not too fond of that either, really; catch/throw somehow seems more
>> heavyweight than warranted by the situation.
> 
> I've wondered if it's worth making a lexical variant of catch/throw that
> could be compiled as goto for these kind of situations.

Yes, although in this case I'd settle for built-in some/every constructs 
without bootstrap trouble, or list comprehensions that aren't a mysterious 
corner of cl-loop.

>> (1) Same as before, but with a comment about what tripped you up:
> 
>> (2) Using cl-loop:
> 
> Assuming (eval-when-compile (require 'cl-lib)) avoids bootstapping
> problems, I think the cl-loop variant is a bit neater; but either way is
> fine with me.

Thank you; I went with the while-loop, on the grounds that it can be readily 
understood by the layman from first principles. I have yet to be entirely 
friends with cl-loop.
Pushed to master.