From @smls

According to http://design.perl6.org/S04.html#line_1380 'start' should probably be a statement prefix.

However, in Rakudo it is currently a subroutine​:

➜ start 41 + 2
Type check failed in binding &code; expected 'Callable' but got 'Int'
  in block <unit> at <unknown file>​:1

➜ say &start
sub start (&code, :catch(&catch)) { #`(Sub|49183056) ... }

Discussion​:

<smls> maybe I'm misinterpreting the design docs?
<smls> it's not super explicit about it.
<masak> "They parse the same as phasers" and `try` already working
  that way both seem to point to your conclusion.
<masak> also, it makes sense to me that `start` would take a blorst.

From @lizmat

Fixed by 211d7a1a1e034876f53e

On 02 Jun 2015, at 14​:53, Sam S. (via RT) <perl6-bugs-followup@​perl.org> wrote​:

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

According to http://design.perl6.org/S04.html#line_1380 'start' should probably be a statement prefix.

However, in Rakudo it is currently a subroutine​:

➜ start 41 + 2
Type check failed in binding &code; expected 'Callable' but got 'Int'
in block <unit> at <unknown file>​:1

➜ say &start
sub start (&code, :catch(&catch)) { #`(Sub|49183056) ... }

Discussion​:

<smls> maybe I'm misinterpreting the design docs?
<smls> it's not super explicit about it.
<masak> "They parse the same as phasers" and `try` already working
that way both seem to point to your conclusion.
<masak> also, it makes sense to me that `start` would take a blorst.

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

From @Mouq

This is tested in S17-promise/start.t.

Closing as resolved :)

~Mouq

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