Obviously similar to bug 1600645, but behavior and output are different so I think it's a different issue.
Obviously similar to bug 1600645, but behavior and output are different so I think it's a different issue.