Activity
From 03/17/2012 to 03/23/2012
03/23/2012
-
11:53 PM Bug #6193: Time.new does not accept seconds as a String
- Here is the patch which will fix the problem with the seconds. There is also pull request for github.
-
12:21 PM Bug #6193 (Closed): Time.new does not accept seconds as a String
- Time.new accepts any or all of the year, month, day, hour, or minute specified as a String, but does not accept a String value for seconds:
>> Time.new("2012", "3", "22", "8", "19", 30)
=> 2012-03-22 08:19:30 -0700
> ...
TypeError: ... -
11:38 PM Bug #6195: String#[] に逆順の Range を渡した場合の挙動
- 前田です。
mrkn (Kenta Murata) wrote:
> 以下のように String#[] に対して、範囲の開始インデックスが文字列の長さ以下の値である逆順の Range (beg > end) を渡した場合に空文字列が返ります。
> ...
私も最初そう思ったのですが、PythonやJavaScriptではどちらの場合も空文字列を返すようです。
# 以下の例はどちらもRubyのs[x...y]相当(s[x..y]ではない)です。
de... -
06:52 PM Bug #6195 (Rejected): String#[] に逆順の Range を渡した場合の挙動
- 以下のように String#[] に対して、範囲の開始インデックスが文字列の長さ以下の値である逆順の Range (beg > end) を渡した場合に空文字列が返ります。
"1"[1..0] #=> ""
"1"[1..-1] #=> ""
"123"[2..1] #=> ""
"123"[2..-2] #=> ""
一方、範囲の開始インデックスが文字列の長さより大きい場合は nil が返ります。
"1"[2..0] #=>... -
07:15 PM Feature #3908: private constant
- Methods are different b/c they can effect state --they can be *dangerous*. If it wasn't for that, there would be little reason to have private methods either.
So, what does this "if you really want to get at them, you still can" look ... -
09:53 AM Feature #3908: private constant
- On Thu, Mar 22, 2012 at 23:46, trans (Thomas Sawyer) <transfire@gmail.com>wrote:
> But codifying that, rather than just documenting it, is bound to be more
> frustrating than useful.
Isn't that the point of trying to crac... -
- Isn't that really best left to a documentation detail?
While these private classes might be an implementation detail in your design, what if someone comes along and wants to build off the work and thus needs to subclass one of these i... -
- On Thu, Mar 22, 2012 at 17:08, trans (Thomas Sawyer) <transfire@gmail.com>wrote:
> I can't think of single reason why anyone would actually have to have a
> "private", as opposed to a "public", constant. Constants are CONSTANT so... -
02:23 AM Feature #3908: private constant
- On Thu, Mar 22, 2012 at 18:08, trans (Thomas Sawyer)
<transfire@gmail.com> wrote:
> I can't think of single reason why anyone would actually have to have a "private", as opposed to a "public", constant.
Private modules and c... -
- What was this deemed significant? I can't think of single reason why anyone would actually have to have a "private", as opposed to a "public", constant. Constants are CONSTANT so they aren't supposed to be changed after they are defined ...
-
- Hello,
trans (Thomas Sawyer) wrote:
> In previous issue #6158 it has been determined that Enumerator::Lazy#take should be lazy. But an eager form of #take would still be useful.
> ...
Enumerator::Lazy#pinch provides a random access ... -
-
-
01:19 PM Bug #6192 (Closed): Integer() doesn't handle UTF-16 input
- This issue was solved with changeset r35120.
John, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* bignum.c (rb_str_to_inum): must be ASCII compatible encoding as... -
01:00 PM Bug #6192: Integer() doesn't handle UTF-16 input
- =begin
I made this patch:
Index: bignum.c
===================================================================
--- bignum.c (revision 35117)
+++ bignum.c (working copy)
@@ -11,6 +11,7 @@
#include "ruby/ruby.h"
... -
- Related, String#to_i:
>> "2007".encode("UTF-16le").to_i
=> 2
-
- >> Integer("2007".encode("UTF-16le"))
ArgumentError: string contains null byte
from (irb):209:in `Integer'
from (irb):209
from /Users/john/.rvm/rubies/ruby-1.9.3-p125/bin/irb:16:in `<main>'
-
11:33 AM Bug #6094 (Closed): [OpenSSL] wrong argument of rsa_generate()
- This issue was solved with changeset r35117.
Nobuyoshi, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
Refix Bug #6094: use unsigned long integer literal.
* ext/o... -
-
06:12 AM Revision 463633e4 (git): transcode.c (documentation for str_encode): Explain
- that transcoding to the same encoding is a no-op
(i.e. no exceptions, no replacements,...).
[ruby-core:43557][Bug #6190]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35121 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- well as String#hex and String#oct. [ruby-core:43566][Bug #6192]
* string.c (rb_must_asciicompat): check if ASCII compatible.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35120 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:38 AM Feature #6154: Eliminate extending WaitReadable/Writable at runtime
- Updated patch with the following changes:
* rb_eEWOULDBLOCKReadable and rb_eEWOULDBLOCKWritable added
* EWOULDBLOCK versions are set to EAGAIN versions if EAGAIN == EWOULDBLOCK
* renamed function rb_readwrite_sys_fail to match error... -
- Ok, will do.
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35119 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35118 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * ext/openssl/ossl_pkey_rsa.c (rsa_generate): fix argument type.
[Bug #6094]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35117 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- This reverts commit r35102.
It breaks tests on FreeBSD.
6) Failure:
test_new_with_exponent(OpenSSL::TestPKeyRSA)
[/usr/home/chkbuild/build/ruby-trunk/20120323T010301Z/ruby/test/openssl/test_pkey_rsa.rb:59]:
<3> expected but was
<12884... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35115 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
03/22/2012
- 10:52 PM Revision e91983b4 (git): * 2012-03-23
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35114 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This reverts commit r35104 because it breaks build on FreeBSD.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35113 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:10 PM Bug #6186: Bug trying to compile Ruby 1.9.3p105
- shevegen (markus heiler) wrote:
> (I want to try to get a static version of ruby)
Well, without any flags a ruby consists of following parts:
1. the ruby binary (/usr/local/bin/ruby)
2. the libruby shared object
3. extensi... -
- shevegen (markus heiler) wrote:
> CFLAGS in use: -static -O2 -g
Do not use -static.
It makes all shared objects linked statically with libc routines.
-
01:23 PM Bug #6186: Bug trying to compile Ruby 1.9.3p105 - >
>Issue #6186 has been reported by shevegen (markus heiler).
>
>----------------------------------------
>Bug #6186: Bug trying to compile Ruby 1.9.3p105
>https://bugs.ruby-lang.org/issues/6186
>
>Author: shevegen (markus... -
01:07 PM Bug #6186: Bug trying to compile Ruby 1.9.3p105
- Sorry that it is so long. Do you need config.log too?
The bug is at:
/Depot/j/ruby-1.9.3p105/.ext/x86_64-linux/enc/encdb.so: [BUG] Segmentation fault
I am not sure what encdb.so is though. :) -
- Hi!
First my system information:
GCC Version: GCC version 4.4.3
Glibc Version: ldd (GNU libc) 2.11.2
CFLAGS in use: -static -O2 -g
Binutils Version: GNU ld (GNU Binutils) 2.22
I am trying to compile ruby version:
... -
- transcoded, just set encoding but leave coderange unchanged as
forcee_encoding. [ruby-core:43557][Bug #6190]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35112 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:05 PM Revision 7cbff3b9 (git): * io.c (static int io_fflush): add the definition.
- Use it in set_binary_mode_with_seek_cur().
* io.c (set_binary_mode_with_seek_cur): refactoring to split the
content into io_unread(). Fix the possibility of buffer overflow.
* io.c (io_unread): add new implementation for Windows. Pre... -
- This issue was solved with changeset r35102.
Nobuyoshi, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* ext/openssl/ossl_pkey_rsa.c (rsa_generate): fix argument t... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35110 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
11:37 AM Feature #6177: array.cのrb_ary_equal()の高速化
- Nobuyoshi Nakada wrote:
>最も大きいのはrb_ary_elt()呼び出しのオーバーヘッドということのようですね。
そのようです。
> ...
おっしゃる通りです…
凡ミスをやらかしてしまいました。
p1,p2が有効であるかどうかのチェックを止め、rb_equal()を呼び出したら有効なポインタを取得するようにしました。
ベンチマークの結果はpatch3.diffとほとんど変わりません。 -
- to time_t directly, not to be affected by TZ unnecessarily.
* win32/win32.c (unixtime_to_filetime): convert time_t to FILETIME
simply.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35109 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35108 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35107 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
-
-
-
-
-
- Also, please include crash report from ~/Library/Logs/CrashReporter or /Library/Logs/CrashReporter.
I suspect this is a similar bug to #6181 which include a CrashReporter log. -
07:25 AM Bug #6184: [BUG] Segmentation fault ruby 1.9.3p165 (2012-03-18 revision 35078) [x86_64-darwin11.3.0]
- Ah, also you can install openssl using rvm.
http://beginrescueend.com/packages/openssl/
:) -
-
- Seems openssl is something wrong.
1. If you're using OS X's default openssl -> do like `brew install openssl` and build with installed openssl, then try again.
2. If you're using openssl that installed by user -> build with OS X defa... -
06:51 AM Bug #6184 (Third Party's Issue): [BUG] Segmentation fault ruby 1.9.3p165 (2012-03-18 revision 35078) [x86_64-darwin11.3.0]
- System:
OSX 10.7.3
Xcode 4.3.1
rvm 1.10.2
bundle 1.1.2
$ ruby -v
ruby 1.9.3p165 (2012-03-18 revision 35078) [x86_64-darwin11.3.0]
I did:
CODE
---------------------------------------
$ rvm ruby-1.9.3-head
$ rvm g... -
07:32 AM Feature #6180: to_b for converting objects to a boolean value
- I too would very much like to see a #to_bool method on every object.
In my opinion, if you define a public API, you should be as strict as possible about what each method returns, so that your users can rely on it, but also to minimiz... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35106 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- have .svn under descendent directories.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35105 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35104 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * lib/mkmf.rb (TRY_LINK): need EXEEXT for cross-compiling.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35103 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- [Bug #6094]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35102 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * lib/mkmf.rb (try_link0, try_compile, try_cpp): check if the target
file get created actually. workaround for the case that the exit
status of a cygwin program seems lost on mingw.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk... -
- * lib/mkmf.rb (try_constant): remove conftest files.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35100 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 02:14 AM Revision 99594056 (git): * 2012-03-22
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35099 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 02:14 AM Revision caf627af (git): * test/ruby/test_io.rb (TestIO#test_pos_with_getc): updated.
- see [ruby-core:43550]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35098 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
03/21/2012
-
11:35 PM Feature #6183 (Rejected): Enumerator::Lazy performance issue
- Hello,
Enumerator::Lazy is not a silver bullet; it removes the overhead for
creating an intermediate array, but brings the drawback for calling
a block. Unfortunately, the latter is much bigger than the former.
Thus, in general, L... -
- Granted that seems like a bit too much overhead, but the advantage to lazy is not in a 1-to-1 comparison with non-lazy. Try removing the `.each` call at the end and adding `.take(10)` instead.
-
10:24 PM Feature #6183 (Closed): Enumerator::Lazy performance issue
- I benchmarked Enumerator::Lazy and that's what I got:
user system total real
Lazy: 0.690000 0.010000 0.700000 ( 0.733160)
Normal: 0.160000 0.010000 0.170000 ( 0.186695)
It seem... -
- Hello,
2012/3/18, nahi <nakahiro@gmail.com>:
> Endoh-san, how do you think?
Thank you for reminding this.
I think this is a duplicate (or a subset) of #4766 which is accepted by matz.
So I'm going to commit my patch within a rea... -
- Hello,
I'm not keen to import this feature.
I'm closing the ticket. Please reopen it if you find a piece of
code in the wild whose bottleneck is solved by #each_ancestor.
--
Yusuke Endoh <mame@tsg.ne.jp> -
- Hello,
2012/3/18, Hiroshi Nakamura <nakahiro@gmail.com>:
> Closing as implemented at 1.9.3.
Thanks.
When I think about it now, 2.0.0 were enough for
this feature. No one thought 2.0.0 would become
close to reality ... -
07:53 PM Feature #6180: to_b for converting objects to a boolean value
- On 21/03/12 01:44, trans (Thomas Sawyer) wrote:
>
> Issue #6180 has been updated by trans (Thomas Sawyer).
>
>
> Also, what you are asking for should probably be called #to_bool.
>
> Where as #to_b can have a broader, and ... -
03:53 PM Feature #6180: to_b for converting objects to a boolean value
- drbrain (Eric Hodel) wrote:
> Issue #6180 has been updated by drbrain (Eric Hodel).
>
> Why do you need to convert objects to boolean values?
1. To avoid breaking encapsulation. For example:
def connected?
!! @... -
- =begin
If you're testing that a method returns exactly true and not a true value you're probably being over-specific in your tests. An assertion that a method returns a true value and not exactly true will allow the tests to be used un... -
- The only problem with that is that Ruby defines #nil? which is a strict check for NilClass instance. Hence #true? and #false? make more sense doing the same for TrueClass and FalseClass.
-
11:26 AM Feature #6180: to_b for converting objects to a boolean value
- @drbrain - Very true but it is nice to be consistent with return values. It makes testing a little easier and fits a little better with the principle of least surprise.
@hasari - to_s could easily be string or symbol. It doesn't seem ... -
- Also, what you are asking for should probably be called #to_bool.
Where as #to_b can have a broader, and generally more useful definition, e.g.
"true".to_b #=> true
"yes".to_b #=> true
"on".to_b #=> true
1.to_b ... -
10:40 AM Feature #6180: to_b for converting objects to a boolean value
- Also, to_b is ambiguous. 'b' can stand for "bits", "bytes", "binary", just to name a few.
-
- It is even shorter if you just omit the !! or the to_b altogether:
$ ruby20 -e'puts RubyVM::InstructionSequence.compile(%[foo]).disasm'
== disasm: <RubyVM::InstructionSequence:<compiled>@<compiled>>==========
0000 trace 1... -
- I think that "to_b" is more clear and fits well with the other to_*. Using "!!" isn't the most obvious choice for people looking to create a boolean. I am a bit disheartened to find out that it's slower.
-
- BasicObject#! is optimized by YARV as following:
% ruby -e'puts RubyVM::InstructionSequence.compile(%[!!foo]).disasm'
== disasm: <RubyVM::InstructionSequence:<compiled>@<compiled>>==========
0000 trace 1 ... -
- Typically this comes up when you have a method ending in a question mark to indicate a boolean return value.
def foo?
!!@foo
end
def has_vowel?
!!(value =~ /[aeiou]/)
end -
- Why do you need to convert objects to boolean values?
-
- When a boolean return value is required it has become common practice is to use "!!" to convert the object. It would be more consistent to provide a "to_b" method on Object.
-
-
- Could you try it with trunk/1.9.3?
-
- Can you show us how we can see that output on our machine?
-
03:20 PM Bug #6182 (Closed): ruby crashed with trace inof below !(Ruby interpreter or extension libraries)
- /home/bourne/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/timeout.rb:75: [BUG] rb_register_sigaltstack. malloc error
ruby 1.9.2p290 (2011-07-09 revision 32553) [i686-linux]
-- control frame ----------
c:0006 p:---- s:0024 b:0024 l:0... -
- The crash is during X509 certificate verification.
-
12:28 PM Bug #6181 (Third Party's Issue): Ruby crash when trying to send a mail (tls/gmail)
- The following code made ruby crash:
require 'net/smtp'
smtp = Net::SMTP.new 'smtp.gmail.com', 587
smtp.enable_starttls
smtp.start("gmail.com", "***edited***", "***edited***", :login) do
smtp.send_message("hello world!!", "... -
- [Bug#6143] [Bug#6144] [Bug#6145]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35097 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- michaelcm (Michael McWilliam) wrote:
> Also, I posted it here because the bugreport.html page said to click on the link for ruby 1.9.2 or 1.9.3, but neither were links, so I looked for something that had 9.3 in it, and that was this bac... -
- Hello,
Ah, I see. RubySpec defines to_a to assert that it's never called, right?
That makes sense.
2012/03/20 2:27 "marcandre (Marc-Andre Lafortune)" <ruby-core@marc-andre.ca
>:
>
>
> Issue #6155 has been updated by ma... - 08:03 AM Revision 51f41bb8 (git): * 2012-03-21
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35096 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 08:03 AM Revision af86dba2 (git): * test/ruby/test_io.rb (TestIO#test_pos_with_getc): added.
- see [Bug #6179][ruby-core:43518]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35095 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:50 AM Bug #4434: make test-all "-j10000" のように大きな並列数を与えると異常終了
- Too many open files を出してるのがマネージャープロセスなら、しょうがないんじゃない。それはRLIMIT上げればいいんだし。
workerプロセスが出してるなら問題で、それはfdリークを意味してるので -j の数によってテストが変わってしまう可能性があるのでよくないよね。
-
06:27 AM Bug #5973: Bus Error in simple project requiring YARD
- Thanks, I tried with 1.9.3-p125 and the problem does seem to be resolved.
-
01:42 AM Bug #6143: Onigmo allows broken regexp: /(?(x.)/
- OnigmoのRubyマージ作業用ブランチにも修正を反映しました。
https://github.com/k-takata/Onigmo/tree/tmp/ruby-2.0.x -
- 1つめは、ENCLOSE_CONDITION で node->target が NULL になることはありません。
チェック無しに node->target をデリファレンスをしているのは、ENCLOSE_STOP_BACKTRACK のケースも同様なので、今回は修正していません。
2つめは修正しました。
https://github.com/k-takata/Onigmo/tree/tmp/ruby-2.0.x -
- sizeof(char*)をsizeof(OnigStackIndex)に修正しました。
https://github.com/k-takata/Onigmo/tree/tmp/ruby-2.0.x -
- Glass_saga (Masaki Matsushita) wrote:
> patchを直し、rb_equal()を実行した後に互いのRARRAY_LENのチェックと
> ...
最も大きいのはrb_ary_elt()呼び出しのオーバーヘッドということのようです
ね。
> >もう一点、&&ではなく||ではないでしょうか。
> ...
たしかに。
> 新しいpatchを添付します。
i != 0 なら常に (p1 != RARRAY_PTR(... -
- It wouldn't break backward compatibility, but it would take time for libraries to adjust to take the most advantage of it. And yet, any library with active development will likely adjust very quickly.
I would expect existing uses of w...
03/20/2012
-
- Nobuyoshi Nakada wrote:
>rb_equal()はメソッドを呼び出すので、その後ではp1,p2が有効である保証がありません。
patchを直し、rb_equal()を実行した後に互いのRARRAY_LENのチェックと
p1, p2の有効性のチェック、無効であれば有効なポインタを得る処理を入れました。
rb_ary_elt()を使えば簡潔に書けるのですが、以下のように遅くなってしまいました。
user syst... -
- =begin
もう一点、(({&&}))ではなく(({||}))ではないでしょうか。
=end
-
- =begin
(({rb_equal()}))はメソッドを呼び出すので、その後では(({p1})),(({p2}))が有効である保証がありません。
=end
-
- Nobuyoshi Nakada wrote:
>先頭だけではなく、同一オブジェクトかどうかを常に先に調べるようにするとどうなるでしょうか。
最初の要素だけobject_idに依らない同値性の判定が必要なケース(先に添付したpatch.diffを適用したrubyにとって最悪のケース)を加えてベンチマークを取りました。
patch1は先に添付したpatch.diffを適用したもので、patch2は同一オブジェクトかどうかを常に先に調べるようにしたものです。
... -
- =begin
先頭だけではなく、同一オブジェクトかどうかを常に先に調べるようにするとどうなるでしょうか。
=end
-
- できる限りVALUEの値の比較のみに留め、必要になったらrb_equal()を用いるという方針でrb_ary_equal()の高速化を試みました。
次のベンチマークを行ったところ、以下のような結果となりました。
require 'benchmark'
A = Array.new(100_0000){|n| n }
B = Array.new(1_0000){|n| n.to_s }
C = Array.new(1_0000){|n| n.to_s }
... -
- I will eventually try again. I don't really understand having #name, but not being able to get the actual constant named by #name.
-
-
- On 19/03/12 23:24, Eric Hodel wrote:
> On Mar 19, 2012, at 10:16 AM, Alex Young wrote:
>> On 19/03/12 11:58, Luis Lavena wrote:
<snip>
>>> $LOADED_FEATURES include full paths
>>
>> Does it? Is that now part of the spec?
>... -
- On Mar 19, 2012, at 10:16 AM, Alex Young wrote:
> On 19/03/12 11:58, Luis Lavena wrote:
>> On Mon, Mar 19, 2012 at 8:06 AM, Alex Young<alex@blackkettle.org> wrote:
>>> On 18/03/12 10:22, nobu wrote:
>>>>
>>>>
>>>> Issue #4523 h... -
- On 19/03/12 11:58, Luis Lavena wrote:
> On Mon, Mar 19, 2012 at 8:06 AM, Alex Young<alex@blackkettle.org> wrote:
>> On 18/03/12 10:22, nobu wrote:
>>>
>>>
>>> Issue #4523 has been updated by nobu.
>>>
>>>
>>> I don't th... -
- h.shirosaki (Hiroshi Shirosaki) wrote:
> Specify options:
> ...
Silly option. Should be 'new_process_group: true' or similar, at least.
> Python module does similar things.
> ...
Sigh. - 01:55 PM Revision 905eb21d (git): * 2012-03-20
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35094 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35093 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- There are no priorities for warnings at present, so any code using warnings would need to be updated to take advantage of the feature, breaking backwards compatibility.
Existing uses of #warn could be set as "lowest priority" which ma... -
- @drbrain Wouldn't using priorities and setting such a warning to a very low priority solve this?
-
- Sometimes when I use Kernel#warn in my code it is a message the user may not be able to do anything about, such as a deprecation message in library "a" that is used in library "b" that has not yet been updated, but the user wishes to use...
-
- Yui NARUSE wrote:
>IO#readpartial は
> ...
IO#readpartialも場合によってはblockする事があるんですね。
勉強になりました。 -
- > I think #flat_map makes more sense than #flatten accepting a block. It's unclear to me what #flatten would do with the block based on the name alone.
I never felt that this is a good kind of argument per-se. For instance, at first I... -
- I think #flat_map makes more sense than #flatten accepting a block. It's unclear to me what #flatten would do with the block based on the name alone.
Also, there is no Enumerable#flatten -
- I see a new method `#flat_map` has been added to Enumerable. Yet passing a block to #flatten has no use. That seems a waste, as it adds yet another method to remember when one we already know can do the job and makes sense.
-
- I will add a note to the documentation to cover the behavior of empty strings.
-
08:26 AM Bug #6089: Test suite fails with OpenSSL 1.0.1
- > Hi Martin,
> ...
Hi Bohuslav, hi Vit,
thanks for the info. OK, if the problem remains, I'll look into it now that 1.0.1 is released. The problem with DSS1 and RSA is probably that DSS1 was defined in combination with DSA signatures. S... -
05:31 AM Bug #4421: [ext/openssl] Fix RSA public key encoding
- MartinBosslet (Martin Bosslet) wrote:
> [...] and you need the latter instead of the former, let me know, I could also provide a code sample for that case.
Martin, I'd appreciate an example for the latter, yes, thanks in advance. In ... -
04:54 AM Bug #6175: watir-2.0.4/lib/watir/ie-class.rb:567: [BUG] Segmentation fault
- michaelcm (Michael McWilliam) wrote:
> Re: win32console, it is used by the ansi 1.4.2 gem, is that also no longer being maintained?
ansi gem do not directly depend on win32console, but you use to support ANSI colors on Windows.
Pl... -
04:43 AM Bug #6175: watir-2.0.4/lib/watir/ie-class.rb:567: [BUG] Segmentation fault
- Re: win32console, it is used by the ansi 1.4.2 gem, is that also no longer being maintained?
-
- Also, I posted it here because the bugreport.html page said to click on the link for ruby 1.9.2 or 1.9.3, but neither were links, so I looked for something that had 9.3 in it, and that was this backport.
http://www.ruby-lang.org/bugre... -
This is the minimum snapshot of code:
require 'watir'
begin
browser = Watir::Browser.attach( :url, /someUrl/i )
rescue
browser = Watir::Browser.start 'http://someUrl'
end
Line 87 in Session.rb that is the last line of ...-
- Hello,
Please don't report issues on the backports projects. Use ruby-trunk instead.
Now, if you can provide code to reproduce the issue we all will appreciate it, reproducibility is the key.
I also see you have win32console gem... -
- See attached log. Occurs about 5% of the time. Not sure why. Running script again immediately avoids the issue.
C:/pslibs/extlib/tools/ruby/1.9.3/lib/ruby/gems/1.9.1/gems/watir-2.0.4/lib/watir/ie-class.rb:567: [BUG] Segmentation fault... -
02:27 AM Bug #6155: Enumerable::Lazy#flat_map raises an exception when an element does not respond to #each
- Hi,
shugo (Shugo Maeda) wrote:
> Why the last example defines to_a? flat_map doesn't call to_a, but to_ary.
I think it's to spec that it doesn't call `to_a`.
-
- Why do we need to specially treat the 2nd central moment, that is standard deviation, than the other nth moment, such as skewness (3rd) and kurtosis (4th)?
You can use NArray for that reason. See http://narray.rubyforge.org/index.html.en
03/19/2012
-
- How about removing CREATE_NEW_PROCESS_GROUP flag by default and providing a way to specify CREATE_NEW_PROCESS_GROUP flag by spawn methods's arguments?
Ruby user can specify CREATE_NEW_PROCESS_GROUP flag if it's needed.
spawn method h... -
06:27 PM Bug #6131: Ctrl-C handler do not work from exec process (Windows)
- r34389 (not 34387) is the revision.
Shirosaki-san, how do you think about this? -
06:08 PM Bug #6131: Ctrl-C handler do not work from exec process (Windows)
- As you may know, this bug is due to the Revision r34387.
If the CREATE_NEW_PROCESS_GROUP flag is specified in a call to the CreateProcess function, CTRL+C signal is disabled for all processes within the new process group.
I think r... -
- I agree with this.
Please commit it. - 09:07 PM Bug #6089: Test suite fails with OpenSSL 1.0.1
- Also, this new OpenSSL is breaking the drb test suite:
$ make test-all TESTS="test/drb/test_drbssl.rb"
/builddir/build/BUILD/ruby-1.9.3-p125/lib/drb/ssl.rb:185: warning: SSL_accept returned=1 errno=0 state=SSLv3 write key exchange A: E... - 08:20 PM Bug #6089: Test suite fails with OpenSSL 1.0.1
- Hi Martin,
so OpenSSL v 1.0.1 is now public [1] and the problem seems to stay. I myself am not SSL expert, but why exactly should signing DSS1 with RSA2048 be a mismatch? I think that it's actually the right behaviour that it doesn't.
... -
- On Mon, Mar 19, 2012 at 8:06 AM, Alex Young <alex@blackkettle.org> wrote:
> On 18/03/12 10:22, nobu wrote:
>>
>>
>> Issue #4523 has been updated by nobu.
>>
>>
>> I don't think it's useful if it may return false.
>
>
> On the ... -
- On 18/03/12 10:22, nobu wrote:
>
> Issue #4523 has been updated by nobu.
>
>
> I don't think it's useful if it may return false.
On the contrary - if it returns false, you know the set of loaded files
hasn't changed. ... -
- No, b/c that's not running in the process and at the point in code which is in question.
-
- If you have two files with the same name isn't `gem which --all` enough to discover the collision?
-
- I haven't worked on the project where such comes into play in a few months, so I can only recollect the obvious usecase at the moment -- When debugging a problem were you suspect the wrong file is being required. Then this could be very ...
-
- On 15/03/12 15:26, Thomas Sawyer wrote:
>
> Issue #1122 has been updated by Thomas Sawyer.
>
>
> How about just `respond` ?
>
> foo.respond(:bar)
>
> And really, there's no reason it can't support delegation style... -
- This issue was solved with changeset r35092.
Dan, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* enumerator.c (lazy_flat_map_func): convert the block value to
... -
- I'll fix lazy flat_map respecting Matz's opinion, but let me clarify one point.
dkubb (Dan Kubb) wrote:
> > > [1, 2, 3].flat_map { |n| n }.to_a
> ...
Why the last example defines to_a? flat_map doesn't call to_a, but to_ary.
... -
- This issue was solved with changeset r35090.
Benoit, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* enumerator.c (enumerable_lazy): add an example of take and fi... -
- optflags='-O0 -g'を付けてビルドしたtrunkを使っていたので、ベンチマークでproposalが不当に有利でした。
optflagsを外してビルドした上でベンチマークを取り直したところ、以下の結果となりました。
trunk(r35087):
user system total real
0.000000 0.000000 0.000000 ( 0.000049)
proposal... -
- 特に添字を使う意味もなかったのでpatchを修正しました。
-
- Array if it doesn't respond to each. [ruby-core:43334]
[Bug #6155]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35092 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:01 AM Feature #4102 (Rejected): Proposal for 'let'. A new approach using block-defaults in 1.9
- The definition of let would be: "def let() yield; end"; I don't think it's worth to add.
Matz. -
- platforms where VALUE is longer than int.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35091 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- to the documentation. [ruby-core:43344] [Bug #6158]
add the description of the behavior when a block is given to zip
or cycle.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35090 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- of if-else with switch for special instructions. based on a
patch by Vasfed. https://github.com/ruby/ruby/pull/105
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35089 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- failed (that's not our fault).
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35088 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:46 AM Feature #3620: Add Queue, SIzedQueue and ConditionVariable implementations in C in addition to ruby ones
- Related issue (but about plain ruby realization)
https://bugs.ruby-lang.org/issues/6174 -
- > and native method could not be interrupted (unless it will)
Sorry, it should be read as "(unless it wish)" -
- 1. Currently, when Thread wakes on timeout, it could not remove itself from ConditionVariable waiters until it acquires lock.
So that, when ConditionVariable#signal is called, it will try to wakeup
such thread, instead of some one else... -
12:23 AM Feature #6154: Eliminate extending WaitReadable/Writable at runtime
- Charles, do you create a patch to introduce 4 constants (+2 for
EWOULDBLOCK) ? We discussed this issue today and we concluded that
that's better than anonymous class caching (to avoid Marshalling
issue.)
I think I can take c...
03/18/2012
-
- The former is analogous to Foo.bar(Misio), while the latter is analogous to Foo.bar("zot").
Object.const_get is mere method call. -
07:23 PM Bug #6172 (Rejected): Inconsistent behaviour of defined?
- Following behavior is obvious:
irb(main):004:0> Object.const_get("Misio")
NameError: uninitialized constant Misio
from (irb):4:in `const_get'
from (irb):4
from /Users/pawel/.rbenv/versions/1.9.4-dev/bin/irb:12:in `<main>'
irb(... -
- re.cのrb_memsearch()では、m == 1な場合にはfor文で各バイトと比較していますが、memchr()を用いると性能の改善がみられます。
次のようなベンチマークを実行したところ、以下のような結果となりました。
require 'benchmark'
str = "hoge" * 10000 + "\n"
Benchmark.bm do |x|
x.report do
str.index("\n")
end
e... -
- Hmm... I just wrote article related to this:
https://github.com/trans/trans.github.com/wiki/2012-02-25-setting-priorities-trumps-warnings
-
-
- I'm sorry, but #categorize has big code smell. Seems like too much functionality is being shoved into one method. It is still not clear to me after reading over explanation many times how #categorize works. So either it is relatively str...
-
10:36 PM Feature #5534: Redefine Range class and introduce RelativeNumeric and RelativeRange
- More of my crazy ideas. Wouldn't it be nice to be able to write:
a, b = 0.5, 10.5
(a..b).each(Integer) { |n| puts n } -
- It would conflict with RSpec's definition of #let.
Other then as a teaching tool for block scope what are the use cases? This seems to have very limited use. I find defining a new method is better way to get clean scope.
-
-
- I would expect `Array#pick` to work too. Which then leads one to think Array might support the equivalent of `Set#pop` as well. But since Array already has `#pop` it's not really a good idea to reuse same term, although in the case of Se...
-
-
- This is the first time I've seen regular expression groups, so it's interesting.
It occurs to me that with this addition MatchData is both a sort of Array and a sort of Hash. That being so consider `md.to_h`.
-
- This feature itself is acceptable, but proposed method name (API) is not acceptable.
-
-
- I don't think it's useful if it may return false.
What's the use case?
I agree that the way to know the loaded path would be useful sometimes, but this doesn't seem nice. -
- Regardless it's acceptable or not, we want to check nobu's local patches first. Don't you have that?
-
-
-
- Please use unpack instead.
-
- It's intended feature, and -1 is prepared for your purpose as Nobu said. #3575
-
-
-
- Nobu, can we close this now?
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- knu, how do you think?
-
06:18 PM Feature #3953: TCPSocket / UDPSocket do not accept IPAddr objects.
- If we implement this feature, we need a method for duck type, such as IPAddr#to_ipaddress to convert to IP-address string.
-
-
-
-
-
-
-
-
-
-
- Endoh-san, how do you think?
-
-
-
-
- Imported from #3330
うっかりruby-listに投げてしまったきしもとです
[ruby-list:47092] で振ってみた話題に関係して、なのですが（ツリーになりませんでしたが）、
mkmf に C++ のヘッダをチェックする機能を追加するパッチです。
```diff
Index: configure.in
===========================================================... -
-
-
-
-
- How about;
```ruby
t = Thread.new(stack_size: 1024)
t.stack_size = 1024
t[:initial_tls_hash] = {}
t.run {
...
}
``` -
-
-
-
-
- Shota, please handle this. We also added you as a maintainer of test/unit. http://bugs.ruby-lang.org/projects/ruby/wiki/Maintainers
-
-
- I don't feel changing `IO#reopen` is great way to solve this issue.
How about `spawn()`?
Since Ruby 1.9, `spawn` provides a primitive for redirection.
It is thread safe.
Apart from that, I think `$stdin`, `$stdout`, `$stderr` c... -
- Method name?
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- I feel following hang is bad behavior.
% mkfifo p
% ruby -v -rfileutils -e 'FileUtils.copy "p", "p2"'
ruby 2.0.0dev (2012-03-16 trunk 35049) [x86_64-linux]
...hang...
However cp also hangs.
% cp p p2
..hang...
... -
- Contribution are welcomed...
-
- argv[0] is not reliable on some environment.
see "#! - the Unix truth as far as I know it."
http://homepages.cwi.nl/~aeb/std/hashexclam.html
I tried to implement with vendor specific functions.
https://gist.github.com/1129437
... -
-
- I mark this Rejected since Matz rejected it. Sorry for not respecting your extra concern. It would be good to file this as a new issue.
-
- closing because no feedback..
-
- I think it is difficult to determine the base directory of relative directory in C.
-
- Pathname is immutable as commented.
-
- As matz already rejeted I hereby close this issue. If you still need it, please open a new ticket with revisied AIPs. Thank you.
-
-
-
- I think Ruby thinks "" has no fields, not one field which have empty string.
So, "".split(",", -1) should return [].
Documentation issue, maybe. -
- Aaron, is this hook extension still needed for your usecase? (assuming Rails?)
Not bad but it would affect performance... -
- Nobuyoshi Nakada wrote:
>* パラグラフモードでも効果があるか
> ...
パラグラフモードでも効果があるかどうかについてですが、次のようなベンチマークを実行してみました。
require 'benchmark'
rs = "\n" * ARGV.first.to_i
str = "hoge#{rs}fuga" * 10_0000
Benchmark.bm do |x|
x.report do
str.ea... -
- * このスレッドの現状をどなたか教えていただけませんか。
* この記法のユースケースをどなたか教えていただけませんか。 -
- This issue was solved with changeset r35081.
Benoit, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* bignum.c (rb_big_pow): estimate result bit size more precisel... -
- mrkn, please handle this.
-
- Marked as Rejected since the original poster agreed that it's less likely to be needed.
-
- Mark as Rejected since Endoh-san said it's duplicated of #3321, and #3321 is rejected.
-
- I think we can cache regexp structure according to regexp source, options, encoding.
If regexp structure is cached, /\A#{pattern}/ and /#{pattern}\z/ is not slow for
second and successive dynamic regexp creation.
If it is not slo... -
- rindex(pattern) would fail to detect proper end_of_string index. It must be /{suffix}\Z/.
-
-
-
- I mark as Closed since it seems we already have it in docs.
Please file a new ticket for the proposed API change since it's dated... -
- This issue was solved with changeset r35079.
Run Paint, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* compile.c: typo fix by Run Paint Run Run.
[ruby-core:283... -
- I feel the optimization (avoid shell when no meta characters) can be removed.
We have many ways to avoid shell such as system(command, arg1, arg2).
And recent computers are fast enough to run command via shell. - 03:21 PM Revision 27c53898 (git): * 2012-03-19
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35087 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * ext/-test-/num2int/num2int.c (print_num2ll, print_num2ull): define
only if long long is available, and use long long printf modifier
checked by configure.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35086 b2dd03c8-39d4-4d8f-... -
- * eval_jump.c (rb_exec_end_proc): need volatile to prevent from
setjmp/longjmp.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35085 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- gettalong wrote:
> I had a similar problem: I wanted to extract a part of a StringScanner-backed string.
> ...
You can use String#byteslice. -
- I close this as 'Rejected' since no update given long time.
-
- * gc.c (aligned_free): fix condition for free. memalign() and
posix_memalign() are not defined together normally.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35084 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- 開発者会議で笹田さんなどと議論したところ、
以下のスクリプトで、2回め以降の ^C で 1 が表示されないのはバグであるという
結論になりました。
% ruby -ve '
Thread.new do
begin
begin
p 1
sleep
ensure
raise
end
rescue
retry
end
end... -
- 現在の挙動。
% cat foo.rb
Thread.new do
begin
begin
p :sleep
sleep
ensure
p :raise
raise
end
rescue
p :retry
retry
end
end.join
% ruby foo.rb
:sleep
^C:raise
:retry
:sleep... -
- Closing as implemented at 1.9.3.
-
-
05:21 AM Bug #6168 (Third Party's Issue): Segfault in OpenSSL bindings
- Hello,
A few days ago I updated my Arch Linux server to OpenSSL 1.0.1-1 and Ruby 1.9.3_p125-2. Since then I have been experiencing an odd service failure where a Ruby TLS service of mine would disconnect users with "invalid MAC" excep... -
11:15 AM Revision 1d006f35 (git): * gc.c (aligned_malloc, aligned_free): added fallback implementations
- for platforms like OSX Leopard.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35083 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Works for me if it works for the API.
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35082 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:20 AM Bug #5544: Lookup scope for class variables in class_eval'd procs changed in 1.9.3
- I suppose so long as it is documented, the difference is ok. I think this can be closed in that case.
-
- Happy St. Patty's Day ;)
I don't seen any green on this site... *pinch* -
- In previous issue #6158 it has been determined that Enumerator::Lazy#take should be lazy. But an eager form of #take would still be useful.
To this end I'll suggest `Enumerator::Lazy#pinch`. Examples of usage:
e.lazy.pinch 1
... -
- [ruby-core:30735][Feature #3429]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35081 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- unlinked_method_entry_list. [ruby-core:43383][Bug #6171]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35080 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I thought about that...it would still be better to add EWOULDBLOCKReadable,
etc, than to pay the .extend toll every time.
On Mar 17, 2012 10:28 AM, "Tanaka Akira" <akr@fsij.org> wrote:
> 2012/3/16 Charles Nutter <headius@headiu... -
- [ruby-core:28368] [Bug #2824]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35079 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:09 AM Bug #6170 (Rejected): Compile error: "implicit declaration of function 'pthread_get_stackaddr_np'", "'pthread_get_stacksize_np'"
- =begin
When compiling Ruby 1.9.3 (I've tested 1.9.3p0 and 1.9.3p125), (({thread_pthread.c})) produces a compile error.
The following is the GCC output for the error:
compiling thread.c
In file included from thread.c:204:
thread... -
- =begin
This is fixed by removing lines 111-116 from (({process.c})), reproduced here:
#ifdef BROKEN_SETREUID
#define setreuid ruby_setreuid
#endif
#ifdef BROKEN_SETREGID
#define setregid ruby_setregid
#endif
Edit: forgot to menti... -
- =begin
When compiling Ruby 1.9.3 (I've tested 1.9.3p0 and 1.9.3p125), process.c produces a compile error
The following is the GCC output for the error:
compiling process.c
process.c: In function 'p_sys_setreuid':
process.c:41... -
- * encoding.c (rb_enc_compatible): return ASCII-8BIT even if 2nd string
is ascii only string. [ruby-core:42354] [Bug #5968]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@35078 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Other incorrect results:
>> "\u0100\u0101".count("a", "\u0100")
=> 1
> ...
=> 1
Both should be 0. -
- >> "\u0100\u0101".count("^\u0100", "^\u0101")
=> 2
Since multiple arguments are intersected, the expected result is 0. Compare:
> ...
=> 0
This takes a different path through tr_setup_table and returns the correct result.
An... - 01:03 AM Revision ef4ea58c (git): * 2012-03-18
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35077 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:03 AM Revision 42c18fe7 (git): * lib/profiler.rb: support calling singleton methods of
- an instance of BasicObject.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35076 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
03/17/2012
-
10:35 PM Bug #6158: Enumerator::Lazy#take: should it be lazy?
- matz:
> use #first. map! etc. do not conform other bang method naming convention.
Thank you for taking the decision.
Shugo:
I understand the use, so I also think it's worth having some form of lazy #take.
However, I think many... -
- use #first. map! etc. do not conform other bang method naming convention.
-
- =begin
Same for me - at first was thinking about having take evaluating makes sense.
But having ability to continue building the lazy chain looks more logical.
Having something like #pinch totally makes sense.
However I'm thinkin... -
- Both "takes" on this seem valid. Could there be a special method similar to take for de-lazying and taking a segment of the enumeration? e.g. maybe #pinch ?
e.lazy.pinch(3)
e.lazy.pinch(4..6)
e.lazy.pinch(2, 4)
-
- On Fri, Mar 16, 2012 at 7:24 PM, Eric Wong <normalperson@yhbt.net> wrote:
>> The only cases that break are cases that check e.class == EAGAIN,
>> which is probably not a good pattern anyway.
>
> I also noticed some test failures wit... -
09:29 AM Feature #6154: Eliminate extending WaitReadable/Writable at runtime
- Charles Nutter <headius@headius.com> wrote:
> I should have mentioned that JRuby has been running this way for a
> while (on master) and we have had no reports of incompatibility. The
> concrete subclass is_a EAGAIN and is_a WaitR... -
- Hi,
In message "Re: [ruby-core:43357] [ruby-trunk - Bug #6155] Enumerable::Lazy#flat_map raises an exception when an element does not respond to #each"
on Sat, 17 Mar 2012 06:42:22 +0900, Marc-Andre Lafortune <ruby-core@marc-... -
- Hi,
Shugo Maeda wrote:
> I doubt that this behavior of Enumerable#flat_map is reasonable.
> ...
I understand your point of view. This behavior was clearly intended in Matz's original commit, though (r25456). Changing this could also... -
12:48 AM Bug #6155: Enumerable::Lazy#flat_map raises an exception when an element does not respond to #each
- > > [1, 2, 3].flat_map { |n| n }.to_a
> ...
I was writing rubyspec for Enumerable::Lazy#flat_map had the same behaviour as Enumerable#flat_map (besides the obvious differences in return value). Here is what I was using as a basis: htt... -
- Hi,
In message "Re: [ruby-core:43358] [ruby-trunk - Feature #5008] Equal rights for Hash (like Array, String, Integer, Float)"
on Sat, 17 Mar 2012 07:13:17 +0900, Marc-Andre Lafortune <ruby-core@marc-andre.ca> writes:
|E... -
- > "Repeating myself, unlike other classes in the table, Hash does not have "natural" conversion from set of values, so that I don't think it's worth provide to_h method."
> ...
I see, you were referring to Enumerable#to_h and meant t... -
- Hi,
Yukihiro Matsumoto wrote:
> Repeating myself, unlike other classes in the table, Hash does not
> ...
Thanks for taking the time to reply.
Even if you will not accept Enumerable#to_h, how about `to_h` for Hash, Struct, OpenSt... -
- =begin
The syck extension should be removed for the following reasons:
Syck only supports YAML 1.0
Syck is not YAML 1.0 compliant.
Syck is not easy to maintain, and many of the bugs existing in it have not been fixed.
Psych ... -
- How can that be by design? What kind of design criteria says that "instance_eval should blow up if a lambda is passed to it"?
So you are saying that instance_eval passes the receiver into the Proc as an argument? Why would it do this... -
- Just the location was fixed. The error is "by design" -- as you discovered, you will need to use Proc.new (or lambda {|*| ... }).
-
- Just to be clear, where both issues fixed? i.e. the fact that an error was raised in this case at all, as well as the location of lambda errors?
-
- =begin
The transliteration string accepted by String#tr, #delete, #squeeze, and #count has its own backslash escape syntax (on top of that provided by string literals), but it isn't documented.
A backlash character escapes the subseq... -
01:49 AM Bug #6160 (Closed): '\\'.delete('\\') raise ArgumentError: empty string
- This issue was solved with changeset r35073.
Kazuhiro, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* string.c (trnext): fix bug with string ending with '\\'.
... -
- r35069 の変更の影響でクリーンビルドすると
../tool/transcode-tblgen.rb:758:in `delete': empty string (ArgumentError)
で止まります。
再現条件を絞り込んだところ '\\'.delete('\\') で ArgumentError になりました。 -
- Benoit Daloze wrote:
> So something like: #<Enumerator::Lazy: 1..5:each> or #<Enumerator::Lazy: #<Enumerator: 1..5:each>>
> ...
I agree that It would be nice. However, unlike Enumerator, Enumerator::Lazy doesn't have enough informatio...