,
9 tweets,
1 min read
Read on Twitter
Can you imagine the meltdown on the #golang github issue if append were being proposed today?
"append() seems too magical. Isn't Go supposed to be a simple language?"
"I think append should be a keyword. s = append s, x is obviously better."
"There's no reason we should use append twice on one line, so we should disallow it."
"I don't like append(), but here's a counterproposal: we'll just write 's, and also x' to append x to s. We just need to add three new keywords to the language. It seems obvious, really. I can't believe nobody has suggested this."
"I haven't read all the feedback yet, but [repeats the same dubious complaint that 30 other posters have already given, including themselves 3 days before]"
[after the core team has spent a hundred hours patiently responding to all this] "Why is the Go team ignoring input and pushing append() through?"
"append() makes code hard to read. Every time I see append(), I'll need to think think carefully about all the stuff happening under the hood."
"My team will not be using append()"
