Christopher Henderson
Christopher Henderson
@sleevi gentle re-engagement on this
\#include @sleevi @cardonator @zakird porting the week's coversation from #491 here trying to break up the conversation a bit. There appears to be a second, equally complex, discussion of what...
@sleevi gentle re-engagement on this
I'm sorry, @alex, but I do not believe that this is quite feasible in our codebase without some interesting gymnastics. The reason is as follows... Consider the definition of a...
Would that not involve yet another fork of `zcrypto` (which itself would require regular pulls from upstream to receive bugfixes), but private to exactly only this lint? ```go func (l...
That's actually a good point. I'm not getting any luck with the following definition, however, so I'm gonna debug what I'm doing wrong here (I even left the `Extension` struct...
(figured it out, `zcrypto/asn1` vomits on it but the standard library likes it just fine)
Alas, boo. I don't think the `asn1` library deals with pointers. Given [getUniversalType](https://cs.opensource.google/go/go/+/refs/tags/go1.17.3:src/encoding/asn1/common.go;l=158) ```go // Given a reflected Go type, getUniversalType returns the default tag number // and expected compound...
@aarongable @vanbroup the change listed in Boulder is reasonably contained (and commented) so I can take a crack at this. Although, I may enlist Aaron (or at least @ mention...
@RufusJWB certainly, I reckon that all we need is a branch in the repo for forks to open PRs against? As far as content of the branch goes I admit...