Re: [go-nuts] mutex in slog/handler.go?

The mutex field of the common handler struct became a pointer-to-mutex at some point IIRC - it is currently, so copying should be fine. Get Outlook for iOS From: golang-nuts@googlegroups.com on behalf of Eli Lindsey Sent: Friday, May 24,

Re: [go-nuts] tuples! tuples! tuples!

F[In (... any), Out (... any)](f func(In) Out)` multiple variadic tuple constraints On Tuesday, April 30, 2024 at 8:12:09 AM UTC-7 roger peppe wrote: > On Mon, 29 Apr 2024 at 22:06, Andrew Harris wrote: > >> 2. On implementation, before considering variadic tuple constraints: There

Re: [go-nuts] tuples! tuples! tuples!

ng conviction on that pedantry...) On Monday, April 29, 2024 at 2:24:46 AM UTC-7 roger peppe wrote: > On Sun, 28 Apr 2024 at 12:10, Andrew Harris wrote: > >> Bouncing out from some recent discussions on the github issue tracker, it >> seems like there's some interest in tuples in G

Re: [go-nuts] tuples! tuples! tuples!

es would be no clearer if the > members of the pair were named or not. > > I think this kind of situation occurs most often in generic code, > which is why perhaps this might be an OK time to add tuples > to Go. > > cheers, > rog. > > (†) named parameters in the fu

[go-nuts] tuples! tuples! tuples!

Bouncing out from some recent discussions on the github issue tracker, it seems like there's some interest in tuples in Go. I thought the discussion in #66651 led to some interesting ideas, but it's also beginning to drift. Maybe this is a better place to brain-dump some ideas. (This could be a

[go-nuts] Does building with an older golang use package sources from that older version?

Say I install golang 1.20.12 and go clean -cache and go clean -modcache. Then I build. Will that executable be using crypto/tls and other packages "as they were in 1.20.12"? Or is golang fetching the newest available compatible sources, and therefore I may be spinning my wheels trying to see

[go-nuts] Re: TLS negotiation bug in go1.21.4?

I tried go1.21.6 and see the same behavior. I'm going to try to backport the project to go1.18 to see what happens. On Wednesday, January 10, 2024 at 3:51:16 PM UTC-8 Andrew Athan wrote: > As you can see in the below output from pprof, the golang TLS > implementation seems to be in som

[go-nuts] TLS negotiation bug in go1.21.4?

As you can see in the below output from pprof, the golang TLS implementation seems to be in some kind of tight loop in crypto/internal/bigmod.addMulVVW2048 causing CPU starvation, wherein the net.HTTP server stops calling my request handler. Eventually the TLS handshakes fail, and the

[go-nuts] Re: Go 1.22 Release Candidate 1 is released

There was some discussion on the GitHub issue(s) that the trailing outer bool is perhaps not adding much in actual usage, shortly after the experiment document. Signatures changed to drop the outer bool, and appearances in docs are vestigial. Of the trailing inner, outer booleans: The inner

Re: [go-nuts] Low memory utilization when using soft memory limit with GOGC=off

Might be worth looking into GOMEMLIMIT. From: golang-nuts@googlegroups.com on behalf of Zhihui Jiang Sent: Monday, December 4, 2023 10:05:52 PM To: golang-nuts Subject: [go-nuts] Low memory utilization when using soft memory limit with GOGC=off Hi there, We

[go-nuts] Help understanding slices, variable arguments, and passing slices to functions

. And what the best approach to take for my situation would be, whereby I am using a temporary buffer slice that is cleared after each iteration for storing data to then pass somewhere else. - Andrew -- You received this message because you are subscribed to the Google Groups "golang-nuts&q

Re: [go-nuts] Re: [slog] customize defaultHandler

Piping JSON output through jq is worth exploring. This much is enough to be nicer to human eyes: cat log.json | jq -c 'del(.time)' There's a nice Go implementation at https://github.com/itchyny/gojq. On Tuesday, August 29, 2023 at 12:59:55 AM UTC-7 Marcello H wrote: > After playing with it

[go-nuts] Re: From which programming language did the idea for Golang's interface mechanism design originate?

The comments on Go Data Structures: Interfaces mention Emerald , maybe this is what you were thinking of? On Thursday, August 24, 2023 at 8:42:43 PM UTC-7 xie cui wrote: > I remembe someone in a video in

Re: [go-nuts] How to be a good slog module?

I've found implementing LogValuer can be a useful approach as well. Depending on the package, it can be enough to suggest a package doesn't need to be doing any logging, and if refactoring code from unstructured to structured logging it's useful in any case. On Wednesday, August 23, 2023 at

Re: [go-nuts] Best IDE for GO ?

The kinds of skills and knowledge covered by https://missing.csail.mit.edu are important and hard to gain from an IDE. I think that's the badge of competence earned here. On Saturday, August 19, 2023 at 11:21:44 AM UTC-7 Robert Engels wrote: The power of IDEs is the ease of refactoring and

Re: [go-nuts] call for data on HTTP routing

I wanted to make a quick observation w/r/t Ian's suggestion of not registering ambiguous patterns. The tradeoff isn't ultimately about what behaviors can be associated with what routes, but around what is required to register routes. To intentionally use the kinds of routes we'd interpret as

Re: [go-nuts] Idiomatic distribute-process-collect pattern

Klausmann wrote: > Hi! > > First off, thanks both Ian and Andrew! > > On Sat, 20 May 2023, Ian Lance Taylor wrote: > > On Sat, May 20, 2023 at 1:23 AM Tobias Klausmann > > wrote: > > > What I wonder about is the collection stage: the assumption that there &

Re: [go-nuts] Idiomatic distribute-process-collect pattern

For aggregating results, an alternative to blocking on outstanding payloads is blocking on outstanding workers. You might find this talk interesting, and it has a pretty clever solution for "outstanding workers":

Re: [go-nuts] interpreting runtime.Stack()

This stack trace was indeed a contexts with very deep parenthood. On Friday, May 12, 2023 at 8:34:40 AM UTC-7 Andrew Athan wrote: > Alex: > > I’ll see how/if this can happen. Among other strangeness in this stack is > that Err() doesn’t take a param but I guess it may b

Re: [go-nuts] interpreting runtime.Stack()

ext was `nil` or otherwise invalid, that would explain why the panic happens. Though I'm not sure how that would happen, unless you use `unsafe` somewhere.On Fri, May 12, 2023 at 5:03 AM Andrew Athan <andrew...@gmail.com> wrote:goroutine 1299607 [runnable]:context.(*valueCtx).Err(0xc00a52c3c0?)

[go-nuts] interpreting runtime.Stack()

goroutine 1299607 [runnable]: context.(*valueCtx).Err(0xc00a52c3c0?) :1 +0x3e context.(*valueCtx).Err(0x48860a?) :1 +0x2a ... repeats many many many times ... ...additional frames elided... created by one_of_my_functions() somefile.go:2092 +0x4a5 What is going on here? is this likely to be

[go-nuts] http.Server ConnState behavior question

I could go read the source code so thanks in advance for saving me that step. Part of the reason I"m writing here is to also understand the recommended pattern... Does StateActive imply the handler function will definitely be called, or can this state occur without the Handler ever being

Re: [go-nuts] Interesting "select" examples

I was surprised looking through old code that I didn't have much in the way of "interesting, non-trivial" selects - in every case where I remember doing something interesting through a select statement, later versions had moved to less interesting selects, more interesting messages from

Re: [go-nuts] "go test": common prefix for errors

I'm not sure I completely grasp the use case here in detail, but FWIW, I explored collation of log lines per-test with https://pkg.go.dev/golang.org/x/exp/slog a while ago and ended up with a struct that implements both testing.TB and slog.Handler. The idea was: (1) testing.TB methods that

[go-nuts] Re: tls panic inside /usr/local/go/src/crypto/tls/conn.go

conn.Close() } ??? I'll install golang 1.20 and see if the code has been improved and/or will submit a PR On Friday, February 10, 2023 at 2:25:53 PM UTC-8 Andrew Athan wrote: > Sorry, I meant to mention this is go 1.19 > > On Friday, February 10, 2023 at 2:24:39 PM UTC-8 Andrew Athan wrote

[go-nuts] Re: tls panic inside /usr/local/go/src/crypto/tls/conn.go

Sorry, I meant to mention this is go 1.19 On Friday, February 10, 2023 at 2:24:39 PM UTC-8 Andrew Athan wrote: > panic: runtime error: invalid memory address or nil pointer dereference > [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x5d073c] > goroutine 4133611

[go-nuts] tls panic inside /usr/local/go/src/crypto/tls/conn.go

panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x5d073c] goroutine 4133611 [running]: crypto/tls.(*Conn).handshakeContext.func2() /usr/local/go/src/crypto/tls/conn.go:1441 +0xbc created by

Re: [go-nuts] %v display of nil map

rgue that the unadorned %v documentation should mention that nil values are folded into the "empty" representation. Anyway, as time allows I'll find the doc source and submit PRs implementing the above suggestions. Thank you for pointing this solution out. Andrew On Wed, Jan 25, 2023 at

[go-nuts] %v display of nil map

I'm sure I'm not the first to say this, but here's my +1: It seems wrong to me that golang displays nil-valued reference types as an empty instance of the type with no indication that the reference is nil. E.g. ``` var m map[string]string fmt.Printf("%+v",m) ``` displays as "map[]" I think it

Re: [go-nuts] Go 1.19 comparison of variables of generic type

Ian: Thanks. The example I posted is a silly uber short simplification of my usecase. In fact, have a complex struct with a large set of methods and only one of the methods requires comparable types; it'd be nice to not have to constrain to comparable at the struct level, and only have actual

Re: [go-nuts] Go 1.19 comparison of variables of generic type

through declarative hoops to make that happen. A. On Wednesday, January 18, 2023 at 4:59:51 PM UTC-8 bse...@computer.org wrote: > On Wed, Jan 18, 2023 at 5:52 PM Andrew Athan wrote: > >> (Possibly related to issues such as those discussed in >> https://groups.google.com/g/go

Re: [go-nuts] Go 1.19 comparison of variables of generic type

ssage so confusing. v==v, after all, involves two variables of the exact same type by definition :) A. On Wednesday, January 18, 2023 at 4:59:51 PM UTC-8 bse...@computer.org wrote: > On Wed, Jan 18, 2023 at 5:52 PM Andrew Athan wrote: > >> (Possibly related to issues such as th

[go-nuts] Go 1.19 comparison of variables of generic type

(Possibly related to issues such as those discussed in https://groups.google.com/g/golang-nuts/c/pO2sclKEoQs/m/5JYjveKgCQAJ ?) If I do: ``` func Foo[V any](v V)bool { return v==v } ``` golang 1.19 reports: ``` invalid operation: v == v (incomparable types in type set) ``` There are two

[go-nuts] Unmarshal variable JSON structures

use of JSON decoding and have seen both my above ideas, as well as just entirely custom Unmarshaller implementations. Hopefully it doesn't come to that. Cheers, Andrew -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe

Re: [go-nuts] Context cancellation: Is it sufficient to make long-running things interruptible?

The precise ordering of things is a bit non-deterministic at the fringe. If precise ordering really matters (maybe for cancelling a stream like this, it doesn’t, sometimes it does), a default case in the select statement is really useful, and it also matters what DoSomething does.

[go-nuts] Re: Why this simple sorting code doesn't work?

ort, or probably there are other variations that don't require reimplementing sorting. On Tuesday, December 6, 2022 at 7:47:04 PM UTC-8 Andrew Harris wrote: > Just as an intuitive argument, we could do: > sort.Slice(s, func(i, j int) bool { log.Println(i, j); return i > j }) > > The appe

[go-nuts] Re: Why this simple sorting code doesn't work?

Just as an intuitive argument, we could do: sort.Slice(s, func(i, j int) bool { log.Println(i, j); return i > j }) The appearances of i and j per step recapitulate the logic of the sorting algo in some weak sense; not slice order On Tuesday, December 6, 2022 at 7:28:39 PM UTC-8 hey...@gmail.com

[go-nuts] Re: Why this simple sorting code doesn't work?

Oh, to reverse by index ... I think this doesn't quite fit in the idea of sorts defined by an ordering function purely dependent on the value of the element. I think there may have been a feature request for a `slices.Reverse` function in

[go-nuts] Re: Why this simple sorting code doesn't work?

Subtly: return s[i] > s[j] Is the right sort func I think it'd be recommended to look at the generics slices package, which also has a sort On Tuesday, December 6, 2022 at 6:39:29 PM UTC-8 hey...@gmail.com wrote: > Hi, > > I have this very simple sorting code: > > s := make([]int, 0,

Re: [go-nuts] Golang 1.19+ preemption model on a preemptive linux kernel?

involved are inlined, etc... On Monday, December 5, 2022 at 3:18:09 PM UTC-8 Andrew Athan wrote: > The statement I made is actually a bit stronger than the one you > confirmed: Even if the goroutines are using atomic load/store, the > preemtive nature of the os threads could easily inte

Re: [go-nuts] Golang 1.19+ preemption model on a preemptive linux kernel?

about same here: https://github.com/alphadose/haxmap/issues/26 (I ran across haxmap while reviewing issues in the golang repo relative to sync.Map) On Monday, December 5, 2022 at 10:45:10 AM UTC-8 Ian Lance Taylor wrote: > On Mon, Dec 5, 2022 at 10:03 AM Andrew Athan wrote: > > >

[go-nuts] Golang 1.19+ preemption model on a preemptive linux kernel?

I'm having trouble finding definitive information about golang's preemption model when running with GOMAXPROCS>1 on a multi-core Intel with preemtive linux kernel. As I understand it, in such a scenario, two goroutines may be scheduled by the go runtime onto two separate system threads on two

Re: [go-nuts] vendors and modules

53:13 PM UTC-8 Ian Lance Taylor wrote: > On Thu, Dec 1, 2022 at 3:23 PM Andrew Athan wrote: > > > > I am new to go devops (but not to the language). First, I must say, the > go module documentation is thorough but absolutely inscrutable for new > users. Googling for things like

Re: [go-nuts] Performance for concurrent requests

I wonder a bit about io.ReadAll versus constructing a JSON Decoder. In general, though, using pprof is the best way to start to break down a question like this. Would the actual workload involve more structured JSON, or more computation with decoded values? On Friday, December 2, 2022 at

[go-nuts] vendors and modules

I am new to go devops (but not to the language). First, I must say, the go module documentation is thorough but absolutely inscrutable for new users. Googling for things like "golang add github module vendor" brings up what appear to be either outdated or incorrect cookbooks. I've already

Re: [go-nuts] Method chaining in multiple lines

Period should be at the end of lines Call(). Chain(). Done() Get Outlook for iOS From: golang-nuts@googlegroups.com on behalf of Denis P Sent: Thursday, November 24, 2022 11:45:54 AM To: golang-nuts Subject: [go-nuts] Method chaining

Re: [go-nuts] Re: How to High-pass filter method for well height data

You might not need FFT for this problem, although it's a powerful tool that would work The minimal LP/HP filter is very little code, https://ccrma.stanford.edu/~jos/filters/Definition_Simplest_Low_Pass.html From: golang-nuts@googlegroups.com on behalf of

Re: [go-nuts] Re: is this a bug in "go fmt"?

I think the result of the proposal explains some rewriting in .go files, at least. I believe the conventional wisdom/best practices here are: - Use separate, parallel files to hold platform- (or tag-) specific code, e.g: init_darwin.go, init_linux.go, init_windows.go - Prefer setting

Re: [go-nuts] Re: is this a bug in "go fmt"?

Is this relevant? https://github.com/golang/go/issues/41184 On Friday, November 11, 2022 at 1:16:02 PM UTC-8 se...@liao.dev wrote: > You'll need to provide more info if you want to report a bug: > > ``` > main » cat main.go > // +build production > // +build linux > > package main > >

