Make Int <-> UInt conversions explicit #149
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Building on the work started by @rajuptvs in PR #123, this converts all implicit Int <-> UInt conversions to explicit typecasts. This is important to migrate over now, because the latest Mojo and MAX nightlies make this a compilation error, rather than a warning. I tested each puzzle problem and solution, and with these casts each now works on the latest nightlies.
Where possible, I tried to have the casts take place in code that we provided to each person attempting to solve a problem, so that they didn't need to account for them in the code they'd write. I'm also trying to keep in mind that we may standardize on Int for many of these interfaces, so attempted to keep the code changes minimal for when that migration may occur.
Fixes #119