-
Notifications
You must be signed in to change notification settings - Fork 8
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
cannot specify module path #215
Comments
Works for me. |
modulePath+name作为go mod init 模块名称。 |
我认为这里的行为更像go mod init 的行为会更合适,允许用户传递任何的modulePath,modulePath+name 会导致用户对于modulePath的作用产生误解,并且当用户希望package name 和 modulePath尾部的name不一致时,这个方案就会无法解决。 I think the behavior here would be more appropriate if it were similar to go mod init, allowing users to pass any modulePath. The modulePath+name approach would cause users to misunderstand the purpose of modulePath, and this solution wouldn't work when users want the package name to be different from the name at the end of the modulePath. |
By default, |
Our team uses
llcppg
to compare the user-provided llpkg with the generated result to ensure the safety of llpkg.However,
llcppg
cannot specify the module path forgo.mod
, which causes the failure of our verification process.In above examples, the module path of user-provided llpkg is
github.com/goplus/llpkg/cjson
while thellcppg
generated one iscjson
, which's not equal.The text was updated successfully, but these errors were encountered: