mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-12-26 21:51:08 +00:00
ccdc3ee406
:not() selectors cannot be radical because the bloomfilter only knows if a value is set in any of the nodes, but cannot determine the opposite (if a value is not set in at least one node), but that would be required for:not() selectors. However, this is very unlikely to happen in the real world, so it's not worth optimizing. Unfortunately, change tracking could know this, so by excluding the :not() selectors from radical changes, the change tracking will now pick them up. If that turns out to be a performance problem, we need to add a special category for radical not filters, so change tracking and bloom filters can deal with them. The testcase demonstrating the problem in widget-factory has been extrated and added. |
||
---|---|---|
.. | ||
change | ||
nodes | ||
parser | ||
style | ||
api.c | ||
api.test.in | ||
data.c | ||
meson.build |