Open akhillanger opened 3 years ago
Generally, I've favored keeping shmem_sync_all
and shmem_barrier_all
because I think that first-time users shouldn't have to understand all the layers of the API to write their first OpenSHMEM program. As users become more familiar with OpenSHMEM, they can peel back the layers of the onion and give themselves more control. If we never had them to begin with, I wouldn't necessarily add them simply for convenience, but I still think they're worth keeping.
For comparison, it was a long time after I first started writing MPI programs that I ever needed a communicator other than MPI_COMM_WORLD
.
@akhillanger Can we close this issue, or would you still like to pursue deprecation?
Since
shmem_sync_all
routine is equivalent to callingshmem_team_sync
on the world team, is there a reason to keepshmem_sync_all
API?