psch: the reduce meta op is not allowed to have any whitespace in it. IIRC it's formally ambiguous with the Array constructor, so it's possible we can't even throw X::Cannot::InlineDefineReduce (if we could, why not just make it work then?)

ZzZombo: you declared a subroutine. Unlike operators, you can't install arbitrarily-named traits and are restricted to `is`, `does`, `hides`, `will`, `of`, `returns`, and `handles` as primary trait keyword, but you can modify the name that follows it by using named attributes

lizmat: if you have in mind p5 modules to be p6’d, maybe you could get people to commit to converting them in a list something like mos5 wantd for p5 to p6 (in some kind of order of importance as you see it).

well, putting a list on the site should be reasonably easy, the hard part is getting thoughts on the importance of modules to be converted. several folks have said p6 is not a good language for beginners because of lack of advanced features--those folks should be making entries on the "most wanted p5 to p6" list.

So I just did a little test, writing a simple REST API (that simulates rolling a bunch of dice, not external dependencies) in Mojo::Lite, Cro and express. All in basically the simplest run types so no WSGI NGINX or other stuff.