wanted: Add :TIMEOUT to all potentially blocking operations.

Bug #721452 reported by William Halliburton on 2011-02-18
This bug affects 4 people
Affects Status Importance Assigned to Milestone

Bug Description

From the TODO:


  Asyncronous unwinds suck horribly, but to implement reliable systems
  one simply needs timeouts. These should probably be local, since
  otherwise they effectively become asynchronous unwinds. Basically,
  for any potentially blocking operation there should be a :TIMEOUT
  arguent (or a version of the operation that accepts the argument).

tags: removed: low
Changed in sbcl:
importance: Undecided → Medium
status: New → Triaged
Changed in sbcl:
assignee: nobody → Nikodemus Siivola (nikodemus)
Nikodemus Siivola (nikodemus) wrote :

Done for threading stuff.

Blocking reads still exist.

Changed in sbcl:
assignee: Nikodemus Siivola (nikodemus) → nobody
Nikodemus Siivola (nikodemus) wrote :

(And writes for that matter.)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers