Mark D. Blackwell

This isn't right yet. Currently, the [code listing](https://github.com/rust-lang/book/blob/036e88a4f135365de85358febe5324976a56030a/listings/ch03-common-programming-concepts/no-listing-07-numeric-operations/src/main.rs#L13) for the ch03-02 Numeric Operations section says: let floored = 2 / 3; // Results in 0 Instead, it should say: let...

> There are several ways of using Dogeify. The first way is to go through ... Dogeify ... itself. > The second way is to modify the String or Array...

Even better: ``` ruby class EngTagger; def hello(s) "Hello, #{s}!" end end module Dogeify Tagger=EngTagger.new public extend self def dogeify(*a) return dogeify_object self if a.empty? dogeify_object a end private def...

Point 1: > With the release of Ruby 2.0.0 we started using a new compile environment. With the new environment it no longer means there is a universal default. Just...

I've addressed the review points. > I think a better implementation would be to print out the short command always as-is, then print out the full command again upon failure....

> > > One other problem with rake printing out the command line is that it is not safe to cut and paste back into a shell line because it...

> > One other problem with rake printing out the command line is that it is not safe to cut and paste back into a shell line > > I...

> > left for some other pull request to handle (including tests)? > > Yes, and it should. Understood. :) Just as a side comment: IMO good human-engineered log output...

Currently, minimally: ``` bash $ ls | wc -l 0 $ rake --version rake, version 11.2.2 $ rake -e "handle_options" rake aborted! SystemStackError: stack level too deep ```

Whenever a requested task (name) is satisfied by no defined task, but only satisfied by a file (or directory) name, Rake could print an announcement (even without `--verbose`). That UI...