If the disassembler were called to render the byte code of the compiled template code in the tests, one would be able to catch errors like the one reported in issue #962, which occur because the byte code is incorrect and the disassembler panics.
One option is then to call the disassembler for example in the TestMultiFileTemplate test (without necessarily checking the disassembler output, since that would require an even more extensive and broad test, which would be outside the scope of these tests).
Current limitation
This is currently not possible as it would result in disassembler panics due to issue #962.
If the disassembler were called to render the byte code of the compiled template code in the tests, one would be able to catch errors like the one reported in issue #962, which occur because the byte code is incorrect and the disassembler panics.
One option is then to call the disassembler for example in the
TestMultiFileTemplatetest (without necessarily checking the disassembler output, since that would require an even more extensive and broad test, which would be outside the scope of these tests).Current limitation
This is currently not possible as it would result in disassembler panics due to issue #962.