Michael Montague writes:
I believe that include-library-declarations is unnecessary. include (and include-ci) should be able to include library declarations if used at the <library-declaration> level.
If you want to include code (which is not wrapped in a begin) in a library, then use (begin (include <filename>)).
The WG decided by unanimous consent to take no action on this ticket.
While this position is certainly logical, I believe it represents the wrong balance between logic and convenience. Including code is a far more common and basic use case than including further declarations: most libraries do not require the latter feature at all. In addition, Scheme 48's module system, on which the draft's system was founded, has the same semantics for include, which it spells files.