Yes I did. Sorry all.
> On Jun 26, 2020, at 7:42 PM, Sebastien Rosset wrote:
>
>
> Did you reply to the wrong thread?
>
>> On Friday, June 26, 2020 at 3:09:42 PM UTC-7, Robert Engels wrote:
>> What about an option to disable the signal on the thread as it crosses the
>> CGo boundary? This
Did you reply to the wrong thread?
On Friday, June 26, 2020 at 3:09:42 PM UTC-7, Robert Engels wrote:
>
> What about an option to disable the signal on the thread as it crosses the
> CGo boundary? This seems better than disabling the async preemption
> entirely?
>
> On Jun 26, 2020, at 4:45 PM,
What about an option to disable the signal on the thread as it crosses the CGo
boundary? This seems better than disabling the async preemption entirely?
> On Jun 26, 2020, at 4:45 PM, Sebastien Rosset wrote:
>
>
>
> Below are the publicly exposed asn1.ObjectIdentifier fields in the
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?).
1. encoding/asn1:
1. My guess is this would be primarily used by SNMP applications
On Fri, Jun 26, 2020 at 12:54 PM 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
> applications, such
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
applications, such as for TLS connection management.
On Friday, June 26, 2020 at
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:
> >
> > @ianlancetaylor , thank you
On Fri, Jun 26, 2020 at 11:03 AM Sebastien Rosset wrote:
>
> @ianlancetaylor , thank you for the quick reply. The reason I was asking is
> because potentially this could have been used to fix `type ObjectIdentifier
> []int` in the `encoding/asn1` package and the `crypto/x509` package.
>
@ianlancetaylor , thank you for the quick reply. The reason I was asking is
because potentially this could have been used to fix `type ObjectIdentifier
[]int` in the `encoding/asn1` package and the `crypto/x509` package.
Currently these package are not fully compliant with the ASN.1
