I still have uses for Durations.
For instance, I want to dispatch a different .Stringy method to Durations than
to Nums. It's convenient to me that the difference between two Instants has a
different type than the difference between 1654321681.123 and 1654321021.65438.
I just think Durations
I understand everything you've written except the following:
On Nov 13, 2010, at 12:09 PM, Jonathan Worthington wrote:
> Hi,
> ...
>
> my Int @x;
>
> Where we get an array of scalar containers, each of which is only allowed to
> contain an Int (strictly, something that Int.ACCEPTS(...) hands
I'm honored that my letter generated so much activity, and thank you all for
your thoughtful responses. I'd like to address a few points.
> On Monday, 8. November 2010 17:20:43 Jon Lang wrote:
>> Solomon Foster wrote:
>>> Well, hyperoperators work fine on Hashes, they operate on the values,
>>>
I just implemented Bag to the point where it passes the spectests.
(https://github.com/masonk/rakudo/commit/2668178c6ba90863538ea74cfdd287684a20c520)
However, in doing so, I discovered that I'm not really sure what Bags are
for, anymore.
The more I think about Bags and Sets, the more my brain
Sorry:
I meant capable *in theory*. It's not in the spec right now for Sets or Bags.
On Oct 25, 2010, at 08:41 PM, Mason Kramer wrote:
> That sounds like a subclass of Bag to me.
>
> But I don't think that thinking about who is subclassing whom is is how to
> think abou
That sounds like a subclass of Bag to me.
But I don't think that thinking about who is subclassing whom is is how to
think about this in Perl 6. All of these types are capable of doing the
Iterable role, and that is what methods that could operate on a List, Array,
Bag, or Set, should be calli
