go mod download is downloading all of the modules in the dependency graph, which it can determine from reading only the go.mod files. It doesn’t know which of those modules are actually needed to satisfy a build, so it doesn’t pull in the checksums for those modules (because they may not be relevant). On the … Read more
You have to declare the slice type with type parameters you want to use for the Map() (or for any other) method: type slice[E, V any] []E And you have to add the type parameters to the receiver, without the constraints (those will be the same as defined at the type declaration), as if you’d … Read more
This feature is used so that you do not receive compilation errors for unused imports from Go. You can deactivate the feature via: Settings (Preferences) > Go > Imports > Optimize imports on the fly However my recommendation is to leave this as is and instead let the IDE manage the imports for you. For … Read more
The Go 1.20 Seed documentation has a typo. Use rand.New(rand.NewSource(seed)) as described in the latest documentation and the Go 1.20 release notes. Create the random source and use methods on the source instead of calling the package functions: r := rand.New(rand.NewSource(seed)) fmt.Println(r.Uint64()) fmt.Println(r.Uint64())
Starting with Go 1.16 the go tool has support for embedding static files directly in the executable binary. You have to import the embed package, and use the //go:embed directive to mark what files you want to embed and into which variable you want to store them. 3 ways to embed a hello.txt file into … Read more
No you can’t. Go is a static typed language. The type of a variable is determined at compile time. If you want to determine dynamically the typeof an interface{} you could use type switching: var t interface{} t = functionOfSomeType() switch t := t.(type) { default: fmt.Printf(“unexpected type %T”, t) // %T prints whatever type … Read more
You can just delete it from you disk: rm -r $GOPATH/src/<PACKAGE_NAME> This will remove the package completely. Alas, there is no tool or go command for removing packages. But this should be simple enough.
No you can’t, but you could create a base type and then embed it into your 2 struct, therefore only needing an implementation for the base type: type WithString struct { str string } type First struct { WithString } type Second struct { WithString } type A interface { PrintStr() //print First.str or Second.str … Read more
What you’re experiencing is commonly known as “variable shadowing”. When you use := with any variable in an inner scope, including in statements like if and for despite the lack of braces, a new value and type are associated with that variable: n := “Example” //Prints the string variable `n` to standard output and // … Read more
Yes it’s possible however your function should return interface{} and not []*interface. func (c Helper) ReturnModels(modelName string) interface{} {} In this case you could use Type Switches and/or Type Assertions to cast the return value into it’s original type. Example Note: I’ve never used Revel, but the following snippet should give you an a general … Read more