Skip Menu |

This queue is for tickets about the Future-AsyncAwait CPAN distribution.

Report information
The Basics
Id: 123465
Status: open
Priority: 0/
Queue: Future-AsyncAwait

Owner: Nobody in particular
Requestors: corion [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

Subject: No support for signatures
Download (untitled) / with headers
text/plain 392b
Hello Paul, thank you for creating Future::AsyncAwait. I found that the current version does not seem to like functions with signatures on them: async sub( $args ) { } fails to compile with Expected async sub NAME to be followed by '{' at ... I suspect the module will need to allow for a signature there, but don't know how to change the module to fix things myself ;) -max
Download (untitled) / with headers
text/plain 612b
Yes; I'm aware of this. I possibly should draw more attention to it in the docs. It's a somewhat unfortunate situation, that I wonder if p5p@ could help me with. The trouble is that I have to do more of the parsing currently than I'd really like. As well as signatures, other things like prototypes and attributes also aren't parsed. The reason being that core doesn't really provide any nice ways to get at the parser for all of that, but still have the raw unchecked optree before the checker/optimiser gets to it. I need it in this initial form to put the OP_ASYNC and OP_AWAIT ops into it. -- Paul Evans
Download (untitled) / with headers
text/plain 108b
This core perl feature might help: -- Paul Evans
Download (untitled) / with headers
text/plain 213b
On Thu Jan 18 21:35:52 2018, PEVANS wrote: Show quoted text
> This core perl feature might help: > >
No progress in a year. I have bumped the ticket again. -- Paul Evans

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to