Work on OpenCoarrays 3.0 aims to produce a new application binary interface (ABI) with no references to compiler-specific descriptors. Two possibilities emerged from the May 13-15 OpenCoarrays Retreat at Dillon Beach, California, and it is likely that both will ultimately be offered was alternatives with different compilers choosing one option or another based on the compiler's intended audience and developer resources:

1. The "Power" implementation: an ABI that accepts Fortran 2018 C descriptors and does the heavy lifting of both managing data structures and transporting data across images.
2. The "Sleek" implementation: an ABI that accepts references to memory locations that are ready for immediate transport without manipulation and potential exposes more opportunities for high-level optimizations at the cost of requiring that compiler to do more work to prepare the data for transport.

Option 1 mirrors prior versions of OpenCoarrays and will be developed first because much of the existing code base can be reused and . Option 2

The plan that emerged from the
Develop a c++ implementation that provides the following functions:

1. functions that require no descriptor
   caf_init(int argc, char* argv[]);
   caf_finalize();
   error_stop();
   num_images();
   this_image(); - with no arguments
   sync_all();
   sync_images();