[pypy-dev] thunk object space : become() quirks

[Boris Borcic]

Carl Friedrich Bolz wrote:
> Hi Boris,
> 
> Carl Friedrich Bolz wrote:
>> Boris Borcic wrote:
>>> Looking for a way to use pypy in any manner, I came up with an idea for a
>>> deterministic sudoku solver that would use the 'become()' feature of the thunk
>>> object space. However, this doesn't work as I expected. The following shell
>>> trace illustrates my problem. Is this a bug or otherwise ? Can anybody explain ?
>>>
>>> BTW, I am using the pypy 1.0.0 build 41438 windows binary distribution.
>>>
>>> [subquestion : is pypy-dev appropriate for such a question ?]
>> It's a bug, I have a clue where it is and will try to fix it. Thanks for 
>> reporting! Yes, the list is completely appropriate.
> 
> Some updates on this thing: We discussed the problem extensively on the 
> sprint and the think is that this shows a serious problem with the way 
> the thunk object space is done. We have no concrete clue how to solve it 
> yet. Thunks themselves are also affected by this bug, but only in more 
> extreme situations.
> 
> I created an issue in the bug tracker for this:
> 
> https://codespeak.net/issue/pypy-dev/issue332

Well, I wouldn't have recognized the issue if you hadn't told me it's the same 
:) Thanks for the followup, glad to be of some help, sorry for the seriousness 
of the problem. Mmmh... I was going to ask whether it made sense for me to try 
implementing my algorithm idea with unification from the logic object space 
instead, but the (doc for the) latter seems to have vanished (while a surprise 
Prolog interpreter popped up, to be sure; fun stuff).

Best regards, Boris