What is the problem you are trying to solve?
Please be civil.
I think this would be a mistake.
+Go's interfaces were designed to solve particular problems.
+Go is not the product of a Whiggish development process.
+complexity is multiplicative
+i always intended to fix the problem; i never saw how.
+apologies.
+The choice cannot be explained, only understood.
+Indeed.
+i see no bug here.
+I support the idea of unrecorded talks.
+We do not accept patches
+Syntax highlighting is juvenile.
+Working as designed.
+I've written programs with twenty implementations of io.Reader inside.
+Who cares? Shut up.
+What is wrong with my analysis?
+I just want to explain something.
+I recommend in the strongest terms that you don't do this.
+Sockets are the X windows of IO interfaces.
+Ignore what I wrote.
+In other words, here's how to do it but don't do it.
+I did indeed.
+I don't understand what you mean by 'reset'.
+I am, and as far as I can tell it makes no difference whatsoever.
+Please put this silly objection to rest. It has no merit.
+Interpretations will vary.
+I think the pattern used well is perfectly acceptable in certain situations.
+Like everything that attracts scrutiny, the key point is to use the idea well: safely, clearly, correctly, and only when appropriate.
+I am not trying to be difficult, but you must understand it's not simple to address your question.
+One step at a time.
+Thanks for grinding through those.
+Hardware has stopped getting faster. Software has not stopped getting slower.
+Ah, right.
+I disagree.
+There is little meaningful difference between bad style and bad practice.
+It's come up before.
+Ah, nice. the woodpeckers are back.
+I recently got the idiotically named but otherwise very well designed, quiet, and comfortable Apple Magic Keyboard.
+It sounds like a mistake to me.
+What a lovely vacuous platitude.
+That is unhelpful.
+Reports of the death of Research are greatly exaggerated.
+There are already courses being taught in `feminist science' and the trend is sure to continue.
+Not quite.
+Please file an issue.
+I'm not convinced there is a "why" other than "that's what happens".
+Working as intended.
+Awwww. Sniff.
+The operation is not to copy but to snarf. It's called snarf because snarf is what it does. There is no design document.
+Automatically deciding what's important in a program's dependencies is not easy.
+Thanks
+Yes, one could, and that would be a stylistic decision.
+Best not to promote the bad idea.
+Nil means nothing.
+People often spend too much time worrying about the things that don't matter.
+Often the reason something was done is more important than what was done.
+I believe this is not a Go issue.
+Are you running Xcode 8.3?
+I don't think so.
+Yup.
+Code comments can be helpful with unusual situations like this.
+The key word is simple.
+If I could, I would disallow it altogether.
+I completely disagree.
+I say leave it alone.
+I wasn't speaking metaphorically.
+A nil map is like a regular map but it has nothing in it, cannot grow, and takes zero space.
+We live in a digital dark age.
projects / plan9front.git / blobdiff