-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
canonicalizePath "." has changed behaviour #42
Comments
/cc'ing also @bgamari whom I help with rls mgmt, but who is ultimately the one in charge and spending his weekends with GHC 8 release managament... :-) |
@ndmitchell just to clarify, the semantic change you're complaining occured in the hackage-released v1.2.5 release, and would therefore constitute a PVP violation? |
@hvr - I tried 7.10 which seems to have 1.2.2.0 and it doesn't include the trailing slash. I tried 1.2.5.0 and it does. I'm not really complaining about PVP violations, more undocumented change that might or might not have been intentional. For info, I've fixed this in Shake with ndmitchell/shake@9f6f901. |
The change occurred in 1.2.3.0. It was not intentional. The new implementation of I'm not sure what's the "right" behavior for this, so I'll just revert to the old behavior. (This change will also affect |
Specifically, what are you passing into |
It looks roughly like this: makeAbsolute path = normalise . (</> path) <$> getCurrentDirectory
canonicalizePath path = normalise <$> (transform =<< makeAbsolute path)
where transform = {- platform-specific function -} Besides uppercasing the drive letter, |
The the version of directory that ships with GHC 8.0 RC2 I see
canonicalizePath "." == "C:\\Neil\\"
. On GHC 7.10 it's"C:\\Neil"
without the trailing slash. This change of behaviour has broken the Shake test suite, and is not documented in the changelog. If it's an intentional change, it should be in the changelog. If it's unintentional, you still have a small window to revert it.CC @hvr, who seems to be doing GHC 8.0 release management things.
The text was updated successfully, but these errors were encountered: