Inconsistent type in golang, cannot use <Type> as <Type>

Question

I am writing an application in Go that uses a Logger object type.
In it I use another application that uses the same logger object type:
App1:

import "gitlab.sio.com/go/zlog"

var logger = zlog.New(append(opts,
    zlog.App(c.Name, typ, version),
    zlog.Env(c.Environment),
)...)
....
router.GET("/get", GetHandler(logger))
....
func GetHandler(logger *zlog.Logger){
    ....
    mdl, _ := security.New(*logger)
    ....
}

App2(security.New from security lib):

package security

import "gitlab.sio.com/go/zlog"

Middleware struct {
    log             zlog.Logger
}

func New(log zlog.Logger){
...
mdw := Middleware{}
mdw.log = log
}

The error what I'm getting at line

mdl, _ := security.New(*logger)

is:

cannot use *logger (type "gitlab.sio.com/go/furtif/vendor/gitlab.sio.com/go/zlog".Logger) as type "gitlab.sio.com/go/security/vendor/gitlab.sio.com/go/zlog".Logger in argument to security.New

Read the message carefully: These are different types. One is from package .../furtif/vendor..., the other from .../security/vendor/.... Fix your vendoring. — Volker
– Volker, Commented Aug 16, 2017 at 7:25

Gokul Raj Kumar · Accepted Answer · 2018-08-28 12:40:50Z

3

The issue is due to the same library imported in two different vendor folders. If you are trying to use the application 2 only as a library, removing the vendor folder in the application 2 will solve this issue.

answered Aug 28, 2018 at 12:40

Gokul Raj Kumar

3632 silver badges9 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

dlsniper · Accepted Answer · 2017-08-16 07:29:45Z

1

You need to fix your import statements to properly point the import types from where they should belong to. Read the error message.

answered Aug 16, 2017 at 7:29

dlsniper

7,6021 gold badge40 silver badges46 bronze badges

1 Comment

Adrian Over a year ago

It's not the import statements at issue. It's that there are two separately-vendored copies of the same library in the GOPATH - seems like they've imported a library that uses vendoring which is, as always, a Bad Thing™.

ozzieisaacs · Accepted Answer · 2018-10-31 15:34:38Z

-1

This error happened to me because I had a type declared more than once across the same package.

answered Oct 31, 2018 at 15:34

ozzieisaacs

8532 gold badges12 silver badges23 bronze badges

Collectives™ on Stack Overflow

Inconsistent type in golang, cannot use <Type> as <Type>

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related