Should, yes, thats why i logged a bug. Carlo tells me that we do indeed support non-const default arguments, and this is an unrelated bug, which will be fixed. that said:
well, some things will, because the compiler cant do stuff that the platform won't allow.
To give an (unrelated to this) example, .NET has stricter tules for what a constructor (ie
init()) can die before it has called the base constructor. No mater what Swift/Xocde allows you to do, if you want to get a valid .NET executable, you'll have to live with he limit .NET imposes, there.