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

Consider alternative implementations #79

Open
propensive opened this issue Dec 2, 2024 · 0 comments
Open

Consider alternative implementations #79

propensive opened this issue Dec 2, 2024 · 0 comments
Assignees
Labels
api Relates to the API design code quality Concerns the standard of code rather than functionality severe Has a significant impact on many users

Comments

@propensive
Copy link
Owner

Several of the original uses of Contextual have been subsequently replaced with macros which operate directly on the StringContext and parts values. The motivation for using Contextual was that macros are hard to use, and they could be avoided. But the use of interpolator objects forces a more complex model for each implementation, which really isn't necessary if you understand macros.

So, we should entertain the idea of chucking out the Interpolator code, and just making it easier to implement each macro as per #78.

@propensive propensive self-assigned this Dec 2, 2024
@propensive propensive added api Relates to the API design code quality Concerns the standard of code rather than functionality severe Has a significant impact on many users labels Dec 2, 2024
@github-project-automation github-project-automation bot moved this to Todo in Soundness Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Relates to the API design code quality Concerns the standard of code rather than functionality severe Has a significant impact on many users
Projects
Status: Todo
Development

No branches or pull requests

1 participant