Confusing error messages for vector-set!/vector-ref

Bug #313459 reported by leppie
2
Affects Status Importance Assigned to Milestone
Ikarus Scheme
Fix Committed
Medium
Abdulaziz Ghuloum

Bug Description

Both of these are a bit confusing:

> (vector-set! (vector 0) 0.0 #f)
Unhandled exception
 Condition components:
   1. &assertion
   2. &who: bitwise-and
   3. &message: "not an exact integer"
   4. &irritants: (-1.0)

> (vector-ref (vector 0) 0.0)
Unhandled exception
 Condition components:
   1. &assertion
   2. &who: vector-ref
   3. &message: "not a valid index"
   4. &irritants: (0.0)

Related branches

Revision history for this message
Abdulaziz Ghuloum (aghuloum) wrote :

The first error for vector-set! was a compile-time error, and is fixed in revision 1737.

What's wrong with the second (vector-ref) error?

Changed in ikarus:
assignee: nobody → aghuloum
importance: Undecided → Medium
milestone: none → 0.0.4
status: New → Fix Committed
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.