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

FEAT: Deprecate implication #176

Closed
andreas-zeller opened this issue Dec 17, 2024 · 0 comments
Closed

FEAT: Deprecate implication #176

andreas-zeller opened this issue Dec 17, 2024 · 0 comments
Assignees
Labels
prio: low Low priority issue scope: enhancement New feature or request status: future work Task is planned for the future

Comments

@andreas-zeller
Copy link
Collaborator

Since

int(<foo>) > 0 -> int(<bar>) > 0

can also be expressed as

not int(<foo>) > 0 or int(<bar>) > 0

there should be no need for an extra implication operator; we should mark it as deprecated.

@andreas-zeller andreas-zeller added the prio: high High priority issue label Dec 17, 2024
@joszamama joszamama changed the title Deprecate implication FEAT: Deprecate implication Jan 14, 2025
@joszamama joszamama added the scope: enhancement New feature or request label Jan 14, 2025
@joszamama joszamama moved this to Backlog in Fandango Roadmap Jan 14, 2025
@joszamama joszamama added status: future work Task is planned for the future prio: low Low priority issue and removed prio: high High priority issue labels Jan 14, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in Fandango Roadmap Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio: low Low priority issue scope: enhancement New feature or request status: future work Task is planned for the future
Projects
Status: Done
Development

No branches or pull requests

3 participants