Cuong Manh Le

303 posts

Cuong Manh Le

Cuong Manh Le

@cuonglm_

go func(){}()

Hanoi, Vietnam Katılım Haziran 2014
388 Takip Edilen352 Takipçiler
Cuong Manh Le
Cuong Manh Le@cuonglm_·
@zigo_101 To be fair, you could replace Golang with any other programming language, and the sentence is still true. There’re rooms for improments, though.
English
1
0
0
71
Cuong Manh Le
Cuong Manh Le@cuonglm_·
The current compiler implementation will print 0 2. However, the value of x is unspecified, only y value is guaranteed to be 2.
English
0
0
2
207
Cuong Manh Le
Cuong Manh Le@cuonglm_·
What's output of this program: package main type I interface { M() int } var x = I(S{}).M() var y = (S{}).M() var z = one() + 1 type S struct{} func (S) M() int { return z } func main() { println(x, y) } func one() int { return 1 }
English
1
1
1
1.4K
Cuong Manh Le retweetledi
Russ Cox
Russ Cox@_rsc·
Breaking my Twitter silence because @junyer has passed away, and this is the site where he was most active. I know we had at least a few followers in common. There is a public memorial page of sorts at github.com/google/re2/iss….
English
3
31
188
23.3K
zigo 101 - Zig + Go
zigo 101 - Zig + Go@zigo_101·
An inconsistency in the current official #Golang compiler. Here, g compiles, f doesn't: func main() { f(0) g(0) } func f[T byte](t T) { const S = "a" _ = S[unsafe.Sizeof(t)] } func g[T byte](t T) { const S = "a" _ = S[unsafe.Sizeof(t)+0] } github.com/golang/go/issu…
English
1
0
4
2K
Cuong Manh Le
Cuong Manh Le@cuonglm_·
@go100and1 That’s with old (buggy) inline static init implementation. The correct one (tip) must make it compile ok, raise runtime error when running.
English
1
0
0
53
zigo 101 - Zig + Go
zigo 101 - Zig + Go@zigo_101·
@cuonglm_ Your blog article says it will raise a compile-time error. Or I misundertand it?
English
1
0
0
53
zigo 101 - Zig + Go
zigo 101 - Zig + Go@zigo_101·
@cuonglm_ It looks the tip toolchain deesn't report errors for var x = f(-1) func f(x int) int { return 1 << x } Need compiler flags to enable it?
English
1
0
1
406
thaidn
thaidn@XorNinja·
Here you go: Fantastic Crypto Bugs and Where to Find Them #slide=id.g228b0426239_0_0" target="_blank" rel="nofollow noopener">docs.google.com/presentation/d… This is pretty basic, but we did find a bunch of bugs during our live demo =) Somebody afterward showed me a padding oracle bug in an important chat app, so I guess the idea works :)
L Dolfi@CrashingBrain

Thanks again for the workshop on opensource crypto @ThylaVdMerwe and organizers! Forgot to ask before leaving, will the slides be made public online? Especially the ones by @XorNinja on crypto bugs in the wild? :)

English
3
20
50
15.7K
Cuong Manh Le
Cuong Manh Le@cuonglm_·
@favadi Or shorter, perl is written once, run everywhere!
English
0
0
1
36
Diep Pham
Diep Pham@favadi·
Everything I saw developers struggle to make awk and sed works om both Linux and macOS, I gently remind them that perl is available everywhere and work the same on all platforms.
English
1
1
1
89
Diep Pham
Diep Pham@favadi·
@cuonglm_ The wisdom is hold on upgrading until .1.
English
1
0
1
45
Dan Lorenc
Dan Lorenc@lorenc_dan·
Is anyone really sure that @golang actually added generics vs. just putting them in the documentation so people would stop complaining?
English
22
13
279
66.9K