[m-rev.] for review: --warn-no-stream-calls

[Zoltan Somogyi]

For review by anyone.

Some questions:

Is this the right functionality for the new option? Specifically,
should the same option govern whether we print warnings for calls
to io.write_string/3 and for calls to io.tell? I put them together
because warnings for the latter without warnings for the former are
error-prone. A piece of code may have N calls to io.write_string/3
between one io.tell/told pair; if you eliminate the tell/told pair
while adding an explicit stream argument to M < N of the calls to
io.write_string/3, you still want to get warnings for the N - M calls
you missed.

Is this the right name for the new option? (This depends on the
answer to the first question, of course.)

Is the existing documentation enough for the new option? (Again,
this depends on the answers to the previous questions.)

Zoltan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Log.no_stream
Type: application/octet-stream
Size: 1709 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20161007/0b3ab5c1/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.no_stream
Type: application/octet-stream
Size: 40667 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20161007/0b3ab5c1/attachment-0003.obj>