ith different fill bytes.
>
>
> -mikeb
>
>
> ________________
> From: Steve Lawrence
> Sent: Thursday, December 17, 2020 9:07 AM
> To: dev@daffodil.apache.org
> Subject: Correct behavior when unparse does not ending on a byte boundary
>
>
Sent: Thursday, December 17, 2020 9:07 AM
To: dev@daffodil.apache.org
Subject: Correct behavior when unparse does not ending on a byte boundary
I was looking at DAFFODIL-1565 thinking it could be closed with all the
recent streaming additions. But as I thought about it more, we have a
clearly asymmetrica
I was looking at DAFFODIL-1565 thinking it could be closed with all the
recent streaming additions. But as I thought about it more, we have a
clearly asymmetrical behavior with parse and unparse that relates to
what this bug is talking about, so now I'm not so sure.
Say we have an element that par
