Re: [go-nuts] Re: [RFC] Syntactic Dissonance

2024-01-06 Thread John Pritchard
Hi, With [VAR] https://blog.merovius.de/posts/2018-06-03-why-doesnt-go-have-variance-in/ we review type diaspora into possibility space. Perhaps the assertion that the abstract operand is incapable of supporting the implications of its communication. Initially, [GST] https://github.com/syntelos/

Re: [go-nuts] Re: [RFC] Syntactic Dissonance

2024-01-06 Thread 'Brian Candler' via golang-nuts
Full explanation here: https://blog.merovius.de/posts/2018-06-03-why-doesnt-go-have-variance-in/ On Saturday 6 January 2024 at 11:55:27 UTC John Pritchard wrote: > Hi, > > Thinking about types and their conception, I could avoid the type > assertion boilerplate and rationalize the type membershi

Re: [go-nuts] Re: [RFC] Syntactic Dissonance

2024-01-06 Thread John Pritchard
Hi, Thinking about types and their conception, I could avoid the type assertion boilerplate and rationalize the type membership relationship if this code compiled. Best, John On Sat, Jan 6, 2024 at 3:21 AM Tamás Gulácsi wrote: > Where does TestObject implement the Comparable interface, esp.

[go-nuts] Re: [RFC] Syntactic Dissonance

2024-01-06 Thread Tamás Gulácsi
Where does TestObject implement the Comparable interface, esp. the Compare method? I don't see such in that rep. The implemented TestObject.Compare method has different signature: it requests a TestObject, not a Comparable interface, as your spec! This is only the first error. The second is that