Skip to content
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.

When two packages use the same Module.Name, neither can be used. #257

Closed
sgillis opened this issue Jan 12, 2017 · 2 comments
Closed

When two packages use the same Module.Name, neither can be used. #257

sgillis opened this issue Jan 12, 2017 · 2 comments
Labels

Comments

@sgillis
Copy link

sgillis commented Jan 12, 2017

Installing libraries that expose modules with the same name results in problems. For example, mdgriffith/elm-style-animation and mgold/elm-animation both expose Animation. When trying to compile, I get this error:

I found multiple modules named 'Animation'.

Module '<mymodule>' is trying to import it.

Modules with that name were found in the following locations:

    package mdgriffith/elm-style-animation
    package mgold/elm-animation

It seems that this could become a bigger problem when the number of packages grows.

I am using Elm 0.18

@process-bot
Copy link

Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

@evancz evancz changed the title Name collision When two packages use the same Module.Name, neither can be used. Jul 8, 2017
@evancz evancz added the problem label Jul 11, 2017
@evancz
Copy link
Contributor

evancz commented Aug 3, 2017

Tracking in elm/compiler#1625 meta issue. Thanks for the report!

@evancz evancz closed this as completed Aug 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants