For what it's worth, another way to do this is to use a language feature
that is only present in a more recent version. For example
const _ = 0o0 // Octal integer literals with the 0o prefix need Go 1.13
or later
Obviously this only works if there's a new language feature introduced at
exact
> Suppose a company pulls in the main module into a monorepo. Such a repo might
> be set up to pull in M1 in its entirety, and thus, recursively, M4 and M5,
> regardless of whether the main module uses it.
Thanks - that's a useful example.
--
You received this message because you are subscribe
Thanks so much for the quick reply. I see where that comes from now.
On Tuesday, April 7, 2020 at 12:40:52 PM UTC-4, Filippo Valsorda wrote:
>
> On Mon, Apr 6, 2020 at 5:45 PM Ian Lance Taylor > wrote:
>
>> [ + filippo ]
>>
>> On Mon, Apr 6, 2020 at 2:00 PM ancientlore > > wrote:
>> >
>> > Hi, we
On Mon, Apr 6, 2020 at 5:45 PM Ian Lance Taylor wrote:
> [ + filippo ]
>
> On Mon, Apr 6, 2020 at 2:00 PM ancientlore wrote:
> >
> > Hi, we’re needing to use FIPS-validated crypto in a particular
> deployment. It looks like the dev.boringcrypto branch would meet our needs
> well. But I’m struggl
I can't answer the question as to whether it will always matter, but at
least that it will sometimes matter.
Suppose a company pulls in the main module into a monorepo. Such a repo
might be set up to pull in M1 in its entirety, and thus, recursively, M4
and M5, regardless of whether the main mo
