The 'is' function doesn't work on terms

Bug #585724 reported by Matt Giuca
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mars
Fix Released
Low
Matt Giuca

Bug Description

Currently is(x, y) where x and y are terms (values of a user-defined type) just returns 0. This is because interpret.ref_eq_vals has no way of checking the identity of a term. For implementing field set (bug #439171), terms will need to have an extra layer of indirection anyway, so as part of this, fix ref_eq_vals to perform an identity check on the terms.

Also update documentation for is (in impure module), removing the note about this bug.

Tags: interpreter

Related branches

Revision history for this message
Matt Giuca (mgiuca) wrote :

Fixed in trunk r1090.

Changed in mars:
status: Triaged → Fix Committed
Matt Giuca (mgiuca)
Changed in mars:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.