Without this the timer will have random values for its State and Lock
entries.  The object can then be in a locked state leading to some HAL
functions returning immediately with an error code (which is unchecked).

This patch fixes such a bug which did manifest itself as PWM not working
correctly for LEDs.

Now that specialized utimeq module has been implenented, revert previous
adhoc changes to uheapq.

This reverts commit 0cbc0722.

Passing -v -v -v on the command line of the coverage build will now print
the parse tree (as well as other things at this verbosity level).

The lexer is very mature and this debug function is no longer used.  If
it's really needed one can uncomment it and recompile.

This check always fails (ie chr0 is never EOF) because the callers of this
function never call it past the end of the input stream.  And even if they
did it would be harmless because 1) reader.readbyte must continue to
return an EOF char if the stream is exhausted; 2) next_char would just
count the subsequent EOF's as characters worth 1 column.

    import utimeq, utime
    # Max queue size, the queue allocated statically on creation
    q = utimeq.utimeq(10)
    q.push(utime.ticks_ms(), data1, data2)
    res = [0, 0, 0]
    # Items in res are filled up with results
    q.pop(res)

And also simplify it to remove the check for small int.  This can be done
because this function is only ever called if the argument is not a small
int.

It's pretty rough way to detect yaota8266 being used, but otherwise allows
to have a filesystem in such config.

Native code can hold pointers to objects on the heap, eg constant objects
like big integers.

It needs an extra pass to compute the size of the constant table for the
l32r instructions.

Required for the testsuite.

This is required to avoid extra level of output "cooking" ("\r\r\n") and
make test infrastructure work. On the other hand, this breaks somewhat
Zephyr console abstraction.