Consistent use: Multiple occurances - Inconsistent Function Definitions

[wesbland]

Problem

Some function definitions are missing or have inconsistent (with similar arguments in other functions) descriptions. See, for example, MPI_TESTALL (page 62) description for the flag argument should use the same text as MPI_TESTANY (page 60), except "true if all..."

Suggested Fix

Suggest asking the bindings committee to review

[wesbland]

Needs scoping, but maybe chapter committee:

• Editor - 2
• Chapter committee - 3
• Errata - 1
• Full Proposal - 1

[wesbland]

Each committee chair should check the box when they're done. Creating a small pull request for each chapter (or group of chapters if you own more than one) is probably as good a way as any to do this. Make sure that in your pull request, you mention this ticket (#280) without saying "Fixes" to avoid automatically closing it since there will be more than one PR to do this work. Also, if there's nothing to be done in your chapter, just check the box.

• Front matter - @wgropp
• Introduction - @wgropp
• Terms - @cblaas
• Point-to-Point - @dholmes-epcc-ed-ac-uk
• Datatypes - @bosilca
• Collectives - @tonyskjellum
• Communicators - @GuillaumeMercier
• Topologies - @RolfRabenseifner
• Partitioned Communication - @regrant
• Environment - @bosilca
• Info - @schulzm
• Process Creation - @hppritcha
• RMA - @wgropp
• External Interfaces - @schulzm
• I/O - @tonyskjellum
• Tools - @mahermanns
• Deprecated - @RolfRabenseifner
• Removed - @RolfRabenseifner
• Backward Incompatibilities - @wesbland
• Bindings - @puribangalore
• Bindings Summary - @RolfRabenseifner
• Change Log - @RolfRabenseifner

@martinruefenacht will add an automated check to look for these empty descriptions with no default description and flag them, causing the check to fail. The chapter committees will need to fix those.