Timeline for SudokuSharp Solver with advanced features
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 5, 2017 at 16:35 | history | edited | Mathieu Guindon | CC BY-SA 3.0 |
no need for obnoxious EDIT banners
|
| Dec 16, 2013 at 17:52 | comment | added | Simon Forsberg | You have some very good points, which will be good to think about for further projects, but for this weekly challenge it would have been even more overkill I think :) | |
| Dec 16, 2013 at 17:29 | comment | added | David Harkness | @SimonAndréForsberg The separation would be between the classes that model 1) the layout and rules of the board, 2) the initial known cells of that particular puzzle, and 3) the mutable model used to solve that puzzle. While very cool, it would be a lot more code for something designed to run in a single-user console app. | |
| Dec 16, 2013 at 16:26 | history | edited | abuzittin gillifirca | CC BY-SA 3.0 |
added 1198 characters in body
|
| Dec 16, 2013 at 15:38 | history | edited | abuzittin gillifirca | CC BY-SA 3.0 |
added 562 characters in body
|
| Dec 16, 2013 at 15:19 | comment | added | Simon Forsberg | I'm not sure how you mean to share state between boards... If they would have been immutable, then I would have needed to make a whole lot of extra code to solve the map, as all the basic solving (the non-brute-force part) would need to create a whole new map.. | |
| Dec 16, 2013 at 14:58 | history | answered | abuzittin gillifirca | CC BY-SA 3.0 |