On Tue, Mar 15, 2022 at 9:09 PM Stavros Filargyropoulos
wrote:
>
> On an embedded 16 core arm device we have been observing infrequent runtime
> crashes, with different signatures every time.
>
> One examples is this:
>
> unexpected fault address 0x6b6fc6da
> fatal error: fault
> [signal SIGSEGV:
On Tue, Mar 15, 2022 at 12:34 PM Lee Trout wrote:
>
> Release notes and docs appear to missing the update to the embed package
> where one can now use the `all:` prefix
>
> https://go-review.googlesource.com/c/go/+/359413/
Thanks. Sent https://go.dev/cl/393234.
Ian
--
You received this messa
Hi,
On an embedded 16 core arm device we have been observing infrequent runtime
crashes, with different signatures every time.
One examples is this:
unexpected fault address 0x6b6fc6da
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x1 addr=0x6b6fc6da pc=0x7f72c]
goroutine 1 [
We're making a log processing program that needs to parse times from the
prefix of a larger string, in this case in a log line such as:
2006-01-02 15:04:05 INFO this is a log message
We need to parse the "2006-01-02 15:04:05" part as a timestamp.
Unfortunately, time.Parse always returns an erro
An email is designated as Spam by a heuristic. The heuristic takes into
account the name of the server where email is originating, properties of
the subject and contents and sender. It's unrelated to the use of Gomail or
any other sending library.
On Monday, 14 March 2022 at 09:11:13 UTC-7 cick
There is nothing new here. Every programming language, framework, and tool
has had the same problem. Quality documentation and training is often the
hardest thing to produce, and is often deemphasized in budgets. It's also
part of the last 10% of doing something that usually takes 90% of the time
Great! Thank you all!
Regards
dharani
On Tue, Mar 15, 2022 at 10:56 AM Heschi Kreinick wrote:
> Hello gophers,
>
> We just released Go 1.18
>
> To find out what has changed in Go 1.18, read the release notes:
> https://golang.org/doc/go1.18
>
> You can download binary and source distributions
Release notes and docs appear to missing the update to the embed package
where one can now use the `all:` prefix
https://go-review.googlesource.com/c/go/+/359413/
On Tuesday, March 15, 2022 at 1:58:17 PM UTC-4 Heschi Kreinick wrote:
> Hello gophers,
>
> We just released Go 1.18
>
> To find out
Hello gophers,
We just released Go 1.18
To find out what has changed in Go 1.18, read the release notes:
https://golang.org/doc/go1.18
You can download binary and source distributions from our download page:
https://golang.org/dl/
If you have Go installed already, an easy way to try go1.18
is b
On Tuesday, 15 March 2022 at 15:51:46 UTC Jan Mercl wrote:
> a struct with a single field is another interesting case that can be
> abstracted out.
Aside: a struct with *no* fields is also more useful than you might think -
e.g. to use a map as a sparse set.
m := make(map[int]struct{}
Hello gophers,
Version v0.0.0-20220315160706-3147a52a75dd of golang.org/x/crypto/ssh
implements client authentication support for signature algorithms based on
SHA-2 for use with existing RSA keys.
Previously, a client would fail to authenticate with RSA keys to servers
that reject signature algo
Yes indeed! These constructions all give us *expressions *with many
consecutive stars. But they don't give us *types *with that. (and you can't
assign a *Number to a **Number, for example)
On Tue, Mar 15, 2022 at 11:50 AM Jan Mercl <0xj...@gmail.com> wrote:
> On Tue, Mar 15, 2022 at 4:41 PM Thoma
On Thu, Mar 10, 2022 at 4:31 AM Rob Pike wrote:
> On Thu, Mar 10, 2022 at 5:08 PM shan...@gmail.com
> wrote:
> >
> > Is this really how you want to be known?
>
> Sure, why not? It's a more interesting program than one might think.
>
> For a richer example of the foundational idea here, see the p
On Tue, Mar 15, 2022 at 4:41 PM Thomas Bushnell BSG
wrote:
> Not in the normal implementation it doesn't. Typically it might be:
>
> type element struct {
> value int
> next *element
> }
>
> next is a pointer to an element, not a pointer to a pointer. That element
> contains within it a poin
On Wed, Mar 9, 2022 at 11:38 PM Jan Mercl <0xj...@gmail.com> wrote:
> A linked list, for example, consists of pointers to pointers to pointers...
>
Not in the normal implementation it doesn't. Typically it might be:
type element struct {
value int
next *element
}
next is a pointer to an ele
Actually the one I was referring to is in the main repo at
test/peano.go, but it's the same idea.
-rob
On Tue, Mar 15, 2022 at 10:10 PM Jochen Voss wrote:
>
> Thanks for the pointer to peano.go, this is fun!
>
> It took me a while to locate the file. In case others are interested:
> peano.go i
Thanks for the pointer to peano.go, this is fun!
It took me a while to locate the file. In case others are interested:
peano.go is
at https://github.com/golang/website/blob/master/_content/doc/play/peano.go
and can also be found by choosing "Peano Integers" from the top-right menu
in the Go p
17 matches
Mail list logo
