Fix passing sync/single variables by ref/blank intent.
Catching up on past 6 weeks regressions...
Add a multilocale test for chdir/cwd().

Suggested by Michael.  Multi-task one is next.
Update the comments on chdir and cwd to represent their behavior in multilocale
situations.
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
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?
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'
Tuesday afternoon REGRESSIONS snapshot
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.
Updating description of walk#9 failure
Updated the error messages, after consulting with Brad.
Add a test to lock in the behavior of chdir and cwd in a parallel environment.
Report error when writing to const array elements.
Adjusted the comments on sync/single .writeThis().
Merge pull request #451 from vasslitvinov/array-const-checking

Report error when writing to const array elements.

It is a small change to functionResolution.cpp. I introduced a new pragma flag that says "when the receiver is constant, the result is constant". Then followed the pattern of/relied on const checking that already was in place.

Several tests updated 'const' arrays. I replaced 'const' with 'var' on those arrays.

In one test I used an array literal for initialization of an array, which remained 'const'.

Reviewed by Tom.
Silencing coverity issues

[trivial, not reviewed]

Coverity wisely warned about not looking at the return values of
stat() and lstat(), which I had ignored in my first implementation.
Here, I throw an internal error if they fail which is a lame-ish
short-term fix that I took, knowing that the isDir()/isLink()
utilities are right around the corner, will have good error
handling, and that I can use them once they're available.
Merge pull request #453 from bradcray/filerator

Silencing coverity issues

[trivial, not reviewed]

Coverity wisely warned about not looking at the return values of
stat() and lstat(), which I had ignored in my first implementation.
Here, I throw an internal error if they fail which is a lame-ish
short-term fix that I took, knowing that the isDir()/isLink()
utilities are right around the corner, will have good error
handling, and that I can use them once they're available.
Changes I meant to include in #451.