Order map and struct keys #74
Labels
x:action/improve
Improve existing functionality/content
x:knowledge/intermediate
Quite a bit of Exercism knowledge required
x:module/representer
Work on Representers
x:size/medium
Medium amount of work
x:type/coding
Write code that is not student-facing content (e.g. test-runners, generators, but not exercises)
The order in which map and struct keys are defined shouldn't matter. We could order them alphabetically.
For example:
Input:
Desired representation:
Important: don't do this for keyword lists.
The issue of whether keys will be replaced by placeholders is still open, so make sure to sort the keys before they are replaced (if they will get replaced).
The text was updated successfully, but these errors were encountered: