Commit 545ab9ff authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files

Remove operation-forced altogether

It was never exported or officially supported. Only SLIME was (ab)using it,
and even cheating it was failing at its purpose.
In gitlab merge request !33 Robert Goldman decided to just get rid of it.
SLIME users, if you use swank.asd, please update your SLIME from git.
parent a52afa09
......@@ -12,7 +12,6 @@
#:error-component #:error-operation #:traverse
#:operation-on-failure #:operation-on-warnings #:on-failure #:on-warnings
......@@ -41,22 +40,6 @@
;; Old deprecated name for the same thing. Please update your software.
(component-sideway-dependencies component))
(defun* (operation-forced) (operation)
"DEPRECATED. Assume it's (constantly nil) instead -- until it disappears."
;; This function exists for backward compatibility with swank.asd, its only user,
;; that still abuses it as of 2016-10-01.
;; The magic PERFORM method in swank.asd only actually loads swank if it sees
;; that the operation was forced. But it actually fails, badly, in that case.
;; The correctness criterion for a build specification (which is _not_
;; specific to ASDF) requires that the effects of a build step must NOT depend
;; on whether the step was "forced" or not. Therefore it is correct that this
;; method should return constantly the same result. Since returning T currently
;; causes massive failure in SLIME, it shall be constantly NIL.
;; see also
(declare (ignore operation))
;; These old interfaces from ASDF1 have never been very meaningful
;; but are still used in obscure places.
(defgeneric operation-on-warnings (operation)
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment