Pre-RFC: Function parameter defaults

jplatte: > But you seem to assert that function param defaults only make sense in combination with named parameters, and I think you should make a case to why, rather than just asserting it. I believe that making defaults always come after the required arguments is a non-starter, because it means that making an argument default, or vice-versa, is a breaking API change.