GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Top level function definition ordering is unnecessarily strict. The type checker will report a function as undefined if it is invoked before its declaration.
What's wrong with that?
I was also surprised by this.
I personally don't have a strong opinion about it, however if we're not considering working on this constraint (cc @kantai), we should definitely document it (cc @moxiegirl).
I think we should fix this --- almost no modern compilers will complain about this kind of ordering.
Handled with #1079