Vladimir Panteleev

For many operations we have the same problem as #60, the attribute would need to be inferred from other user-supplied code we call (allocator, hash function...). Of course, the method...

#182 implements this for `DynamicArray`.

I don't think this is practical right now in D. We need to select the attributes (with/without `@nogc`) depending on the allocator and the `supportGC` parameter, which is currently doable...

I see that d44cb6a6dde18de835ac88b82ce389a8e4a9d85c added `front` and `back` methods which return *values*, which I guess would correspond to the smallest and biggest keys. I think for map-like types it would...

In case of `HashSet`, I think this wouldn't be any more efficient than inserting them one by one. I would suggest using [each](https://dlang.org/library/std/algorithm/iteration/each.html). Maybe more useful would be to have...

The profiler could listen to signals sent by the program when to start and stop profiling. E.g. `OutputDebugString("VERYSLEEPY_START\n")` and `OutputDebugString("VERYSLEEPY_STOP\n")` Would that fit your needs?

[`WaitForDebugEventEx`](https://docs.microsoft.com/en-us/windows/win32/api/debugapi/nf-debugapi-waitfordebugeventex) + [`OUTPUT_DEBUG_STRING_EVENT`](https://docs.microsoft.com/en-us/windows/win32/api/minwinbase/ns-minwinbase-debug_event)

I think polling should work, otherwise there would be no way to reliably receive all debug events. I suppose the implementation (OS) might block the debuggee process until the debugger...

Note that we already have a debugger thread which calls `WaitForDebugEvent` in `debugger.cpp`. This was added in #88.

See also: https://github.com/VerySleepy/verysleepy/issues/5#issuecomment-23163316