Shugo Maeda wrote: > Monkey-patching style has another problem that super cannot be supported in monkey patching. > ... That last line just clicked with me, and I see old problem. This only works at one level. How would one write a ref...trans (Thomas Sawyer)
This definition of `#sample` seems a bit limited. I know it aligns with the statical definition but it is very easy do another way: `shuffle.take(n)`. Also, the interface is a little odd because it can return an element or an Array. Mayb...trans (Thomas Sawyer)
Has any more thought been given to this? I had a recent request to have Ruby Facets to work as refinements, but I hesitate b/c it literally means creating a second copy of every extension method. trans (Thomas Sawyer)
It would more interesting if there were a way to declare an object mutable or not, then when immutable destructive methods would not be available.trans (Thomas Sawyer)
It would be nice if bang methods returned results that where of some additional use. Presently most just return the effected receiver. For example, currently Array#reject! works as follows: a = [1,2,3,4] a.reject!{ |x| x %...trans (Thomas Sawyer)
Philip Claren wrote: > Thomas Sawyer wrote: > ... Is allowing false necessary/useful? On the other hand, if it is, then might a nil-only ternary operator be useful too (regardless of this issue)? trans (Thomas Sawyer)
Laurentiu Macovei wrote: > The same discussion happens to be on TypeScript and ES6 worlds. > ... `..` wouldn't work. But that reminds me. Was `!` ever considered? u!profile!thumbnails!large trans (Thomas Sawyer)
Yukihiro Matsumoto wrote: > I like the idea. My remaining concern is ".?" is too similar to "?." which is chosen by other languages. > ... Maybe there is a better syntax by requiring a space:
That's the irony. One of the reasons I choose #b is because I thought for sure that would almost certainly never become a conflict in the future. I would expect #base to be a much more likely vector for clashing. Giving this more thou...trans (Thomas Sawyer)