Frederik Z.
Frederik Z.
That would be fine with me.
I'm open to better documentation. I'm not sure if this rather small project requires a whole wiki. As a first step I would prefer improvements to the README.
I agree that they should be counted separately. If someone wants to provide a PR I will review it.
The oracle now has a new "definition" command that should be used to implement this feature: https://code.google.com/p/go/source/detail?r=4e56dc65c681338355954fd223c4472c4b41f0d5&repo=tools
Can you give me an example file where this happens and which symbol in which row/column you are trying to select?
Thanks. The problem seems to be Windows/DOS line endings (\r\n) vs. Unix line endings (\n), which results in the calculation of the wrong byte offsets. When I converted a source...
The browser loses the \r characters as soon as the source code is inserted via the .html() method: var text = '1\r\n2\r\n3\r\n4\r\n5\r\n'; text.length == 15; $('#src').html(text); $('#src').text().length == 10;
@restuwahyu13 `pkg.go.dev` doesn't have an API yet, that's why this issue is open and not closed.
The document also [explains what the problems are](https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md#No-parameterized-methods). So what are your solutions to these?
> I pushed my @ implementation in #83. It's not for review, just for discussion. It does seem to work well at least for the Ivy programs I have been...