Making this example clearer
Simplifying logic
David's keen eye noticed that there was in fact a working substring
for ranges in ChapelRange.chpl.  I move body of that version to the
CString module in String.chpl.
Add LLVM backend support for C For Loops
Build fewer LLVM components to speed compile

This patch significantly reduces the build
size and the build time. It omits some LLVM
and Clang components we don't use and only
builds host and x86 and x86-64 backends.

Used to take 23 minutes, now takes 18 minutes
to CHPL_LLVM=llvm time make on my machine. In
addition, llvm/build is now 8G (was 12G)
and llvm/install is now 4.6G (was 5.8G).
Merge pull request #291 from mppf/fix-llvm-c-for-2

Add LLVM backend support for C For Loops

Directly support C for loops in the LLVM backend.
Tested with make check for LLVM and non-llvm builds and
with test/types/range/diten/cForLoops and with zipRange.chpl
therein with --no-scalar-replacement and/or --no-inline. Tests OK.

Also fixes up some previous LLVM code generation that added
unnecessary ICmpNE in some cases.

Reviewed by @ronawho

The LLVM backend seems to be working after this patch. I'll do more testing before the release.
Merge branch 'master' of github.com:chapel-lang/chapel into fix-range-substring
Remove functions/iterators/tzakian/open_inside_file_iter.{bad,future}.

This test was "cured" by #168.
Updated functions/iterators/tzakian/par_iter_recursive.bad due to line number changes in ChapelArray.chpl.
Update TRIAGE and REGRESSIONS files.
Merge branch 'master' of https://github.com/hildeth/chapel
Merge pull request #294 from hildeth/master

More futures cleanup

Marked functions/iterators/tzakian/open_inside_file_iter as passing.
Updated the .bad file for par_iter_recursive, due to line number changes in ChapelArray.chpl
Recorded recent anomalies and regressions in the TRIAGE and REGRESSIONS files.
[Not reviewed.]
Merge pull request #285 from Kyle-B/vim-syntax-update

Update the Vim highlighting for Chapel

* Removes the highlighting for characters and made '...' and "..." equivalent.
* Adds the 'inline' and 'with' keywords
* Removes some commented out rules

A few things still don't highlight correctly, but this is all the effort I want to put in for now.
Removing old Samples

The Samples/ directory used to not be tested and was designed for
illustrative purposes.  It feels very stale, though, and seems like
it could be used for tests that are run for illustrative purposes,
so let's reclaim it.  Removing old samples for now.
Adding a sample test file matching the one in bestPractices/TestSystem.txt
Updating Test System documentation

The main change here was to add information about creating performance
tests to bring the major steps and common features together into one
place.

While here, I took a general wordsmithing pass over the existing text
and added mention of .bad files to the section on futures.

Made the existing (trivial) correctness test point to test/Samples/Correctness
just for completeness, even though it's ridiculous.  Over time, I think we
should add additional tests showing off different test system futures here.
Merge pull request #286 from sungeunchoi/fix-range-substring

Properly implement `string.substring` for ranges

[reviewed by David]

For some reason, I missed the fact that `string.substring(r: range(?))` was implemented in ChapelRange.chpl.  David did not. 

This commit fixes `string.substring` for ranges.  I moved the existing `string.substring`, which was originally written when c_strings and Chapel strings were treated as the same thing, to the `CString` module as `c_string.substring`.  I added a new `string.substring` for ranges (that calls `c_string.substring` and does not leak c_strings) to handle Chapel strings.  I also changed the return type of the string_select primitive to be c_string (yet another thing I missed in a previous commit).

This should fix test/types/string/sungeun/c_string/substr.future.
Adding new sample performance test to the Samples/ directory

Also added it to GRAPHFILES (even though it won't add any useful data)
after nobody objected on chat or chapel_perf.  If we don't like this
over time, we can reconsider, or move it into misc, or ...
Add a top-level README to the Samples/ directory
Stopped treating Samples/ as special in the test system

The Samples/ directory was, historically, meant to be a set of
illustrative tests that were not tested by default; however,
as a result of not being tested, they also became stale and
disused.  Here, I'm repurposing the Samples/ directory to be
tested to keep it live, so am not having start_test skip over
it by default as it used to.  Updated documentation to reflect
this.