Commit e3b0cb52 authored by Robert P. Goldman's avatar Robert P. Goldman
Browse files

Merged the section on what's still wrong with ASDF into the future directions section.

parent b9c9a225
......@@ -347,6 +347,10 @@ sub-bullet under a major header.
**** Would require modifying how DEFSYSTEM is read
**** What about side-effect isolation?
***** See XCVB
*** Make =TRAVERSE= part of the API
**** Pro: Would allow cleaner extensions
......@@ -367,28 +371,25 @@ sub-bullet under a major header.
*** COMMENT --- possible theme here --- having /hierarchical/ plans might make a lot of things easier.
** What is still wrong with ASDF
*** no side-effect isolation
**** see XCVB
*** Configuration is still harder than ideal
*** configuration still harder than ideal
**** We tried to accommodate every previous extension variant.
**** we tried to accommodate every previous extension variant
**** Instead, should we have authoritatively standardized good defaults?
**** instead, we should have authoritatively standardized good defaults?
*** dependency bugs remain
**** Some actually wanted by some people. Others
**** Or does our documentation just stink?
*** FASLs still not separate enough
**** bit us with ASDF 2.006
*** hard to extend
*** The documentation
*** Hard to extend
**** At least partially due to the (lack of) documentation
*** ASDF2 is still not universally available
......
Markdown is supported
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