A bit of attention has been directed at slices recently, with a few high
profile blogs shining a healthy light on them (they can be traps for young
players!)
I'm a bit confused about SliceHeader as found in the reflect package
(https://github.com/golang/go/blob/master/src/reflect/value.go#L1986
On Tuesday, November 10, 2020 at 9:41:09 PM UTC+11 Jan Mercl wrote:
Thank you for taking the time to answer, I'm still a little confused and
have inlined where that confusion is below.
On Tue, Nov 10, 2020 at 11:09 AM shan...@gmail.com
> wrote:
>
> > My confusion is this,
On Tuesday, November 10, 2020 at 10:09:44 PM UTC+11
axel.wa...@googlemail.com wrote:
> On Tue, Nov 10, 2020 at 11:09 AM shan...@gmail.com
> wrote:
>
>> This seems to me to be the better solution (but it's still in the
>> pipeline?) https://github.com/golang/go
Hi all
My bot picked up that there was a release from github of Go for versions
1.16.7, and 1.15.15
But I cannot find any release notes or supporting documentation, and the
release hasn't (yet) made it to downloads
Was this an unintentional release?
--
You received this message because you
Ok lazyreader (IRC) has discovered that the release has a single commit,
relating to a CVE relating to handler panics
The changeset is
https://go-review.googlesource.com/c/go/+/338551/2/src/net/http/httputil/reverseproxy.go
On Thursday, August 5, 2021 at 8:30:23 AM UTC+10 shan...@gmail.com
-review.googlesource.com/c/go/+/338551/2/src/net/http/httputil/reverseproxy.go
On Thursday, August 5, 2021 at 8:30:23 AM UTC+10 shan...@gmail.com wrote:
>
> Hi all
>
> My bot picked up that there was a release from github of Go for versions
> 1.16.7, and 1.15.15
>
> But I cannot find any releas
This morning someone asked about dereferincing a pointer to a pointer to a
pointer
At first nobody had ever thought about, let alone knew the answer, but some
example code was shown, and sure enough ***val is possible
```
package main
import "fmt"
func main() {
a := 0
b := &a
of indirection supported when defining a function. It's a
> silly question that shows the O.P. doesn't understand how compilers work.
> Let alone how people use languages like Go in real life.
>
>
>> On Thu, Mar 10, 2022, 03:59 shan...@gmail.com wrote:
>>
>
t;curiousity" - learn to recognise it so you don't stifle it in
future.
On Thursday, March 10, 2022 at 4:29:54 PM UTC+11 Kurtis Rader wrote:
> On Wed, Mar 9, 2022 at 9:12 PM shan...@gmail.com
> wrote:
>
>> Um
>>
>> Really?
>>
>> Which of th
**p)
> }
>
>
> -rob
>
> On Thu, Mar 10, 2022 at 4:29 PM Kurtis Rader wrote:
> >
> > On Wed, Mar 9, 2022 at 9:12 PM shan...@gmail.com
> wrote:
> >>
> >> Um
> >>
> >> Really?
> >>
> >> Which of these th
g)
Yeah it's definitely above my paygrade and will take some time for me to
get my head around
On Thursday, March 10, 2022 at 8:31:58 PM UTC+11 Rob 'Commander' Pike wrote:
> On Thu, Mar 10, 2022 at 5:08 PM shan...@gmail.com
> wrote:
> >
> > Is this really ho
In the past when I wanted to 'capture' the log output so that I could check
it in a unit test I would 'hijack' os.Stdout like so
```
var osStdout = os.Stdout
func MyCode (){
log.SetOutput(osStdout)
log.Print("My dog has fleas")
}
```
Which could then be tested thus
```
func TestMyCode(t *testi
June 15, 2023 at 2:44:39 AM UTC+10 Tamás Gulácsi wrote:
> github.com/UNO-SOFT/zlog/v2
> NewT(t).SLog()
> returns an *slog.Logger that uses t.Log for printing.
>
> But maybe I don't understand your real problem.
>
> shan...@gmail.com a következőt írta (2023. június 14., sze
13 matches
Mail list logo
