This sounds interesting. A bit of searching is not providing much enlightenment - anyone care to explain in a bit more detail?
Also, if it is so fast, why aren't all the filter add-ons doing it?
Even though, and despite this added burden, I will point out that uBO is almost as performant as DDG Privacy Essentials as per this report.
Furthermore, uBO contains WASM modules but they are not used in the Chromium version of the extension since this would require to add a `wasm-eval` directive to uBO's extension manifest, something I prefer to avoid for the time being, I fear this would cause more lengthy validation of the extension by the Chrome Web Store.
* * *
[1] Able to enforce EasyList, EasyPrivacy et al.
It is a deep dive into how modern content blockers work and what kind of rules they have to enforce (they are usually much more complex than simple domains, though).
As a side node, I recently ran a small experiment and found out that around 90% or blocking from Easylist/EasyPrivacy/uBO lists can be done based on domain information only. But of course this leaves a lot of corner cases where sites might break or ads might still show, and ultimately more granularity is needed to address these cases.
This is used in hash tables, for example: https://en.wikipedia.org/wiki/Hash_table
Object properties in JS are mostly the same thing.
I guess other extensions can't do the same because they don't have a simple value to search in a whitelist, but rather a list of regex which must all be executed.