Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Please answer these questions before submitting your issue. Thanks!
Latest master 1.7.
n/a, but darwin/linux amd64.
I originally tried to use
From there I started hacking on my copy of the go 1.6 source, eventually I got a hold of the 1.7 source and found that at least all of the assets had already been upgraded (now including a polyfill for the ill-fated Object.observe).
However the future surface area fur such drift had only increased since 1.6; compare:
This is truly unfortunate since the only dynamic part of that entire "template" is a URL parameter for the XHR request to load data.
Principled separation between frontend code and server-side code.
I have a proposed change that I'm working to get into Gerrit now.
I plan to add a -trace flag to cmd/go for 1.8, and in that context, a standalone file is even more important for usability.
The bitrot vs the upstream trace viewer code is unfortunate and should be fixed. That's just something we have to maintain.
Indeed, it'd be great to have a different mode for
We could have
In case it's helpful, here's the crud I hacked together when I was last working on this (unstable url): josharian@a5a9f75. I'd love to see it done better.
I look forward to the gerrit CL. Just advance warning, we're in a code freeze, so nothing will go into the tree until it opens for 1.8 (in a few weeks, I think).