-
Notifications
You must be signed in to change notification settings - Fork 263
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
Go 1.11 module support #189
Conversation
…les: import "/path/to/some/package" is now module-aware * require Go compiler >= 1.11, the first version with modules support * delete vendor/ directory, replaced by versioned dependencies in go.mod
imports/a_package.go
Outdated
|
||
import ( | ||
"github.com/cosmos72/gomacro/base/paths" | ||
i "github.com/cosmos72/gomacro/imports" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any particular reason for this import rename?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically, it's not required.
I just preferred not to import a package named "imports" from another package named "imports" too.
Maybe something like "base" or "baseimports" is clearer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It shouldn't be a concern. There's no conflict since a package never sees its own name, and this file is very small, so there's no confusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, replaced the import i "..."
with a plain import "..."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This worked for me.
import "/path/to/some/package" is now module-aware
Open for review & testing