Skip to content

Follow ASDF3 guideline of a single primary system per .asd file #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Uthar
Copy link

@Uthar Uthar commented Jan 10, 2025

ASDF3 recommends declaring a single primary system per .asd file (e.g., FOO), with other, optional subsystems being named with a slash (e.g., FOO/BAR). This ensures that FOO/BAR can be loaded without first having to manually load FOO, as would be the case with e.g. FOO-BAR (ASDF would look for it in a non-existent foo-bar.asd).

See: info asdf find-system

(Bonus: visual clean-ups)

Uthar added 2 commits January 11, 2025 00:34
ASDF3 recommends a single primary system per .asd file (e.g., FOO), with other,
optional subsystems being named with a slash (e.g., FOO/BAR). This ensures that
FOO/BAR can be loaded without first having to manually load FOO, as would be the
case with e.g. FOO-BAR (ASDF would look for it in a non-existent 'foo-bar.asd').

See: info asdf find-system

(bonus: visual clean-ups)
@Uthar
Copy link
Author

Uthar commented Jan 10, 2025

Please check the last commit, where I picked the BSD-3-Clause license which was set in 2013 - probably the BSD-2-Clause license from README was not removed around then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant