error message when using int parameters as subs

[p6rt]

Migrated from rt.perl.org#129772 (status was 'resolved')

Searchable as RT129772$

[p6rt]

From @zoffixznet

If you accidentally use an `int` variable as a Callable, you get a
helpful error​:

  <Zoffix> m​: my int $i; $i()
  <camelia> rakudo-moar 1f29cb​: OUTPUT«No such method 'CALL-ME' for
invocant of type 'Int'␤ in block <unit> at <tmp> line 1␤␤»

However, that's not the case if the variable is a parameter​:

  <Zoffix> m​: sub (int $i) { $i() }
  <camelia> rakudo-moar 1f29cb​: OUTPUT«===SORRY!===␤callee
expression must be an object␤»

Most heinous issue is the line number/file of the issue is missing
from the error message.

[p6rt]

From @jnthn

On Fri Sep 30 21​:17​:55 2016, cpan@​zoffix.com wrote​:

If you accidentally use an `int` variable as a Callable, you get a
helpful error​:

 \<Zoffix> m&#8203;: my int $i; $i\(\)
 \<camelia> rakudo\-moar 1f29cb&#8203;: OUTPUT«No such method 'CALL\-ME' for  

invocant of type 'Int'␤ in block <unit> at <tmp> line 1␤␤»

However, that's not the case if the variable is a parameter​:

 \<Zoffix> m&#8203;: sub \(int $i\) \{ $i\(\) \}
 \<camelia> rakudo\-moar 1f29cb&#8203;: OUTPUT«===SORRY\!===␤callee  

expression must be an object␤»

Most heinous issue is the line number/file of the issue is missing
from the error message.

Now the second gives the same error as the first. Test added in S32-exceptions/misc.t.

[p6rt]

The RT System itself - Status changed from 'new' to 'open'

[p6rt]

@jnthn - Status changed from 'open' to 'resolved'