Hello Nick, > There has to be a better way to handle that. Making "void > foo(){return 1;}" valid code with no warning is just plain sloppy. (In > fact, I've been bitten by that before.) > I wouldn't mind seeing it limited to "return FnReturningVoid();"