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
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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
We should check it again. Now the language did not change recently so may be some glitches appeared due to ast changes.
Le 30/9/15 20:28, Peter Uhnak a écrit :
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I know at least 2 more people who work on this in some way. Should you join efforts?
Uko
On 03 Oct 2015, at 11:24, stepharo <stepharo@free.fr mailto:stepharo@free.fr> wrote:
We should check it again. Now the language did not change recently so may be some glitches appeared due to ast changes.
Le 30/9/15 20:28, Peter Uhnak a écrit :
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
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev https://www.iam.unibe.ch/mailman/listinfo/moose-dev
RIght now I'm focusing on the mooc and the tutorial around the web stack. All the rest is low priority.
Le 3/10/15 12:02, Yuriy Tymchuk a écrit :
I know at least 2 more people who work on this in some way. Should you join efforts?
Uko
On 03 Oct 2015, at 11:24, stepharo <stepharo@free.fr mailto:stepharo@free.fr> wrote:
We should check it again. Now the language did not change recently so may be some glitches appeared due to ast changes.
Le 30/9/15 20:28, Peter Uhnak a écrit :
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Peter Uhnak -
stepharo -
Tudor Girba -
Yuriy Tymchuk