Note that this bug can cause a call on Void target in a void-safe system when
inlining is enabled, because the inlining apparently causes a direct access
of the attribute, rather than a call to the routine that checks whether it is
Void and if so executes the attribute body and returns that value.

I have attached classes that demonstrate the call on Void target in a
void-safe system finalized with inlining enabled.