adp90 (Alexander Patrick)
- Login: adp90
- Email: adp90@case.edu
- Registered on: 08/05/2017
- Last sign in: 08/05/2017
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 0 | 0 |
Activity
08/12/2017
-
02:53 PM Ruby Feature #13795: Hash#select return type does not match Hash#find_all
- Changing the behavior of Hash#select/reject broke a lot of files, some in [very strange ways](https://travis-ci.org/ruby/ruby/builds/263508096?utm_source=github_status&utm_medium=notification).
This makes me think that such a change w...
08/11/2017
-
- I made a pull request: https://github.com/ruby/ruby/pull/1674
08/10/2017
-
- davidarnold (David Arnold) wrote:
> If there is a convention where every class that includes Enumerable has to have a set of functions that returns an instance of the same class, you wouldn't just have to implement #each, you'd have to ...
08/09/2017
-
- davidarnold (David Arnold) wrote:
> Ruby has been not backwards-compatible in several releases, so I don't see that as a reason per se to not entertain the two proposals.
You have a good point. This wouldn't be a big problem.
I wo... -
- This might make the next version of Ruby not backwards-compatible in some instances. It might be better to leave the methods as they are.
There are instances where aliases to the same C functions act differently, such as lazy_super (a... -
- davidarnold (David Arnold) wrote:
> For the purpose of this feature request, I would leave the filter == find_all behavior the same. If the decision in the bug report is that Hash#find_all should match Hash#select, then an alias can be...
08/08/2017
-
- A potential concern could be language bloat. Having too many aliases for the same methods could be confusing.
I was curious which underlying methods have the most aliases, so I wrote a quick script to look through the code.
[C method...
08/05/2017
-
- I made a pull request: https://github.com/ruby/ruby/pull/1672.