I think the selector factory in ng 2.0 should already handle all of that, though. I don't know if there's much value in the outside world extending this, it would make the ecosystem crazier (more "dialects" of angular), and make optimization difficult