Inconsistency between code and doc regarding traps _sigwatch and _sigunwatch

[aktiur]

As the documentation says, kernel traps come in two flavors: regular, or synchronous.
From what I could understand from the code, synchronous traps are implemented by calling ready_appendleft when handling the trap to make sure the current task is rescheduled immediately without another task getting executed in the middle.

Both _sigwatch and _sigunwatch are said in the docs to be synchronous. However, they are implemented in the kernel, using _reschedule_task, allowing another task to get resumed.

[aktiur]

I had not seen @njsmith issue #101 / pull request #103 which may render this specific issue moot. Having a look right now.

[aktiur]

Not a problem anymore with the new implementation of synchronous traps.