Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / jdantonio/functional-ruby issues and pull requests
#33 - Updated gem dependencies.
Pull Request -
State: closed - Opened by jdantonio over 6 years ago
#32 - fix Protocol documentation typo
Pull Request -
State: closed - Opened by iarie over 6 years ago
#31 - Docs for Either seem backwards
Issue -
State: closed - Opened by mmueller over 8 years ago
- 2 comments
#30 - New feature ideas?
Issue -
State: open - Opened by jdantonio almost 9 years ago
- 3 comments
#29 - Follow conventions in either example
Pull Request -
State: closed - Opened by homburg almost 9 years ago
- 1 comment
#28 - Fix typo
Pull Request -
State: closed - Opened by MaksimAbramchuk almost 9 years ago
- 3 comments
#27 - more strict arguments handling, changed NoMethodError behavior
Pull Request -
State: closed - Opened by cvb almost 9 years ago
- 2 comments
#26 - use example class in protocol spec assertion
Pull Request -
State: closed - Opened by abargnesi about 9 years ago
- 1 comment
#25 - Better synchronization across all classes
Pull Request -
State: closed - Opened by jdantonio about 9 years ago
#24 - Updated min Ruby version and all required gem versions.
Pull Request -
State: closed - Opened by jdantonio about 9 years ago
#23 - Remove require spec helper
Pull Request -
State: closed - Opened by rranelli over 9 years ago
#22 - Fix markdown files embedding in documentation
Pull Request -
State: closed - Opened by rranelli over 9 years ago
- 14 comments
#21 - Support subtypes in type based pattern matching
Issue -
State: closed - Opened by beezee over 9 years ago
- 1 comment
#20 - Rescue in __define_method_with_matching__ obscures execution errors
Issue -
State: closed - Opened by beezee over 9 years ago
- 11 comments
Labels: question
#19 - Improving documentation
Pull Request -
State: closed - Opened by lucasallan almost 10 years ago
- 1 comment
#18 - Records can be declared with a type/protocol specification for type safety.
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
#17 - Roadmap
Issue -
State: open - Opened by jdantonio almost 10 years ago
- 11 comments
#16 - Test 2 concurrent ruby bug
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
#15 - Test of Issue #150 in the concurrent-ruby gem.
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
#14 - Update README.md
Pull Request -
State: closed - Opened by elcuervo almost 10 years ago
- 3 comments
#13 - Update README.md
Pull Request -
State: closed - Opened by elcuervo almost 10 years ago
- 2 comments
#12 - Final var
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
#11 - Tuple
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
#10 - Removed Functional::Final.final_attribute due to unforseen inefficiencies
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
#9 - Implemented ValueStruct
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
- 1 comment
#8 - FinalStruct
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
#7 - Keyword final
Pull Request -
State: closed - Opened by jdantonio almost 10 years ago
#6 - Removed all algorithms (collections, sort, search, etc.) classes.
Pull Request -
State: closed - Opened by jdantonio about 10 years ago
#5 - thoughts on the new README
Issue -
State: closed - Opened by 404pnf about 10 years ago
- 3 comments
Labels: question
#4 - re-implement ascending? and friends, with doc and specs
Pull Request -
State: closed - Opened by 404pnf about 10 years ago
#3 - re-implementing ascending? and friends
Issue -
State: closed - Opened by 404pnf about 10 years ago
- 1 comment
#2 - using built-in Array#bsearch for collection bisect_left; bisect_right
Issue -
State: closed - Opened by 404pnf about 10 years ago
- 5 comments
#1 - using each_cons for collectioin ascending?
Issue -
State: closed - Opened by 404pnf about 10 years ago
- 2 comments