GitLab

map() is 5 times slower. That's mostly because of inefficiency of creating
containers from iterables of unknown length (like map()).

Both "bound" (like, length known) and "unbound" (length unknown) are tested.
All of list, tuple, bytes, bytesarray offer approximately the same
performance, with "unbound" case being 30 times slower.

For a trivial operation, calling a function is 5 times slower than doing
operation inline.

bare-arm, stmhal: Disable stack protector

As we are building with -nostdlib gcc features like the stack protector
will fail linking, because the failure handlers are in gcc's internal
libs. Such features are implicitly disabled during compilation when
-nostdlib is used in CFLAGS too.
Signed-off-by: Sven Wegener <sven.wegener@stealer.net>

-nostdlib is the correct option, gcc recognizes the double dash version
when in link-only mode, but not when compiling.
Signed-off-by: Sven Wegener <sven.wegener@stealer.net>

Fix problem with ADC reads and multiple channels

This adds a hook to get/set pyb_uart_global_debug from Python, using
pyb.repl_uart().  You can set it to an arbitrary UART object, and then
the REPL (in and out) is repeated on this UART object (as well as on USB
CDC).

Ultimately, this will be replaced with a proper Pythonic interface to
set sys.stdin and sys.stdout.

Also make stdout_print_strn static (ultimately this function needs to be
merged with stdout_tx_strn).

Still some method names to iron out, and funtionality to add, but this
will do for the first, basic version.

char can be signedness, and using signedness types is dangerous - it can
lead to negative offsets when doing table lookups. We apparently should just
ban char usage.

Add __assert_func

* issue #692

In preparation for unicode support.

We still have that char vs byte dichotomy, but majority of string operations
now use byte.

This will allow roughly the same behavior as Python3 for non-ASCII strings,
for example, print("<phrase in non-Latin script>".split()) will print list
of words, not weird hex dump (like Python2 behaves). (Of course, that it
will print list of words, if there're "words" in that phrase at all, separated
by ASCII-compatible whitespace; that surely won't apply to every human
language in existence).

Getting a length of string may be expensive, depending on the underlying
implementation.

void* is of unknown size

Functionality we provide in builtin io module is fairly minimal. Some
code, including CPython stdlib, depends on more functionality. So, there's
a choice to either implement it in C, or move it _io, and let implement other
functionality in Python. 2nd choice is pursued. This setup matches CPython
too (_io is builtin, io is Python-level).

It needs to be reused for generator functions, too.

Also now returns correct POSIX errno when an IO operation fails.

Addresses issues #516 and #676.