Nested argument mismatch could suggest moving extra parameter outside parenthesis about rust HOT 3 OPEN

@rustbot claim

from rust.

I will work on this issue for only one argument first.

from rust.

After investigation the codebase, I think it is hard to achieve this in current structure because I couldn't find the way to get the argument information (expected and actual arguments and their types) without any subeffects.

A suggestion help: provide the argument is emitted in the method report_arg_errors. I planned to emit the subject suggestion in this method, however there are one problem. In the method report_arg_errors, I wanted to get the expected and actual arguments in the inner call if an argument is method call (or function). However I couldn't find the method to get the information without any subeffects. For example, check_argument_types seems to be good method to get, but this method call self.set_tainted_by_errors that has subeffects.

Another method is to copy the related code from check_argument_types method, but it's dangerous to me without detailed knowledge of the method.

from rust.