Hi Akash, 1.) Sets module is clearly is a dependence for the solveset module, the output of solveset of set and the module also make heavy use of a lot of functionalities of Sets including intersection, union and especially imageset. SymPy's set are **very** flexible and we aim to have the capability to represent every set possible. My limited knowledge in C++ tells me that it might be hard to achieve the flexibility set module in it, you should discuss the details with Ondrej and other people involved with Symengine.
2.) We had to go through a lot of discussion to designing the right input and output API, we have tried to document those decisions here https://github.com/sympy/sympy/blob/master/doc/src/modules/solvers/solveset.rst BTW I don't think solveset is mature enough to be ported to symengine, but porting the sets module to symengine definitely seems like a good idea. On 26 February 2016 at 13:53, Akash Trehan <[email protected]> wrote: > Hi Harsh > > I'm Akash Trehan. > I'm proposing to implement the solveset module in Symengine this GSoC. I > found out that you started solveset in sympy. I wanted some help on certain > things, > 1) How much of the Sets module is being used for solveset? > 2) What were the problems faces in starting a new module? > > Thanks, > Akash > -- Harsh Sent from a GNU/Linux -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CADN8iup7ZhTR1E1Mmtioc54TmOajvkbSNBObJgKps3KHY4uxFg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
