-
Notifications
You must be signed in to change notification settings - Fork 5
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
error comparing declarations: missing ',' in parameter list #39
Comments
The commit that triggered CI was shurcooL/notifications@5a67cc8. It includes the following code: type Router interface {
// IssueURL returns the HTML URL of the specified GitHub issue.
- IssueURL(owner, repo string, issueID uint64, commentID uint64) string
+ IssueURL(owner, repo string, issueID, commentID uint64) string
+
+ // PullRequestURL returns the HTML URL of the specified GitHub pull request.
+ PullRequestURL(owner, repo string, prID, commentID uint64) string
} Just a hunch from the error text, could it be that |
Thanks, I'll get a look at this next, gimmie a little bit as things are pretty intense at the moment.
I'd make the same hunch, but this should be supported, it was one of the main reasons I started using Line 78 in 5f916b1
But perhaps there's an edge case here. |
Seems it's broken in go1.9.0 (working in go1.8.5), didn't notice as I was running an old build. |
|
OK, tests failing were unrelated, I'll create a separate issue for that. I need to be brief (out of time) but the issue is in It does this by changing The issue is the string in this case is: package expr
type ExternalService interface{
MarkRead(ctx context.Context, appID string, repo github.com/shurcooL/notifications.RepoSpec, threadID uint64) error;
Notify(ctx context.Context, appID string, repo github.com/shurcooL/notifications.RepoSpec, threadID uint64, nr github.com/shurcooL/notifications.NotificationRequest) error;
Subscribe(ctx context.Context, appID string, repo github.com/shurcooL/notifications.RepoSpec, threadID uint64, subscribers []github.com/shurcooL/users.UserSpec) error
} Which importantly, contains import path with the type identifiers Adding the following fixes the issue. src = strings.Replace(src, "github.com/shurcooL/", "", -1) The semicolon may also be a problem, but it's been working all this time, I'd be surprised if it's an issue but should be fixed anyway. Thanks for the issue, I'll work on a fix for this. |
No problem, I'm happy if it's helpful. :) Thanks for describing what the issue appears to be, it's interesting for me to learn about. Just for extra visibility, I'll quote this from my original issue report:
|
Something jumps to me here. Where are you getting that from? That looks like a much older version of that interface. The current version of |
I had been manually bisecting older notifications commits, so I might have just noted it from an older, but still broken version. So ignore the age issue. The following definition from master is right? If so, then it must just be me noting an older interface. package expr
type ExternalService interface{
MarkRead(ctx context.Context, repo github.com/shurcooL/notifications.RepoSpec, threadType string, threadID uint64) error
Notify(ctx context.Context, repo github.com/shurcooL/notifications.RepoSpec, threadType string, threadID uint64, nr github.com/shurcooL/notifications.NotificationRequest) error
Subscribe(ctx context.Context, repo github.com/shurcooL/notifications.RepoSpec, threadType string, threadID uint64, subscribers []github.com/shurcooL/users.UserSpec) error
} |
Oh, ok, gotcha. Yeah, that’s the latest. I just wanted to make sure the original issue wasn’t caused due to version skew. |
This is not a critical issue for me; reporting it for your benefit only. You should prioritize accordingly.
I noticed the following unexpected error in GopherCI (https://gci.gopherci.io/analysis/1198) from
apicompat
:The code compiles without errors. I'm not sure what this is. It might be related to alias support (#27), but it doesn't look that way.
notifications.ExternalService
is a pretty simple interface.I can provide additional information if needed, just ask.
The text was updated successfully, but these errors were encountered: