Accept meta-test, expecting the buid to fail. (details)
Remove autogen forward declarations, which are never needed, and cause warnings about static declarations without definitions. (details)
Enable partial autogen for types declared inside functions. (details)
Take test-expect change missed in last commit. (details)
Commit
64f3b9fefe9bf3caf101090443066ca16169610e
by Michael Brooks
Fix support for partial autogen.
Partial autogen means that some lifecycle functions are possible to generate, and needed, while others are impossible to generate, but unneeded. It is a valid situation that a user can implicitly request.
Previous handling of "impossible to generate" left the function in a zombie state, where it could show up as an alternative later. This zombie state is problematic handling caused by a compiler bug. Without the fix, the added test fails by creating zombie states.
This change is also a prerequsite for an upcoming change to avoid gcc warnings by not emitting autogen forward declarations.
Commit
e797179240a99bdf7b97c53740f6886b84225a18
by Michael Brooks
Accept meta-test, expecting the buid to fail.
The fix is forthcoming.
The new test style (nowarn) checks for the absence of warnings. The team has seen inconsistent results with who sees what warning. This meta-test ensures that the checkin-triggered testing can notice a warning. The fix for this failing test will be to make the warning go away.
Commit
36dfdac15a1061978a1b23f2ae753434d890fdd1
by Michael Brooks
Enable partial autogen for types declared inside functions.
Done by giving pass cores finer grained error-recovery points, which causes Resolver's existing error-recovery logic to kick in for autogens within function bodies.