Skip to content
Go

Handle ast changes when interface is aliased #35

Sign in to view logs

Handle ast changes when interface is aliased

Handle ast changes when interface is aliased #35

Triggered via pull request November 15, 2024 15:05
@MakpocMakpoc
synchronize #14
handle-new-alias-type-in-go123
Status Failure
Total duration 20s
Artifacts –

go.yml

on: pull_request
build
11s
build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
build
missing function body
build
syntax error: unexpected [, expecting (
build
missing function body
build
syntax error: unexpected [, expecting (
build
undefined: types.TypeParam
build
undefined: types.NewAlias
build
undefined: types.Alias
build
undefined: types.Alias
build
undefined: types.TypeParamList
build
undefined: types.Alias
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/