@neauoire i was thinking more at a higher level to allow it to work in rules as well, itd be really fun to match against an op code name and ouput gur binary for it in a sequence along side its length in bytes, then have a higher level pattern that takes instruction sequences and converts labels into addresses to make a function.
or rules that move parens around without them matching, like if you wanted to write a program to transform "do"/"end" into "("/")"