Baroque it is. Clojure might be a death sentence for the proguard approach, considering how deeply the terms clojure and invokedynamic seem to be connected. But

Baroque it is. Clojure might be a death sentence for the proguard approach, considering how deeply the terms clojure and invokedynamic seem to be connected. But if you happen to depend on some deep library stacks only for some minor scraps of it's functionality it might still be worth it, define a blanket exception for your own code and, if not picked up automatically, for the few entry points where you call from clojure into the java world. If you don't mind keeping twice as much as strictly necessary, kicking out some low hanging fruits shouldn't be that hard. (but in combination with build times and future friction a division against proguard might still be very, very rational)