Custom type inference and RoelTyper
Hi, Moose/FAMIX uses RoelTyper for type inference, how this does not seem to be maintained (last version 2013), and for my purposes is lacking. So do we have something more advanced, even at the expense of speed? Other alternative would be to either extend RoelTyper or write something custom that would be ran alongside RoelTyper. Examples of such extensions would be extracting the type from meta-annotations and the actual argument names. (e.g. if an argument is named aString, I can safely assume that it will be String). Thanks, Peter
Hi Peter! I am currently working on gradual typing for Pharo. I hope to have something ready for public consumption soon... Alexandre
On Sep 30, 2015, at 8:28 PM, Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi,
Moose/FAMIX uses RoelTyper for type inference, how this does not seem to be maintained (last version 2013), and for my purposes is lacking.
So do we have something more advanced, even at the expense of speed?
Other alternative would be to either extend RoelTyper or write something custom that would be ran alongside RoelTyper.
Examples of such extensions would be extracting the type from meta-annotations and the actual argument names. (e.g. if an argument is named aString, I can safely assume that it will be String).
Thanks, Peter
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Great news :) Doru On Wed, Sep 30, 2015 at 9:31 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Hi Peter!
I am currently working on gradual typing for Pharo. I hope to have something ready for public consumption soon...
Alexandre
On Sep 30, 2015, at 8:28 PM, Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi,
Moose/FAMIX uses RoelTyper for type inference, how this does not seem to be maintained (last version 2013), and for my purposes is lacking.
So do we have something more advanced, even at the expense of speed?
Other alternative would be to either extend RoelTyper or write something custom that would be ran alongside RoelTyper.
Examples of such extensions would be extracting the type from meta-annotations and the actual argument names. (e.g. if an argument is named aString, I can safely assume that it will be String).
Thanks, Peter
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- www.tudorgirba.com "Every thing has its own flow"
Good to hear! Do you have any time estimation (days/weeks)? Also I don't mind looking at something incomplete (after all I learned roassal just from source code ;)) Thanks, Peter -----Original Message----- From: "Tudor Girba" <tudor@tudorgirba.com> Sent: â9/â30/â2015 9:43 PM To: "Any question about pharo is welcome" <pharo-users@lists.pharo.org> Cc: "Moose-related development" <moose-dev@iam.unibe.ch> Subject: Re: [Pharo-users] Custom type inference and RoelTyper Great news :) Doru On Wed, Sep 30, 2015 at 9:31 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote: Hi Peter! I am currently working on gradual typing for Pharo. I hope to have something ready for public consumption soon... Alexandre
On Sep 30, 2015, at 8:28 PM, Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi,
Moose/FAMIX uses RoelTyper for type inference, how this does not seem to be maintained (last version 2013), and for my purposes is lacking.
So do we have something more advanced, even at the expense of speed?
Other alternative would be to either extend RoelTyper or write something custom that would be ran alongside RoelTyper.
Examples of such extensions would be extracting the type from meta-annotations and the actual argument names. (e.g. if an argument is named aString, I can safely assume that it will be String).
Thanks, Peter
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- www.tudorgirba.com "Every thing has its own flow"
Type system is particularly complicated. I did a first implementation (called Type4Pharo on smalltalkhub), but it does not go in the right direction. I will redo it completely. So, nothing will be ready until a few months. Alexandre
On Sep 30, 2015, at 10:01 PM, Peter Uhnak <i.uhnak@gmail.com> wrote:
Good to hear!
Do you have any time estimation (days/weeks)? Also I don't mind looking at something incomplete (after all I learned roassal just from source code ;))
Thanks, Peter From: Tudor Girba Sent: â9/â30/â2015 9:43 PM To: Any question about pharo is welcome Cc: Moose-related development Subject: Re: [Pharo-users] Custom type inference and RoelTyper
Great news :)
Doru
On Wed, Sep 30, 2015 at 9:31 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote: Hi Peter!
I am currently working on gradual typing for Pharo. I hope to have something ready for public consumption soon...
Alexandre
On Sep 30, 2015, at 8:28 PM, Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi,
Moose/FAMIX uses RoelTyper for type inference, how this does not seem to be maintained (last version 2013), and for my purposes is lacking.
So do we have something more advanced, even at the expense of speed?
Other alternative would be to either extend RoelTyper or write something custom that would be ran alongside RoelTyper.
Examples of such extensions would be extracting the type from meta-annotations and the actual argument names. (e.g. if an argument is named aString, I can safely assume that it will be String).
Thanks, Peter
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- www.tudorgirba.com
"Every thing has its own flow"
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Peter contact Pablo Tesone Pablo Tesone <tesonep@gmail.com> Le 30/9/15 22:01, Peter Uhnak a écrit :
Good to hear!
Do you have any time estimation (days/weeks)? Also I don't mind looking at something incomplete (after all I learned roassal just from source code ;))
Thanks, Peter ------------------------------------------------------------------------ From: Tudor Girba <mailto:tudor@tudorgirba.com> Sent: â9/â30/â2015 9:43 PM To: Any question about pharo is welcome <mailto:pharo-users@lists.pharo.org> Cc: Moose-related development <mailto:moose-dev@iam.unibe.ch> Subject: Re: [Pharo-users] Custom type inference and RoelTyper
Great news :)
Doru
On Wed, Sep 30, 2015 at 9:31 PM, Alexandre Bergel <alexandre.bergel@me.com <mailto:alexandre.bergel@me.com>> wrote:
Hi Peter!
I am currently working on gradual typing for Pharo. I hope to have something ready for public consumption soon...
Alexandre
> On Sep 30, 2015, at 8:28 PM, Peter Uhnak <i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>> wrote: > > Hi, > > Moose/FAMIX uses RoelTyper for type inference, how this does not seem to be maintained (last version 2013), and for my purposes is lacking. > > So do we have something more advanced, even at the expense of speed? > > Other alternative would be to either extend RoelTyper or write something custom that would be ran alongside RoelTyper. > > Examples of such extensions would be extracting the type from meta-annotations and the actual argument names. (e.g. if an argument is named aString, I can safely assume that it will be String). > > Thanks, > Peter
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
Pay attention gradual types are the same as type inference. I personnally do not want gradual types in Pharo but I would like to have type inference. Le 30/9/15 21:31, Alexandre Bergel a écrit :
Hi Peter!
I am currently working on gradual typing for Pharo. I hope to have something ready for public consumption soon...
Alexandre
On Sep 30, 2015, at 8:28 PM, Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi,
Moose/FAMIX uses RoelTyper for type inference, how this does not seem to be maintained (last version 2013), and for my purposes is lacking.
So do we have something more advanced, even at the expense of speed?
Other alternative would be to either extend RoelTyper or write something custom that would be ran alongside RoelTyper.
Examples of such extensions would be extracting the type from meta-annotations and the actual argument names. (e.g. if an argument is named aString, I can safely assume that it will be String).
Thanks, Peter
participants (4)
-
Alexandre Bergel -
Peter Uhnak -
stepharo -
Tudor Girba