A few improvements #13
Open
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
Also allows Torrent constructor to consume a block Adds comparable methods to determine if a torrent is equal to others Adds a Torrent.from_file function to read in torrent files and populate Torrent objects. Makes set_infohash be invoked by build
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.
Adds the ability to use blocks within the initializers for instances.
Adds Torrent.from_file to create an object based on the contents of a file
Removes version constraint on Rake and makes it a development dependency rather than an install dependency (this breaks when it interacts with other gems that rely on rake, it's not needed at run-time).
Adds the comparable interface, so you can tell if one torrent is equal to another, either because the info segment is the same (via == ) (they have the same files) or because the whole torrent hash is the same (via eql?) (they share tracker information as well).
Removes nil.empty? conflicts for when you are not running this against rails environments