25% of the survey takers answered the question means 75% of the survey
takers think there is no need to and any features in the language. This is
a common mistake of SURVIVOR BIAS.
On Wednesday, December 23, 2020 at 4:49:48 AM UTC+8 Ian Lance Taylor wrote:
> On Tue, Dec 22, 2020 at 1:24 AM Mar
Try to export your struct fields.
Sent from my iPhone
On Dec 25, 2020, at 6:30 PM, Amit Saha wrote:
On Sat, 26 Dec 2020, 10:25 am Hamsa Hesham,
mailto:hamsahesha...@gmail.com>> wrote:
package main
import "encoding/json"
import "log"
import "fmt"
type book struct {
IDint
ti
On Sat, 26 Dec 2020, 10:25 am Hamsa Hesham, wrote:
> package main
> import "encoding/json"
> import "log"
> import "fmt"
>
> type book struct {
> IDint
> title string
> pubDate string
> authorstring
> genre string
> publisher string
> language st
package main
import "encoding/json"
import "log"
import "fmt"
type book struct {
IDint
title string
pubDate string
authorstring
genre string
publisher string
language string
}
func main(){
b := book{
ID:1,
title: "Standard",
pubD
On Fri, 2020-12-25 at 18:11 +0100, Martin Hanson wrote:
>
> What are you on about!? This is my second post on this list, and even
> though both are about
> generics, they are adequately different to be kept about otherwise it
> becomes a big mess.
Some mailers do not properly handle headers neces
Dnia 2020-12-25, o godz. 11:28:54
"Space A." napisał(a):
> What a ridiculous bullshit.
Please keep discussion here civilized.
This is not a proper place for name-calling and expletives.
--
Wojciech S. Czarnecki
<< ^oo^ >> OHIR-RIPE
--
You received this message because you are subscribed to
What a ridiculous bullshit.
пятница, 25 декабря 2020 г. в 19:49:26 UTC+3, Henrik Johansson:
> Ok maybe this thread has gone on too long.
> Both Java and C++ has benefited greatly from generics and most of their
> respective communities wouldn't want them gone. I am pretty sure that's
> what wi
On Dec 25, 2020, at 8:48 AM, Henrik Johansson wrote:
>
> Both Java and C++ has benefited greatly from generics and most of their
> respective communities wouldn't want them gone. I am pretty sure that's what
> will happen with Go as well. Can we leave it now before we go from
> "corruption" to
Your patience is inspiring! Thank you!
--
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 golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the
> You are repeatedly starting new threads, keeping the same subject as already
> existing ones.
> Don't do that please, if you respond to a certain topic keep the thread
> intact.
>
> That way all the conversation is in a single place.
What are you on about!? This is my second post on this lis
Ok maybe this thread has gone on too long.
Both Java and C++ has benefited greatly from generics and most of their
respective communities wouldn't want them gone. I am pretty sure that's
what will happen with Go as well. Can we leave it now before we go from
"corruption" to whatever hyperbole is ne
Yes, I agree with you. I use go for more than 3 years. The language is
simple and elegant. But generics will destroy this. Generics bring a lot of
complexity, make language seems ugly with only a few benifit. They say you
can ignore it. Infact you can not. This language is on the way of
corru
You are repeatedly starting new threads, keeping the same subject as already
existing ones.
Don't do that please, if you respond to a certain topic keep the thread intact.
That way all the conversation is in a single place.
--
You received this message because you are subscribed to the Google G
13 matches
Mail list logo
