Landon Curt Noll

Some care would need to be used in determining which constants were pre-defined and what values they would have. Consider these lists of constants: * [Wikipedia Mathematical constants](https://en.wikipedia.org/wiki/Mathematical_constant) and [Wikipedia...

> Yes, the SI (i.e. MKS) units are probably the best. > > I still suspect some sort of namespacing might be best for most things other than e or...

> I was thinking more of something like `math.phi` (for the golden ratio) and `physics.G` (for the gravitational constant) myself. Maybe `pi` and `e` are too common for that, but...

> Presumably, when the constants are assigned to variables, they will "will" no properties for their assignees to "inherit". Correct. The variables will have numerical values (rational (NUMBER) or complex...

> My # 1 as in main or primary, not issue #1 that was resolve in 2018. 😁 > requirement to package calc as a Qt/C++ object is to sandbox...

> `e` and `pi` are clearly too common to want to have qualified, but `G` or `k_b` (Boltzmann's constant) might not be common enough to want in the main namespace...

> Alternate (and elegant) solution to my initial "inheritance" issue. Control of "inheritance" still a good feature. Interesting point, @kcrossen. Calc does have the concept of scope. Consider a valuable...

> Without JIT, pure interpreted code is very slow. As @pmetzger said on my thread, it's about more than 40 minutes to complete. With JIT, it only took a few...

> `https://github.com/notifications/unsubscribe-auth/` > > To @kcrossen: Consider stopping answering by email without removing this link, anyone can click on it and unsubscribe you. I agree with you, @ilyakurdyukov. FYI: @kcrossen:...

> I don't understand what you said. With JIT, everything is compiled on the fly when you executing the code. Nothing to save and restore here. Sorry, we responded to...