Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to combine DebuggerHidden with iterator block methods?
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI don't really understand your design decision of hiding exceptions this way. I can see two situations that can occur: 1) You're writing a library to be used by other developers. In this case, they don't have your sources and in VS the lowest visible stack level will be ThrowIterator. So it is what you wanted in the first place. 2) This code is used only by your team, internally, for your project. In this case, why would you let an uncaught exception slip like that and not handle it? In case it's thrown, even when debugging, you actually want to see that it's inside ThrowIterator, and most imp
      singulars
    2. COSurely it doesn't matter why I'm using this feature. It's there and I just want to see how to get it to work in all circumstances.
      singulars
    3. COBut if you're curious, consider a `PerformQuery` method, which throws if the arguments make no sense. It's only used internally by our team. The exception is uncaught because it's a debug build, which *specifically avoids* catching exceptions *just* so that Visual Studio stops at exactly the right place. If the project just closed with a generic "there was a problem" message, wouldn't that only make debugging unnecessarily harder? We *know* there's a bug, might as well stop at exactly the right line!
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload