X-Git-Url: https://git.lizzy.rs/?a=blobdiff_plain;f=lib%2Frsc;h=29a15e338dfc9de0c99d921819a82a3e57d13205;hb=12df6f9658de9237754629c75be82d8901a0dd0b;hp=ab3c98ba0dc6038ab0df610cfa3762a20d7c9489;hpb=20b2f7a38ef20b6ce866c515bc911f8c988b6d79;p=plan9front.git diff --git a/lib/rsc b/lib/rsc index ab3c98ba0..29a15e338 100644 --- a/lib/rsc +++ b/lib/rsc @@ -121,3 +121,116 @@ i don't look at build failures at all anymore because they are all false positiv Grumble grumble. I don't remember the last time I saw a sam-fans message. I'll fix it. +working as intended; please don't file an issue. +sure +I would love it if someone would create a well-tested emacs Go module. +Honestly it sounds like you have not written any Go programs. +I'm not convinced this needs to be in the standard library. +I haven't thought about it yet. +Don't do that. +Don't overthink this. +I don't know what you are arguing for or against. +We understand your point of view. +Thanks for letting us know. +It happened. +i do not want to support a linux/amd64p32 port right now. +No. I've answered this before. +If this isn't solved soon I think we should turn off commit access for everyone. +Very small changes can still contain very large bugs. +I don't intend to try to fix rc. +That's fine. +This is a serious mistake. +I am going to be away for the rest of the week. +At the risk of sounding pedantic, package url is not an http server. +don't worry about it. +You can't make everything faster all the time. +Thanks. +Please just wait. +I haven't logged into a real Plan 9 system in many years +I did not promise it was going to happen. +Please don't. +no. +I just did +The docs are incorrect. +Where you see a hack I see an elegant design. +For now you just have to fight the temptation. +Just for comparison, godoc is 16 MB on my laptop. +In general, for me, the answer to whether there is a problem depends on how complex the solutions are. +what's going on with freebsd-386, plan9-386, and plan9-amd64? +All our arm builders seem to have disappeared. +Please stop. +what's going on with freebsd-386, plan9-386, and plan9-amd64? +All our arm builders seem to have disappeared. +Please stop. +Yes, it is intentional. +No, please do NOT do this. +Why does http://build.golang.org/perf say 'Error: no commits'? +You're designing a tool. Stop. +Let's start with a wiki page. +This is almost certainly noise. +It's done; move on. +Thanks but no thanks. +I filed the bug that change fixed. +I will fix this. +It sounds reasonable to me. +Thanks for your patience. +LGTM (not actually looking carefully) +I'd like to disable more than just the test. +swtch.com is in the process of moving to the cloud. +Yes, there have been many ad-hoc solutions. +Sure. +That's fun. +I want to echo what Rob said. +It's just a mistake. +Yes, absolutely. I agree with you 100%. +This scenario is definitely confusing. +It's 2015. Why do terminal programs interpret 1970s escape codes instead of html? You'd think by now 'echo bold' would work. +What happened to build.golang.org? +I think I'm missing something. +The outline below is my attempt at a skeleton for a streamlined version of the proposal proposal. +I'm not trying to write the last word. +I'm sorry, but I disagree. +Nice debugging. +I'm sorry but I don't exactly understand. +Do you have evidence that this is important and that your change would help? +We're still struggling with this. My apologies. +All the CLs are reviewed, right? +Let's move on. +Sorry, but it's too late. +If I had more free time I would port C++ and Java to Plan 9 just to annoy you. +Honestly, it looks like a compiler bug. +I do understand that many people are confused. +Let's write tutorials and improve diagnostics. +Thank you for writing a 3rd party tool. +It's true that there are no plans yet, but I think it's also true that we need to start planning. +Yes, that's confusing. +Please do not spend time on this. +Maybe this is true, but I haven't seen it. +The fundamental design question here is whether the benefit outweighs the complexity being added. +Enough with the religion. Please. +It should just work. +Sorry for not replying earlier. I don't really know. +Great. +This seems OK. +Let's take our time and do it right (whatever that is). +Really we're just behind on triaging bugs. +I'll dig the code up and post it somewhere. I never made it truly usable. +Will follow up off list. +Wait a second. +I think it's always been this way. +I would wait until there's a more established pattern of a problem before introducing additional mechanisms. +How easily can you write a test? +We broke the rule, and we shouldn't have. Our bad. +ML is indeed a fantastic language for writing compilers. +We can't keep the code running indefinitely. +Have you filed a bug about this? +Thanks for letting us know. +Why? +I'm sorry you are insulted and distressed by this. ++golang-nuts bcc golang-dev +This looks pretty O(N^2) to me +If you want to discuss that proposal, please do it on the Reddit post, not here. +You said you were going to write some benchmarks. +Is anyone else having a hard time getting through all.bash on Sierra? +Please don't. +You are speaking like a compiler author instead of a user.