TaskThe Modern Task RunnerA fast, cross-platform build tool inspired by Make, designed for modern workflows.
Instead, add missing details relevant for debugging. Some people like to complain that Go requires writing tons of âif err != nil { return err }â blocks. Those people donât understand Go errors. The thing is, what they complain about is actually a completely wrong way of handling errors in Go: return err is an antipattern. Let me show what I mean on some sample code: a helper library for configuri
**ãã¹ãé§åéçº(TDD)ã§åºç¤ã身ã«ã¤ãã¾ãããã**Goã¯TDDãå¦ç¿ããã®ã«é©ããè¨èªã§ãããªããªããå¦ç¿ããã®ãç°¡åãªè¨èªã§ããããã¹ããçµã¿è¾¼ã¾ãã¦ããããã§ãã
ã¯ããã«TIGçéã§ããè²ä¼æãã§ãã ãã¥ã¼ãã£ã¼ç¤¾å ã®ã¿ã¹ã¯ã©ã³ãã¼ã¯makeãTaskãªã©è¤æ°ã®æµæ´¾ãããããã¼ã ã«ãã£ã¦ä½¿ãåãããã¦ãã¾ããå人çã«ã¯makeã§è¯ãããããªããã¨æã£ã¦ãã¾ãããTaskãè¯ãã§ãããã makeã¯ç´°ããè¨æ³ããã¤ãå¿ããï¼èª¿ã¹ãã¨Cè¨èªåãã®æ å ±ãåºã¦ãã¦è³å å¤æã«æéãæãããããmakeãç¨ãã¦Webããã¯ã¨ã³ãã¢ããªãGoã§éçºããã¨ãããã¨ããã¼ãã«ãå½¹ç«ã¡ãããªæ å ±ãã¾ã¨ãã¾ãã ãªããä»è¨äºã«ãããmakeã¯ãGNU Makeãæãã¾ãããã¼ã¸ã§ã³ã¯ä»¥ä¸ã§åããã¦ãã¾ãã Makefileã®ããã®EditorConfigMakefileã®ã¤ã³ãã³ãã¯ãã¼ãã¿ãã§ããå¿ è¦ãããã¾ãã誤ããé²ãããã«ãEditorConfigãè¨å®ãã¦ããã¨è¯ãã§ãããã makeã¯é常ãMakefileã¨ããåç§°ãããã©ã«ãã§èªèãã¾ãããåä¸ãã©ã«ã
Go ã® Fuzzy Finder ã©ã¤ãã©ãªã§ãã go-fzf ãä½ãã¾ããã go-fzf ã使ç¨ããã¨æ¬¡ã®ãã㪠Fuzzy Finder ãç°¡åã«å®è£ ãããã¨ãã§ãã¾ãã ä¸ã®ä¾ã§å®è¡ãã¦ãã main.go ã®å 容ã¯ããã ãã§ãã package main import ( "fmt" "log" "github.com/koki-develop/go-fzf" ) func main() { items := []string{"hello", "world", "foo", "bar"} f, err := fzf.New() if err != nil { log.Fatal(err) } idxs, err := f.Find(items, func(i int) string { return items[i] }) if err != nil { log.Fatal
ããªãã«ã¨ã£ã¦éè¦ãªãããã¯ãååã®ææ°æ å ±ãå ¥æãã¾ãããææ°ã®æ´å¯ã¨ãã¬ã³ãã«é¢ããææ°æ å ±ãå³åº§ã«åãåãã¾ãããã ç¶ç¶çãªå¦ç¿ã®ããã«ãç¡æã®ãªã½ã¼ã¹ã«æè»½ã«ã¢ã¯ã»ã¹ãã¾ãããããããã¯ããã©ã³ã¹ã¯ãªããä»ãåç»ãããã³ãã¬ã¼ãã³ã°ææã è¨äºãä¿åãã¦ããã¤ã§ãèªããã¨ãã§ãã¾ãè¨äºãããã¯ãã¼ã¯ãã¦ãæºåãã§ããããã¤ã§ãèªãã¾ãã
ããªãã«ã¨ã£ã¦éè¦ãªãããã¯ãååã®ææ°æ å ±ãå ¥æãã¾ãããææ°ã®æ´å¯ã¨ãã¬ã³ãã«é¢ããææ°æ å ±ãå³åº§ã«åãåãã¾ãããã ç¶ç¶çãªå¦ç¿ã®ããã«ãç¡æã®ãªã½ã¼ã¹ã«æè»½ã«ã¢ã¯ã»ã¹ãã¾ãããããããã¯ããã©ã³ã¹ã¯ãªããä»ãåç»ãããã³ãã¬ã¼ãã³ã°ææã è¨äºãä¿åãã¦ããã¤ã§ãèªããã¨ãã§ãã¾ãè¨äºãããã¯ãã¼ã¯ãã¦ãæºåãã§ããããã¤ã§ãèªãã¾ãã
ããªãã«ã¨ã£ã¦éè¦ãªãããã¯ãååã®ææ°æ å ±ãå ¥æãã¾ãããææ°ã®æ´å¯ã¨ãã¬ã³ãã«é¢ããææ°æ å ±ãå³åº§ã«åãåãã¾ãããã ç¶ç¶çãªå¦ç¿ã®ããã«ãç¡æã®ãªã½ã¼ã¹ã«æè»½ã«ã¢ã¯ã»ã¹ãã¾ãããããããã¯ããã©ã³ã¹ã¯ãªããä»ãåç»ãããã³ãã¬ã¼ãã³ã°ææã è¨äºãä¿åãã¦ããã¤ã§ãèªããã¨ãã§ãã¾ãè¨äºãããã¯ãã¼ã¯ãã¦ãæºåãã§ããããã¤ã§ãèªãã¾ãã
Docker and Go: why did we decide to write Docker in Go?AI-enhanced description The document discusses Docker, a platform for developing, shipping, and running applications in containers to solve complex deployment scenarios. It covers Docker's architecture, its implementation in Go, advantages such as static compilation, and various drawbacks to be aware of. Additionally, it highlights the separat
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ã¡ã³ããã³ã¹
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}