Sacha Ligthert sacha
0 Followers · 0 Following
Repositories
10
 Projects Packages Public Activity Starred Repositories
sacha opened issue golang/sudoku-funpark#27 2025-02-02 19:18:46 +01:00
Improve workload calculation and splitting of tasks
sacha pushed to trunk at golang/sfcs 2025-01-29 23:20:46 +01:00
14012dabd7 Initial Commit (Read: Dirty AF)
sacha created repository golang/sfcs 2025-01-29 20:51:55 +01:00
sacha pushed to trunk at golang/sudoku-funpark 2025-01-29 17:45:11 +01:00
c1f2a28ac1 Provided tests for functions that can be tested (Closes #20).
sacha closed issue golang/sudoku-funpark#20 2025-01-29 17:45:11 +01:00
Create tests
sacha released v20250128 Minor update at golang/sudoku-funpark 2025-01-28 21:28:33 +01:00
sacha pushed tag v20250128 to golang/sudoku-funpark 2025-01-28 21:28:33 +01:00
sacha pushed to trunk at golang/sudoku-funpark 2025-01-28 21:09:49 +01:00
cd54fdf345 Update the README.md
sacha pushed to trunk at golang/sudoku-funpark 2025-01-28 21:02:16 +01:00
cced4f04b2 Allow to set verbosity of output (Closes #26)
sacha closed issue golang/sudoku-funpark#26 2025-01-28 21:02:16 +01:00
Set verbosity of output
sacha opened issue golang/sudoku-funpark#26 2025-01-28 21:01:49 +01:00
Set verbosity of output
sacha pushed to trunk at golang/sudoku-funpark 2025-01-28 19:50:45 +01:00
2bdcdcb1dd Add JSON render + small refactoring (Closes #25)
sacha closed issue golang/sudoku-funpark#25 2025-01-28 19:50:45 +01:00
Output as JSON
sacha pushed to trunk at golang/sudoku-funpark 2025-01-28 18:29:15 +01:00
71fefd760e Rework how priting of solutions are handled.
2461f5b417 Forgot a function.
Compare 2 commits »
sacha pushed to trunk at golang/sudoku-funpark 2025-01-28 18:12:07 +01:00
b83d6bdde4 Give each function its own file.
sacha opened issue golang/sudoku-funpark#25 2025-01-28 02:32:57 +01:00
Output as JSON
sacha pushed to trunk at golang/sudoku-funpark 2025-01-28 02:30:28 +01:00
a314e945ed Change int64 for select variables to uint64. (Closes #21)
sacha closed issue golang/sudoku-funpark#21 2025-01-28 02:30:28 +01:00
Look into getting uint128/uint256 for counter and iter
sacha commented on issue golang/sudoku-funpark#21 2025-01-28 02:17:09 +01:00
Look into getting uint128/uint256 for counter and iter

This isn't going to work with the atomic.int64. Could retool is to use uint64

sacha pushed to trunk at golang/sudoku-funpark 2025-01-28 01:59:38 +01:00
2735074515 Use strings instead of ints to store blocks (Closes #23)