josdejong
  • Joined on 2022-10-05
josdejong commented on issue glen/typocomath#1 2022-12-22 15:18:52 +00:00
How to specify dependencies non-redundantly?

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…

josdejong commented on issue glen/typocomath#1 2022-12-22 14:13:04 +00:00
How to specify dependencies non-redundantly?

Ok in the branch signature_scheme_generic I implemented a new function unequal in /numbers/relational.ts,…

josdejong created branch signature_scheme_generic in glen/typocomath 2022-12-22 14:04:18 +00:00
josdejong pushed to signature_scheme_generic at glen/typocomath 2022-12-22 14:04:18 +00:00
22f114d7f9 feat: implement generic square (WIP)
9aec1bca17 feat: implement function unequal
Compare 2 commits »
josdejong commented on issue glen/typocomath#1 2022-12-22 13:34:53 +00:00
How to specify dependencies non-redundantly?

👍 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…

josdejong commented on issue glen/typocomath#1 2022-12-21 14:22:36 +00:00
How to specify dependencies non-redundantly?

👍

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…

josdejong commented on issue glen/typocomath#1 2022-12-21 08:57:58 +00:00
How to specify dependencies non-redundantly?

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…

josdejong commented on issue glen/typocomath#1 2022-12-16 13:38:45 +00:00
How to specify dependencies non-redundantly?

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…

josdejong commented on issue glen/typocomath#1 2022-12-13 11:57:11 +00:00
How to specify dependencies non-redundantly?

I am planning to use the published typescript-rtti package for this.

o wow, that is exactly what we need 😎

So, trying to understand…

josdejong commented on issue glen/typocomath#1 2022-12-12 11:45:14 +00:00
How to specify dependencies non-redundantly?

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…

josdejong commented on issue glen/pocomath#55 2022-12-02 14:08:51 +00:00
With return types, specifications of implementations are too complicated

👍

The plan there is to make it a template Vector<T> but allow T to be any to cover the inhomogeneous case

👌 that sounds perfect and future proof

josdejong commented on issue glen/pocomath#55 2022-12-02 09:43:58 +00:00
With return types, specifications of implementations are too complicated

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…

josdejong commented on issue glen/pocomath#55 2022-10-18 10:01:17 +00:00
With return types, specifications of implementations are too complicated

Thanks a lot, sounds good. Good luck with finishing your book!

josdejong commented on issue glen/pocomath#55 2022-10-13 15:02:35 +00:00
With return types, specifications of implementations are too complicated

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…

josdejong commented on issue glen/pocomath#55 2022-10-13 12:03:53 +00:00
With return types, specifications of implementations are too complicated

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…

josdejong commented on issue glen/pocomath#55 2022-10-11 09:07:07 +00:00
With return types, specifications of implementations are too complicated

(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…

josdejong commented on issue glen/pocomath#55 2022-10-06 10:53:33 +00:00
With return types, specifications of implementations are too complicated

(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…

josdejong commented on issue glen/pocomath#55 2022-10-05 10:14:15 +00:00
With return types, specifications of implementations are too complicated

So currently we can have up to four nestings I think:

  1. an object with function names as key, and signatures as value (optional)
  2. and object with arguments as key, and a factory function…
josdejong commented on issue glen/pocomath#55 2022-10-05 10:13:55 +00:00
With return types, specifications of implementations are too complicated

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…