This feels wrong

[Steven Schveighoffer via Digitalmars-d]

On 2/2/16 10:21 AM, Shachar Shemesh wrote:
> On 02/02/16 17:00, Steven Schveighoffer wrote:
>
>> Just put try around the opApply specific parts you want to monitor.
>> Don't guard the call to dg.
> The call to dg is, obviously, part of a loop. That whole loop body is
> inside a try/catch.

I don't see a big difference from this:

     int opApply( scope int delegate(int) dg ) {
         foreach(int i; 0 .. 50) {
             int res = dg(i);
  	    try {
                 if( res!=0 ) {
                     writefln("Delegate returned %s", res);
                     return res;
                 }
             } catch(Exception ex) {
                 writefln("Caught in loop: %s", ex.msg);
             }
         }

         return 0;
     }

> My problem isn't so much the actual how to solve it, but rather that it
> is a potential pitfall when implementing that I don't think is documented.

OK, I understand what you are saying. It could be listed in the docs as 
something to avoid.

-Steve