Ruby Issue Tracking System

06/30/2017

02:01 PM Ruby Feature #13683: Add strict Enumerable#single

nobu (Nobuyoshi Nakada) wrote:
> `Enumerable#first` returns not only the first element, the elements at the beginning up to the number given by an optional argument.
> ...
The purpose of the `single` suggested is to return one and only... dnagir (Dmytrii Nagirniak)

01:57 PM Ruby Feature #13683: Add strict Enumerable#single

shevegen (Robert A. Heiler) wrote:
> What would the results be for the following code?
I would expect the following:
```ruby
[].single # => error
[1].single # =>1
[1,2].single # => error
[1,2,3].single # => error

{}.single... dnagir (Dmytrii Nagirniak)

06/27/2017

06:08 AM Ruby Feature #13683 (Feedback): Add strict Enumerable#single

### Summary
This is inspired by other languages and frameworks, such as LINQ's [Single](https://msdn.microsoft.com/en-us/library/bb155325%28v=vs.110%29.aspx) (pardon MSDN reference), which has very big distinction between `first` and ... dnagir (Dmytrii Nagirniak)

06/12/2011

07:40 PM Ruby Bug #4821: Random Segfaults (in start_thread?)

It seems the problem is related to the `therubyracer` gem. If I remove it, no errors occur. I'll lodge bug there. Would be nice if it could be confirmed. dnagir (Dmytrii Nagirniak)

07:09 PM Ruby Bug #4821: Random Segfaults (in start_thread?)

It looks like I have the same (or very similar issue) in Rails 3.1.0.rc1-4.
I was trying to run request specs using Capybara from source and sprockets.
Attaching the Gemfile.lock with all the dependencies used and the terminal output. dnagir (Dmytrii Nagirniak)