Given the analysis by Maciej in #3, this seems like something we won't fix in the 5.0 branch. It it works in current master, it is expected to work in 5.1. Marking as won't fix.
Given the analysis by Maciej in #3, this seems like something we won't fix in the 5.0 branch. It it works in current master, it is expected to work in 5.1. Marking as won't fix.