newline to make sphinx happy: ```suggestion - https://github.com/OSGeo/gdal/pull/5257: [FEATURE] Add (initial) ```

```suggestion manner, i.e. it does not break the ABI, and can thus be implemented in ```

I assume you are speaking about the multidimensional API here? Should be precised

cf above remark if we really need a type alias.

```suggestion - ``GDT_CFloat16`` --> ``std::complex<GFloat16`` / ``_Complex GFloat16`` ```

It should be mentioned here that at least the HDF5, GTiff and Zarr drivers already handle float16, but by exposing it as float32, using software conversion routines in port/cpl_float.h. For HDF5, older version of he HDF5 library, do that conversion internally. Most recent ones, when built with float16 support, directly return the float16 values, and GDAL does the the float16<-->float32 conversion (https://github.com/OSGeo/gdal/pull/10052)

The Gxxxx typedefs are mostly of legacy interest. They were introduced long before C/C++ standardized fixed-size types ([u]int[8/16/32/64] etc), and we hope to get rid of them at some point (cf https://gdal.org/development/rfc/rfc95_standard_int_types.html , which is postponed to an hypothetical GDAL 4.0). So here I would go to just using ``_Float16`` (is that standardized for C ? I saw that C++23 has standardized std::float16, but do all C++ implementations that understand std::float16 understand ``_Float16`` ?)