This has been formally requested several times. For example:
https://github.com/golang/go/issues/20443
https://github.com/golang/go/issues/22876
I'm also willing to bet you are basing your request on experience with a
language such as C. Adopting ideas from other languages is fine but
blindly, an
I am using Ubuntu 20.04, Golang 16.2, then I downloaded the required
protobuf release here:
https://github.com/protocolbuffers/protobuf/releases/download/v3.15.8/protoc-3.15.8-linux-aarch_64.zip
for my system, and extract it in "Download directory", well you say that in
No. 2:
- Unzip and a
Hi Go-Masters
It will be very useful to get constant arrays in Golang.
Programmers asked about it for years .
For now we all should write not exported array definitions
and exported functions to get read access to it.
*What we need*
const *M*yArray = [n]T = {...} or initMyArrayFunc()
*What we
I hold the same view, but..
The most helpless thing is that my boss forced me to do something which is
difficult and meaningless...
在2021年4月10日星期六 UTC+8 上午3:55:36 写道：
> On Fri, Apr 9, 2021 at 6:00 AM JX Zhang wrote:
> >
> > Asm in go is in style of plan9. Now I need to compile the asm files i
> On Apr 11, 2021, at 14:23, K. Alex Mills wrote:
>
> Well I'm convinced this is art, and once it's viewed that way, I think it
> stops being confounding and becomes delightful.
>
> Sending it to my Art History contacts for analysis. Maybe by putting it in
> the proper context we can come to
> On Apr 11, 2021, at 14:18, Axel Wagner wrote:
>
> I don't understand what you are trying to say. And I feel the fact that
> everyone talking about is either confused, or speaking in riddles instead of
> just plainly explaining what they are trying to say, speaks for itself.
--
You receiv
On Sun, Apr 11, 2021, 5:15 AM Jesper Louis Andersen <
jesper.louis.ander...@gmail.com> wrote:
> On Sun, Apr 11, 2021 at 5:11 AM Kurtis Rader wrote:
>
>>
>> It is nice that the specification allows for an efficient implementation.
>> But I agree with Dan that your documentation is opaque, obtuse,
I don't understand what you are trying to say. And I feel the fact that
everyone talking about is either confused, or speaking in riddles instead
of just plainly explaining what they are trying to say, speaks for itself.
On Sun, Apr 11, 2021 at 1:55 PM Petite Abeille
wrote:
>
>
> > On Apr 11, 20
> On Apr 11, 2021, at 12:14, Jesper Louis Andersen
> wrote:
>
> It's an art installation. A lament to the mistakes we've made. The documents
> WE've written. But no-one reads. We revel in the 113 lines of pure
> specification, as a temple to Alan Kay. Documentation must be executable! The
> On Apr 11, 2021, at 05:11, Kurtis Rader wrote:
>
> It is nice that the specification allows for an efficient implementation. But
> I agree with Dan that your documentation is opaque, obtuse, inscrutable, etc.
> So much so that I initially thought it was some sort of April Fools Day joke.
>
> On Apr 11, 2021, at 12:22, 'Axel Wagner' via golang-nuts
> wrote:
>
> Everything around it certainly emits the air of pretentiousness that the fine
> art market is famous for.
There is a method to it:
https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Ftextprotoco
Everything around it certainly emits the air of pretentiousness that the
fine art market is famous for.
On Sun, Apr 11, 2021 at 12:15 PM Jesper Louis Andersen <
jesper.louis.ander...@gmail.com> wrote:
> On Sun, Apr 11, 2021 at 5:11 AM Kurtis Rader wrote:
>
>>
>> It is nice that the specification
On Sun, Apr 11, 2021 at 5:11 AM Kurtis Rader wrote:
>
> It is nice that the specification allows for an efficient implementation.
> But I agree with Dan that your documentation is opaque, obtuse,
> inscrutable, etc. So much so that I initially thought it was some sort of
> April Fools Day joke.
>
13 matches
Mail list logo
