Skip to content

Commit 5c85fdd

Browse files
authored
Remove LINK phaser
grep -FR 'LINK' in rakudo and roast repos turn up nothing
1 parent b6a1b5d commit 5c85fdd

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

doc/Language/phasers.pod6

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,6 @@ Here is a summary:
2121
2222
BEGIN {...} # * at compile time, ASAP, only ever runs once
2323
CHECK {...} # * at compile time, ALAP, only ever runs once
24-
LINK {...} # * at link time, ALAP, only ever runs once
2524
INIT {...} # * at run time, ASAP, only ever runs once
2625
END {...} # at run time, ALAP, only ever runs once
2726
@@ -122,7 +121,6 @@ teardown usually want to happen in the opposite order from each other.
122121
123122
BEGIN {...} # at compile time, ASAP, only ever runs once
124123
CHECK {...} # at compile time, ALAP, only ever runs once
125-
LINK {...} # at link time, ALAP, only ever runs once
126124
COMPOSE {...} # when a role is composed into a class
127125
128126
Execution Begins
@@ -188,15 +186,6 @@ Code that is generated at run time can still fire off C<CHECK> and C<INIT>
188186
phasers, though of course those phasers can't do things that would require
189187
travel back in time. You need a wormhole for that.
190188
191-
=head2 X<LINK|Phasers>
192-
193-
Runs at link time, As late as possible, only runs once.
194-
195-
Can have a return value that is provided even in later phases.
196-
197-
The compiler is free to ignore C<LINK> phasers compiled at run time since
198-
they're too late for the application-wide linking decisions.
199-
200189
=head2 X<INIT|Phasers>
201190
202191
Runs after compilation during main execution, as soon as possible, only runs

0 commit comments

Comments
 (0)