rename Singleton to SupSingleton to sidestep conflicts with ruby's Singleton #271
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
|
frankly, i am not happy with the name SupSingleton, Couldn't Sup's Singleton be placed inside the Redwood module and then used as Redwood::Singleton or Util::Singleton (if we make an Util module instead)? |
|
|
|
My ruby-fu is weak. I thought having a |
|
Proposition of revert and fix in #275 |
|
i am new to ruby, and i pushed SupSingleton mostly to show you what i am working on. i didn't expect it to be merged so fast :-) |
gauteh
added a commit
that referenced
this pull request
Mar 27, 2014
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.
@eMBee's conversion from Singleton to SupSingleton to make sure there is no conflict with Rubys orignal. The Mail library uses Rubys and things get a little messed up.