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

ScopeShadowing warnings are repeated #3759

Open
jjl opened this issue Nov 28, 2019 · 3 comments
Open

ScopeShadowing warnings are repeated #3759

jjl opened this issue Nov 28, 2019 · 3 comments

Comments

@jjl
Copy link

jjl commented Nov 28, 2019

[165/237 ScopeShadowing] src/Gargantext/Components/Search/SearchField.purs:4:1

  4  import Prelude
     ^^^^^^^^^^^^^^
  
  Shadowed definitions are in scope for value div from the following open imports:
  
    import Prelude
  
  These will be ignored and the declaration from Reactix.DOM.HTML will be used.

[166/237 ScopeShadowing] src/Gargantext/Components/Search/SearchField.purs:4:1

  4  import Prelude
     ^^^^^^^^^^^^^^
  
  Shadowed definitions are in scope for value div from the following open imports:
  
    import Prelude
  
  These will be ignored and the declaration from Reactix.DOM.HTML will be used.

These point to the same line in the same file.

I actually got 35 of them for this line rather than 2, so I presume it's something about use site rather than definition site.

@hdgarrood
Copy link
Contributor

Can you please include a minimal reproducing example?

@jjl
Copy link
Author

jjl commented Nov 28, 2019

I've spent about 20m trying to reproduce it on a smaller test case but I haven't succeeded.

I don't want to give you nothing, but all I can offer is that this branch is the one i experienced it on. There's a compile error too, but I started going through the warnings before fixing that since the number of them seemed excessive (it was from warning 165 when i built it - is this deterministic?)

Purescript 0.13.5

@garyb
Copy link
Member

garyb commented Dec 7, 2019

Maybe this is related to purescript-psa rather than purs itself? (The warnings here are being printed psa style). Perhaps --stash doing something weird.

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

No branches or pull requests

3 participants