Anonymous user
Talk:Maze generation: Difference between revisions
→Python solution: incorrect
(Quarantine) |
|||
| (4 intermediate revisions by 4 users not shown) | |||
Line 28:
: From my perspective, I like it. I look forward to seeing specializations and variations, too. When that eventually happens, "Maze generation" will probably be a term for a class of tasks, rather than a specific task itself. For now, I don't see a problem with it. --[[User:Short Circuit|Michael Mol]] 19:52, 18 December 2010 (UTC)
:I'd say we can change it to a real task. As a rule, I would propose that if a draft task didn't receive any objections for a certain time (say, one or two weeks), it is ready for graduation. Are there any other criteria? --[[User:Abu|Abu]] 07:01, 20 December 2010 (UTC)
:I think the main criteria now would be "who wouldn't want it out of draft and why"? If the task author and the writers of the several implementations haven't signalled any remianing problems then why not go ahead and change it? --[[User:Paddy3118|Paddy3118]] 08:10, 20 December 2010 (UTC)
:: As a general routine, that makes sense. The one remaining criteria for future tasks is that there may need to be multiple implementers. --[[User:Short Circuit|Michael Mol]] 14:45, 20 December 2010 (UTC)
== Python solution: incorrect ==
At least the sample output of the Python code is wrong. There are three small blocks at the bottom that are sealed off, which shouldn't happen because of the recursive nature of the method specified by the task. --[[User:Ledrug|Ledrug]] 19:33, 30 June 2011 (UTC)
:This has also happened with the D solution, likely because it was a translation of the Python solution. --[[User:Bnlott|Bnlott]] 19:40, 30 June 2011 (UTC)
Can anyone explain to me how the python code works?
| |||