Fix passing sync/single variables by ref/blank intent.
Followed up on reviewers' comments.
Added tests. Retired a future.
Added another isX test; strengthened type-tests.chpl.
type-tests.todo.chpl is now covered by type-tests.chpl,
so I removed it.
More test adjustments.
Also allowed sync/singles in tuple *types*
- see parallel/sync/diten/tupleOfSync.chpl
Fix for io_test C compilation error.

The error message being displayed by the C compiler (GCC version 4.4.1 or newer) is
meaningful.  It warns that the program is attempting to free something that is not
heap-allocated -- in this case "\n" and the definitions of other ioLiterals.

The reason why the error only appears when --fast is supplied is that aggressive inlining
brings the call to free() into the function where an ioLiteral is passed to it, so under
those circumstances the C compiler can see that something stupid is being attempted.

In the original code, the author thought is was safe to free by explicitly avoiding known
cases where the contents of a c_string was owned by another program entity.  However,
since the IO module also supplies unowned c_strings it is unsafe in general to delete
them.  I added comments liberally to the module code where c_strings are accessed, so
future programmers are warned away from this practice.

Looking forward, except where performance is a concern, strings should be used in
preference to c_strings.  The new implementation of strings will manage memory correctly,
so the programmer who uses such objects need not concern himself with ownership details.
Followed up on the second round of Brad's comments.

Two TODOs:
* [ ] David's review of test/modules/diten/moduleNotInitialized.chpl
* [ ] why passing sync/single by reference is specific to ref/blank intents?
Merge branch 'master' into fixCStrings
Followed up on Brad's latest comments and group discussion.
* writeThis() is a compile-time error on sync/single
* corresponding test changes - added readFE/readFF when writing
* moved max() error testing from error-min-on-syncs.chpl into separate file
* adjusted an error message to say 'currently'
Add a primer for array vector operations

This primer walks through the new vector-like capabilities on 1D arrays.
Merge branch 'master' into fixCStrings
Updating re2 build to use -mmic for intel+knc builds

Following the lead of other third-party Makefiles, if we're building for
KNC using the intel compiler, throw the -mmic flag when building re2.
While here, I did some other cleanup:

* broke a long line of commands across several lines
* passed CXX into both recursive make steps just for symmetry (I don't
  believe it's used for the install step)
* removed the set of CC as it doesn't seem to be used by re2's Makefile
Merge pull request #447 from bradcray/re2ByDefault

Updating re2 build to use -mmic for intel+knc builds

Following the lead of other third-party Makefiles, if we're building for
KNC using the intel compiler, throw the -mmic flag when building re2.
While here, I did some other cleanup:

* broke a long line of commands across several lines
* passed CXX into both recursive make steps just for symmetry (I don't
  believe it's used for the install step)
* removed the set of CC as it doesn't seem to be used by re2's Makefile
More test updates - add readFE/readFF when writing sync/single.

I used readFF() on a sync, instead of readFE, in a few cases
where the computation is over, to say ''read the value and
keep it there just in case''.

I also slightly updated the sync/single primer with sync/single
generic formals, mention we can't just write them, added
some clearly missing newlines.
Adding a primer for the standard module Random.

This primer intentionally does not include any functionality with Private in
the name.  It also does not include the SeedGenerators record, as that record
only includes our default random generator settings.
Updated the error messages, after consulting with Brad.
Add indication of the new primer to the READMEs
Add Vass's suggestions to the array vector ops primer

Vass reviewed and made a few suggestions, so implemented them here.
Updated comments with new info from c_string interface investigation.
Update arrayVectorOps.good

I forgot to update the .good after adding Vass's suggestions.
Taking Vass's comments into account.