厲害,沒(méi)點(diǎn)技術(shù)還真寫(xiě)不出來(lái),numbers[2]沒(méi)有賦值,其默認(rèn)值為0。
2016-03-30
# command-line-arguments
../345/7306/4fm0/index.go:12: syntax error: unexpected ), expecting semicolon or newline or }
../345/7306/4fm0/index.go:12: syntax error: unexpected ), expecting semicolon or newline or }
2016-03-30
mm2["scala"]=25
mm2["erlang"]=50
mm2["python"]=0
這樣寫(xiě)貌似也可以通過(guò)啊,,,如果map中已經(jīng)存在,相當(dāng)于直接覆蓋原來(lái)的對(duì)吧
mm2["erlang"]=50
mm2["python"]=0
這樣寫(xiě)貌似也可以通過(guò)啊,,,如果map中已經(jīng)存在,相當(dāng)于直接覆蓋原來(lái)的對(duì)吧
2016-03-20
會(huì) PHP、會(huì) Python、看著都感覺(jué)累,為啥一開(kāi)始跟我扯這么多概念???
2016-03-06
go func() {
var sender Sender = myChannel
sender <- number
}()
go func() {
var receiver Receiver = myChannel
fmt.Println("Received!", <-receiver)
fmt.Println("Sent!")
}()
var sender Sender = myChannel
sender <- number
}()
go func() {
var receiver Receiver = myChannel
fmt.Println("Received!", <-receiver)
fmt.Println("Sent!")
}()
2016-03-06
這道題的判題程序有問(wèn)題?
代碼應(yīng)該是沒(méi)錯(cuò)吧,當(dāng)通道長(zhǎng)為0時(shí),執(zhí)行到sender <- number時(shí)第一個(gè)go語(yǔ)句塊就被阻塞了,直到通道值被接收,也就是說(shuō)第二個(gè)go語(yǔ)句塊執(zhí)行完,才執(zhí)行fmt.Println("Sent!"),因此最后的結(jié)果Received!應(yīng)該在Sent!之前。
這樣理解對(duì)嗎?
代碼應(yīng)該是沒(méi)錯(cuò)吧,當(dāng)通道長(zhǎng)為0時(shí),執(zhí)行到sender <- number時(shí)第一個(gè)go語(yǔ)句塊就被阻塞了,直到通道值被接收,也就是說(shuō)第二個(gè)go語(yǔ)句塊執(zhí)行完,才執(zhí)行fmt.Println("Sent!"),因此最后的結(jié)果Received!應(yīng)該在Sent!之前。
這樣理解對(duì)嗎?
2016-03-01