I was able to reproduce the error with 13.7 so added a problem report, TPR#19541, and sent it off to engineering. The good news is that the code compiled and ran correctly with our internal develpment compiler, meaning that our engineer had already found and fixed the problem. Hopefully this means that the fix will be available in the 13.9 release.