Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Top-down programming support #778
Top-down programming support
(Sorry for my poor English writing)
As the complex
let calc arg1 arg2 = let x = ... let y a = ... let z a b = let q c = ... ... ...
But if the
let calc arg1 arg2 = ... where z a b = ... where q c = ... where y a = ... where x = ...
Thus, the main expression is placed just after the
Estimated cost: M
Affidavit (please submit!)
Please tick this by placing a cross in the box:
Please tick all that apply:
This is somewhat analogous to the requests to remove requirements for types being defined before being used and the knock-on effects on file order in F#. I like the current behavior. When learning Haskell and playing with Idris, the "where" syntax annoyed me. It's just another way to accomplish almost the same thing as let, but differently. I prefer the simplicity of "let" syntax only and I like that I know where to find the result of an expression every time without thinking (at the bottom). I'm curious to see if other people share this opinion.
This touches upon the following decision criteria:
Which I think would rule this out unless there were more you could accomplish with it than you can today with inner