[#78949] [Ruby trunk Feature#13095] [PATCH] io.c (rb_f_syscall): remove deprecation notice — kosaki.motohiro@...
Issue #13095 has been updated by Motohiro KOSAKI.
3 messages
2017/01/03
[#78997] [Ruby trunk Bug#13110] Byte-based operations for String — shugo@...
SXNzdWUgIzEzMTEwIGhhcyBiZWVuIHVwZGF0ZWQgYnkgU2h1Z28gTWFlZGEuCgoKTGV0IG1lIHNo
3 messages
2017/01/06
[#79228] Re: [ruby-cvs:64576] naruse:r57410 (trunk): Prevent GC by volatile [Bug #13150] — Eric Wong <normalperson@...>
naruse@ruby-lang.org wrote:
5 messages
2017/01/23
[#79511] Re: [ruby-cvs:64576] naruse:r57410 (trunk): Prevent GC by volatile [Bug #13150]
— Eric Wong <normalperson@...>
2017/02/13
Eric Wong <normalperson@yhbt.net> wrote:
[#79518] Re: [ruby-cvs:64576] naruse:r57410 (trunk): Prevent GC by volatile [Bug #13150]
— Nobuyoshi Nakada <nobu@...>
2017/02/13
On 2017/02/13 10:04, Eric Wong wrote:
[#79298] [Ruby trunk Bug#13085][Assigned] io.c io_fwrite creates garbage — nobu@...
Issue #13085 has been updated by Nobuyoshi Nakada.
3 messages
2017/01/29
[#79337] Re: [ruby-changes:45397] normal:r57469 (trunk): io.c: recycle garbage on write — SASADA Koichi <ko1@...>
Eric:
4 messages
2017/01/31
[#79352] Re: [ruby-changes:45397] normal:r57469 (trunk): io.c: recycle garbage on write
— Eric Wong <normalperson@...>
2017/01/31
SASADA Koichi <ko1@atdot.net> wrote:
[ruby-core:79255] [Ruby trunk Feature#13156] In-tree copy of ruby/spec
From:
shyouhei@...
Date:
2017-01-25 01:23:38 UTC
List:
ruby-core #79255
Issue #13156 has been updated by Shyouhei Urabe. I'm neutral or somewhat positive to this. It sounds worth trying. At least I have no reason to object. ---------------------------------------- Feature #13156: In-tree copy of ruby/spec https://bugs.ruby-lang.org/issues/13156#change-62668 * Author: Benoit Daloze * Status: Open * Priority: Normal * Assignee: Yukihiro Matsumoto * Target version: ---------------------------------------- I would like to integrate an in-tree copy of ruby/spec under spec/rubyspec/ (at the same location ruby/spec is currently cloned to ease transition). This way, implementation and tests can be changed in a single commit, just like with MRI tests. I will keep synchronizing the changes to ruby/spec, so it can be used directly and other people can contribute there. I know this synchronization works because I have been doing it for over 2 years. This process is also well documented: https://github.com/ruby/spec/wiki/Merging-specs-from-JRuby-and-other-sources My main motivation is the current status is suboptimal as ruby/spec is a different repository and there are synchronization problems. For example, if a change happens on MRI trunk and it needs to adapt ruby/spec, it will pass either ruby/ruby CI or ruby/spec CI but never both. I want to fix this and I want to encourage CRuby developers to write specs. If you want more details, please look at my ruby-core post: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/78633 Please state you opinion, I would like to integrate this soon. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>