On Sat, Sep 13, 2008 at 02:30:30PM +0200, Jonathan Worthington wrote:
>>> (2) Test.pm gets Object rather than Any on its multis; this may or 
>>> may not be the Right Thing.     
>> perl6-language may end up disagreeing with me on this, but I would
>> much prefer things (from a implementation bootstrapping perspective)
>> if Test.pm didn't rely on type checking and Junctions in order to work 
>> properly.  
>>   
> Yes - I think you're right. It did it so we could keep on passing the  
> junction tests for the time being. We can either:
>
> * Rely on auto-threading, once the dispatcher handles that, to thread  
> calls into Test.pm for us [...]
>
> * Modify the junctions tests to make sure they never will pass a  
> junction into Test.pm. If Test.pm isn't to have to handle junctions,  
> then I suspect this is our best option.

Personally I greatly prefer this second option (modify the junction 
tests) -- I'd like the tests to be explicit about what they're 
testing and not rely on specific behaviors of the testing 
functions or parameter passing.

> Of course, we can also remove Object now and stop running the junctions  
> tests too. But I thought it better to put something in place, even if  
> temporary, to keep us passing them for the time being while the Right  
> Answer was worked out. 

Sure, I agree -- I just wanted to get my comments in the email record
(and maybe prompt some discussion on p6l about what the Right Thing
should be).

>>> (3) Because Parrot doesn't yet give us a way to type-map MultiSub,  
>>> and because we're not using .HLL yet anyway, we need to do a  
>>> workaround in a block's loadinit.
>>
>> Instead of having a special '!TOPERL6MULTISUB' function, could
>> this be done instead with 'morph'?  
>> [...]
>
> I was expecting that we'd HLL map MultiSub and just get the correct type  
> in the first place, rather than having to fix it up later (since fixing  
> it up later is runtime cost, which feels like something we shouldn't  
> need for this). 

If it maps correctly on load in the first place, that's definitely
better.  I don't know if HLL_map can handle this or be made to handle
it.  (Regardless, we end up with runtime cost on our subs anyway to
be able to get everything into the correct namespaces.)

Pm

Reply via email to