I assume this is caused by alignment regions not getting optimized out
with the recent changes to the alignment algorithm. It's now more
correct, but it's more pessimistic.
A hammer to just disable alignment might be a reasonable solution, but
I'd be concerned there are alignment regions that
So, we seem to be seeing a lot of regressions in various DFDL schemas like
most recently NITF, previously PNG.
What if users run into this in their own DFDL schemas?
These are showing unparser deadlocks due to cyclic relationships. At one
time we discussed adding a "big hammer" property or
I have not had time to test the vscode debugger recently.
We could hold off doing that, or I could do that as part of the rc1
evaluation process if you prefer before we vote on accepting it.
On Tue, Feb 22, 2022 at 3:06 PM John Wass wrote:
> All issues are resolved. If we are good to
