-
Notifications
You must be signed in to change notification settings - Fork 664
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
Importing multiple modules that have the same named functions #1945
Comments
Thank you for the nice SSCCE! It looks like this is a regression. With 0.18 I am getting:
Looking into it further now! |
Based on the change in 82a8be3 I am now seeing the following error:
So this should be available once 0.19.1 is ready for release. Before the patch, this regression manifested in only some cases of ambiguous imports: import First exposing (..)
import Second exposing (..)
-- GOOD gives error
import First exposing (number)
import Second exposing (..)
-- GOOD gives error
import First exposing (..)
import Second exposing (number)
-- BAD no error
import First exposing (number)
import Second exposing (number)
-- BAD no error So I hope that this regression is relatively rare in practice since 0.19 came out. |
Quick Summary: Elm lets you import 2 modules and use a function with the same name from both modules.
SSCCE
Additional Details
I feel this could be dangerous and confusing with a bigger codebase that use many modules.
I'm pretty new to elm and I know that my example isn't the most kosher one but maybe the compiler shouldn't let you use duplicate function names especially if they return the same type?
The text was updated successfully, but these errors were encountered: