-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/tools/cmd/digraph: permit larger tokens in use of bufio.Scanner #57807
Comments
digraph does not look like any tool under the Go project. |
To increase the maximum token size, use the |
ok to create a CL to use is it an bad idea to change |
@ukai Are you referring to this? https://github.com/golang/tools/blob/master/cmd/digraph/digraph.go |
yes |
@seankhliao Given that digraph is part of x/tools, can you reopen this issue? |
CC @adonovan Perhaps somebody should rewrite digraph to not use |
if an input line is too long (more than bufio.MaxScanTokenSize), bufio.Scanner returns bufio.ErrToolong. Use bufio's ReadString instead. Fixes golang/go#57807
like this? golang/tools#423 |
if an input line is too long (more than bufio.MaxScanTokenSize), bufio.Scanner returns bufio.ErrToolong. Use bufio's ReadString instead. Fixes golang/go#57807
https://go-review.googlesource.com/c/tools/+/462053 merged , Is it possible to close this issue? |
ah, I think so. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
when we pass
digraph-input.txt
(not related with go tools, though), which has long lines.What did you expect to see?
shows the set of all nodes
What did you see instead?
can we have an option to specify buffer for bufio.Scanner for digraph command to handle long lines?
(or make digraph package (graph, nodeset type and digraph func) out of digraph command,
so we could use digraph functionalities in other tools?)
The text was updated successfully, but these errors were encountered: