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

Rename binaries before uploading #248

Merged
merged 2 commits into from
Jul 28, 2020
Merged

Conversation

lukel97
Copy link
Collaborator

@lukel97 lukel97 commented Jul 28, 2020

Also use zip as compression method for Windows
Fixes #225

Also use zip as compression method for Windows
Fixes haskell#225
@lukel97 lukel97 requested a review from jneira July 28, 2020 11:33
@lukel97 lukel97 requested a review from Ailrun July 28, 2020 14:19
@jneira
Copy link
Member

jneira commented Jul 28, 2020

LGTM, only one doubt: does continue being necessary the --disable-documentation arg? we don't have docs enabled in cabal.project now

@lukel97
Copy link
Collaborator Author

lukel97 commented Jul 28, 2020

@jneira good catch, will drop that flag

Copy link
Member

@Ailrun Ailrun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me :)

@lukel97
Copy link
Collaborator Author

lukel97 commented Jul 28, 2020

@jneira I'm also going to disable the 8.8.4 build on windows, I've had zero luck with

cabal build exe:hls -O2 $LINUX_CABAL_ARGS || \
         cabal build exe:hls -O2 $LINUX_CABAL_ARGS -j1

:(

It's encountered the segfault every single time now. Maybe another
release :(

Also remove the disable-documentation flag since the cabal.project file
has been updated
@lukel97 lukel97 merged commit cd68c15 into haskell:master Jul 28, 2020
pepeiborra pushed a commit that referenced this pull request Dec 27, 2020
* Fix #248 and #250

This fixes hover for types, classes and type variables.

Information about spans includes a `Maybe Type` which is `Just` for data-level
expressions and `Nothing` for type-level expressions.

`AtPoint.atPoint` which is the oddly-named function responsible for constructing
hover information, runs in the `Maybe` monad, and aborted at the first sight of
a `Nothing`, thus producing no hover information for type-level spans.

In the process of fixing this, I have refactored the function to

+ separate the construction of data-level and type-level hover info

+ make the components that make up the hover info (and their construction) more
  clear

I can see plenty little improvements that could be made to the functionality of
the code (and lots that could be made to its organization), but the most
important fixes of the basic missing functionality are here.

Fix #248
Fix #250

* Revert behaviour of locationsAtPoint to match its name

The name suggests that it returns all locations, while the last commit changed
this to return at most one.

* Fix issue numbers in test titles

There was some confusion about which tests addressed issue 248 vs 249
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.

Properly name the binaries before gzipping them
3 participants