Added a bug future on a missing const check
Merge pull request #117 from chapel-lang/addRecordArgConstCheckingFuture

Added a bug future on a missing constness check.

From .future: an assignment to a field of a record-typed formal passed by blank intent is not flagged as an error.

Constness checking implemented in SVN r22963 needs to be extended to
report an error in this code. That's because since a record passed
by blank intent is considered "const", it should not be assignable.

proc myProc(y: MyRecord) {
  y.myField = 7;   <--- should be an error                                                                                       
  writeln(y);
}

Thanks to Tim Z for bringing this to my attention.