Earlier quoted context omitted.
It's not a bad thing to realize that one can be wrong and then strive for change.
There’s a fine line between being willing to change your mind and getting the basics wrong. Go has repeatedly gotten the basics wrong.
Go: Support for Generic Methods
21–30 of 288 posts
Re: Go: Support for Generic Methods
#22Re: Go: Support for Generic Methods
#23Earlier quoted context omitted.
Scheme is (or at least was) coherent. You don't need to look any further than set/setf/setq to see that Common Lisp is "organically grown" from the fertilizer of a committee. CL does its best to make every other lisp more attractive.
Which Scheme are we talking about? R5RS? R7RS-small? R6RS? With SRFIs? Without? Which scheme? Is it `(library...)` or `(define-module...)`?
Re: Go: Support for Generic Methods
#24slowly implementing all the things they said we didn't need
It's not a bad thing to realize that one can be wrong and then strive for change.
Re: Go: Support for Generic Methods
#25Earlier quoted context omitted.
There’s a fine line between being willing to change your mind and getting the basics wrong. Go has repeatedly gotten the basics wrong.
Declaring a highly successful language as having the basics wrong means that you are not correct about the basics that were needed.
Re: Go: Support for Generic Methods
#26This is great. Will be useful for data access methods! As for the detractors, from the first generics proposal this was called out as a "not now", not never. There were questions of implementation. They aren't a super large team, and they try to do things incrementally and do them well.
Re: Go: Support for Generic Methods
#27Re: Go: Support for Generic Methods
#28Earlier quoted context omitted.
There’s a fine line between being willing to change your mind and getting the basics wrong. Go has repeatedly gotten the basics wrong.
Declaring a highly successful language as having the basics wrong means that you are not correct about the basics that were needed.
If it came out of anywhere else, it might have struggled even to hit the homepage here.
Re: Go: Support for Generic Methods
#29Earlier quoted context omitted.
There’s a fine line between being willing to change your mind and getting the basics wrong. Go has repeatedly gotten the basics wrong.
Declaring a highly successful language as having the basics wrong means that you are not correct about the basics that were needed.
A good example of where they're kind of stuck is date formatting - it's stupid, unclear, and likely a mistake, but it's not a fundamental flaw; it's just a quirk.
Re: Go: Support for Generic Methods
#30Earlier quoted context omitted.
So which language had it right from the start? is there a language that has a very low rewrite status?
I'd particularly like examples of statically typed languages that "got it right" (since I love me my types)