You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to be intended, as per the comment from InlayHints.cpp:
// Do not show parameter hints for operator calls written using operator// syntax or user-defined literals. (Among other reasons, the resulting// hints can look awkard, e.g. the expression can itself be a function// argument and then we'd get two hints side by side).
However, I think it'd be fine to be lenient on function call to operator(): They are formed in a normal function call syntax, and I didn't find a case where they are inappropriate.
However, I think it'd be fine to be lenient on function call to operator(): They are formed in a normal function call syntax, and I didn't find a case where they are inappropriate.
We don't show parameter hints for a user-defined function call operator() nor a call to lambda, for example:
This seems to be intended, as per the comment from InlayHints.cpp:
However, I think it'd be fine to be lenient on function call to
operator()
: They are formed in a normal function call syntax, and I didn't find a case where they are inappropriate.Nathan, what do you think? @HighCommander4
The text was updated successfully, but these errors were encountered: