Hello, 2016-05-04 22:27 GMT+03:00 Nicholas Clark <nick@ccl4.org>: > I have commit 73949fca082fe50bf47755c5ffa328259057ae36 cherry-picked onto > v5.22.0: > > c813842 (HEAD) make PadlistNAMES() lvalue again. > 70f63a4 (tag: v5.22.0) Coro is known broken on blead Commit 73949fca082fe50bf47755c5ffa328259057ae36 has never actually made it into the 5.22 branch. Is it possible to cherry-pick it for the next maint release (while they are), as it's currently the only thing that prevents Coro from compiling on 5.22? Best regards, Sergey AleynikovThread Previous | Thread Next