On Fri, Aug 25, 2023 at 1:55 PM محمد بومنذر
wrote:
>
> It's actually plain text but copied right from my editor with the theme
> styles, I'll use the playground for future examples.
Thanks. Then I guess my request is to paste as plain text without styles.
Ian
> Thank you for clarifying.
It's actually plain text but copied right from my editor with the theme
styles, I'll use the playground for future examples.
Thank you for clarifying. I do see how the compiled version will need to be
repetitive, although as you mentioned this piece of code is not a common
case.
في Friday,
On Fri, Aug 25, 2023 at 7:43 AM محمد بومنذر
wrote:
>
> I'm writing a parser based on Go's `encoding/xml`, I tried to use the
> following pattern but it was deemed invalid:
>
> ```
> To me, it'd make sense if it was allowed since both types are structs and
> both of them share the field
Yes, as Luke Crook mentioned I think those requirements are more ALM
functionality than IDE functionality.
Generally, ALM addresses concerns broader than individual concerns whereas
IDEs are more focused on individual productivity.
Just my opinion, but I would expect you'd be better off
==?
On Friday, August 25, 2023 at 4:44:02 PM UTC+2 محمد بومنذر wrote:
> Greetings everyone,
>
> I'm writing a parser based on Go's `encoding/xml`, I tried to use the
> following pattern but it was deemed invalid:
>
> ```
> switch tok := p.tok.(type) {
> case xml.StartElement, xml.EndElement:
>
When I run 'go get github.com/user/packge' I get a TLS Handshake :
go: module github.com/user/package: Get
"https://proxy.golang.org/github.com/user/package/@v/list": net/http: TLS
handshake timeout
So I set GOPROXY=direct
Now I get
go: downloading github.com/user/package v0.5.0
go:
Greetings everyone,
I'm writing a parser based on Go's `encoding/xml`, I tried to use the
following pattern but it was deemed invalid:
```
switch tok := p.tok.(type) {
case xml.StartElement, xml.EndElement:
tok.Name.Local == "types"
}
```
To me, it'd make sense if it was allowed since both
Not sure if it's a good idea, but you could put them in a separate Go
module and only import that from tests. That way they *should* not get
downloaded when the module is only imported as a dependency. I think. OTOH
you'd have to use `go:embed` to export them, which means every `go test`
has to
You're right, thanks.
Do you have any simple solution for this (beside deleting those files)?
Putting such files in a git submodule or git-LFS seems appropriate but
complex.
Axel Wagner a következőt írta (2023. augusztus 25., péntek, 10:08:47 UTC+2):
> ISTM that's because they include a lot
ISTM that's because they include a lot of PDFs for samples and test data in
their repository now:
https://github.com/pdfcpu/pdfcpu/tree/master/pkg/samples (245 MB)
https://github.com/pdfcpu/pdfcpu/tree/master/pkg/testdata (77 MB)
This isn't due to the module mirror doing anything weird, it's just
go get github.com/pdfcpu/pdfcpu@v0.5.0 hung, so I've investigated:
$ go get -x github.com/pdfcpu/pdfcpu/pkg/api@latest
# get http://proxy.golang.org/github.com/@v/list
# get http://proxy.golang.org/github.com/pdfcpu/pdfcpu/@v/list
# get
11 matches
Mail list logo
