Relates to: https://github.com/amit-davidson/Chronos/issues/26
The problem is that when calling a mutex interface, it's possible to determine the mutex and callCommon.Args is nil.
The program would therefore panic since it expected the first argument to be the receiver. A solution is to use pointer analysis but we ignore it for now since it's not a common use case.
Relates to: https://github.com/amit-davidson/Chronos/issues/26 The problem is that when calling a mutex interface, it's possible to determine the mutex and
callCommon.Argsisnil. The program would therefore panic since it expected the first argument to be the receiver. A solution is to use pointer analysis but we ignore it for now since it's not a common use case.