core.watchman.register-snapshot-trigger
both of these approaches use NFAs under the hood, which means O(m * n) matching. our approach is fundamentally different: we encode lookaround information directly in the automaton via derivatives, which gives us O(n) matching with a small constant. the trade-off is that we restrict lookarounds to a normalized form (?<=R1)R2(?=R3) where R1/R2/R3 themselves don’t contain lookarounds. the oracle-based approaches support more general nesting, but pay for it in the matching loop. one open question i have is how they handle memory for the oracle table - if you read a gigabyte of text, do you keep a gigabyte-sized table in memory for each lookaround in the pattern?
，详情可参考91视频
At this point, since we're writing our own resolver function, we can provide any logic we like over
│ gVisor Sentry (Ring 3)│ ◄── USER-SPACE KERNEL
Россиянам назвали отрасли со средней зарплатой выше 400 тысяч рублей08:35