Not the greatest rationale: Graal native-image complains that the tap-loop thread starts during class-loading. It is possible to delay starting it until the first tap registers, which is exactly what the attached patch does.
Screened by: Alex Miller
Refresh patch to apply to master
I think this approach has the problem of bottling up tapped values until a tap is started (which is not desired). Perhaps tap> should also force the tap loop thread?
added patch that delays tap-loop init until first interaction with tap system