Ronan Lamy <[email protected]> added the comment: That kind of user error should be caught earlier, in the annotation stage, where we already have the machinery in place to give sensible feedback to the user. More precisely, we should define the annotation of op.eq(<string>, <unicode>) to raise an AnnotationError.
Also, this issue is an instance of a more general problem: we should define clearly RPython's behaviour when comparing objects of incompatible types. ---------- nosy: +rlamy status: unread -> chatting ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1689> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-issue
