functions

daamath maintains collections of functions that are called typically as op(a, b, …). they may sometimes be called operators.

functions in daamath are actually thin wrappers that call the corresponding function definition in dm.context.

functions will always have a fixed arity (take a certain number of arguments) and will never be overloaded to change behaviour depending on different warities. why?

have you tried debugging log(y/8*(49-1)+1,49) and wondered 'why is this scaled weirdly?', only to realize after painful eye strain that its not log with base e. there is a second argument giving base=49. the problem was that the function changed behaviour depending on arity, and it was hard to read the arity by eye. we should guarantee that log always takes two arguments, and that the one-argument version of log (like ln, log2, log10) should always make their base clear. that way, there is no confusion of 'is this log taking base or not?' because you can see from the function name directly.

context and function behaviour

daamath maintains a .context object that determines idfk

function sets

daamath maintains mathematically defined functions, as well as some numerically inclined functions such as from IEEE 754

rant

note to self: the arithmetic, trigonometry, logic, and interval function sets are done. quantize and variadic are not done. i hate that they are hard to define or grasp. this is tough