On Mon, Apr 27, 2015 at 4:29 PM, Nicolas Goaziou <m...@nicolasgoaziou.fr> wrote:
> No, it is a genuine bug from parser. This should be fixed in
> eb77fed33fa0306ebed2224f7895b688320847b2.
Confirmed that it is fixed. Thank you.

Regards,
Jake

Reply via email to