| Age | Commit message (Collapse) | Author |
|---|
|
* Improve argument handling of c2json
* Add automagic
|
|
|
|
|
|
|
|
|
|
|
|
* Add data driven dip switches
* Autogen weak matrix_mask
|
|
|
|
|
|
mass-compile`. (#22160)
Co-authored-by: Duncan Sutherland <dunk2k_2000@hotmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Joel Challis <git@zvecr.com>
|
|
|
|
compile`, using `--compiledb` (#21549)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functions in filters did not work properly except when used in the last
(or only) filter. The problem was caused by the peculiarity of the
`lambda` behavior in Python — any variables from the outer scope are
captured only by reference, therefore any subsequent reassignment of
those variables is propagated to all lambdas created earlier in the same
scope. Together with the laziness of `filter()` (it returns an iterator
which performs filtering on demand) this resulted in all function
filters using the values of the `key` and `value` variables which
correspond to the last filter in the sequence, therefore the result of
filtering was wrong if some filter with a function was not the last one
in the sequence.
Apparently the shortest way to make a Python lambda capture some
variables by value is to add arguments with default values for such
variables (default values are evaluated when the lambda is created, and
any subsequent reassignments in the outer scope no longer changes them).
This makes filters with functions work properly even when such filters
are not at the last position in the sequence.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Recommendations from @sigprof
* Fix CI tests
|
|
|
|
|
|
|
|
|
