Hello,
I would like to know if there is elegant way to json encode very long field
(with io.Reader)?
For example: (play ground https://go.dev/play/p/QxlbNMy3ERK )
```
func TestJSONStreamBytes(t *testing.T) {
type MyStruct struct {
Reader1 io.Reader `json:"field1"`
Reader2 io.R
thanks, and the playground is nice.
I think this is saying that if I want a baz and bar executable (chmod +x)
then I need the "package main" in separate folders/directories
I don't think I'm close enough to understanding this stuff to focus on
optimizing it to
the fewest possible go.mod files, b
On Fri, Dec 9, 2022 at 5:38 AM Marcello H wrote:
>
> Since we have great linters, I wonder why it seems that the Go source itself
> isn't linted?
> (Because when I do lint it, I see a lot of suggested improvement)
1) Linters are optional and opinionated, and it kind of matters which
linter you m
Since we have great linters, I wonder why it seems that the Go source
itself isn't linted?
(Because when I do lint it, I see a lot of suggested improvement)
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop r
Plus, you don't need to do a "go mod init" in each subdirectory. The
top-level directory names the module and the package within it; you can
refer to packages in subdirectories using this module name with the
subdirectory appended.
A typical layout would look like this:
(top level)
go mod ini
