Reorder map initialization so 'point' is correctly interpreted #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…efore all of the generic mappings. When the base class registered the base mappings, it registered "int" as (^int). Later, when it went to look up type 'point', it would match this, and think that 'point' was an integer. This changes it so that the specializations are registered after the generic ones are, so that when it looks up 'point', it finds these specializations, instead of finding 'int'
fjl82
added a commit
that referenced
this pull request
Apr 20, 2015
Reorder map initialization so 'point' is correctly interpreted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When initializing the type map, the specializations were registered before all of the generic mappings.
When the base class registered the base mappings,
it registered "int" as (^int). Later, when it went to look up type 'point',
it would match this, and think that 'point' was an integer.
This changes it so that the specializations are registered after the generic
ones are, so that when it looks up 'point', it finds these specializations,
instead of finding 'int'