[Proposal]: if maximum execution times. For ex.: if ( a == b, 1){...}

[ichensky]

Often in loops, an if statement only needs to execute once or several times and then isn't necessary anymore.

When functions are executed within if statements, they are sometimes optimized to load result from a cache, and sometimes not.

Example.

for (int i = 0; i < 123; i++) {
    if (a == HeavyFunction()){
       Foo();
     }
    
    Bar();
}

It would be great to have an optional parameter within an if call that specifies that if body should be executed a maximum of maxCount times and then if should be ignored or removed from the function code at runtime.

if ( a == b, 1){
}

Example 1

for (int i = 0; i < 123; i++) {
    if (a == HeavyFunction(), 1){
         Foo();
     }
     
    Bar();
}

Which should work similarly to the code.

var flag = true;
for (int i = 0; i < 123; i++) {
    if (flag && a == HeavyFunction()){
          flag = false;
          Foo();
     }
     
    Bar();
}

Example 2

for (int i = 0; i < 123; i++) {
    if (a == HeavyFunction(), 3){
         Foo();
     }
     
    Bar();
}
return;

Which should work similarly to the code.

var count = 0;
for (int i = 0; i < 123; i++) {
    if (count < 3 && a == HeavyFunction()){
          count ++;
          Foo();
          
          if (count == 3 {
              for (int j = i; j < 123; j++) {     
                  Bar();
                  return;
              }
          }
     }
     
    Bar();
}
return;

Often people are lazy to write code with caching or just don’t want to clutter up the code with such flags.

[HaloFour]

IMO, the explicit code to manage that state and execution is substantially clearer than trying to bake it into the language, plus would be much more flexible. Having if have a different syntax and behavior based entirely on whether it happened to be nested in a loop doesn't feel like it fits in a language like C#.

[TahirAhmadov]

Yes, to me this looks like a niche use case, and existing language is perfectly fine.