Examples of using
Go程序员
in Chinese and their translations into English
{-}
Political
Ecclesiastic
Programming
许多Go程序员过度使用goroutine,特别是刚开始时。
Many Go programmers overuse goroutines, especially when they are starting out.
Go程序员常常被称为地鼠(gopher)。
Go programmers are often called gophers.
Go程序员应该觉得他们可以通过Go语言完成很多工作。
Go programmers should feel that they can get a lot done with Go..
Go程序员很棒!
Go programmers are great!
Go程序员往往把所有的Go代码放入到一个workspace中。
Go programmers typically keep all their Go code in a single workspace.
成为Go程序员的7个阶段.
The 7 stages of becoming a Go programmer.
正如RobPike所说,“Go程序员想要正确的长度的标识符”。
As Rob Pike said,"Go programmers want the right length identifiers".
这就是Go程序员所说的“给你的结构一个有用的零值”。
This is what Go programmers talk about when they say"give your structs a useful zero value".
既是初始化了变量又引入了一些Go程序员不喜欢的new关键字的罕见用法。
Which is both explicitly initialising a variable andintroduces the uncommon use of the new keyword which some Go programmer dislike.
通过所有这些不同的方式来声明变量,我们如何避免每个Go程序员选择自己的风格??
With all these different ways of declaring a variable,how do we avoid each Go programmer choosing their own style?
一概览Go程序员通常会将所有Go代码保存在一个工作区中。
Go programmers typically keep all their Go code in a single workspace.
这是一个关于GotchaIn-Go的经验报告,它至少捕获每个Go程序员一次。
This is an experience report about a gotcha in Go that catches every Go programmer at least once.
Go程序员应该感受得到,他们在工作中可以从很多东西中受益了。
Go programmers should feel that they can get a lot done with Go..
鉴于包的符号的访问有限控件,Go程序员应遵循哪些实践来避免创建过于复杂的包层次结构??
Given the limited controls available to control access to a package's symbols,what practices should Go programmers follow to avoid creating over-complicated package hierarchies?
你会经常听到有经验的Go程序员谈论sliceheader,因为它真的是存储在切片变量中。
You will often hear experienced Go programmers talk about the"slice header" because that really is what's stored in a slice variable.
最令人震惊的是我们现在的位置:保守估计至少有50万Go程序员。
The most astonishing is at our current position: a conservative estimate suggests thereare at least half a million Go programmers.
与new(Thing)相同,这就是为什么一些Go程序员对重复感到不满。
Which does the same as new(Thing), hence why some Go programmers are upset by the duplication.
因为接口让Go程序员描述他们的package提供了什么-而不是它怎么做的。
Interfaces let programmers describe what their package provides, not how it does it.
但是,对于Go程序员来说,依赖倒置在实践中意味着什么呢??
But what does dependency inversion mean, in practice,for Go programmers?
中文
Bahasa indonesia
日本語
عربى
Български
বাংলা
Český
Dansk
Deutsch
Ελληνικά
Español
Suomi
Français
עִברִית
हिंदी
Hrvatski
Magyar
Italiano
Қазақ
한국어
മലയാളം
मराठी
Bahasa malay
Nederlands
Norsk
Polski
Português
Română
Русский
Slovenský
Slovenski
Српски
Svenska
தமிழ்
తెలుగు
ไทย
Tagalog
Turkce
Українська
اردو
Tiếng việt