You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've opened a PR here with tests for the functionality I would expect: #7631
Currently if there's a collision between a trait name and the name of a type which is currently in scope, there's no way to import this trait such that I can make use of the method syntax to call trait methods. Instead I have to use the function syntax for this trait which is a worse UX.
I would expect that I should be able to rename the trait during import to a non-colliding name and use it as normal.
The text was updated successfully, but these errors were encountered:
I've opened a PR here with tests for the functionality I would expect: #7631
Currently if there's a collision between a trait name and the name of a type which is currently in scope, there's no way to import this trait such that I can make use of the method syntax to call trait methods. Instead I have to use the function syntax for this trait which is a worse UX.
I would expect that I should be able to rename the trait during import to a non-colliding name and use it as normal.
The text was updated successfully, but these errors were encountered: