Have massof(Species()) and chargeof(Species()) throw an error.

[DavidSagan]

Right now, massof(Species()) and chargeof(Species()) just return 0. Throwing an error would make the code much safer. Anyone have any objections?

[rot4te]

No objections. I can do that today.

…

On Jan 7, 2025, at 3:59 PM, David Sagan ***@***.***> wrote: Right now, massof(Species()) and chargeof(Species()) just return 0. Throwing an error would make the code much safer. Anyone have any objections? — Reply to this email directly, view it on GitHub <#121>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APVF2CELJ7YMNVC524W7QDD2JQ53BAVCNFSM6AAAAABUYQJBTKVHI2DSMVQWIX3LMV43ASLTON2WKOZSG43TGNZSGQ4TCMA>. You are receiving this because you are subscribed to this thread.

[rot4te]

Turns out this is a bit weird.
For some reason the definition of massof is now inside the APCdef macro, which I don't think it should be.
Furthermore, it's defined as a constant, rather than a function. This is true for chargeof as well. Did I miss a conversation about this? It makes more sense to me that the massof and chargeof functions get defined with the other particle functions and exported.
I'll do that in a branch and we can talk about it next week