I just ran into this myself, and wanted to note that newer, Swift 3 compatible versions of the Silver compiler now also require the _ in the first parameter position as well. Like so:
(I like to implement these interface/protocols as extensions of course - more Swift-like).
A related item I would like some feedback on is the implicit mapping of Swift/Silver Int to the underlying Java Integer. I would expect the above Int32 to be able to be replaced with ‘Int’ - the default Swift integer type, and have the Silver compiler implicitly cast it to the underlying Android ‘int’. But it does not do this. It requires using the Java-like Integer or the Swift Int32 as seen above.
Note that it does appear that the Swift ‘Bool’ is properly being implicitly cast to the Android/Java ‘boolean’. I verified this with OnSeekBarChangeListener.