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
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
The vm receiver and argument name for v53 type is unfortunate as it's used in pair with vm package. When you have vm variable in scope, one can't access vm package.
Method gets vm receiver and refers to vm package in it's arguments list.
If function body will ever need something from that package, it would be an unpleasant experience to have.
The text was updated successfully, but these errors were encountered:
quasilyte
changed the title
A lots of avoidable imported package name shadowing
Lots of avoidable imported package name shadowing
Nov 17, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
vm
receiver and argument name forv53
type is unfortunate as it's used in pair withvm
package. When you havevm
variable in scope, one can't accessvm
package.It could be OK to rename
vm
tov
, for example.Simple example of shadowing is:
Method gets
vm
receiver and refers tovm
package in it's arguments list.If function body will ever need something from that package, it would be an unpleasant experience to have.
The text was updated successfully, but these errors were encountered: