NashornPrimitiveLinker is doing double duty right now: both providing linking and type conversion for primitive types, as well as extending the "dyn:new" operator semantics on a StaticClass (so we can use the "new X() { ... }" syntax). I want to pull it apart in two, with all handling of JS primitive types in NashornPrimitiveLinker, and only handling of StaticClass operational semantics extension in separate NashornStaticClassLinker. Having things organized like that might be a useful architectural direction for the future too if we want to extend some of the semantics of other operations on types from Dynalink too (i.e. having a linker for DynamicMethod that provides "dyn:getMethod:bind", "dyn:getMethod:call", and "dyn:getMethod:apply" etc.)