問題文
A nested type is declared without the keyword that would detach it from what surrounds it, and it is then handed a field that the whole family of such values would share. Which rule turns that field declaration away?
選択肢
- The declaration is turned away because a nested type of that kind is tied to an enclosing instance and reachable from inside of it so it has nowhere to keep a field that stands apart from a single one of them.
- The declaration is turned away because a nested type of that kind is closed to inheritance by a modifier written in its header so it has nowhere to keep a field that stands apart from a single one of them.
- The declaration is turned away because a nested type of that kind is resolved during a run through a lookup made at that moment so it has nowhere to keep a field that stands apart from a single one of them.
- The declaration is turned away because a nested type of that kind is compiled into a separate unit that loads by itself later on so it has nowhere to keep a field that stands apart from a single one of them.