Benjamin Bannier created MESOS-8662:

             Summary: Consider introducing a clang-tidy check to catch 
ambiguous use of FUTURE_DISPATH
                 Key: MESOS-8662
             Project: Mesos
          Issue Type: Bug
          Components: libprocess
         Environment: Currently {{FUTURE_DISPATCH}} cannot distinguish between 
two dispatched functions with identical signatures, see MESOS-5886.

As solving this issue on the implementation side seems tricky, we should 
investigate whether we can more quickly come up with a {{clang-tidy}} check to 
catch instances of such ambiguity. The general workflow seems to be
 * For every use of {{FUTURE_DISPATCH}}
 ** get type of dispatched to actor
 ** get signature of dispatched to function
 ** iterate over methods of actor checking for possible ambiguities with the 
dispatched to function's signature
 *** diagnose ambiguity
            Reporter: Benjamin Bannier

This message was sent by Atlassian JIRA

Reply via email to