Alternative for `releaseable?` that doesn't always evaluate to `true`. by EvenMoreIrrelevance · Pull Request #2 · uncomplicate/commons · GitHub
Skip to content

Alternative for releaseable? that doesn't always evaluate to true. - #2

Open
EvenMoreIrrelevance wants to merge 2 commits into
uncomplicate:masterfrom
EvenMoreIrrelevance:master
Open

EvenMoreIrrelevance wants to merge 2 commits into
uncomplicate:masterfrom
EvenMoreIrrelevance:master

Conversation

@EvenMoreIrrelevance

Copy link
Copy Markdown

Due to how satisfies? works and due to Object and nil implementations being defined for Release, release? effectively is a clone of any? under any sensible circumstances.

Simply altering releaseable? is a breaking change, so this pull request introduces a nontrivially-releaseable? fn which checks if the object isn't nil and if its implementation is different from Object's and a note about it in release?'s docs.

@blueberry

blueberry commented Jan 29, 2025 •

Copy link
Copy Markdown
Member

@EvenMoreIrrelevance

EvenMoreIrrelevance commented Jan 29, 2025 •

Copy link
Copy Markdown
Author

Searching for releaseable?, releaseable_QMARK_ or looking for usages of (satisfies? Releaseable ...) didn't yield any usage results in all uncomplicate repos (somewhat expected honestly).

@blueberry

Copy link
Copy Markdown
Member

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