0
\$\begingroup\$

I recently found the closed Crash your favorite compiler question and was wondering how a type of question like this could be changed to fit the requirements of a challenge question as outlined in the Help Center.

Could we break it down into "crash your favorite IDE" vs "crash your favorite compiler?" What about crashes related to memory corruption or crashes not found by fuzzing? Would any of these contestants make this question on-topic?

| |
\$\endgroup\$
  • 1
    \$\begingroup\$ "Too broad" can be confusing/misleading. It's using pop-con as an excuse for having no specification. What counts as a right answer, what counts as wrong? The "what makes one answer better than another" may be subjective, but it doesn't exist leading to it's close \$\endgroup\$ – Downgoat Jun 8 '16 at 21:09
  • \$\begingroup\$ @Upgoat so would specifying to crash an interpreter or compiler itself (without maxing out the machine's RAM or something like that) be enough to make the question appropriate for a code challenge? \$\endgroup\$ – JAL Jun 9 '16 at 12:45
  • \$\begingroup\$ The main problem with editing the challenge in these ways would be that most of the answers would be invalidated, and have to be deleted by mods. A decent way to approach this might be to sandbox a say code golf challenge with a much more rigorous validity criterion. \$\endgroup\$ – FryAmTheEggman Jun 9 '16 at 13:25

You must log in to answer this question.

Browse other questions tagged .