Foreach -Parallel Breakpoints?

Just thought I'd throw this discussion point out there.

If we know by the AST that someone is doing foreach -parallel, we are going to know the behavior. Can we hook into those created runspaces and drop breakpoints there, and then maybe monitor for them to go into InBreakpoint state and trigger the debugger there?

The net effect would be that users could put breakpoints in a Foreach -Parallel loop and expect it to break there for troubleshooting parallel runs, rather than the current procedure of removing -Parallel and any $USING references in order to debug.

Probably not feasible, lots of issues:

1. How do we pause the other runspaces at the same time
2. Have to fetch all the state and ensure it works the same thru all the existing tests
3. etc.

No se especifican archivos, pruebas ni puntos de entrada. Primero hay que determinar dónde Foreach -Parallel crea y administra los runspaces y cómo se gestionan los estados de Breakpoint e InBreakpoint. Para darlo por terminado sería necesario un diseño definido que admita breakpoints dentro de bucles paralelos, coordine los demás runspaces y preserve el comportamiento existente.