Grokbase
›
Users
›
Henry-Adi-Sumarto
FAQ
Groups
Users
Badges
Henry-Adi-Sumarto
name
Henry-Adi-Sumarto
seen
Jun 17, 2016
since
Apr 28, 2015
112
posts
1
group
1
badge
1 group
golang-nuts
(112)
in
go
112 posts
Jun 2016
[go-nuts] Testing best practice: passing and failing test
Jun 2016
Re: [go-nuts] A question about passing arguments to closure
Jun 2016
[go-nuts] Re: golang strange behaviour
Jun 2016
[go-nuts] Re: golang strange behaviour
Jun 2016
Re: [go-nuts] Destructor/Finalizer pattern?
Jun 2016
[go-nuts] Destructor/Finalizer pattern?
May 2016
[go-nuts] Re: Nil Safety in Go
May 2016
Re: [go-nuts] Cover report in multiple packages
May 2016
Re: [go-nuts] Re: some thinkings in golang
May 2016
Re: [go-nuts] some thinkings in golang
May 2016
[go-nuts] Re: Which is better to develop by ourself or to use existing package as suitable design pattern on product
May 2016
Re: [go-nuts] Re: Minimal interfaces, and fallback implementations
May 2016
Re: [go-nuts] Go has caught up Rust in the number of github stars
Apr 2016
Re: [go-nuts] Re: [golang-dev] some thoughts on Go's simplicity
Apr 2016
[go-nuts] Re: [golang-dev] some thoughts on Go's simplicity
Apr 2016
Re: [go-nuts] Stumped with a classic 'inheritance' problem.
Apr 2016
Re: [go-nuts] Stumped with a classic 'inheritance' problem.
Apr 2016
[go-nuts] Stumped with a classic 'inheritance' problem.
Mar 2016
[go-nuts] Re: SOLID Design Patterns in GO
Mar 2016
[go-nuts] Efficient functional programming?
Mar 2016
[go-nuts] Re: New idea about error handling. Would really like your opinions.
Mar 2016
[go-nuts] I am Biginner But I have Error import cycle not allowed in Hello word program
Feb 2016
[go-nuts] Re: What is the best way to avoid such bugs related to slice capacity
Feb 2016
[go-nuts] Re: Thoughts on Go's Interface Improvement
Feb 2016
[go-nuts] Re: Thoughts on Go's Interface Improvement
Feb 2016
[go-nuts] Thoughts on Go's Interface Improvement
Feb 2016
[go-nuts] Re: interface in implementation package or caller
Feb 2016
[go-nuts] interface in implementation package or caller
Jan 2016
[go-nuts] Re: A Little Design Issue
Jan 2016
Re: [go-nuts] Re: A Little Design Issue
Jan 2016
[go-nuts] Re: A Little Design Issue
Jan 2016
[go-nuts] A Little Design Issue
Jan 2016
Re: [go-nuts] Re: Go proverbs
Jan 2016
[go-nuts] Re: Why Go is not OOP
Dec 2015
[go-nuts] Error handling - idea
Dec 2015
[go-nuts] How do you navigate in your $GOPATH/src?
Nov 2015
Re: [go-nuts] Strange behavior explanation?
Nov 2015
[go-nuts] Strange behavior explanation?
Nov 2015
[go-nuts] Want a tool to do static analysis of Go code
Oct 2015
[go-nuts] Inline error handling
Oct 2015
[go-nuts] Re: Remarks from a number-cruncher using Go, and a request
Oct 2015
[go-nuts] Appropriate Programming Paradigm for Go
Sep 2015
Re: [go-nuts] Re: New language based on Go
Sep 2015
Re: [go-nuts] Re: Good Cyclomatic Complexity Number for Go
Sep 2015
Re: [go-nuts] Re: Good Cyclomatic Complexity Number for Go
Sep 2015
Re: [go-nuts] Re: Good Cyclomatic Complexity Number for Go
Sep 2015
[go-nuts] Re: Good Cyclomatic Complexity Number for Go
Sep 2015
[go-nuts] Re: Good Cyclomatic Complexity Number for Go
Sep 2015
[go-nuts] Good Cyclomatic Complexity Number for Go
Sep 2015
Re: [go-nuts] Re: [golang-dev] Performance of Go code Vs C/C++/Java code
1
2
3
next ›