You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Encountered this regression via nextest's test suite
(nextest-rs/nextest#2001). If a table is empty,
it would be treated as a unit value. If attempted to be deserialized
via a `Default` impl, it would lead to deserialization failing with an
error like
```console
profile.default-miri: invalid type: unit value, expected struct CustomProfileImpl
```
A bisect appears to indicate that
ec36bff is responsible. For empty
tables where the Default impl is supposed to work, it no longer would.
I've attempted to restore the old behavior of putting in an empty
table, specifically this section:
ec36bff#diff-c5423e2d2d6c87501239c0304c0f496742e00440defdd20368cf548ba42ab184L175-L178
I'm happy to make changes if there's a better approach.
0 commit comments