-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: basic CI #9
Conversation
@@ -108,7 +108,8 @@ func (*Extras[C, R]) getter() (g ExtraPayloadGetter[C, R]) { return } | |||
|
|||
// mustBeStruct panics if `T` isn't a struct. | |||
func mustBeStruct[T any]() { | |||
if k := reflect.TypeFor[T]().Kind(); k != reflect.Struct { | |||
var x T | |||
if k := reflect.TypeOf(x).Kind(); k != reflect.Struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my own understanding, why is TypeOf
preferred to TypeFor
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TypeFor
was only introduced in 1.22
and because we're on an old geth upstream it's on an older Go version.
Why this should be merged
Move fast but don't break things.
How this works
Action to run
go test -short
after filtering for flaky upstream tests. I've opened #10 to investigate these. I've also updated thelibevm
branch protection to require that the job passes.How this was tested
Through the horrible experience that is testing and re-testing Github Actions 🤦