That's a great idea. Thank you! I am doing that right now.
On Wed, Apr 7, 2021 at 5:05 PM 'Keith Randall' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> If you look at CL 304251, there's one place where we added "return false".
> Put a panic just before that line (in 1.15.11 or 1.16.3),
, 2020, at 4:45 PM, Sebastien Rosset > wrote:
>
>
>
> Below are the publicly exposed asn1.ObjectIdentifier fields in the
> golang/go repo. It has fairly limited exposure,
> but I'm sure some people will argue it's too much (maybe ok in go 2.x but
> not 1.x?).
2020 at 12:53:43 PM UTC-7, Sebastien Rosset wrote:
>
> As an aside, the most common use of the encoding/asn1 package is most
> likely crypto/x509. x509. Certificate exposes public fields that use the
> asn1.ObjectIdentifier, so asn1 ends up being exposed in a lot of
> application
:09 PM UTC-7, Sebastien Rosset wrote:
>
> sure, thank you. I will go through the PR review process for asn1 and
> x509, maybe some good ideas will come up.
> Sebastien
>
> On Friday, June 26, 2020 at 11:51:05 AM UTC-7, Ian Lance Taylor wrote:
>>
>> On Fri, Jun
sure, thank you. I will go through the PR review process for asn1 and x509,
maybe some good ideas will come up.
Sebastien
On Friday, June 26, 2020 at 11:51:05 AM UTC-7, Ian Lance Taylor wrote:
>
> On Fri, Jun 26, 2020 at 11:03 AM Sebastien Rosset > wrote:
> >
> > @ianla
9 AM UTC-7, Sebastien Rosset wrote:
>
> First apologies for initially bringing up the topic as a github issue
> rather than golang-nuts. I am copy-pasting my question here with
> @ianlancetaylor
> response.
>
>
> A default type value can be specified in C++ templates. I was ask
y to solve the
ASN.1 compliance issue.
> @sebastien-rosset We have not considered default types for generic type
parameters. The language does not have default values for function
arguments, and it's not obvious why generics would be different. In my
opinion, the ability to make existi
