Drop nullable-question for `simple_array`, `array` and `json`?

When answering "yes" to the nullable-question ("Can this field be null in the database (nullable)"), the result is:

/**
 * @ORM\Column(type="json", nullable=true)
 */
private $col1 = [];

/**
 * @ORM\Column(type="simple_array", nullable=true)
 */
private $col2 = [];

/**
 * @ORM\Column(type="array", nullable=true)
 */
private $col3 = [];

But if each new entity is instantiated with an empty array ([]), I only see two ways how this could ever be null in the database:

• You set it to null yourself, explicitly: (new Foo())->setCol1(null)
• You enter it manually in the database, without Doctrine

Both seem to be "special" cases. So I'm wondering if it wouldn't be better to omit the nullable-question for these types, and just silently default to non-nullable - requiring those few people who need this, to manually add it.

Start by locating the nullable-question handling for the simple_array, array, and json types and any tests covering their generated annotations. Review the existing discussion before deciding whether these types should omit the question or preserve an explicit nullable option; done means the behavior and its tests clearly reflect the agreed decision.