https://github.com/kevinmichaelchen/vgo-embedded-struct/blob/master/main.go

package main

import "fmt"
import "github.com/kevinmichaelchen/foo"

type A struct {
	foo.Cow
}

func main() {
	fmt.Println("vim-go")
}

https://github.com/kevinmichaelchen/foo/blob/master/foo.go

package foo

type Bar struct {
}

Cuz there is no Cow type in package foo. This has nothing to do with vgo.

@AlexRouSg Yup, my bad. Fixed it and vgo build -o woo_built_with_vgo . now works.

I was trying (unsuccessfully) to reproduce an issue in github.com/sfreiberg/gotwilio:

# works
$ go build -o woo_built_with_go .

# fails
$ vgo build -o woo_built_with_vgo .
./access_token.go:93:2: undefined: jwt.StandardClaims

Check your go.mod file, jwt.StandardClaims was added in v3.0.0.

As vgo doesn't allow using > v1 without a go.mod file present, and since there is a v1.0.0 tag. I suspect it defaults to v1.0.0. As legacy packages would use either v1.0.0 or the pseudo version v0.0.0-date-hash, since v1.0.0 is "newer" than v0.0.0 it uses that.

I feel like I've seen a issue to fix the order, but I cannot find it. So if using the latest vgo is still showing the same behavior then what you can do is either get the package maintainer of github.com/dgrijalva/jwt-go to add a go.mod file and change the import paths of github.com/sfreiberg/gotwilio to use github.com/dgrijalva/jwt-go/v3 or change your go.mod file to use the v0.0.0-date-hash syntax.

@AlexRouSg thanks, so this has nothing to do with vgo. I was just had wrong configurations.

This is what I ended up with:

require (
    github.com/dgrijalva/jwt-go v0.0.0-20180308231308-06ea1031745c
)