A new TYPEKIND parameter?

[tclune]

For MAPL, I would like to have the ability to specify a TYPEKIND for an import that "matches" the TYPEKIND of the export that it is connected. Something like ESMF_TYPEKIND_MATCH or ESMF_TYPEKIND_MIRROR etc.

As usual, since the dkind component is public, I can implement this entirely within MAPL, but am offering it as a change to ESMF in case there is value in this for NUOPC.

The scope of this may grow, as there are other import attributes that should also mirror, but I think a new parameter is only needed for those that otherwise have a sensible default. (I can just use an unallocated allocatable as a "match" value in the other cases.) For better or worse, MAPL has a default for import specs of ESMF_TYPEKIND_R4.

[theurich]

We talked about this on the regular NASA call. Action item:

• I need to explore whether this feature on the ESMF level could eventually become useful for NUOPC mirroring
• If that could lead to some ESMF APIs that actually use such a new ESMF_TYPEKIND, then adding it on the ESMF level will make sense.
• If no ESMF API actually make use of such a new TYPEKIND, then it should not be added on the ESMF level. MAPL can still add it for GEOS use, but not something ESMF supports.