We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Reminder issue: Currently both go/types and types2 accept string(1 << s) while the compilers don't.
go/types
types2
string(1 << s)
For details see #45114.
cc: @findleyr
If we disallow this, re-enable the disabled test in test/fixedbugs/bug193.go.
test/fixedbugs/bug193.go
Change https://golang.org/cl/303094 mentions this issue: test: enable fixedbugs/bug193.go for -G compiler option
test: enable fixedbugs/bug193.go for -G compiler option
Change https://golang.org/cl/379256 mentions this issue: go/types, types2: report error for invalid string(1 << s)
go/types, types2: report error for invalid string(1 << s)
Change https://golang.org/cl/379274 mentions this issue: cmd/compile/internal/types2: use orig. compiler error message for a shift error
cmd/compile/internal/types2: use orig. compiler error message for a shift error
Activity
griesemer commentedon Mar 19, 2021
If we disallow this, re-enable the disabled test in
test/fixedbugs/bug193.go.gopherbot commentedon Mar 19, 2021
Change https://golang.org/cl/303094 mentions this issue:
test: enable fixedbugs/bug193.go for -G compiler optiontest: enable fixedbugs/bug193.go for -G compiler option
gopherbot commentedon Jan 18, 2022
Change https://golang.org/cl/379256 mentions this issue:
go/types, types2: report error for invalid string(1 << s)gopherbot commentedon Jan 19, 2022
Change https://golang.org/cl/379274 mentions this issue:
cmd/compile/internal/types2: use orig. compiler error message for a shift error7 remaining items