wanted: Add :TIMEOUT to all potentially blocking operations.

Bug #721452 reported by William Halliburton
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
SBCL
Triaged
Wishlist
Unassigned

Bug Description

From the TODO:

TIMEOUTS

  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: feature
tags: removed: low
Changed in sbcl:
importance: Undecided → Medium
status: New → Triaged
Changed in sbcl:
assignee: nobody → Nikodemus Siivola (nikodemus)
Revision history for this message
Nikodemus Siivola (nikodemus) wrote :

Done for threading stuff.

Blocking reads still exist.

Changed in sbcl:
assignee: Nikodemus Siivola (nikodemus) → nobody
Revision history for this message
Nikodemus Siivola (nikodemus) wrote :

(And writes for that matter.)

Douglas Katzman (dougk)
Changed in sbcl:
importance: Medium → Wishlist
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.