Enhancement: treat decorated routine as first-class citizen

[dumblob]

Currently, only routines can be first-class citizens:

0$ dao -e 'routine @d(f(args): routine) {io.writeln("@d")}; r=routine() {io.writeln("r")}; r()'
r
= none
0$ dao -e 'routine @d(f(args): routine) {io.writeln("@d")}; @d routine r() {io.writeln("r")}; r()'
@d
= none

0$ dao -e 'routine @d(f(args): routine) {io.writeln("@d")}; r=@d routine() {io.writeln("r")}; r()'
[[WARNING]] in file "command line codes":
  At line 1 : Statements not seperated properly;
[[ERROR]] in file "command line codes":
  At line 0 : Invalid function definition --- " __main__() ";
  At line 1 : Invalid virtual machine instruction --- " CALL:4,512,5 ";
In code snippet:
      4 :  LOAD        :     1 ,     0 ,     4 ;     1;   (
>>    5 :  CALL        :     4 ,   512 ,     5 ;     1;   r()
      6 :  RETURN      :     5 ,     1 ,     0 ;     1;   )
  ** Invalid number of parameter --- " too few parameters ";
     Assuming  : @routine<f:routine=>none>;

[Night-walker]

You simply mistook with the syntax:

(dao) routine @d(f(args): routine) {io.writeln("@d")}
= none
(dao) r = @d(routine() {io.writeln("r")})
= routine_17_023CBB88
(dao) r()
@d
= none

[dumblob]

I did :( Thanks!

[dumblob]

Reopening, because the syntax ... r = @d routine() {... should be detected as syntax compile-time error in this case.

[Night-walker]

Emm.. Isn't it what 'Statements not seperated properly' tries to say?

[dumblob]

It's just warning, then the parsing successfully continues, then the code is run and first then, an error is issued:

In code snippet:
      4 :  LOAD        :     1 ,     0 ,     4 ;     1;   (
>>    5 :  CALL        :     4 ,   512 ,     5 ;     1;   r()
      6 :  RETURN      :     5 ,     1 ,     0 ;     1;   )
  ** Invalid number of parameter --- " too few parameters ";
     Assuming  : @routine<f:routine=>none>;

[Night-walker]

Oh, right.