Yes, intentional.  This will be true any time expected .map results are generated on a Windows/crlf platform.

This is why I had to add the noSlashRn calls in my previous pull requests, to get the tests to pass at all on Windows.  The test cases explicitly strip out \r\n from both the generated and expected output before comparison.