On Tue, Aug 27, 2024 at 11:32 AM Michael Mitchell
wrote:
>
> At the end of dlog trace, we get the following.
> These seem like basic assembly instructions with addresses but I have no idea
> what any of it means, and I can't find any documentation for it. Can someone
> take the time to go throu
At the end of dlog trace, we get the following.
These seem like basic assembly instructions with addresses but I have no
idea what any of it means, and I can't find any documentation for it. Can
someone take the time to go through the significance of each one by one,
and that way at least if
I should also note that for programs built using the go.mod "go" directive,
with a version set to a pre-1.22 value, due to GODEBUG semantics the
default behavior will not have changed, since it will be automatically set
to the value that enables the old behavior.
On Tuesday, August 27, 2024 at 1
I agree that in this case the release note we provided was likely not
informative enough. We try to walk the line of providing useful yet concise
notes about changes, but in this particular case we did not provide enough
detail specifically about how this change may cause breakage.
In general t
The statement "Especially that of a previously compiled program will run under
a new compiler version with the same behaviour” is not true with many
platforms. Even with Java, with a great backwards guarantee, this is not the
case (i.e. running on a later JVM) - although this is a somewhat recen
On Tuesday, August 27, 2024 at 8:00:27 AM UTC+10 robert engels wrote:
I don’t think being concerned about the user is correct - I suspect that
many (most?) of the users have no idea the program is even written in Go…
This is a builders responsibility imo to either fail at start-up with a
use
On Tuesday, August 27, 2024 at 11:56:44 PM UTC+10 Ian Lance Taylor wrote:
On Mon, Aug 26, 2024 at 10:16 PM Robert Engels
wrote:
>
> Hmm. Aren’t the endpoints supposed to negotiate the available
cryptographic methods?
>
> So wouldn’t this affect non Go endpoints as well - which puts the bu
On Mon, Aug 26, 2024 at 10:16 PM Robert Engels wrote:
>
> Hmm. Aren’t the endpoints supposed to negotiate the available cryptographic
> methods?
>
> So wouldn’t this affect non Go endpoints as well - which puts the burden back
> on the side trying to use the latest Go version which is removing s
I’m using gomobile to compile an Android aar. The issue I have is when there is
a crash in the native code, I don’t see any stack trace. Crash reports from the
Google Console are equally useless.
If anyone has stack traces figured on on gomobile, I’d love your help to learn
how.
My build flags
