Runtime-optimized Subclass Namespaces #298
Merged
Conversation
This file contains hidden or 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
jdantonio
added
enhancement
Member
Author
Member
|
👍 |
jdantonio
added a commit
that referenced
this pull request
May 16, 2015
Runtime-optimized Subclass Namespaces
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.
Addresses #261
With this release we've developed a new convention for declaring runtime-optimized classes. This first class to follow this convention was
Synchronization::Object. This updates the following classes to use this convention:NOTE: ExecutorService does not follow this convention because it does not follow this pattern. It is a completely different module/class configuration in which only the names are similar.