Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
x/playground: support txtar input files #32040
(Pulling out of related third-party imports bug #31944)
This is a tracking bug to support multiple input files.
We'll start with txtar format, and use txtar behind the scenes when saving shared snippets. But we might add web UI to have separate
Have you considered a behavior where the first file doesn't need to specify the
The txtar archive comment, if present, becomes
Or, a more important/common situation if as I understand correctly that future shared snippets (that import third-party packages?) will have a go.mod file automatically appended:
The motivation is similar to how v1 of modules doesn't require a
The advantage of the current requirement of first header is that it's more visible when txtar is used or not used.
referenced this issue
May 15, 2019
@ianthehat, I plan to add that, but doing it with the nacl backend would involve doing some wasted work, as I'd need to do the whole zip thing that we do for tests now with misc/nacl/mkzip.go and make some syscall changes to shove it in.
I'd rather do it once we've moved the playground to linux/amd64, and then just write the files to "disk" (tmpfs) and access them directly.