Re: [go-nuts] understanding interface conversions

2022-09-23 Thread Rory Campbell-Lange
On 23/09/22, Ian Davis (m...@iandavis.com) wrote: > On Thu, 22 Sep 2022, at 11:27 PM, Rory Campbell-Lange wrote: > > I just wanted to respond to this part: > > > I suppose my question is (and forgive me if this is a terrifically naive), > > how can one negotiate the go landscape of commonly used

Re: [go-nuts] understanding interface conversions

2022-09-23 Thread Rory Campbell-Lange
On 22/09/22, burak serdar (bser...@computer.org) wrote: > On Thu, Sep 22, 2022 at 4:27 PM Rory Campbell-Lange > wrote: > > > ...I'm interested to learn how people negotiate interface > > interchangeability in their programmes as my query above showed a basic > > misunderstanding of how that

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread Kurtis Rader
On Thu, Sep 22, 2022 at 7:14 PM 'Dan Kortschak' via golang-nuts < golang-nuts@googlegroups.com> wrote: > On Thu, 2022-09-22 at 20:01 -0500, Robert Engels wrote: > > The world figured out long ago that OO and it’s principles are a > > better way to go. > > This is a very strong assertion (pun not

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread 'Dan Kortschak' via golang-nuts
On Thu, 2022-09-22 at 20:01 -0500, Robert Engels wrote: > The world figured out long ago that OO and it’s principles are a > better way to go. This is a very strong assertion (pun not intended). I heartily disagree with the claim, particularly when it comes to how OO is implemented by class-based

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread burak serdar
On Thu, Sep 22, 2022 at 7:01 PM Robert Engels wrote: > Exactly. The world figured out long ago that OO and it’s principles are a > better way to go. The fact that Go is not OO doesn’t make it bad or not > useful - but the proponents of that state doesn’t make it better. > I, for one, disagree

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread Robert Engels
As a follow up, good OO is not easy. It’s not for everyone. If you have a utility need it’s probably overkill - but so many of the discussions in this list revolve around people not understanding OO and what it provides. > On Sep 22, 2022, at 8:01 PM, Robert Engels wrote: > >  > Exactly.

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread Robert Engels
Exactly. The world figured out long ago that OO and it’s principles are a better way to go. The fact that Go is not OO doesn’t make it bad or not useful - but the proponents of that state doesn’t make it better. > On Sep 22, 2022, at 7:58 PM, burak serdar wrote: > >  > > >> On Thu, Sep

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread burak serdar
On Thu, Sep 22, 2022 at 6:30 PM Robert Engels wrote: > I would like to understand the reason to type assert but not cast? That is > an OO design flaw. > You can only type-assert an interface. With type-assertion, you are either checking if the underlying value of an interface is a specific

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread Robert Engels
I would like to understand the reason to type assert but not cast? That is an OO design flaw. > On Sep 22, 2022, at 7:24 PM, burak serdar wrote: > >  > > >> On Thu, Sep 22, 2022 at 6:08 PM Robert Engels wrote: >> 100% true. The difficulty when examining a “large” system is that it becomes

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread burak serdar
On Thu, Sep 22, 2022 at 6:08 PM Robert Engels wrote: > 100% true. The difficulty when examining a “large” system is that it > becomes very difficult to understand the relationships. Documentation can > help but it is not a great substitute for automated tools. > > In Java - actually all of OO -

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread burak serdar
On Thu, Sep 22, 2022 at 4:27 PM Rory Campbell-Lange wrote: > This email follows my email yesterday "cannot convert fs.FS zip file to > io.ReadSeeker (missing Seek)". Thanks very much to those who replied and > provided solutions. > > Following that, I'm interested to learn how people negotiate

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread Robert Engels
100% true. The difficulty when examining a “large” system is that it becomes very difficult to understand the relationships. Documentation can help but it is not a great substitute for automated tools. In Java - actually all of OO - type casting is severely frowned upon - but it seems a lot

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread Ian Davis
On Thu, 22 Sep 2022, at 11:27 PM, Rory Campbell-Lange wrote: I just wanted to respond to this part: > I suppose my question is (and forgive me if this is a terrifically > naive), how can one negotiate the go landscape of commonly used modules > to re-utilise, where possible, a more commonly

Re: [go-nuts] understanding interface conversions

2022-09-22 Thread Robert Engels
I struggle with the same in any large project. You have to hope they documented the api very well. Needless to say I’m not a fan of “duck typing”. It makes a few things easier and a lot of important things much harder. > On Sep 22, 2022, at 5:27 PM, Rory Campbell-Lange > wrote: > > This

[go-nuts] understanding interface conversions

2022-09-22 Thread Rory Campbell-Lange
This email follows my email yesterday "cannot convert fs.FS zip file to io.ReadSeeker (missing Seek)". Thanks very much to those who replied and provided solutions. Following that, I'm interested to learn how people negotiate interface interchangeability in their programmes as my query above