Issue 586 in moose-technology: Compute invocation candidates with different strategies seems to be broken

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Issue 586 in moose-technology: Compute invocation candidates with different strategies seems to be broken

moose-technology

Comment #19 on issue 586 by [hidden email]: Compute invocation  
candidates with different strategies seems to be broken
http://code.google.com/p/moose-technology/issues/detail?id=586

indeed :)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 586 in moose-technology: Compute invocation candidates with different strategies seems to be broken

moose-technology

Comment #20 on issue 586 by [hidden email]: Compute invocation  
candidates with different strategies seems to be broken
http://code.google.com/p/moose-technology/issues/detail?id=586

Like previous time, I was just able to implement something that skip the  
problem. RoelTyper-cyrilledelaunay.84.
If the collection is empty, it returns. This make the test pass

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 586 in moose-technology: Compute invocation candidates with different strategies seems to be broken

moose-technology
Updates:
        Status: Fixed

Comment #21 on issue 586 by [hidden email]: Compute invocation  
candidates with different strategies seems to be broken
http://code.google.com/p/moose-technology/issues/detail?id=586

Thanks. It looks like the issue is fixed and it does not throw errors  
anymore. We do not know about the correctness anymore.

One problem we have to look for is that the fix was done in RoelTyper, and  
thus it can have other repercussions in the Pharo-world.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 586 in moose-technology: Compute invocation candidates with different strategies seems to be broken

moose-technology

Comment #22 on issue 586 by [hidden email]: Compute invocation  
candidates with different strategies seems to be broken
http://code.google.com/p/moose-technology/issues/detail?id=586

Cyrille can you explain what was the problem?

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 586 in moose-technology: Compute invocation candidates with different strategies seems to be broken

moose-technology

Comment #23 on issue 586 by [hidden email]: Compute invocation  
candidates with different strategies seems to be broken
http://code.google.com/p/moose-technology/issues/detail?id=586

I don't know what is the problem, I just put a '^self' when encountering  
problematic case (the empty collection). Like my previous change ,  I think  
it does not break anything, but just let RoelTyper less precise for some  
cases (that are not working)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12