Skip to content
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

Refactors in configuration-layer #16351

Conversation

bcc32
Copy link
Collaborator

@bcc32 bcc32 commented Apr 4, 2024

This PR just contains some behavior-preserving refactors in
core-configuration-layer.el, as part of preparing to address #16346.

@bcc32 bcc32 force-pushed the preparatory-refactors-in-configuration-layer branch from a008518 to 7dc6553 Compare April 4, 2024 01:26
bcc32 added 4 commits April 3, 2024 21:28
string< can be used directly with symbols.
This makes its calling convention consistent with
cfgl-package-enabled-p and so on.
This should have no real behavior change, except that the predicate
functions may not be called on all elements of the input list if it
returns nil on an earlier one.
@bcc32 bcc32 force-pushed the preparatory-refactors-in-configuration-layer branch from 7dc6553 to fca0b53 Compare April 4, 2024 01:28
@smile13241324 smile13241324 merged commit 8a3c09c into syl20bnr:develop May 11, 2024
8 checks passed
@bcc32 bcc32 deleted the preparatory-refactors-in-configuration-layer branch May 14, 2024 03:56
2ynn pushed a commit to 2ynn/spacemacs that referenced this pull request Jul 8, 2024
* [configuration-layer] Simplify configuration-layer//sort-packages

string< can be used directly with symbols.

* [configuration-layer] Simplify configuration-layer//filter-objects

* cfgl-package-used-p: Add inhibit-messages argument

This makes its calling convention consistent with
cfgl-package-enabled-p and so on.

* [core-configuration-layer] Refactor to use cl-every

This should have no real behavior change, except that the predicate
functions may not be called on all elements of the input list if it
returns nil on an earlier one.
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.

2 participants