ASDF Self Upgrades Broken on SBCL 2.0.1
This is related to !131 (merged). A consequence of #+ emitting a full warning if sb-eval is tested for is that, with default settings, ASDF can no longer self upgrade on SBCL 2.0.1 without error. Working around it requires either having the !131 (merged) patch, setting
uiop:*compile-file-error-behaviour* to something other than :error, or choosing the accept restart.
Should something be done about this? For the short term, the only options I can think of are to cut a new release so that users don't have to use a devel version to get an error free experience and/or make an announcement on the mailing lists to try and spread awareness.
For the long term, perhaps ASDF self upgrades should bind
uiop:*compile-file-error-behaviour* to :warn?
A minor side note is that until SBCL upgrades its bundled version of ASDF,
sb-kernel:lexical-environment-too-complex won't be on the list of usual uninteresting conditions, even after a successful self upgrade, even with !131 (merged).