[go-nuts] Microsoft Adaptive card

2022-07-18 Thread Rich
I need to be able to render adaptive cards, we have tons of adaptive cards that we already use but because the system that rendered them is going away -- I've got to figure out how to render them myself. I've googled and couldn't find anything, was hoping someone here might know of a way to ren

Re: [go-nuts] Issues with time.Time

2022-07-18 Thread Ian Lance Taylor
On Sun, Jul 17, 2022 at 6:20 AM Andrew Phillips wrote: > > I've discovered a few problems with time.Time but thought I better discuss > here first before creating issues at https://github.com/golang/go/issues (in > case I missed something obvious :). These are mainly performance issues, but >

[go-nuts] How to single step into runtime code

2022-07-18 Thread 'chris zhang' via golang-nuts
Hi everyone, I wonder how can I single step into runtime code (presumably in Visual Studio Code). I don't think this problem ties to any specific version of Go, but for context I'm using 1.18.3 on Intel Mac. What I want to do: given the source code, I want to track how map assignment happens t

Re: [go-nuts] Re: Error running gollvm on Ubuntu 20.04

2022-07-18 Thread hiter adole
Sorry for confusing, but I got something wrong: gollvm still does not work under root. It seems problems related with split-stack, but I do not know how to fix it yet. 在2022年7月17日星期日 UTC+8 22:59:14 写道: > Hi khanh: > > I met that problem too, and I thought I somehow fix it. I located the > sour

[go-nuts] go/packages.Load() returns different types.Named for identical code

2022-07-18 Thread Xiaoyi Shi
I'm trying to determine if two types are identical with `go/types.Identical`, and surprisingly enough, types of the same piece of code returned by different `packages.Load` calls are always different. Am I making a wrong assumption about those APIs? package main import ( "fmt" "go/type

[go-nuts] Re: Is Go 1.19 the last 1.x release?

2022-07-18 Thread Christoph Berger
The talk is from 2017. The version numbers Russ Cox used back then are certainly only examples. As long as all changes and additions to Go are backward-compatible, Go will stay at 1.x. On Saturday, July 16, 2022 at 4:08:26 PM UTC+2 peterGo wrote: > Natasha, > > No. > > Planning Go 1.20 >