The size of the post should not be a major consideration. We've had questions about everything from one-liners up to the 64 kB limit.
Rather, the issue is whether there is unity in the question — a unifying theme that is more substantial than whether they are all problems from Project Euler or from CS123 Problem Set 9.
Namely, the criteria should be:
- Is there any shared code among the solutions?
- Is there any pattern that would indicate a potential for sharing code?
In this specific example, main calls the code to print all five solutions. Perhaps an answer could point out a way to extract printfn "Solution to Project Euler %i: %i".
Also, several of the solutions use the |> Seq.filter … |> Seq.max and the |> Seq.filter |> Seq.head pattern. It might be possible to write an answer that address all of the uses of Seq.filter.
Given those observations, I would give @EBrown the benefit of the doubt.
That said, perhaps a better way to ask would be to post a smaller question, wait for answers, and post another small question that incorporates the feedback from earlier reviews.
Note that in the past, I have forced users to split up questions. For example, such as UPenn CIS 194 Homework 1, which covered credit card number validation and log file parsing.