I am thinking if loading in WASM and executing it like-native works well… maybe that could be the future of custom tokenizers, custom dql functions, custom data types… What a cool draw that would be as an extensibility feature on this system.
Custom tokenizers right now are doable but not fun since you have to build a go plugin shared object, which has a big restriction of having to have 100% the same imports/versions to be able to be loaded into dgraph :/. Something sandboxed may be better.