I will see if I can get it to type properly. Should I branch again from signature_scheme_generic or add a commit to it?
Yes please, feel free to edit the branch and merge it into `signature_sc…
Ok in the branch signature_scheme_generic I implemented a new function unequal
in /numbers/relational.ts
,…
👍 yeah let's iterate a bit more on the two approaches, and when all is clear, summarize the main differences in a comparison table and discuss the pros/cons of each.
Let me try to add a…
👍
I've started a POC where I convert pocomath JS straight into "basic" TS. It works like a charm as far as I can see, but I may be overlooking something. Can you have a look at it? Please…
Having to define declare module "../core/Dispatcher"
once per module instead of for every function is a big win indeed!
I've had a look at signature_scheme
. Defining the implementations and…
Thanks, I better understand your concerns now.
So you see, there is an explosion of type declarations we need, for all combinations of argument types that clients of the operation might…
I am planning to use the published typescript-rtti package for this.
o wow, that is exactly what we need 😎
So, trying to understand…
Thanks Glen for starting the prototype!
(A) I do not yet fully understand your approach, I suspect I'm two steps behind where you are already and missing something.
To make sure we're on…
👍
The plan there is to make it a template
Vector<T>
but allowT
to beany
to cover the inhomogeneous case
👌 that sounds perfect and future proof
whoooow, that is unbelievable! Man, that refactoring will be totally worth it! Not only a much better architecture, but also better performance 😄 Please get yourself a beer on my cost. I…
Thanks a lot, sounds good. Good luck with finishing your book!
About NumInt: sounds good to try it out in the prototype to see how it works out, thanks.
Thanks for your explanation, I think I understand what you mean. To me, having something like…
I am unclear where you've landed as far as whether mathjs types should be restricted to correspond precisely to TypeScript types.
At this moment I do not have a clear overview of where…
(f) from a functional point of view dynamic return types based on config are indeed no problem: it works already in pocomath (on a side note... it's impressive that you got all of this…
(f) Hmm. Yes I'm starting to understand the difficulties you mention regarding return types and TypeScript. Would it be even possible to determine the return types statically at all, when…
So currently we can have up to four nestings I think:
- an object with function names as key, and signatures as value (optional)
- and object with arguments as key, and a factory function…
Yes, interesting thoughts.
it's the argument types that are unique among implementations
This is indeed true, but I think pocomath can just guard against this and throw an error when…