yes for example. Stef
On Mar 26, 2013, at 11:02 AM, Tudor Girba <[email protected]> wrote: > I like this project proposal. A little addition would be to add type > inference for code written in the inspector where we already have concrete > types that we could leverage for development tools. Would you consider that? > > Cheers, > Doru > > > On Tue, Mar 26, 2013 at 10:51 AM, Camille Teruel <[email protected]> > wrote: > Hi Janko, > > Here is another project proposition. > Programming tools for Pharo based on Type Inference > > > Level: intermediate/advanced > > Possible mentor: Camille Teruel > Possible second mentor: Stéphane Ducasse > > Description: Type inference mechanisms can be used to compute the types of > variables from the source code. This information is very interesting in the > context of a dynamically-typed language like Smalltalk. Several type > inference tools already exists for Smalltalk but the type information they > bring has not revealed all its potential yet. The student will have to > leverage this type information with new programming tools. > > Example of such tools are: > > Code analysis tools: > better "implementors of" and "senders of" lists > dead code finder > Development tools: > type mismatch hints at compile time > better code completion > Technical details: > > The student will have to analyze existing type inference tools and choose an > appropriate solution. Then he will have to learn how to build UIs with Spec. > Benefits for the Pharo community > > New useful development tools > Improvement of existing code base thank to these tools > Benefits for the student > > Use a highly reflective dynamic language > Learn the basics of type inference > Learn how to make UIs with Spec > Have an impact on the code base of a large project > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"
