An interesting aside about Java Interfaces that most people don't know is that you can have an empty Interface without methods or members and then declare different objects as implementing that empty interface. The purpose of this in Java is different then in Golang but it allows arbitrary instance of classes (objects) to be passed around without using Object as the class. I found this out while looking at Koopla source code and it is a handy trick for Java programmers to know. Sorry, this hint isn't really about Golang.
On Saturday, October 8, 2016 at 9:14:34 AM UTC-4, Fei Ding wrote: > > Recently I've been asked a question which is, what's the difference > between Golang and Java about *interface*? > > > I know there are some 'syntax-sugar level' differences, what I am > interested is anything beneath the ground, like how does Golang and Java > implement interface? What's the biggest difference? Which one is more > efficient? Why? > > > Could anyone post blog links or source code about this topic? The only > code I can find is in src/runtime/iface.go, but I cannot understand it or > get anything useful by myself yet. Source code is better. > > > Thanks. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
