Re: [go-nuts] How Does This Work?

On Sunday, 6 March 2022 at 20:40:17 UTC Kurtis Rader wrote: > On Sun, Mar 6, 2022 at 12:33 PM jlfo...@berkeley.edu > wrote: > >> Thanks for the quick reply. Let's say I wanted to pass "fileinfo" from my >> program to another function. What would I say in function's argument list >> for

[go-nuts] how to solve the go.mod conflict when 2 sub-modules point to break version of a common module

Hi team, I'm working on a new package, *demo*, which has a dependency on *a* and *b*. Both *a* and *b* are pointing to `go.opentelemetry.io/otel` *a* points to *go.opentelemetry.io/otel* v0.20.0 *b* points to *go.opentelemetry.io/otel* v0.25.0 However, the *go.opentelemetry.io/otel* introduced

[go-nuts] Re: how to solve the go.mod conflict when 2 sub-modules point to break version of a common module

Sorry to say, but *go.opentelemetry.io/otel * is a dumpster fire of API breakage and flux. I don't know other solution than modify a or b to use the same version of otel. ian.zh...@gmail.com a következőt írta (2022. március 7., hétfő, 17:49:17 UTC+1): > Hi

[go-nuts] Re: how to solve the go.mod conflict when 2 sub-modules point to break version of a common module

As a v0.x.y module, it's explicitly signaling that it may introduce incompatible changes between minor versions, as has happened here. unfortunately for you, a module can only exist at a single version within a build, so you'll have to modify your dependencies. Some time ago, OpenTelemetry

[go-nuts] Re: how to solve the go.mod conflict when 2 sub-modules point to break version of a common module

Thanks for your reply. It's sad that *a* and *b* are imported but not developed by my team I guess I will have to split my *demo* to smaller modules to make sure *a* and *b* are in a different module. I tried to have something like this, demo/ pkg/ onlya/ a.go

Re: [go-nuts] Re: Why, oh why, do people do this? Things that annoy me in Go code.

Latest interface my colleagues wrote (it's PHP) --- interface UnreceivedMasterOrdersInterface { public function getUnreceivedByProductsWarehouseAndCompany(array $productIds, int $warehouseId, int $companyId): array; } --- There is interest to switch to Go for some of the stuff we write, but I

Re: [go-nuts] Why, oh why, do people do this? Things that annoy me in Go code.

GoBOL, anyone? > On Mar 7, 2022, at 2:20 PM, Rob Pike wrote: > > It could have been > > interface > UnreceivedMasterOrdersInterfaceThatCanBeUsedToCallGetUnreceivedByProductsWarehouseAndCompany > > Seriously, though, your example isn't even on the same planet as some > of the examples I've

[go-nuts] Re: how to solve the go.mod conflict when 2 sub-modules point to break version of a common module

yup, I'm thinking split module, then one of them will leverage the other one's binary.. You are 100% right, when group them together... the top-level dependency tree will break again.. I just hope *go.opentelemetry.io/otel * will mature soon, then I can drop

Re: [go-nuts] How Does This Work?

On Sun, Mar 6, 2022 at 11:47 AM jlfo...@berkeley.edu wrote: > > Fine, but notice that "fileStat" isn't capitalized. This means this symbol > isn't > exported outside the "os" package. Yet, somehow the "fileinfo" variable is > assigned > this type. This has been answered, but I'm going to give

Re: [go-nuts] Re: Why, oh why, do people do this? Things that annoy me in Go code.

It could have been interface UnreceivedMasterOrdersInterfaceThatCanBeUsedToCallGetUnreceivedByProductsWarehouseAndCompany Seriously, though, your example isn't even on the same planet as some of the examples I've seen. (Neither is my parody.) Sympathies. -rob On Tue, Mar 8, 2022 at 7:49 AM

[go-nuts] Re: how to solve the go.mod conflict when 2 sub-modules point to break version of a common module

Splitting the uses of a/b into their own modules/repo won't work if you ultimately import them into a single module. It would be the same problem, just further down the dependency tree. On Monday, March 7, 2022 at 7:14:17 PM UTC ian.zh...@gmail.com wrote: > > Thanks for your reply. > > It's sad

[go-nuts] [ANN] Templatizer - A real templates engine to create dynamic repositories

Are you sick & tired of creating template repositories that nobody wants to use? It’s not your fault, the problem is the Git Repositories servers such as Github, Gitlab, or Bitbucket don’t provide a handy mechanism to take advantage of Template Repositories... I’m happy to announce to you that

Re: [go-nuts] Why, oh why, do people do this? Things that annoy me in Go code.

Naming things is one of the hardest things a programmer needs to do. Seriously. On Tuesday, March 8, 2022 at 6:08:09 AM UTC+7 ba...@iitbombay.org wrote: > GoBOL, anyone? > > > On Mar 7, 2022, at 2:20 PM, Rob Pike wrote: > > > > It could have been > > > > interface >