-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
Migrate to OsPath #3046
Comments
Oh bummer. Well, if we really want to, it should be ok to embed |
https://gitlab.haskell.org/ghc/ghc/-/issues/21887#note_443922 It may be possible to provide updated GHC releases that include new filepath. But this is still in discussion. |
@kokobd you mean between String and OsPath? |
Can you run cabal bench ghcide and share the contents of the ghcide/bench-results folder minus the binaries ? |
I'll take a look, but in the meantime CI shows that it works fine on 8.10.7. Would you be able to run it there? EDIT: nevermind, I see that 8.10.7 won't do |
Next steps:
|
Real Soon, we will benefit from the performance improvement with all versions of GHC supported by HLS. Next steps:
|
I think this is mostly done. Was there more to do? |
I haven't looked at it, but I wonder how you do file operations etc. I'm guessing you convert back to filepath somewhere? In that case the conversion is not complete |
It looks like the situation is:
|
So in ten years, I guess? |
Two major GHC versions, so yeah, a while. Or I guess if someone is keen and wants to do it with conditional logic they could do! |
We have a better alternative to FilePath now. See: https://hasufell.github.io/posts/2022-06-29-fixing-haskell-filepaths.html
What we should do:
NormalizedFilePath
toNormalizedOsPath
after the issue in lsp to support OsPath Migrate to OsPath lsp#445 is solved. Profiling it to make sure the performance improves.FilePath
toOsPath
However, this can not be done until
ghc-9.6
is released (ships the newfilepath
library), or all ghc shipped libraries are available on Hackage.The text was updated successfully, but these errors were encountered: