Skip to content
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

doc(hack): Add explanation to hack and test HLS #329

Merged
merged 3 commits into from
Aug 18, 2020

Conversation

sir4ur0n
Copy link
Collaborator

I think this kind of documentation, even though it may seem obvious to HLS maintainers, are helpful to newcomers who wish to give it a shot hacking HLS 😄

README.md Outdated Show resolved Hide resolved
@jneira
Copy link
Member

jneira commented Aug 16, 2020

This was not my workflow but it is a good one
I am installing hls globally in my default bin path or, if i am hacking on a pr i change the hls path in the vscode config to a fixed external location and install with cabal --installdir=/path/to/custom/hls install -w ghc-xxx. This way i have them stored in case i have to switch between branches or compare some behaviour between them.
cabal install does not reuse the entire cache with cabal build so sometimes you have to wait though.

@sir4ur0n sir4ur0n requested review from jneira and wz1000 August 17, 2020 16:27
@jneira jneira merged commit 7bb4aee into haskell:master Aug 18, 2020
pepeiborra added a commit that referenced this pull request Dec 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants