[GSoC18] Willing to contribute Ruby, and have a question.

takamasa saichi

unread,

Mar 3, 2018, 11:14:58 AM3/3/18

to Ruby Google Summer of Code

Hello everyone.

I'm Takamasa Saichi, a fourth-year student of the University of Tsukuba in Japan, and will be master's course from next April. I'm getting familiar with Ruby and C, and have a basic knowledge of parsing (I have used yacc, bison, ANTRL). I interested in topic "Experimental Type Annotation Syntax Support" in ideas for MRI. I want to help and contribute!

Now, I have some questions about the goal of above topic. Where should I discuss that question? in slack? here? or sending a mail to potential mentors?

Thanks.

Takamasa Saichi.

Tony Arcieri

unread,

Mar 3, 2018, 11:18:30 AM3/3/18

to takamasa saichi, Ruby Google Summer of Code

Any of those will work just fine (by the way, I am an interested mentor for that project)

--
You received this message because you are subscribed to the Google Groups "Ruby Google Summer of Code" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubygsoc+unsubscribe@googlegroups.com.
To post to this group, send email to ruby...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubygsoc/63ccc04c-ad9e-48c9-99cc-7391c7d03608%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Tony Arcieri

takamasa saichi

unread,

Mar 3, 2018, 12:30:02 PM3/3/18

to Ruby Google Summer of Code

Thanks for reply.

Ok, I write here. I have two questions.

1. Do type annotations need to consider all the syntax of all available Ruby versions? or only latest version?

2. Is the purpose of this idea to support official type annotation that is not like gems?

Thanks.

Takamasa Saichi

Tony Arcieri

unread,

Mar 3, 2018, 12:57:48 PM3/3/18

to takamasa saichi, Ruby Google Summer of Code

On Sat, Mar 3, 2018 at 9:30 AM, takamasa saichi <s.wak...@gmail.com> wrote:

1. Do type annotations need to consider all the syntax of all available Ruby versions? or only latest version?

The long-term goal would be something like Ruby 3.0+

2. Is the purpose of this idea to support official type annotation that is not like gems?

Yes, the goal is to make type annotations a first-class feature of the language so every gem/typechecker/etc that wants type information doesn't have to invent its own syntax

--

Tony Arcieri

takamasa saichi

unread,

Mar 3, 2018, 1:56:53 PM3/3/18

to Ruby Google Summer of Code

The long-term goal would be something like Ruby 3.0+

Ok, I understand.

so every gem/typechecker/etc that wants type information doesn't have to invent its own syntax

I am pleased because I am studying the static analysis of dynamically typed languages (e.g. Ruby). I just want to need type information.

There are additional questions. What do you think the most difficult part to achieve this idea? I think that it is to keep consistency with existing syntax, and implementation is not too difficult.

I'd like to work on this idea. Before filing a proposal, is there anything to be done? Or, do you have the necessary knowledge?

(I am not good at English, a reply may be delayed. sorry.)

Thanks.

Takamasa Saichi

2018年3月4日日曜日 2時57分48秒 UTC+9 Tony Arcieri:

Tony Arcieri

unread,

Mar 4, 2018, 1:15:54 PM3/4/18

to takamasa saichi, Ruby Google Summer of Code

On Sat, Mar 3, 2018 at 10:56 AM, takamasa saichi <s.wak...@gmail.com> wrote:

I am pleased because I am studying the static analysis of dynamically typed languages (e.g. Ruby). I just want to need type information.

Great! That is exactly what this project is intended to solve.

There are additional questions. What do you think the most difficult part to achieve this idea? I think that it is to keep consistency with existing syntax, and implementation is not too difficult.

I think the most difficult part will be designing the type annotation grammar and corresponding AST representation thereof. This includes mapping out all parts of the current language syntax where type information could be added and what the type annotation syntax would look like. Should we support generics? unions/sum types? structural typing ala "Any Object that responds to #foo and returns a String"?

I imagine if your goal is to write static analysis tools for dynamically typed languages you'll have a pretty good idea of what sort of information you'd want to consume from the AST.

I'd like to work on this idea. Before filing a proposal, is there anything to be done? Or, do you have the necessary knowledge?

You can start putting together a proposal if you're interested. GSoC student proposals open officially on March 12th.

takamasa saichi

unread,

Mar 6, 2018, 9:04:36 AM3/6/18

to Ruby Google Summer of Code

I imagine if your goal is to write static analysis tools for dynamically typed languages you'll have a pretty good idea of what sort of information you'd want to consume from the AST.

I think so too. I will consider RDL etc. as a reference.

You can start putting together a proposal if you're interested. GSoC student proposals open officially on March 12th.

I just started writing proposal's draft. Should I follow https://github.com/rubygsoc/rubygsoc/wiki/Student-Application ?

2018年3月5日月曜日 3時15分54秒 UTC+9 Tony Arcieri:

Tony Arcieri

unread,

Mar 6, 2018, 9:55:36 AM3/6/18

to takamasa saichi, Ruby Google Summer of Code

On Tue, Mar 6, 2018 at 6:04 AM, takamasa saichi <s.wak...@gmail.com> wrote:

You can start putting together a proposal if you're interested. GSoC student proposals open officially on March 12th.

I just started writing proposal's draft. Should I follow https://github.com/rubygsoc/rubygsoc/wiki/Student-Application ?

Yep, exactly

takamasa saichi

unread,

Mar 9, 2018, 11:43:04 AM3/9/18

to Ruby Google Summer of Code

Thank you for answering the questions!

I will ask again if there is a question.

Takamasa Saichi

Reply all

Reply to author

Forward