-
Notifications
You must be signed in to change notification settings - Fork 14
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
Scan for conflicts in internal functions? #108
Comments
Yeah, this indicates a problem with the psych package. It's unfortunately outside of the scope of conflicted. |
Might there be a way for automatically checking/knowing what went wrong? Somehow I had the impression that this class of bugs was supposed to be impossible--it makes me worry if there might be other combinations of packages that are affecting each other in ways that not even |
@emstruong it is generally impossible. The fact that psych is experiencing suggests that it's using some sort of custom evaluation mechanism or something is wrong with its namespace. It's a not a widespread problem that you need to worry about. |
Alright, well I'm convinced by that--thanks! |
Hello,
This is related to this
I'm not sure how to describe the issue, but is there a way to scan for conflicts in the internal functions of libraries?
Please see the following reprexes:
This works
Created on 2024-02-25 with reprex v2.1.0
Session info
But this doesn't
Created on 2024-02-25 with reprex v2.1.0
Session info
I don't know the right terminology to use, but I thought conflicts in the internal functions were supposed to be impossible or else you'd have no idea whether the combination of packages you've loaded may have led to computational irreproducibility. It also makes testing for correctness of results very difficult...
The text was updated successfully, but these errors were encountered: