Background
As part of issue #4958 (rename internal modules to `mapl__mod` convention), `base3g/Comms.F90` and `infrastructure/esmf/comms/MAPL_Comms.F90` both initially resolved to the same module name `mapl_Comms_mod`, causing a collision.
Current State
The two files are not duplicates — they are distinct implementations:
- `base3g/Comms.F90` — large legacy implementation with collective gather/scatter, request types, round-robin PE lists, broadcast variants, etc. Currently retains the old name `MAPL_CommsMod` as a deliberate exception.
- `infrastructure/esmf/comms/MAPL_Comms.F90` — newer, leaner 3G implementation. Has the correct name `mapl_Comms_mod`.
Desired Resolution
`base3g/Comms.F90` should eventually be renamed to `mapl_Comms_mod` (after merging/reconciling with the 3G version) or deprecated and removed entirely as base3g migration completes.
Related
Background
As part of issue #4958 (rename internal modules to `mapl__mod` convention), `base3g/Comms.F90` and `infrastructure/esmf/comms/MAPL_Comms.F90` both initially resolved to the same module name `mapl_Comms_mod`, causing a collision.
Current State
The two files are not duplicates — they are distinct implementations:
Desired Resolution
`base3g/Comms.F90` should eventually be renamed to `mapl_Comms_mod` (after merging/reconciling with the 3G version) or deprecated and removed entirely as base3g migration completes.
Related