.Object and .object are too similar

[dcousens]

Thankfully, the consequences are typically immediately obvious due to value types, but, still.

[dcousens]

Perhaps .object should be removed from the API... pre-compilation is almost always advised anyway and .object prevents that.

[dcousens]

Removed it.

This is a breaking change, and the implications of using it directly are really bad due to it not using compiled types internally.
This lead to weird behaviour with strict flags on since you couldn't handle undefined values where it was expecting a type function.

Going to release a patch.

For anyone that sees this thread, you should be using typeforce.compile, not typeforce.object.

[dcousens]

Or not, actually, breaking changes are never OK.
Resolved the issue with ebf68d9#diff-168726dbe96b3ce427e7fedce31bb0bcR86 by compiling inline with the type rather than special casing it in compile... just like all the others do.