Background¶ There are three use cases where we need a CRuby parser which is independent of other CRuby features like Object, GC. I call such a parser a Universal Parser. Use Universal Parser from Ruby applications. For example RuboCop. RuboCop needs a parser to get AST of source code. Currently RuboCop uses parser gem. In this sense Universal Parser is a replacement of parser gem. Use Universal Pa

How about adding a syntax for one-line pattern matching: <expr> in <pattern> ? [1, 2, 3] in x, y, z #=> true (with assigning 1 to x, 2 to y, and 3 to z) [1, 2, 3] in 1, 2, 4 #=> false More realistic example: json = { name: "ko1", age: 39, address: { postal: 123, city: "Taito-ku" } } if json in { name:, age: (20..), address: { city: "Taito-ku" } } p name #=> "ko1" else raise "wrong format" end It i

I propose new pattern matching syntax. Pattern syntax¶ Here's a summary of pattern syntax. # case version case expr in pat [if|unless cond] ... in pat [if|unless cond] ... else ... end pat: var # Variable pattern. It matches any value, and binds the variable name to that value. | literal # Value pattern. The pattern matches an object such that pattern === object. | Constant # Ditto. | var_ # Ditto

まつもと ゆきひろです In message "Re: [ruby-dev:38725] [Bug #1720] [NaN] == [NaN] が true になる" on Fri, 3 Jul 2009 21:43:24 +0900, tadayoshi funaba redmine@ruby-lang.org writes: NaN = 0.0/0 [NaN] == [NaN] が true になりますが、 NaN == NaN #=> false [1] == [1.0] #=> true という結果からするとおかしいように思います。 確かに。rb_equal()が両辺が同じオブジェクトのときにメソッド呼 び出しを行わずに真を返しているせいですね。NaNというのは、 equal?が成立しても==が成立しないという特異なオブジェクトであ るためにこの問題が発生しています。 とはいえ、こ

はじめまして。谷道と申します。 既出だったらすみません。bugs.ruby-lang.org でも検索したんですが それっぽいチケットが見当たらなかったので確認させてください。 Refinements で定義した to_s を String interpolation が呼んでくれないのですが、これって仕様なんですかね？ String literal の評価が using B しているスコープの外で行われる、ということでしょうか。 $ ruby -v ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16] class A end module B refine A do def to_s 'b' end end end class C using B def initialize @a = A.new end def c1

object.c: Kernel#yield_self object.c (rb_obj_yield_self): new method which yields the receiver and returns the result. [Feature #6721]

Hello, the following patch contains a new implementation of hash tables (major files st.c and include/ruby/st.h). Modern processors have several levels of cache. Usually,the CPU reads one or a few lines of the cache from memory (or another level of cache). So CPU is much faster at reading data stored close to each other. The current implementation of Ruby hash tables does not fit well to modern pr

I think the following method is missing from Ruby: class Object def yield_self(*args) yield(self, *args) end end I do not know a good use case, but it looks very natural to me. It can be used in method chains. What do you think? Is there an alternative?

開発者の手引き¶ English version: DeveloperHowto bug report¶ Redmine Ruby master Ruby 1.8 Rubyforge の Ruby プロジェクト の Bug Tracking System Debian FreeBSD NetBSD Fedora MacPorts coding style¶ indent C は 4 Ruby は 2 tab/space Ruby コードは TABなし [ruby-dev:19388] CコードでもTABを使わずspaceだけを使う [Bug #14246] 改行コード 関数の宣言のスタイル 1.8はK&R1e、1.9 からは ANSI C style VC のバグを回避するために、ポインタを利用する無引数関数は関数定義以外にプロトタイプ宣言をすること 標準 C99 Travis/AppVe

Abstract¶ I optimized built-in library Rational. It is more than 3.7 times faster now in some cases. Background¶ Rational is increasing its importance year by year. Ruby 1.9.2 uses Rational as internal representation of Time. Ruby 2.1 introduced Rational literal ("r" suffix). But it's performance is not good enough because its implementation uses Ruby-level method calling with rb_funcall(), in spi

=begin 2011年2月10日14:15 あつし よしだ redmine@ruby-lang.org: Bug #4388: open-uriで環境変数http_proxyを使うときに認証付きのProxyが使えません http://redmine.ruby-lang.org/issues/show/4388 内容はタイトルのままです。 マルチユーザ環境において環境変数は他人から見られるものであり、 パスワードを入れるのに適切な場所ではないので、 この変更は受け入れられません。 [田中 哲][たなか あきら][Tanaka Akira] =end

What about making the default UTF-8. This is the same as source encoding for many scripts now. According to the experts at the Ruby Committer meeting, the information about the script encoding is only available in the parser.

Sometimes, I need to apply divmod repeatedly. For example, in order to convert a number expressing seconds into approx year, day, hour, minutes, seconds (approx in the sense of ignoring leap day and leap second), I can repeatedly apply divmod: seconds = 289342751 minutes, seconds = seconds.divmod(60) # => [4822379, 11] hours, minutes = minutes.divmod(60) # => [80372, 59] days, hours = hours.divmod

I am the creator of the Contributor Covenant, a code of conduct for Open Source projects. At last count there are over 13,000 projects on Github that have adopted it. This past year saw adoption of Contributor Covenant by a lot of very large, very visible projects, including Rails, Github's Atom text editor, Angular JS, bundler, curl, diaspora, discourse, Eclipse, rspec, shoes, and rvm. The bundle

Actually, the problem is worse than that: I tried making a simple change to have ruby_cleanup reset the global flag, but it looks like modules never clean up after themselves! E.g. void Init_frozen_strings(void) { assert(!frozen_strings); frozen_strings = st_init_table_with_size(&fstring_hash_type, 1000); } frozen_strings never gets reset to NULL. Which means the second time ruby_setup is called,

For example ruby -v -e 'true ? 1.tap do |n| p n end : 0' Result by 2.1.5 ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-darwin14.0] 1 Result by 2.2.0 ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin14] -e:1: syntax error, unexpected keyword_do_cond, expecting ':' true ? 1.tap do |n| p n end : 0 ^ -e:1: syntax error, unexpected tIDENTIFIER, expecting keyword_do or '{' or '(' true ? 1.tap

I sometimes write following code with rails application: u = User.find(id) if u && u.profile && u.profile.thumbnails && u.profiles.thumbnails.large ... or # Use ActiveSupport if u.try!(:profile).try!(:thumbnails).try!(:large) ... I hope to write shortly above code. Groovy has above operator named "Safe navigation operator" with "?." syntax. Ruby can't use "?." operator. Can we use ".?" syntax. lik

When creating a new hash using { **hash1, **hash2 } literal, there are different behaviors between 2.2.0 or later and 2.1.7 or earlier like below. ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin13] ruby 2.1.3p242 (2014-09-19 revision 47630) [x86_64-darwin13.0] [1] pry(main)> hash1 = { duplicate_key: 1, key: 1 } => {:duplicate_key=>1, :key=>1} [2] pry(main)> hash2 = { duplicate_key: 3 } =>