pattern to avoid is:
class foo {
  method () { use b; }
  b () ;
}
inline b()
{
  code;
}
because the use of b in external libs doesn't know which
implementation of b to use, the one from foo's lib, or
the inline created version in the using code's lib.

Change-Id: Ie52e17eabb7aaf42ef9a4985a2293e283e925753