Fixes e2e tests using checks with UNIX paths.

[esdrubal]

On Windows the output error and warning paths use \ as path separator.
e2e tests have checks with hardcoded UNIX paths that use / as path separator character.

Solution was to replace \ by / on compile_and_capture_output.

[mitchmindtree]

Thanks for the PR @esdrubal!

I'm not sure we should start adding patches like this until we actually decide to properly support Windows within Sway, Forc, etc too. #1526 shares a rough path ahead for this for anyone interested in having a go at native Windows support.

[tritao]

Thanks for the PR @esdrubal!

I'm not sure we should start adding patches like this until we actually decide to properly support Windows within Sway, Forc, etc too. #1526 shares a rough path ahead for this for anyone interested in having a go at native Windows support.

I think this PR is basically the first step towards your Check all path handling task in the issue.

I have no idea about other Windows issues, but this fix (or a variation) will always be needed. On Windows, we want to display Windows-style paths when displaying diagnostics, yet the tests are written with Unix-style paths. We don't really want to change all tests FileCheck directives, so the only two options I can see are either:

1. convert the paths in check directives to Windows-style when parsing them
2. convert the compiler output paths to Unix-style before matching the checks

This PR implements 2) which I think is a good enough solution for the issue.

There are currently other Windows issues which still need addressing (compiling in debug is comptetely broken with a stack overflow issue for instance) but IMHO we shouldn't not merge this one because of that, since it brings us one step closer to being able to setup a Windows CI.

[otrho]

I agree. A tiny change like this is helpful in the short term and can't really hurt.

Unless we explicitly don't want Sway on Windows... 😉