On Wed, Jan 5, 2022 at 11:09 AM Brieuc Jeunhomme <bjeunho...@gmail.com> wrote:
> But here ,since under non-windows platforms, I can't import the package, it > means I have to define wrappers for everything I use: types, constants, > functions. I don't get it. Put the common code in a file/in files with no build constraints and the target specific bits in files with build constraints for the target. What wrappers are needed and why? Package level declarations are visible in all files within a package - meaning they have package scope. The sole exception is the package qualifier explicitly or implicitly declared by an import statement. Such identifier has file scope. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAA40n-X1sC9DekAwAw8hxTcqdGVL0mQSHM1Ou71t1BQVCC1EWg%40mail.gmail.com.
