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

Detect duplicate non-cyclical project imports #9933

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

philderbeast
Copy link
Collaborator

@philderbeast philderbeast commented Apr 24, 2024

A follow on from #9578. Uses an IORef to better report on duplicates (including cycles) and to detect duplicates that are not cycles. This was originally included in #9578 but punted at review, #9578 (comment).

  • Patches conform to the coding conventions.
  • Any changes that could be relevant to users have been recorded in the changelog.
  • The documentation has been updated, if necessary.
  • Manual QA notes have been included.
  • Tests have been added. (Ask for help if you don’t know how to write them! Ask for an exemption if tests are too complex for too little coverage!)

@philderbeast philderbeast changed the title Detect duplicate but not cyclical project imports Detect duplicate non-cyclical project imports Apr 24, 2024
@grayjay
Copy link
Collaborator

grayjay commented Apr 30, 2024

@Mikolaj Do you know if there is someone else who could review this pull request? This followup change doesn't really affect the dependency solver, and I'm currently focusing on #9743.

@philderbeast
Copy link
Collaborator Author

@TeofilC I'm inviting your review as cabal could perhaps be enhanced to output a list of files imported from a project in the future for use by other tools, input-output-hk/haskell.nix#2144 (comment).

@Mikolaj
Copy link
Member

Mikolaj commented Apr 30, 2024

@alt-romes: could you maybe have a look?

@Kleidukos
Copy link
Member

Looks like you may need to rebase on master so that the changes specific to #9578 don't appear anymore? At least the changelog entry for it is extraneous here. :)

@philderbeast philderbeast force-pushed the fix/y-fork-project-import branch 2 times, most recently from c5ab2b7 to b708112 Compare May 14, 2024 09:52
@philderbeast
Copy link
Collaborator Author

Thanks @Kleidukos for pointing out the stray changelog entry. Rebasing didn't clear it so I deleted it and then squashed related commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants