I am delighted to learn that I, the original author of Go's fmt and bytes
packages, am actually Satoshi Nakamoto. I always wondered who he was.
Thanks for clearing that up.
All kidding aside, I do not understand what you are trying to achieve by
claiming authorship of this code. Or even if that's
On Wed, Jul 26, 2023 at 12:32 AM Bravo Moua wrote:
> For a fact, bytes, fmt, and packages in those category are from Satoshi
> Nakamoto and myself.
Extraordinary claims require extraordinary evidence.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
You are correct, bitcoin wasn't written in go. I built Decred on Jan 4 and
finished on Jan 8 2009 and tested it, then went on to build Btcd with go
soon after. I will look into it some more, well if you were working on go
during that time, i m sure you know what was there on golang. Thank you,
On Tue, Jul 25, 2023 at 3:29 PM Bravo Moua wrote:
>
> How bout prior to the public release in nov 2009? Well here's the story, Im
> looking for the creator of Bitcoin, I was a part of the creation of Bitcoin
> from the beginning. We ve coded some codes in Golang in Jan 2009. Just asking
> arou
How bout prior to the public release in nov 2009? Well here's the story,
Im looking for the creator of Bitcoin, I was a part of the creation of
Bitcoin from the beginning. We ve coded some codes in Golang in Jan 2009.
Just asking around if there is any history that is prior to the release of
g
How bout prior to the public release in nov 2009? Well here's the story,
Im looking for the creator of Bitcoin, I was a part of the creation of
Bitcoin from the beginning. We ve coded some codes in Golang in Jan 2009.
Just asking around if there is any history that is prior to the release of
g
I ran into the same issue and am curious why this is observed only on
windows and not mac/linux considering that the issue seems independent of
the platform ?
On Friday, February 4, 2022 at 3:23:45 PM UTC-8 Pablo Caballero wrote:
> Hi Ian! Thank you so much for sharing that link with me. It wa
There will be an issue if we have test cases with larger delay. If one test
case executed, then the following has larger execution time , then the
whole test framework will fail. Im trying to define a test class to handle
these kinds of issues.
--
You received this message because you are subs
