--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
These were worst than the first. Before sharing, make sure you give everybody read permission.
This looks awesome! Can't wait to try it out
--
This is great. Did a bit of playing with it and took note of a couple of things:On Wed, Sep 11, 2013 at 5:44 AM, Alan Donovan <adon...@google.com> wrote:
> [this time with working links]
>
> I'm pleased to announce the Go Oracle, a new tool built atop the static
> analysis libraries under construction in the go.tools repository
> (https://code.google.com/p/go/source/browse?repo=tools).
>
> The oracle is designed to answer, quickly and precisely, a range of
> questions about your Go program, such as "where can this dynamic call
> dispatch to?" or "who sends values on this channel?".
>
> The tool is still in a rough state, but already useful if you're the "early
> adopter" type. (I use it all the time.) The tool has only been tested on
> linux-amd64 and so far the only editor with which it is integrated is Emacs.
> It requires a recent (=tip) version of the GOROOT libraries.
>
> At this stage, the kind of feedback we're most interested in hearing is
> about the general shape of the tool: its external interfaces and how it
> should integrate with editors, IDEs and other tools and scripts. All its
> interfaces are subject to change---now is your chance to influence that.
> Reports of serious bugs are welcome too; send them directly to me.
>
> User manual
> https://docs.google.com/a/golang.org/document/d/1SLk36YRjjMgKqe490mSRzOPYEDe0Y_WQNRv-EiFYUyw/edit
>
> Design document
> https://docs.google.com/a/golang.org/document/d/1WmMHBUjQiuy15JfEnT8YBROQmEv-7K6bV-Y_K53oi5Y/edit#
>
> cheers
>
- Vast majority of unsafe pointer conversion warnings happen in
"syscall". I'd be ok just whitelisting that package.
- Byte offset is a bit tricky to work around in acme. Using byte
offsets also makes it possible to specify a range that's inside a
UTF-8 sequence, but the tool seems to handle that fine. I don't know
how convenient switching to rune offsets would be, but I'd prefer
that.
- implements mode seems to be broken when called from the command
line. It needs a position, but when I give it a dummy one, it notifies
me that it cannot find it, even if the position exists.
- freevars reports each assignment to field selector. You could clean
up the output by just reporting the value.
On 11 September 2013 08:29, Daniel Morsing <daniel....@gmail.com> wrote:- Byte offset is a bit tricky to work around in acme. Using byte
offsets also makes it possible to specify a range that's inside a
UTF-8 sequence, but the tool seems to handle that fine. I don't know
how convenient switching to rune offsets would be, but I'd prefer
that.We could easily add that as an option.
Awesome! I have a few UI suggestions
How much time do you want to put into this project going forward? I would love to develop this approach (perhaps integrated into godoc, not sure) but my powers of GUI are weak.
This is a really nice demo, and I'm impressed by how quickly you put it together.
The go oracle is a bad name , because there is a famous database named this ,
--
those googlers sure are cheeky :)
When refactoring, finding equivalent structures in the code is sometimes
helpful (go fix e.g.). How easy would it be to include the capacity to
find AST subtree matches (structure and type only) to a selection in the
rest of the project?
On Mon, Sep 16, 2013 at 4:10 AM, Andrew Gerrand <a...@golang.org> wrote:At first sight, I thought it was a database tool.
> To be honest, I've known about this project of Alan's for months and the
> coincidence never occurred to me!
2. Can we have an option to make the oracle output pane on the left or right rather than at the bottom?
--
You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golang-nuts/CwdIJZs6Tfc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.