Fernando Correa de Oliveira
Fernando Correa de Oliveira
I totally agree with that, but I think that it should also automatically await the blocks return if it’s Awaitable, something like this: https://glot.io/snippets/h7sotvz66u
Just as an (bad) argument: that's what happens on JS.
Here is a suggestion on what it could do (not a suggestion on how to do it): https://glot.io/snippets/h7sotvz66u
> Another thing that jumped to mind is that the proposed change would presumably make andthen/orelse blocking (synchronous) methods unlike the current non-blocking / asynchronous behavior. The block passed to...
But the .result and .cause do not need to be called when the method runs, but, if it's implemented using .then, it could do something like: ```raku method andthen(&block) {...
What I think was meant by: > I'm not sure if these methods should be documented in the current form - they could get changed, so they get result/cause instead...
this works: ```perl6 multi trait_mod:(Attribute $attr, :&bla!) {say 42}; my &a = {;}; role :: { has $.a is bla(&a) } ```
I was wrong... that haven’t work: https://colabti.org/irclogger/irclogger_log/perl6?date=2019-01-18#l394
Sorry for the delay... but it seems that "error" are on current HEAD: https://colabti.org/irclogger/irclogger_log/raku?date=2020-05-11#l317
This also works: ```raku sub foo( [ Int $i, Str $s ] ) { 'yo' }; foo [1, "A"]; #yo ```