Re: [go-nuts] Re: Error Handling Question

> In many cases, including in the standard libraries, there are functions that return errors and then accompanying functions with names like MustFoo() that just call Foo() and panic if there's an error. At least inside the standard lib, the uses of MustXxx document why they behave the way they

Re: [go-nuts] Error Handling Question

Comparing 'panic' and 't.Fatal', they are similar in that there's no notion of recovering and making further progress, they abruptly terminate the process. Still, a wonky thing to say is that a 't.Fatal' call is completely legitimate as a form of "checked"-style error handling. It will log what

Re: [go-nuts] Struggling w/ use of a waitgroup

I think Matthew is correct about the immediate source of the deadlock - because the defer is placed too late in the body of grepFile(), the deferred decrement of the waitGroup isn't run on an os.Open() error. I had the same impression as Jan, I think there is a concern here: the condition for

Re: [go-nuts] Invalid memory address of string object

could p.Data could be nil here? On Monday, September 26, 2022 at 12:03:20 AM UTC-7 Bernd Fix wrote: > On 9/25/22 19:05, Kurtis Rader wrote: > > Insufficient information. Show us the panic > panic: runtime error: invalid memory address or nil pointer dereference > [signal SIGSEGV: segmentation

Re: [go-nuts] How to resolve error Cannot use 'struct{ width, height float64 }{2.0, 3.0}' (type struct {...}) as the type struct {...}

I believe anonymous definitions of structs here is the cause. While equivalent, each anonymous definition is a distinct type. Get Outlook for iOS From: golang-nuts@googlegroups.com on behalf of Richard Whatever Sent: Tuesday, August 30,

Re: [go-nuts] Go generics and bloating

This particular example might be hiding some benefits of having the type parameter in the method signature. The type parameter can be useful in something like: func (lhs BinaryPlusOp[T]) Eval( rhs T) T Or, for being explicit about why func (t Number[T]) Sum( []T ) T can't accept a slice of

Re: [go-nuts] About Go 1.19 memory model clarificaitons on atomic operations.

On Monday, August 15, 2022 at 9:50:17 AM UTC-7 jake...@gmail.com wrote: > On Monday, August 15, 2022 at 5:20:58 AM UTC-4 ma...@changkun.de wrote: > >> Atomic operations on a and b are two different statements. It remains >> unclear where exactly is the sentence that tries to say this: atomic >>

[go-nuts] Re: Go generics and bloating

https://planetscale.com/blog/generics-can-make-your-go-code-slower is the best breakdown I've seen of current implementation details as they hit assembly. There is a little bit of oil/water thing with interfaces and generics - they don't exactly mix, but you can cook however you like ... On

[go-nuts] Re: Small language change for additional type safety (Go2?)

Hi Marc, thanks for your comment: > The thing is, if you try to cover this for a mistake, then we can cover every mistake, right? Not at all. I think the idea is to try to catch at compile-time common mistakes, that are easily made, can be missed during testing and can have serious

[go-nuts] Small language change for additional type safety (Go2?)

Just thought I'd run this one by you... I used to often forget to specify the 2nd variable in a for-range: sum := "" for v := range []string{"1", "2", "3"} { sum += v } luckilly (or because Go is so good at type safety) this generates the error: invalid operation: sum +=

[go-nuts] Re: Using generics to solve Optional argument problem for multiple methods

There's a trivial conversion from any shared option to a flavored optionFunc[T]: type optionFunc[T any] func(*client) func reflavor[T any]( shared func(*client)) optionFunc[T] { return optionFunc[T](shared) } I'm not sure exactly where reflavoring shared -> optionFunc[T] would fit in

[go-nuts] lift - a package for generics and type lifting

Hi! Experimenting with Go generics since the 1.18 release, my best trick has been: type enum[T any] struct{} This resulting parametric type has lifted a type flavor, but can be boxed non-parametrically and still match any similarly flavored enum. Recently I tried pulling this idea into a

Re: [go-nuts] Issues with time.Time

Thanks for the feedback. I should explain that efficiency is not (currently) a problem. The thing I love about Go is that there is always a simple and obvious (and reasonably efficient) way to do things. I'm currently call time.Now().UTC() no more than a few thousand times per second and

[go-nuts] Issues with time.Time

I've discovered a few problems with time.Time but thought I better discuss here first before creating issues at https://github.com/golang/go/issues (in case I missed something obvious :). These are mainly performance issues, but there is also the serious problem that it is easy to

[go-nuts] req an HTTP scripting language

Hi all, req is an HTTP scripting language that I've been working on. The intention behind it is to provide a high-level language for quickly scraping data off of web APIs or web pages. Just recently, v1.1.0 has been released which adds support for working with cookies. Feel free to check it out

Re: [go-nuts] Structured configuration in Go

> I think there are two big advantages to making your application > consume either plain JSON or YAML configs: > 1. Everyone is familiar with them > 2. You can use a more advanced tool like cue or jsonnet to generate > them I can see why people would prefer JSON, and I think it's fine for storing

Re: [go-nuts] Structured configuration in Go

> Out of interest, have you come across CUE? > I have heard of it, but not explored it in depth. At a glance it seems too heavyweight for what I wanted. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop

[go-nuts] Structured configuration in Go

An article I wrote about a new configuration library I developed in Go for working with structured configuration. Article: https://andrewpillar.com/programming/2022/04/09/structured-configuration-in-go/ Repo: https://github.com/andrewpillar/config -- You received this message because you are

[go-nuts] Re: Go http/2 implementation is x5 less per performant than http/1.1

, Andrew On Monday, November 8, 2021 at 12:59:31 PM UTC-5 kirth...@gmail.com wrote: > http/2 implementation seems ~5x slower in bytes per seconds (when transfer > is cpu capped). > > POC: https://github.com/nspeed-app/http2issue > > I submitted an issue about this 3 months ag

Re: [go-nuts] Re: What are the options to fake SQL database for testing?

Another choice to throw into the mix is https://github.com/cockroachdb/copyist. It comes with different trade offs but if you buy into its framework, it should be much faster than running the database. On Thu, Jul 29, 2021 at 3:13 AM Brian Candler wrote: > You might also want to look at podman,

Re: [go-nuts] TestSetuidEtc fails during test execution in a container

This should be fully resolved at HEAD now. On Friday, May 14, 2021 at 10:57:22 AM UTC-7 Andrew G. Morgan wrote: > > Indeed. I neglected to heed the comment I left expressly for this purpose. > :( > > Thanks! > > Andrew > > On Friday, May 14, 2021 at 10:25:18 AM UT

Re: [go-nuts] TestSetuidEtc fails during test execution in a container

Indeed. I neglected to heed the comment I left expressly for this purpose. :( Thanks! Andrew On Friday, May 14, 2021 at 10:25:18 AM UTC-7 ksri...@gmail.com wrote: > I applied your patch in-flight from your review, > https://go-review.googlesource.com/c/go/+/319591/, > and I am see

Re: [go-nuts] TestSetuidEtc fails during test execution in a container

through the review cycle for this change (or something evolved from it). Cheers Andrew On Wednesday, May 12, 2021 at 8:27:35 PM UTC-7 ksri...@gmail.com wrote: > Yes I was wondering about that. > > Meanwhile, is there a way to exclude that test ? > > Kumar > > On Wed, May 12, 20

Re: [go-nuts] TestSetuidEtc fails during test execution in a container

to investigate and document what I find. Cheers Andrew On Wednesday, May 12, 2021 at 3:48:15 PM UTC-7 Andrew G. Morgan wrote: > OK. I've filed this bug. If we want to go this route, please assign it to > me: > > https://github.com/golang/go/issues/46145 > > > On Wednesday, May 1

Re: [go-nuts] TestSetuidEtc fails during test execution in a container

OK. I've filed this bug. If we want to go this route, please assign it to me: https://github.com/golang/go/issues/46145 On Wednesday, May 12, 2021 at 2:53:19 PM UTC-7 Ian Lance Taylor wrote: > On Wed, May 12, 2021 at 2:47 PM 'Andrew G. Morgan' via golang-nuts > wrote: > > >

Re: [go-nuts] TestSetuidEtc fails during test execution in a container

,cap_net_raw,cap_sys_chroot,cap_mknod,cap_audit_write,cap_setfcap The environment appears to be denying cap_setgid - which is why the Setgroups() call is failing. Is adjusting that environmental choice possible? Cheers Andrew On Wednesday, May 12, 2021 at 2:34:09 PM UTC-7 Ian Lance Taylor wrote

Re: [go-nuts] Transferring host's go-mod-download cache into docker container

There are a couple ways I know of that you can do this. You can vendor or copy as you mention. Another approach is to create a "build" image that contains relevant credentials and a few `go env -w` directives to set up your build environment, which you build separately and derive other

[go-nuts] unexpected fault address 0xfffffff800000019

A situation has arisen a few times lately where we've seen segfaults that have strange looking address values. Another thing that makes the situation confusing is that the memory referenced by the stack trace should have been allocated at init time. This seems to only be happening on macOS. The

Re: [go-nuts] now that the election is over can we please remove the political ad for golang.org

This conversation has not been adhering to Go’s values of being respectful and charitable with each other. I’d like to request it come to an end. Additionally, please do not make assumptions about specific members of the community and their role in things. I was

Re: [go-nuts] Go PostgreSQL? pg versus pgx

is a very good thing. Just trust it for now and raise concerns in the context of problems backed by data. When you start to have a bad time for real rather than perceived reasons, come back and let us know. -Andrew On Mon, Feb 22, 2021 at 10:09 AM Paul Förster wrote: > Hi Andrew, > > >

Re: [go-nuts] Go PostgreSQL? pg versus pgx

, especially if they are standard “x” libraries and things from the library author as is the case here. Best, Andrew On Mon, Feb 22, 2021 at 9:56 AM Paul Förster wrote: > Hi Matthew, > > > On 22. Feb, 2021, at 15:28, Matthew Holiday > wrote: > > > > From the &qu

[go-nuts] Go generic set with interesting real world applications

I am an avid user of Go who loves how it makes my life so much easier due to its amazing simplicity. I am thrilled to find that a great deal of progress has been made in adding (simple) generic types and functions to the language, which will make my life even simpler! When I discovered the

[go-nuts] Blog: Announcing the 2020 Go Developer Survey

ue was set or not internally", so that we can use plain Go type in the library. Here is a link to the problem: https://github.com/mxschmitt/playwright-go/issues/49 Thanks, Andrew -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To u

[go-nuts] "go run" vs. "go install" and $GOPATH

Hi, On my system "go run" creates ~/go and places pkg there, even though $GOPATH is set. Whereas "go install" places pkg under $GOPATH. Ideally, I would like ~/go to never be created. $ ls ~/go ls: /Users/foo/go: No such file or directory $ echo $GOPATH /Users/foo/Google

[go-nuts] Go 1.15 is released

Hello gophers, We just released Go 1.15 To find out what has changed in Go 1.15, read the release notes: https://golang.org/doc/go1.15 You can download binary and source distributions from our download page: https://golang.org/dl/ If you have Go installed already, an easy way to try go1.15 is

[go-nuts] Go 1.14.6 and Go 1.13.14 are released

Hello gophers, We have just released Go versions 1.14.6 and 1.13.14, minor point releases. View the release notes for more information: https://golang.org/doc/devel/release.html#go1.14.minor You can download binary and source distributions from the Go web site: https://golang.org/dl/

Re: [go-nuts] Block-based data structures and the Type Parameters - Draft Design

Hey Roger, Thanks for taking the time to engage with me on this. Really appreciate it! On Monday, June 22, 2020 at 6:01:46 PM UTC-4, rog wrote: > > > > On Mon, 22 Jun 2020 at 22:49, Andrew Werner > wrote: > >> >> >> On Monday, June 22, 2020 at 5:42:12 PM

Re: [go-nuts] Block-based data structures and the Type Parameters - Draft Design

On Monday, June 22, 2020 at 5:42:12 PM UTC-4, rog wrote: > > > Thanks for pointing this out. I'm cool with this approach. I'll update my >>> library to utilize it (and consider also adopting the list.List, though I >>> do like my freedom to pool list nodes). >>> >> > Personally, I'd start by

Re: [go-nuts] compiler RFE

Is there an existing tool that can generate a DOT digraph of a program's call graph? Andrew -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to g

Re: [go-nuts] Block-based data structures and the Type Parameters - Draft Design

On Monday, June 22, 2020 at 10:17:01 AM UTC-4, rog wrote: > > > > On Mon, 22 Jun 2020 at 14:59, Andrew Werner > wrote: > >> >> >> On Mon, Jun 22, 2020 at 9:45 AM roger peppe > > wrote: >> >>> >>> >>> On Mon, 22 Jun 202

Re: [go-nuts] Block-based data structures and the Type Parameters - Draft Design

On Mon, Jun 22, 2020 at 9:45 AM roger peppe wrote: > > > On Mon, 22 Jun 2020 at 14:26, Andrew Werner wrote: > >> Hey Rog, >> >> I think I sent you a private reply earlier. My bad. I now see what you're >> proposing in the first proposal think it makes a

Re: [go-nuts] Block-based data structures and the Type Parameters - Draft Design

me understand how it differs? On Monday, June 22, 2020 at 7:58:43 AM UTC-4, rog wrote: > > Thanks for the interesting use case, Andrew! > > I've experimented with a slightly different approach: > > https://go2goplay.golang.org/p/AkqzbWmpj6t > > It expects the call

[go-nuts] Re: [generics] Zero value

In order to get a zero value, does the following work today? Is it acceptable? func GenericFunc(type T)() T { return func() (t T) { return t }() } This could also just be written like below but above I was trying to demonstrate how to make a zero value within another function. func

Re: [go-nuts] Block-based data structures and the Type Parameters - Draft Design

ype [...]T } Thanks for dealing with my very long-winded way of saying that. On Sunday, June 21, 2020 at 12:35:53 PM UTC-4, David Finkel wrote: > > > > On Sat, Jun 20, 2020 at 1:22 AM Andrew Werner > wrote: > >> [The body of this email is a duplication of the README

[go-nuts] Block-based data structures and the Type Parameters - Draft Design

[The body of this email is a duplication of the README in https://github.com/ajwerner/go2dequeue/ which also contains the sample implementation] Exercise building a dequeue with the go2 Type Parameter Draft This project is an exploration with the go2go / Type Parameters - Design Draft

[go-nuts] Re: [generics] gRPC bistream quantization

:= ReadOne(*dummyStream, int, int)(nil, getStream, 13) https://go2goplay.golang.org/p/RQEyhRRQb0p Cheers, Andrew Ekstedt -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving email

[go-nuts] Subject: Go 1.14.3 and Go 1.13.11 are released

Hello gophers, We have just released Go versions 1.14.3 and 1.13.11, minor point releases. View the release notes for more information: https://golang.org/doc/devel/release.html#go1.14.minor You can download binary and source distributions from the Go web site: https://golang.org/dl/

[go-nuts] Go 1.14.2 and Go 1.13.10 are released

Hello gophers, We have just released Go versions 1.14.2 and 1.13.10, minor point releases. View the release notes for more information: https://golang.org/doc/devel/release.html#go1.14.minor You can download binary and source distributions from the Go web site: https://golang.org/dl/

[go-nuts] Re: [HIRING] Software Engineer - LLVM & Go Toolchain

Does Red Hat have internships working on the LLVM or Go toolchains? I'm an undergrad in my third year and would love to contribute to either codebase. Andrew On Thursday, January 23, 2020 at 1:46:58 AM UTC+1, Derek Parker wrote: > > The Red Hat Platform Toolchain team is looking for a So

Re: [go-nuts] Re: [Proposal] database/sql: add interface that unite DB and Tx

This may be helpful. https://godoc.org/github.com/golang-sql/sqlexp#Querier On Thu, Jan 16, 2020 at 1:09 AM Tamás Gulácsi wrote: > 2020. január 16., csütörtök 8:20:17 UTC+1 időpontban Shulhan a következőt > írta: >> >> ## Problem >> >> At some point we have a function that receive an instance

[go-nuts] macOS binaries and installer identifiers are changing

Hi folks Per golang.org/issue/35854, on macOS, we are updating our Go package identifier namespace from com.googlecode.* to org.golang.*. If your infrastructure relies on our installer having a specific identifier, you should use the new value starting with 1.13.5 and 1.12.14, which have yet to be

  1   2   3   >