The method Thread.destroy has been unimplemented since 1.0. The only value it
has right now is to destroy the *invoking* thread, which can be done more
reasonably, and so this is a thin excuse indeed. We should deprecate this
method as a form of public hygiene -- better the ignorant user get a compiler
warning (with encouragement to remove it) than it blow up later at runtime
in the field.