Dmitri Shuralyov

> the workaround from https://github.com/shurcooL/vfsgen/issues/36#issuecomment-347504650 only runs if `generate.go` is in the same directory as the main package. As soon as I move it out of there I get the...

Using `go test` to piggyback some code to package `main` is a very interesting idea, one that I wasn't aware of in the past. Thanks for coming up with it....

How are you generating `vfsdata.go`? If you want your `assets` variable to be accessible outside the `template` package, you need to make it exported, i.e., `Assets`. If all you want...

Hi, thanks for raising an issue about this. I have some questions to understand this better. > There doesn't seem to be an option to turn off automatic compression of...

Some open questions remaining: 1. Small question. What to name the generated common file. I went with "vfsgencommon.go", is that okay? It should always be the same name so that...

I would like to complete the general idea started here, but it will happen no earlier than a few weeks from now, and I plan to start relying on modules...

@cryptix I expect major future development changes (such as this one) for this project will need to be rebased to consider the Go 1.16's `//go:embed` and `io/fs.FS`. So this is...

@segevfiner In module mode, `build.Import` can only be used to find Go packages, meaning the directory needs to contain at least one .go file. In your snippet: ```Go var Assets...

Thanks for sharing this scenario that you've encountered. vfsgen is a simple tool that operates on whatever arbitrary input you provide it. I'm not sure if it's viable to detect...

Thanks for reporting this. That sounds like a bug, seeking should be fully supported. I'd really like to fix it. Would it be possible for you to share some code...