Last week I had started reworking my noinit tests now that _defaultOf is in the
repository.  This is just storing all those changes until I can get back to it
Merge branch 'master' into betterNoinitTests
Remove .future files for usedWithSync and usedWithSingle.

A while back, we came to the consensus that syncs and singles should not support
noinit, so their behavior today is correct.
Update some more tests.

I need to task switch so I'm going to save what I've done today.
Update four more tests.

There's a lot that still need updating, but progress is good.
Revert "Remove .future files for usedWithSync and usedWithSingle."

This reverts commit 2d6f5bf95a49b00d7d9b8a6248a7be25dc50403f.

Tom advised waiting to remove these futures until we'd had a group discussion on
the semantics of noinit for syncs and singles, so I'm reverting this change.
Rearrange the output to catch reversal cases.

If noinit were somehow using _defaultOf and the default case was skipping it
entirely, this test would not have caught that case.  Thanks, Tom, for pointing
it out!
Merge pull request #809 from lydia-duncan/betterNoinitTests

Clean up/strengthen the noinit tests [reviewed by hilde]

Previously, the noinit tests had relied on accurate
later assignment and a hacky grep of the generated
code (in the case of enums as it was simpliest) to
assure us that default initialization had been properly
skipped. Brad had suggested way back when that we
would be able to better test if noinit had actually worked
by using the _defaultOf functionality - by redefining the
default behavior to include displaying a message
whenever it was invoked, the absence of this
message would indicate when the default behavior
did not occur. Now that _defaultOf is in the language,
I have replaced/updated some of the tests in this
directory to use this improved method of determination.