Google Summer of Code - New Trait Implementation
Hello, I am planning in working in a new Traits implementation, the idea is to have an implementation that can work as a loadable module. So you can use it or not as another library. Also the idea is improve the support of all the tools by improving the polymorphism between traits and classes. Clean up a little the API and add support to have stateful traits. I would like to know if you have any suggestion or have a problem that I could try to solve. I have been talking with some people in the community to get ideas, but always having more opinions is better. Thanks in advance. Pablo -- Pablo Tesone. tesonep@gmail.com
go go go go On Fri, Mar 31, 2017 at 2:14 PM, tesonep@gmail.com <tesonep@gmail.com> wrote:
Hello,
I am planning in working in a new Traits implementation, the idea is to have an implementation that can work as a loadable module. So you can use it or not as another library.
Also the idea is improve the support of all the tools by improving the polymorphism between traits and classes. Clean up a little the API and add support to have stateful traits.
I would like to know if you have any suggestion or have a problem that I could try to solve. I have been talking with some people in the community to get ideas, but always having more opinions is better.
Thanks in advance. Pablo
-- Pablo Tesone. tesonep@gmail.com
Hey Pablo Great idea ! Submit your proposal ASAP at summerofcode.withgoogle.com for review and feedback. Good luck :) Best Jigyasa Grover GSoC 2017 Org Admin, Pharo Consortium On Fri, Mar 31, 2017 at 6:26 PM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
go go go go
On Fri, Mar 31, 2017 at 2:14 PM, tesonep@gmail.com <tesonep@gmail.com> wrote:
Hello,
I am planning in working in a new Traits implementation, the idea is to have an implementation that can work as a loadable module. So you can use it or not as another library.
Also the idea is improve the support of all the tools by improving the polymorphism between traits and classes. Clean up a little the API and add support to have stateful traits.
I would like to know if you have any suggestion or have a problem that I could try to solve. I have been talking with some people in the community to get ideas, but always having more opinions is better.
Thanks in advance. Pablo
-- Pablo Tesone. tesonep@gmail.com
Thank you, I have submitted. Cheers, Pablo On Fri, Mar 31, 2017 at 3:29 PM, Jigyasa Grover <grover.jigyasa1@gmail.com> wrote:
Hey Pablo
Great idea !
Submit your proposal ASAP at summerofcode.withgoogle.com for review and feedback.
Good luck :)
Best Jigyasa Grover GSoC 2017 Org Admin, Pharo Consortium
On Fri, Mar 31, 2017 at 6:26 PM, Stephane Ducasse <stepharo.self@gmail.com
wrote:
go go go go
On Fri, Mar 31, 2017 at 2:14 PM, tesonep@gmail.com <tesonep@gmail.com> wrote:
Hello,
I am planning in working in a new Traits implementation, the idea is to have an implementation that can work as a loadable module. So you can use it or not as another library.
Also the idea is improve the support of all the tools by improving the polymorphism between traits and classes. Clean up a little the API and add support to have stateful traits.
I would like to know if you have any suggestion or have a problem that I could try to solve. I have been talking with some people in the community to get ideas, but always having more opinions is better.
Thanks in advance. Pablo
-- Pablo Tesone. tesonep@gmail.com
-- Pablo Tesone. tesonep@gmail.com
participants (3)
-
Jigyasa Grover -
Stephane Ducasse -
tesonep＠gmail.com