On Fri, Apr 19, 2019, 4:48 PM Rob Pike wrote:
> I just use 1 so I don't have to look up what it's called these days, but
> I'm seriously old school.
>
Does that pass code review or do people give you the benefit of doubt?
>
--
You received this message because you are subscribed to the
I just use 1 so I don't have to look up what it's called these days, but
I'm seriously old school.
-rob
On Sat, Apr 20, 2019 at 3:19 AM Michael Jones
wrote:
> I’ve been doing that since 6th Edition, 1976/77
>
> On Thu, Apr 18, 2019 at 8:00 AM andrey mirtchovski
> wrote:
>
>> > offset, err :=
On Friday, April 19, 2019 at 7:44:42 AM UTC-7, Marvin Renich wrote:
>
> * Dave Cohen > [190419 10:25]:
> > I'm working on code that signs a message with an ed25519 key.
> >
> > I expected that when signing the same message over and over, I'd get a
> > different signature each time.
> >
> >
I’ve been doing that since 6th Edition, 1976/77
On Thu, Apr 18, 2019 at 8:00 AM andrey mirtchovski
wrote:
> > offset, err := f.Seek(0, io.SeekCurrent)
>
> my code has been written so long ago i didn't even notice os.SEEK_CUR
> is deprecated :)
>
> --
> You received this message because you are
* Dave Cohen [190419 10:25]:
> I'm working on code that signs a message with an ed25519 key.
>
> I expected that when signing the same message over and over, I'd get a
> different signature each time.
>
> But I find when I run the test (below) more than once, I get the same
> signature bytes
I'm working on code that signs a message with an ed25519 key.
I expected that when signing the same message over and over, I'd get a
different signature each time.
But I find when I run the test (below) more than once, I get the same
signature bytes each time. Here's sample (identical) output
