Fix a typo in the TOperator test

[Gnimuc]

We may need to find a way to catch this.

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[Vipul-Cariappa]

I cannot see a codecov bot comment. Is it not running?

[Vipul-Cariappa]

The change being done here is the self argument. Using both object and toperator is acceptable. And in both cases we are reusing the variable declared before.
I would say object is better as it conveys the correct usage.

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[Gnimuc]

I would say object is better as it conveys the correct usage.

Could you elaborate on the correctness of using object? object is a dangling pointer that points to a destructed object in another test case above.

[mcbarton]

I cannot see a codecov bot comment. Is it not running?

@Vipul-Cariappa This is due to the accidentally removal of the coverage job from the ci. This PR fixes it #577 . Once this PR is in, rebase this PR and you should see a coverage comment. Feel free to review and approval the PR, if it hasn't already been done, when you see this message.

[Vipul-Cariappa]

My bad. I assumed you were invoking a constructor, so I thought it did not matter what the object pointed to. But I see that it is a method that is being invoked. This is correct, and the previous usage was wrong.
LGTM!