On Thu, 25 Feb 2016, at 07:26 AM, Peter Morris wrote: > This discussion started when the need for a 'guard if' was removed because > we ensured that the object we return behaves the same in all experienced > cases. Injecting new differences to the interface would seem to be moving > away from that ideal.
It sounds as though what you’re saying is that you just don’t like duck typing. Is that a reasonable interpretation, or am I misunderstanding? For clarity, here’s how wikipedia describe duck typing: "In duck typing, a programmer is only concerned with ensuring that objects behave as demanded of them in a given context, rather than ensuring that they are of a specific class.” That’s how I think of it (“in a given context” being the key bit). -- You received this message because you are subscribed to the Google Groups "North West Ruby User Group (NWRUG)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. Visit this group at https://groups.google.com/group/nwrug-members. For more options, visit https://groups.google.com/d/optout.
