You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying out the repro for #1067, it failed to find the autogenerated Paths_ghcid. This was because of two things:
The resolution of stack ghci should be usable with minimal dependencies #817 was to not do a build if there are no explicit targets. I don't think this is the right solution to the problem, and it makes the behavior of stack ghci inconsistent.
I think the solution is to remove the changes from #817 and #810 and instead adopt the following resolution:
Ignore build errors which occur during the implicit build which comes before running ghci. This will consist of catching ExcecutionFailure exceptions, thrown from here, and warn the user that the errors were ignored.
While trying out the repro for #1067, it failed to find the autogenerated Paths_ghcid. This was because of two things:
The resolution of stack ghci should be usable with minimal dependencies #817 was to not do a build if there are no explicit targets. I don't think this is the right solution to the problem, and it makes the behavior of
stack ghciinconsistent.The resolution of
stack ide startfails to start if the project has compile errors #810 was to only build the dependencies. I don't think this is the right solution to the problem, because if the project has never been built then autogenerated modules won't exist.I think the solution is to remove the changes from #817 and #810 and instead adopt the following resolution:
Ignore build errors which occur during the implicit build which comes before running ghci. This will consist of catching
ExcecutionFailureexceptions, thrown from here, and warn the user that the errors were ignored.