jub0bs
jub0bs@infosec.exchange
<p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="tag">#<span>infosec</span></a> enthusiast • <a href="https://infosec.exchange/tags/golang" class="mention hashtag" rel="tag">#<span>golang</span></a> dev & trainer • contributor to the Go project • minimalist • chaotic good • trying to make sense of the Web • he/him<br />Free Go course: <a href="https://github.com/jub0bs/go-course-beginner" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/jub0bs/go-course-be</span><span class="invisible">ginner</span></a></p><p>Free 🇵🇸! Leave 🇱🇧 alone!</p>
Posts
-
Post #894456
I love how the conjunction of #golang&#39;s modules system and build constraints lets you have your cake and eat it too! 🍰 You can let users of your library take advantage of the bleeding edge if they so wish without cutting off one of the currently supported Go toolchains. When something tantalising gets merged at tip, you can put code that relies on it in a file guarded by a //go:build go1.27 build constraint and its pre-1.27 counterpart in a file guarded by a //go:build !go1.27 build co...