Self-referential functions and the design of options
I've been trying on and off to find a nice way to deal with setting options in a Go package I am writing. Options on a type, that is. The package is intricate and there will probably end up being dozens of options. There are many ways to do this kind of thing, but I wanted one that felt nice to use, didn't require too much API (or at least not too much for the user to absorb), and could grow as ne
research!rsc: Go += Package Versioning (Go & Versioning, Part 1)
We need to add package versioning to Go. More precisely, we need to add the concept of package versions to the working vocabulary of both Go developers and our tools, so that they can all be precise when talking to each other about exactly which program should be built, run, or analyzed. The go command needs to be able to tell developers exactly which versions of which packages are in a particular
The Go type system for newcomers · rakyll.org
Home Archive About GitHub Mastodon Subscribe to the feed. This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. This blog is served by Hugo. Wed, Dec 27, 2017 It is real struggle to work with a new language, especially if the type doesn’t resemble what you have previously seen. I have been there with Go and lost my interest in the language when it first c
📺 Understanding nil
Gophercon2016ã§ã® francesc ã®ãƒˆãƒ¼ã‚¯ã‚’見ãŸã€‚Goã®nilã¨ã¯ä¸€ä½“何ãªã®ã‹ã€ã©ã†ã„ã£ãŸã‚·ãƒãƒ¥ã‚¨ãƒ¼ã‚·ãƒ§ãƒ³ã§æ´»ç”¨ã§ãã‚‹ã®ã‹ã€ã©ã†ã„ã£ãŸãƒãƒžã‚Šã©ã“ã‚ãŒã‚ã‚‹ã®ã‹ã¨ã„ã†nilã®ç†è§£ã‚’æ·±ã‚ã‚‹ã“ã¨ãŒã§ãる内容ã ã£ãŸã€‚ nilã¨ã¯ä½•ã‹ï¼Ÿè¨€èªžã«ã‚ˆã£ã¦null, nil, Noneç‰ä¼¼ãŸã‚ˆã†ãªã‚‚ã®ãŒå˜åœ¨ã—ã¦ã„ã‚‹ãŒã€ã„ãšã‚Œã‚‚æ„図ã™ã‚‹ã¨ã“ã‚ã¯ç•°ãªã£ã¦ã„る。nullã¯ã€Œä¸å®šã€ã ãŒã€nilã¯ã€Œã‚¼ãƒã€ã‚’指ã™ã€‚ I call it my billion-dollar mistake. It was the invention of the null reference in 1965. — Antony Hoare Goã®ç¥–å…ˆã§ã‚‚ã‚ã‚‹CSPã®é–‹ç™ºè€…トニーホーアã¯ã€å®‰æ˜“ã«nullã‚’å°Žå…¥ã—ãŸã®ã¯å¤±æ•—ã ã£ãŸã¨ã„ã†ãŒã€Goã®nilã¯å¤±æ•—ã§ã¯ãªã„。 panic: runtime error: invalid m
Error handling in Upspin
The Upspin project uses a custom package, upspin.io/errors, to represent error conditions that arise inside the system. These errors satisfy the standard Go error interface, but are implemented using a custom type, upspin.io/errors.Error, that has properties that have proven valuable to the project. Here we will demonstrate how the package works and how it is used. The story holds lessons for the
golang ã®ãƒ¬ã‚¤ãƒ¤æ§‹é€ ã«ãŠã„ã¦ã€ä»–ã®ã‚³ãƒ¼ãƒ‰ã«å½±éŸ¿ãªãインフラレイヤã®ãƒ‡ãƒ¼ã‚¿ã‚½ãƒ¼ã‚¹å®Ÿè£…ã‚’å·®ã—替ãˆã‚‹ã“ã¨ã¯å¯èƒ½ã‹? - pospomeã®ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°æ—¥è¨˜
最近ã€golang ã®ãƒ¬ã‚¤ãƒ¤æ§‹é€ ã«ãŠã„ã¦ã€ä»–ã®ã‚³ãƒ¼ãƒ‰ã«å½±éŸ¿ãªãインフラレイヤã®ãƒ‡ãƒ¼ã‚¿ã‚½ãƒ¼ã‚¹å®Ÿè£…ã‚’å·®ã—替ãˆã‚‹ã“ã¨ã¯å¯èƒ½ã‹? ã¨ã„ã†è³ªå•ã‚’å—ã‘ãŸã€‚ 回ç”時間ãŒé™ã‚‰ã‚Œã¦ã„ã‚‹ä¸ã§è³ªå•ã‚’å—ã‘ãŸã®ã§ã€ 「ç¾å®Ÿçš„ã«ã¯é›£ã—ã„ã€ã¨ã„ã†é›‘ãªå›žç”ã—ã‹ã§ããªã‹ã£ãŸã€‚ ã•ã™ãŒã«é›‘ã™ãŽã‚‹ãªã¨æ€ã£ãŸã®ã§ã€ 自分ãªã‚Šã®å›žç”ã‚’ã¡ã‚ƒã‚“ã¨æ®‹ãã†ã¨æ€ã†ã€‚ 影響をå—ã‘る対象ã¨ãªã‚‹ã‚³ãƒ¼ãƒ‰ã¯? MySQL -> PostgresSQL ã¸ã®å·®ã—替㈠MySQL -> WebAPI ã¸ã®å·®ã—替㈠インフラレイヤã«DBä¾å˜ã®ã‚³ãƒ¼ãƒ‰ã‚’ã¾ã‚‹ã£ã¨å®Ÿè£…ã—ã¦ã—ã¾ã† DDDã®å ´åˆ 独自ã®æŽ¥ç¶šã‚ªãƒ–ジェクトを作る DDD本 & IDDD本ã®ã‚µãƒ³ãƒ—ルã¯ã©ã†ãªã£ã¦ã„ã‚‹ã‹? å·®ã—替ãˆã‚‹å¿…è¦ã¯ã‚ã‚‹ã®ã‹? ã¾ã¨ã‚ 影響をå—ã‘る対象ã¨ãªã‚‹ã‚³ãƒ¼ãƒ‰ã¯?golang ã®ãƒ¬ã‚¤ãƒ¤æ§‹é€ ã«ãŠã„ã¦ã€ä»–ã®ã‚³ãƒ¼ãƒ‰ã«å½±éŸ¿ãªãインフラレイヤã®ãƒ‡ãƒ¼ã‚¿ã‚½ãƒ¼ã‚¹å®Ÿè£…ã‚’å·®ã—替ãˆã‚‹ã“ã¨ã¯å¯èƒ½ã‹? ã¨ã„
Goアプリケーションã«ãŠã‘るテストè¨è¨ˆã‚’考ãˆã‚‹ ～Javaã¨ã®æ¯”較ã§ç†è§£ã™ã‚‹Goã®ä¾å˜æ€§ã®åˆ†é›¢
è¿‘å¹´ã€æ–°èˆˆè¨€èªžã¨ã¯æ€ãˆãªã„ç°¡æ½”ã•ã‚„実行時パフォーマンスã®è‰¯ã•ãªã©ã‹ã‚‰GoãŒæ³¨ç›®ã‚’集ã‚ã¦ã„ã¾ã™ã€‚サイãƒãƒ¼ã‚¨ãƒ¼ã‚¸ã‚§ãƒ³ãƒˆã®ãƒ¡ãƒ‡ã‚£ã‚¢ãƒ‡ã‚£ãƒ™ãƒãƒƒãƒ—メント事æ¥æœ¬éƒ¨ã§ã‚‚Goã®å°Žå…¥ã‚’進ã‚ã¦ãŠã‚Šã€Goアプリケーションã®é–‹ç™ºã‚’通ã˜ã¦ãã®åˆ©ç‚¹ã‚„æ¬ ç‚¹ãªã©ã‚’身をæŒã£ã¦å¦ã¶ã“ã¨ãŒã§ãã¾ã—ãŸã€‚ã“ã®è¨˜äº‹ã§ã¯ã€Goアプリケーションã®è‡ªå‹•åŒ–å˜ä½“テストを行ã†ã«ã‚ãŸã£ã¦ã€ãƒ†ã‚¹ãƒˆã®å®Ÿæ–½ã‚’容易ã«ã™ã‚‹ã«ã¯ã©ã®ã‚ˆã†ãªè¨è¨ˆã‚’è¡Œã†ã¹ãã‹ã‚’ã€ä¾å˜æ€§ã®åˆ†é›¢ã¨ã„ã†è¦³ç‚¹ã‹ã‚‰ç´¹ä»‹ã—ã¾ã™ã€‚ä¾å˜æ€§ã®åˆ†é›¢ã¯ã€å˜ä½“テストã«ãŠã„ã¦ç¢ºä¿ã—ãªã‘ã‚Œã°ãªã‚‰ãªã„è¦ç´ ã®ä¸€ã¤ã§ã™ã€‚ä¾å˜æ€§ã®åˆ†é›¢ã‚’è¡Œã†ã“ã¨ã«ã‚ˆã£ã¦ã€ä¸€ã¤ã®ãƒ†ã‚¹ãƒˆã§å®Ÿè¡Œã•ã‚Œã‚‹æœ¬ç•ªã‚³ãƒ¼ãƒ‰ã®ç¯„囲を制é™ã™ã‚‹ã“ã¨ãŒã§ãã€ãƒ†ã‚¹ãƒˆãŒå¤±æ•—ã—ãŸã¨ãã®åŽŸå› 究明ãŒå®¹æ˜“ã«ãªã‚Šã¾ã™ã€‚ã¾ãŸã€ãƒ†ã‚¹ãƒˆã®å†ç¾æ€§ã®æ‹…ä¿ã‚‚容易ã«ãªã‚Šã¾ã™ã€‚ ã¯ã˜ã‚ã« åˆã‚ã¾ã—ã¦ã€‚æ ªå¼ä¼šç¤¾ã‚µã‚¤ãƒãƒ¼ã‚¨ãƒ¼ã‚¸ã‚§ãƒ³ãƒˆ ソフトウェアエンジニアã®å¤§æ¾¤ç¿”å¾ã¨ç”³ã—ã¾ã™ã€‚ç§ã®æ‰€å±žã—ã¦ã„
Stupid Gopher Tricks
Stupid Gopher Tricks GolangUK 21 August 2015 Andrew Gerrand Video A video of this talk was recorded at GolangUK in London. Watch the talk on YouTube 2 This talk This talk is about things you might not know about Go. Some of this stuff you can add to your Go vocabulary. Other things are probably best left for special occasions. 3 Language 4 Type literals (1/2) Here's a familiar type declaration: ty
Standard Package Layout
Vendoring. Generics. These are seen as big issues in the Go community but there’s another issue that’s rarely mentioned — application package layout. Every Go application I’ve ever worked on appears to have a different answer to the question, how should I organize my code? Some applications push everything into one package while others group by type or module. Without a good strategy applied acros
Goã®ã‚µãƒ¼ãƒã‚µã‚¤ãƒ‰å®Ÿè£…ã«ãŠã‘るレイヤè¨è¨ˆã¨ãƒ¬ã‚¤ãƒ¤å†…実装ã«ã¤ã„ã¦è€ƒãˆã‚‹ - pospomeã®ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°æ—¥è¨˜
devfest 2017 tokyo ã®ç™ºè¡¨è³‡æ–™ã§ã™ã€‚ Goã®ã‚µãƒ¼ãƒã‚µã‚¤ãƒ‰å®Ÿè£…ã«ãŠã‘るレイヤè¨è¨ˆã¨ãƒ¬ã‚¤ãƒ¤å†…実装ã«ã¤ã„ã¦è€ƒãˆã‚‹ from pospome 当日ã¯å…¥å®¤ã§ããªã„人もã„ãŸã‚‰ã—ã„ & æ©Ÿæトラブルã§10minã»ã©é–‹å§‹ãŒé…ã‚Œã¦ã—ã¾ã£ãŸ ã¨ã„ã†ã“ã¨ã§ç”³ã—訳ãªãæ€ã£ã¦ã„ã¾ã™ã€‚ ã¾ãŸã€ç«‹ã¡è¦‹ã™ã‚‹ä¾¡å€¤ãŒã‚る内容をæä¾›ã§ããŸã®ã ã‚ã†ã‹? ã¨ã‚‚æ€ã£ã¦ã„ã¾ã™ã€‚ スライドã¯å˜ä½“ã§ã‚‚発表内容ãŒä¼ã‚るよã†ã«æ–‡ç« を多ã‚ã«è¼‰ã›ã¦ã„ã‚‹ã®ã§ã€ 是éžç¢ºèªã—ã¦ã¿ã¦ãã ã•ã„。 100ページ越ãˆã¦ã„ã¾ã™ãŒãƒ»ãƒ»ãƒ»ã€‚ #DevFest_room2 入れãªã‹ã£ãŸã€‚。— t.junichi (@tjun1) 2017å¹´10月9æ—¥ ã‚‚ã®ã™ã”ã„ç«‹ã¡è¦‹äººæ•° #Devfest17 #DevFest_room2— ãƒãƒˆãƒ«ãƒ—ãƒã‚°ãƒ©ãƒžãƒ¼æŸ´ç”°æ™ºä¹Ÿ@少女終末旅行 (@tomoya_shibata) 2017å¹´10月9æ—¥ ルーム2ã“ã‚Œã‹ã‚‰ä¸¦ã¶æ–¹ã¯ã¾
Challenge to Advanced API Architecture in Go
The presentation slides on golang.tokyo#9 by @__timakin__
Go: Ten years and climbing
Drawing Copyright ©2017 Renee French This week marks the 10th anniversary of the creation of Go. The initial discussion was on the afternoon of Thursday, the 20th of September, 2007. That led to an organized meeting between Robert Griesemer, Rob Pike, and Ken Thompson at 2PM the next day in the conference room called Yaounde in Building 43 on Google's Mountain View campus. The name for the languag
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Understanding concurrency with behavioural types
GitHub - frapposelli/wwhrd: You have licenses to manage, What Would Henry Rollins Do?
📺 Go proverbs
High Performance Go
http://idiomaticgo.com/post/best-practice/server-project-layout/
http://idiomaticgo.com/post/best-practice/accept-interfaces-return-structs/
Eight years of Go - The Go Programming Language
proposal: spec: add support for unlimited capacity channels · Issue #20352 · golang/go
{{#tags}}- {{label}}
{{/tags}}