[#74190] [Ruby trunk Feature#12134] Comparison between `true` and `false` — duerst@...
SXNzdWUgIzEyMTM0IGhhcyBiZWVuIHVwZGF0ZWQgYnkgTWFydGluIETDvHJzdC4KCgpUc3V5b3No
3 messages
2016/03/07
[#74269] Type systems for Ruby — Rob Blanco <ml@...>
Dear ruby-core,
5 messages
2016/03/10
[#74395] [Ruby trunk Feature#12142] Hash tables with open addressing — shyouhei@...
Issue #12142 has been updated by Shyouhei Urabe.
3 messages
2016/03/17
[ruby-core:74295] Re: Type systems for Ruby
From:
"NARUSE, Yui" <naruse@...>
Date:
2016-03-14 04:07:37 UTC
List:
ruby-core #74295
2016-03-14 5:04 GMT+09:00 Rob Blanco <[email protected]>: > Soft typing doesn't make any syntactic changes and instead performs a sort > of best-effort type inference at runtime. This was directly the approach of > the RubyConf 2014 opening keynote, as summarized here: > https://www.omniref.com/blog/2014/11/17/matz-at-rubyconf-2014-will-ruby-3-dot-0-be-statically-typed/ Matz says about Soft Typing in the Keynote, but he also says he want static type checking. (I personally think they are conflicted) > So, to sum up, is there interest in either one of these approaches predominantly over the other, or is it a question open to exploration? What would be the best way to go about investing Ruby with these capabilities? Type System is a tool to solve a problem. Matz says there's three expected problem for it: * performance * debug (compile time check) * documentation If you tackle this, you should decide what problem will you solve. Because Matz says and Ruby programmers are lazy, it is better if people doesn't need to write type. But it's must be useful in some portion. People can write type if it is really worth writing. You may need to find a best mix with optional typing. NOTE: Matz strongly objects to introduce any syntactic annotations to Ruby now. But he also says he don't forbid to embed annotations as comments (or rdoc). -- NARUSE, Yui <[email protected]> Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>