From @quester

If you absent-mindedly type in keywords that should be capitalized in lower case, the compiler will not suggest the correct upper case form. For example​:

$ perl6

say EVAL "2+2";
4
say eval "2+2";
===SORRY!=== Error while compiling <unknown file>
Undeclared routine​:
  eval used at line 1. Did you mean 'val'?

BEGIN {say pi}
3.14159265358979
begin {say pi}
===SORRY!=== Error while compiling <unknown file>
Undeclared routine​:
  begin used at line 1

Best regards,
quester

From @smls

Rakudo now suggests `EVAL` when you type `eval`​:

  ➜ eval "say 42"
  ===SORRY!=== Error while compiling -e
  Undeclared routine​:
  eval used at line 1. Did you mean 'EVAL', 'val'?

However, it still does not suggest the correct spelling when you lowercase `BEGIN` (or other phasers, like `CATCH`).

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

From @lizmat

Fixed with 1728139 , tests needed, MasterDuke17++ for actual code.

On 05 Oct 2015, at 08​:18, quester (via RT) <perl6-bugs-followup@​perl.org> wrote​:

# New Ticket Created by quester
# Please include the string​: [perl #​126264]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=126264 >

If you absent-mindedly type in keywords that should be capitalized in lower case, the compiler will not suggest the correct upper case form. For example​:

$ perl6

say EVAL "2+2";
4
say eval "2+2";
===SORRY!=== Error while compiling <unknown file>
Undeclared routine​:
eval used at line 1. Did you mean 'val'?

BEGIN {say pi}
3.14159265358979
begin {say pi}
===SORRY!=== Error while compiling <unknown file>
Undeclared routine​:
begin used at line 1

Best regards,
quester

From @zoffixznet

Tests added in Raku/roast@50b60804b3

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