I like the proposal. I also wonder if we shouldn't be able to able to reject nils at Set creation time, as nil rarely makes sense as a set value. bozhidar (Bozhidar Batsov)
For me a big problem is that the syntax additions obviously affect what's being valued/promoted and so on. In the example you gave about the safe navigation operator, the real problem is that `f` could be nil in the first place. When you...bozhidar (Bozhidar Batsov)
> I disagree. To only accept uncontroversial features is the death knell for progress. Design by committee is the last thing Ruby needs. I'm not a fan of design by committee as well. I was referring to the fact he seemed unhappy with ...bozhidar (Bozhidar Batsov)
> I definitely prefer @1 over %1 for Ruby, because for me it 'rhymes' with @instance_var and @@class_var, as jeremyevans0 has explained. That's why I dislike it so much. Block vars would ideally not look like class/instance vars. Apar...bozhidar (Bozhidar Batsov)
> $it can already be defined, so this is not backwards compatible. It can, but that's extremely unlikely, so I think the impact to backwards compatibility would be negligible. I've almost never seen anyone define globals themselves. I...bozhidar (Bozhidar Batsov)
> While I'm not totally against your opinion, I would like you to understand that this feature was not made out of thin air; it was feature requested. People think this is a neat feature. If you are against the feature itself not against...bozhidar (Bozhidar Batsov)
I also dislike the use of `@` for this. It looks very weird and evokes strong references to instance variables in my mind. I'm not sure which characters exactly are an option, but I think we should avoid the use of `@`. Will something li...bozhidar (Bozhidar Batsov)
jeremyevans0 (Jeremy Evans) wrote: > bozhidar (Bozhidar Batsov) wrote: > ... Yeah, I completely agree with you. Excellent point about using `size` in different contexts! Generally I'm not trying to suggest changes for the sake of makin...bozhidar (Bozhidar Batsov)
bozhidar (Bozhidar Batsov) wrote: > phluid61 (Matthew Kerwin) wrote: > ... Also I'm curious who'd claim that adding an empty method doesn't make sense for something like `Tempfile` or `StringIO`. bozhidar (Bozhidar Batsov)
phluid61 (Matthew Kerwin) wrote: > mikegee (Michael Gee) wrote: > ... Yeah, in this case I'd argue that it's better to use some `top-level` methods of `File` instead, but in general every object that has the notion of size should also ...bozhidar (Bozhidar Batsov)
bozhidar (Bozhidar Batsov)09:41 AM Ruby Feature #17208: Add `Set#compact` and `Set#compact!` methods