Golang equivalent to Python's NotImplementedException

go playground
python to golang
golang python interpreter
golang slice
go vs python
golang append
golang range
go tutorial

Is there an equivalent in Golang to raising a NotImplementedException in Python when you define an interface with methods that you don't want to implement yet? Is this idiomatic Golang?

For example:

type MyInterface interface {
    Method1() bool
    Method2() bool

// Implement this interface
type Thing struct {}
func (t *Thing) Method1() bool {
    return true

func (t *Thing) Method2() bool {
    // I don't want to implement this yet

Usually in golang if you want to implement error handling you return an error

type MyInterface interface {
    Method1() bool
    Method2() (bool, error)

Then you can return an error. You can also log, or panic as @coredump said in the comments.

Python equivalent of Golang's select on channels, Go has a select statement that works on channels. From the documentation: The select statement lets a goroutine wait on multiple communication operations. A� Golang is now considered to be an alternative to Python, and there is an incessant discussion about Golang web development vs Python. And here is why. While simplicity is Python’s main advantage, there are also several downsides.

a empty var will do this

var _ MyInterface = &Thing{}

if Thing doesn't implement the interface MyInterface, compile will fail

Go for Pythonistas, Go for Pythonistas. Francesc Campoy Flores. Gopher at Google. Video. A recording of this talk is available. youtu. Related: Top 5 Websites to Learn Python Online for FREE. Golang vs. Python: Language Features. Python is an easy-to-learn language and is often used to teach programming concepts to beginners. Part of the reason is the easy syntax, which is less reliant on symbols like semicolons than other languages.

Here's an example that was generated from my implementation of gRPC in Go:

import (
    status "google.golang.org/grpc/status"

// . . .

// UnimplementedInstanceControlServer can be embedded to have forward compatible implementations.
type UnimplementedInstanceControlServer struct {

func (*UnimplementedInstanceControlServer) HealthCheck(ctx context.Context, req *empty.Empty) (*HealthCheckResult, error) {
    return nil, status.Errorf(codes.Unimplemented, "method HealthCheck not implemented")

Alternatively, you could log an error inside the method and then return a nil to satisfy the method contract.

Golang equivalent of Python's context manager, in Python I may define context managers which do stuff before and after an action A Golang equivalent I came up with is something like (see� Question: Tag: go What is the equivalent of python's chr() and ord() functions in golang?. chr(97) = 'a' ord('a') = 97 Answer: They are supported as simple

Need help with equivalent of Python dicts : golang, I'm coming to Go as a primarily Python coder, and I'm certainly not any better than intermediate at that. I have some programming experience in the … Golang vs. Python: Execution. Now, let's compare how Go code and Python code is executed. So first of all, Python is a dynamically typed language and Golang is a statically typed language. Python

How about this for a Golang version of Python's 'with' : golang, 15 votes, 31 comments. 121k members in the golang community. Ask questions and post articles about the Go programming language and related tools … Golang vs Python: Execution. Now, let’s compare how Go code and Python code is executed. So first of all, Python is a dynamically typed language and Golang is a statically typed language. Python and Go use an interpreter and a compiler respectively.

Why We Switched from Python to Go, Deciding on a programming language is always a difficult choice, learn why Stream switched from Python to Go as our language of choice. Golang can replace python as the server-side language for building concurrent services. Developers need to choose a programming language considering their nature and size of the development project. Python has plenty of libraries, tested in numerous environments to work productively.

  • Is it important if it is idiomatic? If it helps you, panic or log, that should be enough.
  • Not necessarily important, but I am still learning Go and want to understand the proper ways to use it.
  • I feel there's no correct answer to this. Interfaces are implemented implicitly, so if you created the interface in this case, then you should just modify it or separate into two separate interfaces. If you haven't, you should probably read the documentation and figure out how whatever uses the interface behaves and when would Method2 be called anyway (e.g. if it's close file and you don't have a file to close, you can just do nothing and return success). In short, highly recommend that you give more information to get a better answer.