Conversation
jonringer
force-pushed
the
deprecate-spliced-packages
branch
from
January 4, 2026 05:45
08c0c4a to
7811ae3
Compare
jonringer
changed the title
jonringer
force-pushed
the
deprecate-spliced-packages
branch
from
January 4, 2026 05:50
7811ae3 to
8439fd6
Compare
jonringer
marked this pull request as draft
January 4, 2026 05:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Try to remedy ergonomic issues around mkManyVariants and splice packages by moving toward explicit spliced scope usage and migrate to overriding on how the package is used rather than it being an "input" to "function call".
Rendered: https://github.com/ekala-project/eeps/blob/deprecate-spliced-packages/eeps/0038-deprecate-spliced-packages.md