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

ambiguous definition message not giving enough suffix to disambiguate suggestions #5359

Open
aryairani opened this issue Sep 19, 2024 · 1 comment

Comments

@aryairani
Copy link
Contributor

Describe and demonstrate the bug

Code in the scratch file references Cloud.run.withConfig. UCM thinks it's ambiguous, but the suggested names it offers are even more ambiguous. withConfig isn't defined in the scratch file, but is defined in multiple indirect dependencies.

  I couldn't figure out what Cloud.run.withConfig refers to here:
  
      9 | testMonotonicStaging = do Cloud.run.withConfig staging do submit default() do
  
  The name Cloud.run.withConfig is ambiguous. Its type should be: i -> (Unit ->{𝕖,
  Exception, Cloud} Text) -> Text
  
  I found some terms in scope that have matching names and types. Maybe you meant one
  of these:
  
  withConfig : ClientConfig -> (Unit ->{g, Cloud} a) ->{g, IO} a
  withConfig : ClientConfig -> (Unit ->{g, Cloud} a) ->{g, IO} a
  withConfig : ClientConfig -> (Unit ->{g, Cloud} a) ->{g, IO} a

Screenshots

Environment (please complete the following information):

Additional context
Add any other context about the problem here.

@aryairani aryairani added the bug label Sep 19, 2024
@aryairani
Copy link
Contributor Author

possibly related to #5357

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

No branches or pull requests

1 participant