-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
full_name function broken #107
Comments
Fixed in the full_name_fix PR |
@rot4te |
Very odd. In my environment it works for everything. Nameof is also exported by Julia.base, so full_name is an easier choice.
… On Dec 12, 2024, at 2:20 PM, David Sagan ***@***.***> wrote:
@rot4te <https://github.com/rot4te> full_name still is broken for atomic species (but sub-atomic is OK). Also changing the name of the function to nameof would be in keeping with the naming of the other functions.
—
Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APVF2CGXE3534IHP66A6QB32FHOZJAVCNFSM6AAAAABTAWTFLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZZHAZDSMJYGQ>.
You are receiving this because you were mentioned.
|
@rot4te Looks like the problem is that in the
is trying to compare |
Yes, and I fixed that (by species.charge.val == -1) locally, and thought it was included in my push. Guess I’ll check it again.
… On Dec 12, 2024, at 3:23 PM, David Sagan ***@***.***> wrote:
@rot4te <https://github.com/rot4te> Looks like the problem is that in the full_name function something like:
elseif species.charge == -1
is trying to compare species.charge which has units with -1 which does not have units.
—
Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APVF2CA2C5DPEXOERM4L3C32FHWFPAVCNFSM6AAAAABTAWTFLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZZHE2DMMJXGU>.
You are receiving this because you were mentioned.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: