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
Stan, via extensions, appears to be prepending the hs-source-dirs from the .cabal file verbatim onto the module name. This means if the .cabal file uses / as its path separators, the returned file paths (and associated extension map) will be broken for Windows users.
For example, if your cabal file has:
hs-source-dirs: extension-tests/language-pragma
... then the resulting Map key winds up looking like this for Windows users:
This results in Map lookups missing, which in turn results in Stan not recognizing any of a project's enabled extensions. (One of the causes for the above-mentioned HLS issue.)
From a quick look, I think the issue might be happening around here somewhere. (I do see some Cabal version checks, not sure how those play into this...)
The text was updated successfully, but these errors were encountered:
Thanks for the report. stan and extensions have very little active maintainership currently. I'm happy to oversee and advise a patch to fix this, but I won't have time to do it myself any time in the near future. Perhaps @0rphee is interested?
Discovered while working on this HLS PR: haskell/haskell-language-server#4023, related to these issues:
Stan, via
extensions
, appears to be prepending thehs-source-dirs
from the.cabal
file verbatim onto the module name. This means if the.cabal
file uses/
as its path separators, the returned file paths (and associated extension map) will be broken for Windows users.For example, if your cabal file has:
... then the resulting Map key winds up looking like this for Windows users:
This results in Map lookups missing, which in turn results in Stan not recognizing any of a project's enabled extensions. (One of the causes for the above-mentioned HLS issue.)
From a quick look, I think the issue might be happening around here somewhere. (I do see some Cabal version checks, not sure how those play into this...)
The text was updated successfully, but these errors were encountered: