WKT round-tripping fail with MULTIPOINT(EMPTY) vs MULTIPOINT EMPTY

[mwtoews]

A MULTIPOINT(EMPTY) geometry has one empty item, while MULTIPOINT EMPTY is the same type but no items. They round-trip fine with WKB, but not with WKT. Here is a bash loop to compare the outputs using GEOS 3.12.0:

for geom_type in MULTIPOINT MULTILINESTRING MULTIPOLYGON; do
  geom="$geom_type(EMPTY)"
  echo "input: $geom"
  echo -n "  wkt: "
  ./bin/geosop -a "$geom" -f wkt
  echo -n "  wkb: "
  ./bin/geosop -a "$geom" -f wkb
done

shows the unexpected WKT differences

input: MULTIPOINT(EMPTY)
  wkt: MULTIPOINT EMPTY
  wkb: 0104000000010000000101000000000000000000F87F000000000000F87F
input: MULTILINESTRING(EMPTY)
  wkt: MULTILINESTRING EMPTY
  wkb: 010500000001000000010200000000000000
input: MULTIPOLYGON(EMPTY)
  wkt: MULTIPOLYGON EMPTY
  wkb: 010600000001000000010300000000000000

Meanwhile, these are all expected:

for geom_type in MULTIPOINT MULTILINESTRING MULTIPOLYGON; do
  geom="$geom_type EMPTY"
  echo "input: $geom"
  echo -n "  wkt: "
  ./bin/geosop -a "$geom" -f wkt
  echo -n "  wkb: "
  ./bin/geosop -a "$geom" -f wkb
done

shows expected zero-length collections:

input: MULTIPOINT EMPTY
  wkt: MULTIPOINT EMPTY
  wkb: 010400000000000000
input: MULTILINESTRING EMPTY
  wkt: MULTILINESTRING EMPTY
  wkb: 010500000000000000
input: MULTIPOLYGON EMPTY
  wkt: MULTIPOLYGON EMPTY
  wkb: 010600000000000000

There are no issues with GeometryCollection, which can round-trip GEOMETRYCOLLECTION(POINT EMPTY) without issue. PostGIS seems to handle these geometries as expected.

I'm almost certain this has been brought up somewhere, but I cannot find this. Empty strikes again!