Hello, I'm working on a project where there is a very (machine generated) large slice literal in the source tree: around 6MB. The slice is declared in a separate file, and it contains instances of an interface.
Each time I use go-guru (go-guru-referrers, for example) in emacs, it takes a while before it completes, sometimes even a minute or so. Maybe it's a bad idea to have such a large slice literal in the code. It is machine generated, and the data could also easily be fed in as a JSON or CSV file, read in during initialization. But then we will get other issues: copy this into the container where it is to be run, etc. Are there any pragmas / annotations that can be added to source files, to indicate that go-guru et al should ignore them? Best regards, David -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
