Skip to content

Remove unused Data.Foldable.foldr import#4042

Merged
JordanMartinez merged 2 commits intopurescript:masterfrom
kl0tl:remove-unused-Data.Foldable.foldr-import
Apr 3, 2021
Merged

Remove unused Data.Foldable.foldr import#4042
JordanMartinez merged 2 commits intopurescript:masterfrom
kl0tl:remove-unused-Data.Foldable.foldr-import

Conversation

@kl0tl
Copy link
Copy Markdown
Member

@kl0tl kl0tl commented Apr 3, 2021

Description of the change

We added an import for Data.Foldable.foldr to Language.PureScript.CoreImp.Optimizer.TCO in #3958. The build passed (https://travis-ci.org/github/purescript/purescript/builds/763606846) but subsequent builds started to fail with “The import of ‘Data.Foldable’ is redundant” since we merged #4013. The latter upgraded base-compat and GHC but base-compat-0.10.5 already exported Prelude.Compat.foldr, and according to GHC documentation -Wunused-imports was already implied by -Wall in v8.6.5 so I really don’t understand what’s going on 🤷‍♂️


Checklist:

  • Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
  • Linked any existing issues or proposals that this pull request should close
  • Updated or added relevant documentation
  • Added a test for the contribution (if applicable)

Copy link
Copy Markdown
Member

@rhendric rhendric left a comment

Choose a reason for hiding this comment

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

Should this even be mentioned in the changelog at all? Otherwise, :shipit:.

@JordanMartinez
Copy link
Copy Markdown
Contributor

Yeah, I think it should. It provides accountability as to what changed. Besides, it's easier to remove unneeded things before making a release than it is to remember what to add.

@JordanMartinez JordanMartinez merged commit cc23032 into purescript:master Apr 3, 2021
@hdgarrood
Copy link
Copy Markdown
Contributor

I don’t think we need accountability here and I’m not sure a strict policy of having every change noted in the changelog is a good way of achieving that anyway. We already have the git history for cases where we want to be able to look at every change and who made it don’t we? It probably doesn’t matter now but I think this could have been left out.

@kl0tl
Copy link
Copy Markdown
Member Author

kl0tl commented Apr 4, 2021

Duly noted! We can clean the changelog when releasing the next minor version.

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.

4 participants