-
-
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
Bump ghcide to wz1000 hls-2 branch #184
Conversation
At 747ec1401c62257ec849319eb2dda966a8008b09 Also bump cabal-project index-state to 2020-07-01T16:33:28Z stack 8.10.1 to nightly-2020-06-29 stack 8.8.3 to lts-16.3
Note, the limitation on Cabal comes from http://hackage.haskell.org/package/stylish-haskell-0.11.0.0
I am finding that go to definition for a record field does not work. e.g. in GHC Expr.hs | RecStmt
{ recS_ext :: XRecStmt idL idR body
, recS_stmts :: [LStmtLR idL idR body]
-- The next two fields are only valid after renaming and in Utils.hs mkRecStmt anns stmts = (emptyRecStmt' anns) { recS_stmts = stmts } Putting the cursor on For me this is a blocker. PS, I have deleted |
After this is merged into the master, I got this error while trying to build hls on nix ( ghc-8.6.5 ):
|
@korayal did you try |
@bubba I'm manually updating the revision for submodules. So it looks like I was using the correct revision: Was this caused by a submodule of ghcide? |
Found the cause. I must have bumped one dependency higher than what ghcide requires. one of these should be the reason for the error above:
|
extra-1.7.2 moved duration to MonadIO instead of IO. It really looks like you are using extra-1.7.1 or lower. Can you make triple sure your extra is new enough? |
@ndmitchell I've tested it again with 1.7.3 and it did work. I must have somehow bumped the version and forgot to change (it seems, in that commit I did the same for opentelemetry too) the SHA256 hash in the nix expression (so even though the version says it's 1.7.3, I was using the already compiled version of 1.7.1), because it doesn't match to what I'm looking at right now. sorry about bothering you both about this. |
...using its default configuration layers
At 747ec1401c62257ec849319eb2dda966a8008b09
Also bump cabal-project index-state to 2020-07-01T16:33:28Z
stack 8.10.1 to nightly-2020-06-29
stack 8.8.3 to lts-16.3