golang interface compliance compile type check

Question

I see the following statements from camlistore(http://code.google.com/p/camlistore/source/browse/pkg/cacher/cacher.go).

var (
        _ blobref.StreamingFetcher = (*CachingFetcher)(nil)
        _ blobref.SeekFetcher      = (*CachingFetcher)(nil)
        _ blobref.StreamingFetcher = (*DiskCache)(nil)
        _ blobref.SeekFetcher      = (*DiskCache)(nil)
)

I understand that no variables are created and the statements ensure compiler checks that CachingFether implements public functions of StreamingFetcher and SeekFetcher. RHS portion uses a pointer constructor syntax with a nil parameter. What does this syntax mean in Go language ?

I'm curious as to why that check is necessary. It seems to me that if they ever actually /used/ those values, the compiler would do the check? The only explanation I can think of is that they use the unsafe package, and they are going to do non-checked operations that they want the compiler to check anyway. But they don't import unsafe in that file. Any ideas? — joshlf
– joshlf, Commented Aug 1, 2013 at 15:03
It's a static (compile time) check if the RHS type satisfies the LHS interface. With such check an accidental change to the RHS method set is immediately rejected by the compiler. — zzzz
– zzzz, Commented Aug 1, 2013 at 17:43

zzzz · Accepted Answer · 2013-08-01 12:50:49Z

18

(*T)(nil) is a Conversion. In this case it stands for a typed nil, ie. the same value which, for example

var p *T

has before assigning anything to it.

The standard syntax of a conversion is T(expr), but the priority of the * would bind it wrongly in

*T(expr)

This syntax means dereferencing the return value of function T with one argument expr. That's why the conversion has an alternative syntax:

(T)(expr)

where T can of course be *U. Therefore

(*U)(expr)

is the generalized form of what you see in the Camlistore repository.

answered Aug 1, 2013 at 12:50

zzzz

92k17 gold badges184 silver badges140 bronze badges

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

Collectives™ on Stack Overflow

golang interface compliance compile type check

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related