Activity
From 07/21/2020 to 07/27/2020
07/27/2020
-
11:36 PM Feature #16345: Don't emit deprecation warnings by default.
- I'm not sure if this is the right way.
I agree that a deprecation warning is annoying for end users. I also understand that application developers don't want them to be nervous.
However, disabling the warnings by default does not so... -
09:02 PM Bug #17007: SystemStackError when using super inside Module included and lexically inside refinement
- Eregon (Benoit Daloze) wrote in #note-4:
> Thanks for the fix!
> ...
It's a consequence of the fix (skips the currently activated refinement during super), but I wouldn't say it is intended. Ideally, the fix would only affect looping ... -
07:30 PM Bug #17007: SystemStackError when using super inside Module included and lexically inside refinement
- Thanks for the fix!
BTW this changes the behavior on a new spec, is that intended? (result is [:A, :C] instead of [:A, :LOCAL, :C] on < 2.8)
https://github.com/ruby/spec/commit/b0da11b52560860e844470d145acee0ff4d4acea?w=1 -
03:18 PM Bug #17007 (Closed): SystemStackError when using super inside Module included and lexically inside refinement
- Applied in changeset commit:git|eeef16e190cdabc2ba474622720f8e3df7bac43b.
----------
Prevent SystemStackError when calling super in module with activated refinement
Without this, if a refinement defines a method that calls super and
in... -
08:14 PM Bug #12671 (Open): Hash#to_proc result is not a lambda, but enforces arity
- Is there a reason why the arity was not fixed to `1` (instead of `-1`)?
-
07:41 PM Revision 126fd5f1 (git): Update to ruby/spec@07164da
-
07:41 PM Revision 7429841a (git): Update to ruby/mspec@9cffee9
-
07:40 PM Revision 35ba2783 (git): Use a linked list to eliminate imemo tmp bufs for managing local tables
- This patch changes local table memory to be managed by a linked list
rather than via the garbage collector. It reduces allocations from the
GC and also fixes a use-after-free bug in the concurrent-with-sweep
compactor I'm working on. -
07:36 PM Misc #17053: RDoc for Hash Keys
- Thanks, @marcandre. Your first update above makes things much clearer to me. I'll continue studying this.
-
07:22 PM Misc #17053: RDoc for Hash Keys
- burdettelamar@yahoo.com (Burdette Lamar) wrote:
> My view has been this: This is API reference documentation. Ruby/ruby should have *the reference documentation*, and therefore should omit nothing.
This is a very ambitious goal I'm... -
06:37 PM Misc #17053: RDoc for Hash Keys
- Let me first repeat that I am very grateful of all efforts to improve our documentation.
Documentation can be difficult because it requires deep understanding of what needs to be documented and good experience with what is actually usef... -
05:55 PM Misc #17053: RDoc for Hash Keys
- Should have linked to the source of the remarks: https://github.com/ruby/ruby/pull/3139#issuecomment-663281047
-
04:36 PM Misc #17053: RDoc for Hash Keys
- Where is the source of the quote? Neither of the links seems to lead to it.
-
03:42 PM Misc #17053 (Open): RDoc for Hash Keys
- marcandre [comments](https://github.com/ruby/ruby/pull/3139#issuecomment-663281047) on my pull request regarding [documentation of Hash in Rdoc](https://docs.ruby-lang.org/en/master/Hash.html#class-Hash-label-Hash+Keys):
> The only th... -
06:12 PM Feature #17054 (Open): Some NilClass methods are faster if implemented in Ruby
- Sorry, looks like I misread.
-
05:59 PM Feature #17054 (Rejected): Some NilClass methods are faster if implemented in Ruby
-
05:00 PM Feature #17054: Some NilClass methods are faster if implemented in Ruby
- Patch was created.
https://github.com/ruby/ruby/pull/3366 -
04:54 PM Feature #17054 (Closed): Some NilClass methods are faster if implemented in Ruby
- Looking at these pull requests, I wondered "Is it faster to implement some NilClass methods in Ruby?"
* https://github.com/ruby/ruby/pull/3264
* https://github.com/ruby/ruby/pull/3277
So I tried implementing some NilClass methods ... - 03:18 PM Revision c5ae79d7 (git): * 2020-07-28 [ci skip]
-
03:18 PM Revision eeef16e1 (git): Prevent SystemStackError when calling super in module with activated refinement
- Without this, if a refinement defines a method that calls super and
includes a module with a module that calls super and has a activated
refinement at the point super is called, the module method super call
will end up calling back into ... -
03:16 PM Bug #17028 (Closed): On the latest OpenSSL adaptation
-
03:02 PM Bug #17052: Ruby with LTO enabled has issues with SIGSEGV handler
- Actually, the platform might not matter. It might fail just randomly, because now I have caught the same issue also on x86_64.
-
12:27 PM Bug #17052 (Closed): Ruby with LTO enabled has issues with SIGSEGV handler
- Fedora aims to enable link time optimization (LTO) of packages in next release. The specific changes in configuration options are available here [1]. Since that time, I observe following errors [2] at least on {aarch64,ppc64le} (and poss...
-
01:13 PM Bug #16492: TestBugReporter#test_bug_reporter_add test failures
- After a lot of testing, I think that the test should not fail with the timeout, because the input for the asserts is collected quite early and the system just does not have time to finish the threads and the child process. Since we don't...
- 06:25 AM Revision cb512792 (git): * 2020-07-27 [ci skip]
-
06:24 AM Revision c4f8095e (git): Use typewriter notation for var[:sym] correctly
07/26/2020
-
10:34 PM Bug #17051 (Third Party's Issue): Crash when attempting to load schema in Rails application
-
06:33 PM Bug #17051: Crash when attempting to load schema in Rails application
- I have confirmed you are correct. After switching back to my original installation of mysql, all is good.
-
04:23 PM Bug #17048: Calling initialize_copy on live modules leads to crashes
- nobu (Nobuyoshi Nakada) wrote in #note-10:
> Tried it.
> ...
Right, removing `Module.allocate` is one way since `dup`/`clone` uses the alloc function directly (and does not call `allocate`).
I think calling `Module.allocate` in user... -
06:21 AM Bug #17048: Calling initialize_copy on live modules leads to crashes
- Tried it.
https://github.com/nobu/ruby/tree/uninitialized-module - 12:24 PM Revision a8e5f785 (git): * 2020-07-26 [ci skip]
-
12:24 PM Revision d210a397 (git): Fixed a typo
-
09:33 AM Bug #16498: Hash#transform_values in 2.7.0 sets new hash's default to old hash's default_proc
- ruby_2_7 05c4c88767b54808cd1459a1d6da11179c422cfa merged revision(s) 1b4d406e3a04032b6d01e92b6d184a16945c6ac3.
-
09:32 AM Bug #16914: Hash.new with `default_proc` returns this `default_proc` instead of calling it sometimes
- ruby_2_7 05c4c88767b54808cd1459a1d6da11179c422cfa merged revision(s) 1b4d406e3a04032b6d01e92b6d184a16945c6ac3.
-
09:32 AM Revision 05c4c887 (git): merge revision(s) 1b4d406e3a04032b6d01e92b6d184a16945c6ac3: [Backport #16498] [Backport #16914]
- Hash#transform_values should return a plain new Hash
[Bug #16498] -
09:11 AM Bug #16522: Ruby 2.7 logs deprecation warning when Warning[:deprecated] is set to false.
- We are discussing on the deprecated warning category feature in 2.7.2 on #17000 too.
As these are keyword arguments warnings, these will be suppressed by default in 2.7.2 anyway.
-
08:59 AM Bug #16801: The default Struct constructor improperly handle keyword arguments
- ruby_2_7 61c6d433060881e952140d2154c06f8c9803dc8a.
-
08:45 AM Revision 61c6d433 (git): partially merge revision adf709a78534c1483ba851ccb0490464ca31503c: [Backport #16801]
- Classes made from Struct should have default new singleton method.
Co-authored-by: Yusuke Endoh mame@ruby-lang.org
Co-authored-by: John Hawthorn john@hawthorn.email
Co-authored-by: Adam Hess HParker@github.com
... -
07:19 AM Bug #16846: Commit - win32ole: separate global variable declarations and definitions - backport?
- ruby_2_7 43cc6997c59d2fbe3b91e91ee52faaa8749e9349 merged revision(s) a0bc3f2a1c2c98f225612101cb4e1ea1a6813546,75a0447c15a7ab017bd4240c2a9cc69b134b80b9,f1699314147bad2cf5550cc582693424fdbc2510.
-
07:19 AM Revision 43cc6997 (git): merge revision(s) a0bc3f2a1c2c98f225612101cb4e1ea1a6813546,75a0447c15a7ab017bd4240c2a9cc69b134b80b9,f1699314147bad2cf5550cc582693424fdbc2510: [Backport #16846]
- Suppress C4267 "possible loss of data" warnings
Suppress C4267 "possible loss of data" warnings
Just cast down explicitly.
win32ole: separate global variable declarations and definitions
https://gcc.gn...
07/25/2020
-
11:27 PM Misc #17050: profiler gem
- I was able to profile 200+ million* allocations with my fork which was impossible with the current implementations. Right now my current plan is to upstream these changes to `memory_profiler`. (*sorry, incorrectly said billions previousl...
-
01:15 PM Misc #17050: profiler gem
- @ioquatrix I’m curious. What’s the difference between your memory-profiler and the existing memory_profiler?
For context I’ve been working on https://github.com/shopify/heap-profiler for the last week, and I’m also very interested in ... -
01:12 PM Misc #17050: profiler gem
- In the `profile` stdlib, both files are used: `-rprofile` starts the profiler immediately, while `profiler.rb` is like a library:
https://github.com/ruby/ruby/blob/ruby_2_6/lib/profile.rb
So it seems to me not advisable to reuse thos... -
11:10 AM Misc #17050: profiler gem
- I agree all your points. I already have working `profiler-memory` to a certain extent.
-
09:38 AM Misc #17050: profiler gem
- I'd recommend starting with something specific like `profiler-memory`.
`profiler` is very generic but therefore also unclear and will make people think it's a stdlib-like profiler, but I guess it will not be.
I also think it's too ... -
04:10 AM Misc #17050: profiler gem
- My initial goal is to expose some general data structures for efficiently capturing large memory profiles on top of `ObjectSpace` and `GC` modules, similar to how memory_profiler gem works. I don't mind making separate gem, but it seems ...
-
03:39 AM Misc #17050: profiler gem
- Can you tell us shortly what you plan to use that gem/namespace for? If it's something that can (in some reasonable way) replace the (former?) profile/profiler functionality, then please go for it. At one point, I was planning to work on...
-
12:25 AM Misc #17050: profiler gem
- Also I'd be happy to receive/resuse the `profile` namespace too but either one is fine and the `profile` gem actually has an interesting implementation.
-
12:03 AM Misc #17050 (Closed): profiler gem
- I would like to reuse profiler gem namespace:
https://rubygems.org/gems/profiler/versions
It currently conflicts with `profile/lib/profiler.rb` however this is no longer part of stdlib.
cc @ko1 -
09:01 PM Bug #17051: Crash when attempting to load schema in Rails application
- I think you are correct Alan. During my rebuild of the laptop, I inadvertently installed v 8 instead of 5.6. What threw me off was the other Rails app working without issue, using the same ruby version, mysql2 version, and Mysql database...
-
08:09 PM Bug #17051: Crash when attempting to load schema in Rails application
- > Thank you for responding Alan. Is 2.5.8 sufficient?
Actually, you seem to be running into a known problem in the mysql2 gem.
Please see https://github.com/brianmario/mysql2/issues/1036 and https://github.com/brianmario/mysql2/issue... -
07:47 PM Bug #17051: Crash when attempting to load schema in Rails application
- Thank you for responding Alan. Is 2.5.8 sufficient?
-
07:31 PM Bug #17051: Crash when attempting to load schema in Rails application
- Support for the 2.4 series has [ended](https://www.ruby-lang.org/en/news/2020/04/05/support-of-ruby-2-4-has-ended/). Could you see if upgrading to a newer version of Ruby solves the crash?
-
06:42 PM Bug #17051 (Third Party's Issue): Crash when attempting to load schema in Rails application
- I am experiencing a crash when running `rake db:schema:load` or `rake db:migrate` in a Rails 4.2.9/Mysql2 0.4.0 application.
I don't believe it is a specific issue with a ruby version, as I have tried with Rubies 2.3.1, 2.3.8, and 2.... -
06:33 PM Bug #17048: Calling initialize_copy on live modules leads to crashes
- > How about having an initialized flag that's set by #initialize and #initialize_copy and checked in both of these methods if we want a quick fix?
That doesn't work because you can trigger the bug without ever calling `initialize` on th... -
10:32 AM Bug #17048: Calling initialize_copy on live modules leads to crashes
- Should we rather design a good way to allow copying but yet not have to deal with uninitialized state?
Right now the only well-defined protocols for copying are
* `dup = allocate, copy @ivars, initialize_dup (which calls initialize_c... -
02:35 AM Bug #17048: Calling initialize_copy on live modules leads to crashes
- I agree with @alanwu, that it won't be worth.
```diff
diff --git c/class.c i/class.c
index 6835d2d7289..f7a56601634 100644
--- c/class.c
+++ i/class.c
@@ -354,6 +354,13 @@ static void ensure_origin(VALUE klass);
VALUE
rb_mod_... -
12:42 PM Bug #16780: Net::FTP PUT command issuing Net::ReadTimeout too quickly
- ruby_2_7 578bacc471fa3fa14f8607fe67adccce21e81657 merged revision(s) 5e81e8675a020ecd493620a4ff38db8fcf4b972a.
-
12:42 PM Revision 578bacc4 (git): merge revision(s) 5e81e8675a020ecd493620a4ff38db8fcf4b972a: [Backport #16780]
- Ignore exceptions when closing data connections [Bug #16780]
Patch by koshigoe (Masataka SUZUKI). Thanks! -
10:12 AM Feature #17016: Enumerable#accumulate
- y.annikov (Yakov Annikov) wrote in #note-22:
> I've created a PR with the implementation of `scan` and `lazy.scan` methods https://github.com/ruby/ruby/pull/3358
> ...
I renamed it to `reflect` for a while though I like `scan` more.
Her... -
07:49 AM Feature #17016: Enumerable#accumulate
- nobu (Nobuyoshi Nakada) wrote in #note-23:
> RubyBugs (A Nonymous) wrote in #note-19:
> ...
I think this is way too generic. In the same vein, we could call it "return", because it returns all intermediate states.
Also, I think "proje... -
06:20 AM Feature #17016: Enumerable#accumulate
- parker (Parker Finch) wrote in #note-21:
> nobu (Nobuyoshi Nakada) wrote in #note-20:
> ...
I fully agree. Lazy variants of methods should only differ with respect to laziness, not anything else.
-
05:17 AM Bug #16834: rb_profile_frame_classpath only recognize class singleton methods, not module singleton methods
- ruby_2_7 12391cdbe11f3fbeb3b04c30b944139e5bbd9ea6 merged revision(s) cbe4f75ef802f13d05f94e42274b65a062bd3666.
-
05:17 AM Revision 12391cdb (git): merge revision(s) cbe4f75ef802f13d05f94e42274b65a062bd3666: [Backport #16834]
- Fix rb_profile_frame_classpath to handle module singletons
Right now `SomeClass.method` is properly named, but `SomeModule.method`
is displayed as `#<Module:0x000055eb5d95adc8>.method` which makes
profiling annoy... -
04:41 AM Bug #16854: Using (...) when the method name is a keyword generates error
- ruby_2_7 be359442cb07c25fdc769431ffed3249b9016829 merged revision(s) 71c166e11e761dcaaa943f9b94da38f86ada1bdb.
-
04:40 AM Revision be359442 (git): merge revision(s) 71c166e11e761dcaaa943f9b94da38f86ada1bdb: [Backport #16854]
- Fixed argument forwarding in reserved word method [Bug #16854]
-
03:00 AM Bug #16798: ENV.replace on Windows with a variable name not respecting case will clear it
- ruby_2_7 89f06ce8b8a887f12b53ea190d79a58e98b59008 merged revision(s) 08529a61153e5c40f57a65272211357511d6e6db.
-
03:00 AM Revision 89f06ce8 (git): merge revision(s) 08529a61153e5c40f57a65272211357511d6e6db: [Backport #16798]
- Compare environment variable names in those manor [Bug #16798]
-
02:56 AM Bug #16767: Time#strftime not working correctly with a big precision on recurred formats like "%c"
- ruby_2_7 2e9626fddd168bd12352b4f5dc3412c6a33ce44e merged revision(s) 2f1895fa15386fb3cdc91c5604171290828b9da8.
-
02:56 AM Revision 2e9626fd (git): merge revision(s) 2f1895fa15386fb3cdc91c5604171290828b9da8: [Backport #16767]
- Fixed formatted substring expansion [Bug #16767]
07/24/2020
-
10:59 PM Bug #17025: `Time#ceil` does not work like `Rational#ceil` or `Float#ceil`
- I've added a pull request to fix this: https://github.com/ruby/ruby/pull/3362
-
10:29 PM Bug #17048: Calling initialize_copy on live modules leads to crashes
- In principle I agree that allowing initialization only once is a good way to go, but the way `Module.allocate` is currently setup makes implementing this a bit complicated. At the moment there is not really a pre-init state for modules a...
-
05:52 PM Bug #17048: Calling initialize_copy on live modules leads to crashes
- I would recommend to have `initialize_copy` always raise instead of only raising if the module has children. It's more consistent, and there is no reason anyone should be calling `initialize_copy` more than once. This shouldn't be cons...
-
05:23 PM Bug #17048: Calling initialize_copy on live modules leads to crashes
- I'm not proposing that we remove `initialize_copy`, but to make it raise when the receiver has children. So this is what it would look like:
```ruby
module A
end
A.send(:initialize_copy, Module.new) # fine, no one inherits from A... -
04:40 PM Bug #17048: Calling initialize_copy on live modules leads to crashes
- Removing `Module#initialize_copy` would probably require changes to `Module#{dup,clone}`. Maybe we can set a flag in `Module#initialize_copy` such that calling the method raises if called again on the same module (not sure if that is w...
-
04:09 PM Bug #17048 (Closed): Calling initialize_copy on live modules leads to crashes
Here's a repro script
```ruby
loop do
m = Module.new do
prepend Module.new
def hello
end
end
klass = Class.new { include m }
m.send(:initialize_copy, Module.new)
GC.start
klass.new.hello rescue ...-
09:12 PM Bug #17049: Net::IMAP - Handling of NOOP untagged responses sent by Zimbra
- Per RFC 3501 Section 7: `The client MUST be prepared to accept any response at all times.` Arguably, raising an exception is not proper preparation. Looking at the formal grammar, it does not appear that `* NOOP` is a valid server resp...
-
07:53 PM Bug #17049 (Closed): Net::IMAP - Handling of NOOP untagged responses sent by Zimbra
- Zimbra server sends invalid untagged responses to prevent some clients from disconnecting during long-running requests.
As they are invalid, they raise an exception in Net::IMAP, while they could be clearly identified and safely ignored... -
08:17 PM Bug #17044 (Closed): ObjectSpace.dump allocates one string per anonymous class and module
-
12:08 PM Revision 3ead2770 (git): Respect visibility in non-array Enumerable#inject [Bug #13592]
-
11:17 AM Bug #17046 (Closed): Time#to_a yday is 0(given timezone info)
- Applied in changeset commit:git|2735da2039b9e441e41b11b606ba362db350a658.
----------
Fix Time#to_a behavior with timezone [Bug #17046] -
11:17 AM Revision 2735da20 (git): Fix Time#to_a behavior with timezone [Bug #17046]
-
02:30 AM Feature #17016: Enumerable#accumulate
- RubyBugs (A Nonymous) wrote in #note-19:
> In keeping with the Ruby-ish collection methods that end with "-ect", how about
> ...
I'd like that “this "reflects" all intermediate states” part. - 02:11 AM Revision 922fe4da (git): * 2020-07-24 [ci skip]
-
02:00 AM Revision ba99eae2 (git): [ruby/optparse] Fix ls-files matching regexp
- As splitting by NUL means to allow the file names to contain
newlines, path names should match at beginning-of-string instead
of beginning-of-line.
https://github.com/ruby/optparse/commit/df3933aa2b
07/23/2020
-
10:25 PM Bug #17031: `Kernel#caller_locations(m, n)` should be optimized
- I've added a pull request that addresses this issue: https://github.com/ruby/ruby/pull/3357
-
10:21 PM Feature #17047 (Open): Support parameters for MAIL FROM and RCPT TO
- ## Proposal
In `Net::SMTP`, add support for parameters for `MAIL FROM` and `RCPT TO`, such as [SMTPUTF8](https://tools.ietf.org/html/rfc6531) and [REQUIRETLS](https://tools.ietf.org/html/rfc8689).
I suggest extending `Net::SMTP#mailf... -
09:44 PM Feature #17016: Enumerable#accumulate
- I've created a PR with the implementation of `scan` and `lazy.scan` methods https://github.com/ruby/ruby/pull/3358
Feel free to reject it but any comments are appreciated. I got a lot of fun writing this code and looking at Ruby source... -
03:39 PM Feature #17016: Enumerable#accumulate
- nobu (Nobuyoshi Nakada) wrote in #note-20:
> With https://github.com/ruby/ruby/pull/3337, you can
> ...
Thank you for writing that nobu! That is exactly the behavior we need.
I'm worried about the backwards compatibility of changing... -
03:12 AM Feature #17016: Enumerable#accumulate
- With https://github.com/ruby/ruby/pull/3337, you can
```ruby
(1..).lazy.inject(0, :+).first(10) #=> [0, 1, 3, 6, 10, 15, 21, 28, 36, 45]
``` -
08:57 PM Feature #17043: Invokable module for custom Proc-like objects
- Got it, that make sense. But, just to be clear my proposal is not to include my module in the standard library, but to include a module that would generalize the notion of a Proc, much as `Enumerable` generalizes the notion of a collecti...
-
06:43 PM Feature #17043 (Rejected): Invokable module for custom Proc-like objects
- > But, it'd be great to be able to treat sets as predicate functions
Note that since Ruby 2.5, `Set#===` is an alias for `include?`, so you can do `ary.grep(Set[...])` for example.
> ...
Most of the standard library is being made ... -
06:19 PM Feature #17043: Invokable module for custom Proc-like objects
- Yeah, I guess I wasn't that clear. I'm curious if an officially blessed "Invokable" module might be a useful thing for the standard library. I obviously don't have the perspective you do, but it seems that could be a powerful thing to ma...
-
05:16 AM Feature #17043 (Feedback): Invokable module for custom Proc-like objects
- While your library seems great, what is proposed in this ticket is not that obvious. How can we help? What can we do?
-
12:42 AM Feature #17043 (Rejected): Invokable module for custom Proc-like objects
- Ruby beautifully integrates Functional and Object-Oriented Programming, and there's more moving in the direction of supporting Functional Programming. A generalization of the Proc interface would enable users to integrate functional appr...
-
07:28 PM Bug #16921: s390x: random test failures for timeout or segmentation fault
- I sent this PR related to this ticket.
https://github.com/ruby/ruby/pull/3354
It's to apply test-scale to test_nogvl_poll.
Other tests I showed above is applying time-scale.
I ran the Ruby tests with `RUBY_TEST_TIMEOUT_SCALE=100 ... -
03:06 PM Bug #16921: s390x: random test failures for timeout or segmentation fault
- > Try an environment variable RUBY_TEST_TIMEOUT_SCALE. If you set RUBY_TEST_TIMEOUT_SCALE=10, all timeout tests wait 10 times longer.
Sorry for late response. I confirmed the environment variable improves. You can see https://bugs.rub... -
07:22 PM Bug #16492: TestBugReporter#test_bug_reporter_add test failures
- > Therefore I wonder if there is any other possible solution?
Another option might be using `--retry` with jobs.
https://github.com/ruby/ruby/blob/098e8c2873ed7cfa276aa87967ce28ac711cbb30/tool/lib/test/unit.rb#L194
But it seems it... -
03:15 PM Bug #16492: TestBugReporter#test_bug_reporter_add test failures
- > > I extended the timeout and so far the test was executed in the more then 56 seconds for the worst case. I am afraid that even 60 seconds timeout would not be enough in some case.
> ...
How about just running the tests with large ti... -
03:02 PM Bug #16492: TestBugReporter#test_bug_reporter_add test failures
- I took a look at the code.
```
RUBY_TEST_TIMEOUT_SCALE=5 \
make runruby TESTRUN_SCRIPT="-Itool/lib test/-ext-/bug_reporter/test_bug_reporter.rb -v"
```
`test/-ext-/bug_reporter/test_bug_reporter.rb` calling
`tool/lib/test/uni... -
06:54 PM Bug #17046: Time#to_a yday is 0(given timezone info)
- Patch was created: https://github.com/ruby/ruby/pull/3355
-
06:37 PM Bug #17046 (Closed): Time#to_a yday is 0(given timezone info)
- I interest in Time#to_a behavior(background is Bug #17042)
Tried whether yday is displayed correctly in `Time #to_a`.
But, yday seems to be 0 when passing the time zone.
```bash
$ ruby -v
ruby 2.8.0dev (2020-07-23T14:44:25Z mast... -
02:44 PM Revision 098e8c28 (git): Suppress "assigned but unused variable" warnings
- 01:49 PM Revision e43d6295 (git): [ruby/observer] add symbol usage example to Observer#add_observer [doc]
- https://github.com/ruby/observer/commit/62a94e3799
-
08:52 AM Feature #17045 (Closed): ObjectSpace.dump_all should allocate as little as possible in the GC heap
- For context I'm working on a [heap profiler](https://github.com/Shopify/heap-profiler). In short the use case is like this (pseudo code):
```ruby
GC.disable
ObjectSpace.dump_all(output: file1)
# run the user code
ObjectSpace.dump_... -
08:47 AM Bug #16764: Module.const_source_location does not work on autoloaded constants
- ruby_2_7 c65aae118ccff86096b9983641b371491bc23434 merged revision(s) 927308108cced69cae478798004524b9a5d2f252.
-
08:47 AM Revision c65aae11 (git): merge revision(s) 927308108cced69cae478798004524b9a5d2f252: [Backport #16764]
- Fix source location of autoloaded constant [Bug #16764]
-
08:30 AM Bug #16749: File.lchmod specs fails on linux since glibc 2.31.9000
- ruby_2_7 4437f9eb0bf8369bcf12bd7cd324e11b5d885e07 merged revision(s) da05c1552ee519d8f180b48d97148d28501acb35.
-
08:30 AM Revision 4437f9eb (git): merge revision(s) da05c1552ee519d8f180b48d97148d28501acb35: [Backport #16749]
- Update to ruby/spec@cc7b9e5
-
08:23 AM Bug #16662: lchmod available in linux since glibc 2.31.9000
- ruby_2_7 c53cee7a0e7b3e87ba3fbafa86bd74460af18d93 merged revision(s) 72c02aa4b79731c7f25c9267f74b347f1946c704.
-
08:22 AM Revision c53cee7a (git): merge revision(s) 72c02aa4b79731c7f25c9267f74b347f1946c704: [Backport #16662]
- Moved not-implemented method tests [Bug #16662]
Test not-implemented method with the dedicated methods, instead of
platform dependent features. -
08:02 AM Bug #16519: pp [Hash.ruby2_keywords_hash({})] shows `[nil]`
- Seems already backported at bb93659fefd7f4557129043742771a33bd30c255.
-
07:59 AM Bug #16501: Support marshaling of ruby2_keywords flag
- ruby_2_7 ae804b143455075687c8b4a401fba48fda72a217 merged revision(s) b23fd59cbb3f097bcd559d0c85a86ff7a1eeeb7e.
-
07:59 AM Revision ae804b14 (git): merge revision(s) b23fd59cbb3f097bcd559d0c85a86ff7a1eeeb7e: [Backport #16501]
- marshal.c: Support dump and load of a Hash with the ruby2_keywords
flag
It is useful for a program that dumps and load arguments (like drb).
In future, they should deal with both positional arguments and keyword... -
07:57 AM Revision 54acb3dd (git): Improved Enumerable::Lazy#zip
- | |compare-ruby|built-ruby|
|:-------------------|-----------:|---------:|
|first_ary | 290.514k| 296.331k|
| | -| 1.02x|
|first_nonary | 166.954k| 169.178k|
| ... -
07:57 AM Revision 6b3cff12 (git): Improved Enumerable::Lazy#flat_map
- | |compare-ruby|built-ruby|
|:-------|-----------:|---------:|
|num3 | 96.333k| 160.732k|
| | -| 1.67x|
|num10 | 96.615k| 159.150k|
| | -| 1.65x|
|ary2 | 103.836k| 17... -
07:57 AM Revision 89a86788 (git): New functions to pass more elements than passed
-
07:56 AM Revision f1563edc (git): Get rid of use of magic number 'E'
-
07:17 AM Bug #17044 (Closed): ObjectSpace.dump allocates one string per anonymous class and module
- This is because it dump the module/class names using `rb_class2name` which will create an ad hoc name for anonymous classes (e.g. `"#<Class:0x00007fc8bdcda630>"`)
Since `ObjectSpace.dump_all` is used to observe the heap, it should ide... -
05:57 AM Revision 347639ad (git): Removed fragile tests in https://github.com/ruby/ruby/pull/3349
-
05:30 AM Revision ff397d00 (git): dln.h: delete unused codes
- defines.h already has them. Also __cplusplus can never be defined here.
-
05:30 AM Revision c4fc737f (git): include/ruby/util.h: delete unused codes
- - util.h includes defines.h,
- ... which includes ruby/backward/2/stdarg.h,
- ... which always defines _.
This `#ifndef _` must never happen. -
05:17 AM Revision 1d8b689b (git): Remove unused field in rb_iseq_constant_body
- This was introduced in 191ce5344ec42c91571f8f47c85be9138262b1c7
and has been unused since beae6cbf0fd8b6619e5212552de98022d4c4d4d4 -
05:02 AM Bug #16830: URI.parse raises NoMethodError instead of URI::InvalidURIError
- ruby_2_7 4f714939efde6d6b3b74c09e1e151e6ce6818b90 merged revision(s) e04418bb16cd99b4a4402e7457d3bdc967284f98.
-
05:02 AM Revision 4f714939 (git): merge revision(s) e04418bb16cd99b4a4402e7457d3bdc967284f98: [Backport #16830]
- [ruby/uri] Check if DN exists
https://bugs.ruby-lang.org/issues/16830
https://github.com/ruby/uri/commit/b4bf8c1217 -
04:51 AM Bug #16826: ObjectSpace::WeakMap#key? returns false if value is nil
- ruby_2_7 9da6470d7b3aa136b4b92469c8bbc522beb1ac31 merged revision(s) a2be428c5fec31b8adbd5ac087e7637ddf7e54d0.
-
04:50 AM Revision 9da6470d (git): merge revision(s) a2be428c5fec31b8adbd5ac087e7637ddf7e54d0: [Backport #16826]
- Fix ObjectSpace::WeakMap#key? to work if the value is nil
* Fixes [Bug #16826] -
03:13 AM Bug #17033: Infinite Traceback when encountering an Exception while catching an Exception
- ruby_2_7 27fa1c61b78c1685ccf9ac203a95cfa9041d618f merged revision(s) 579645d9f870fa4116dcd3200bbbb6e2c0b7f400.
-
03:13 AM Revision 27fa1c61 (git): merge revision(s) 579645d9f870fa4116dcd3200bbbb6e2c0b7f400: [Backport #17033]
- Fixed infinite loop at error in printing cause [Bug #17033]
-
02:52 AM Revision caf565f7 (git): Ensure time object meets a given condition [Bug #17042]
-
02:46 AM Bug #16760: backport #67305 / e39f7e64 to 2.6?
- I just find that e39f7e64b73f0506def7adc88226d6821608da54 (r67305) is included in ruby_2_7.
-
02:35 AM Revision afacf85e (git): Merge pull request #3352 from S-H-GAMELINKS/bug/17042-strftime
- Fix Time#strftime with timezone [Bug #17042]
-
02:35 AM Bug #17042 (Closed): Times with timezones return incorrect week numbers
- Applied in changeset commit:git|8ed687a4d7b7a77f30f8e937f58aae74bfb699b6.
----------
Test for weeknumber with timezone [Bug #17042] -
02:33 AM Revision 8ed687a4 (git): Test for weeknumber with timezone [Bug #17042]
-
02:33 AM Bug #17024: Times with timezones return incorrect wday and yday
- ruby_2_7 4be9bf1f67b997fc519625d56a93b8a68a70d124 merged revision(s) 99a9c3fe2eaab8157765d792dc871da6daea0327.
-
02:33 AM Revision 4be9bf1f (git): merge revision(s) 99a9c3fe2eaab8157765d792dc871da6daea0327: [Backport #17024]
- Fixed yday and wday with timezone [Bug #17024]
-
02:16 AM Bug #16918: Dir.mktmpdir should yield a copy of the dir to protect cleanup
- ruby_2_7 13d2ab0d88bbf72ed310efaec6edc46dd96fdb4d merged revision(s) 2ecfb88ee50510955acd3ae9fc94a5f109e7f109.
-
02:16 AM Revision 13d2ab0d (git): merge revision(s) 2ecfb88ee50510955acd3ae9fc94a5f109e7f109: [Backport #16918]
- Correctly remove temporary directory if path yielded is mutated
Another approach would be to freeze the string, but that could
cause backwards compatibility issues.
Fixes [Bug #16918] -
02:11 AM Bug #16925: Backport request: net/http raises in ensure and replaces the original error
- ruby_2_7 cc39480cf9f2767967b6bcc69ccb3c201e5b2231 merged revision(s) 5a79d8e0507cd143100bf928a88a59a8b5a5bca6,160511d851375f7cb922faae3a9310633187f51f.
-
02:11 AM Revision cc39480c (git): merge revision(s) 5a79d8e0507cd143100bf928a88a59a8b5a5bca6,160511d851375f7cb922faae3a9310633187f51f: [Backport #16925]
- Fix error raised by Net::HTTPResponse#inflater if the block raises
* See https://bugs.ruby-lang.org/issues/13882#note-6
Quarantine specs which fail frequently with CHECK_LEAKS=true -
01:57 AM Revision f120e652 (git): [ruby/optparse] Define OptionParser::Version
- https://github.com/ruby/optparse/commit/4c0021b5b2
-
01:57 AM Revision cd429e68 (git): [ruby/optparse] Update required ruby version
- Now needs `DidYouMean#formatter` which is provided since
did_you_mean 1.2, which requires ruby 2.5.
https://github.com/ruby/optparse/commit/d44bb5c715 -
01:52 AM Revision 6a0cb1d6 (git): Avoid allocating a string when dumping an anonymous module or class
-
12:06 AM Revision 5d04ac6e (git): Enhanced RDoc for Array (#3350)
- * Enhanced RDoc for Array
Methods:
==
eql?
hash
include?
<=>
07/22/2020
-
11:01 PM Revision 37e6c836 (git): Lazily insert origins on prepend to save memory
- 98286e9850936e27e8ae5e4f20858cc9c13d2dde made it so that
`Module#include` allocates an origin iclass on each use. Since `include`
is widely used, the extra allocation can contribute significantly to
memory usage.
Instead of always alloc... -
07:47 PM Bug #17023: How to prevent String memory to be relocated in ruby-ffi
- tenderlovemaking (Aaron Patterson) wrote in #note-16:
> I think Lars was having trouble expanding strings that are frozen, not pinning them. I suggested that strings could be expanded such that they cannot be embedded in the Ruby objec... -
06:23 PM Bug #17023: How to prevent String memory to be relocated in ruby-ffi
- Eregon (Benoit Daloze) wrote in #note-15:
> Maybe we need a pin function that doesn't mind if the String is frozen?
> ...
I think Lars was having trouble expanding strings that are frozen, not pinning them. I suggested that strings co... -
06:19 PM Bug #17023: How to prevent String memory to be relocated in ruby-ffi
- Maybe FFI should discourage cases where the native function saves the RSTRING_PTR() and still use it after the native call returned?
That seems quite dangerous if e.g. the Ruby String is mutable.
Is it commonly used, do we have a real ... -
05:57 PM Bug #17023: How to prevent String memory to be relocated in ruby-ffi
- One idea I had is that we could make `RSTRING_PTR`, `StringValueCStr`, `StringValuePtr`, etc ensure that the character buffer it returns is not embedded in the object. So, if it's an embedded string, move it to `malloc`. We could intro...
-
09:45 AM Bug #17023: How to prevent String memory to be relocated in ruby-ffi
- @Hanmac The string must be kept as a ruby object in an instance variable or constant, etc. and must not be modified as long as it's in use in the C library. Similar on the C side the string must not be modified and freeing it is not allo...
-
07:41 AM Bug #17023: How to prevent String memory to be relocated in ruby-ffi
- the problem there is that ruby can't know how long the C lib is going to use the String. Depending on the C Function, might even take "ownership" of the string and does free it itself, so when Ruby would free the string too, it causes a ...
-
07:32 PM Bug #17042: Times with timezones return incorrect week numbers
- Created patch.
https://github.com/ruby/ruby/pull/3352 -
07:15 PM Bug #17042: Times with timezones return incorrect week numbers
- This code resolve this behaviour.
```c
static VALUE
time_strftime(VALUE time, VALUE format)
{
struct time_object *tobj;
const char *fmt;
long len;
rb_encoding *enc;
VALUE tmp;
GetTimeval(time, tobj);... -
06:43 PM Bug #17042: Times with timezones return incorrect week numbers
- Apparently the calculation result `ret = ((timeptr->tm_yday + 7 - wday) / 7);` is negative(`timeptr->tm_yday` is negative).
```c
static int
weeknumber(const struct tm *timeptr, int firstweekday)
{
int wday = timeptr->tm_wday;
i... -
05:56 PM Bug #17042: Times with timezones return incorrect week numbers
- Same behaviour in `2.7` & `2.6`(checked `2.7.1`, `2.7.0`, `2.6.6`, `2.6.5`).
-
02:08 PM Bug #17042 (Closed): Times with timezones return incorrect week numbers
- Times with timezones return incorrect week numbers from strftime. For example:
$ irb -r tzinfo
irb(main):001:0> Time.utc(2020, 7, 22, 12, 0, 0).strftime('%U %V %W')
=> "29 30 29"
irb(main):002:0> Time.new(2020, 7, 2... -
06:12 PM Feature #17016: Enumerable#accumulate
- parker (Parker Finch) wrote in #note-18:
> Are there other names you think should be considered?
In keeping with the Ruby-ish collection methods that end with "-ect", how about
* **`reflect`** -- the idea is to contrast with `inject`,... -
05:23 PM Feature #17016: Enumerable#accumulate
- matz (Yukihiro Matsumoto) wrote in #note-17:
> I don't see any real-world use-case for `scan_left`. Is there any?
I think there are real-world use cases!
Would you consider converting a history of transactions into a history of ... -
05:46 PM Bug #17029 (Closed): URI.parse considers https://example.com/### invalid when browsers consider it valid
-
05:28 PM Misc #17041: DevelopersMeeting20200831Japan
- * [Feature #16989] Sets need ♥️, aka the "Set Program" (marcandre)
* Bring `Set` into core
* Insure interoperability with `Array` (e.g so `array & set` works and is efficient)
* Shorthand syntax for static frozen sets of string/... -
08:04 AM Misc #17041: DevelopersMeeting20200831Japan
- Please note that it may not be possible to go though all topics that are raised in this agenda because we will discuss 2.8/3.0 release schedule. (Perhaps, we will prioritize the topics related to 2.8/3.0, such as Ractor.) Thanks.
-
06:06 AM Misc #17041: DevelopersMeeting20200831Japan
- * [Feature #17040] cleanup include/ruby/backward* (shyouhei)
* Is anybody against it? -
05:58 AM Misc #17041: DevelopersMeeting20200831Japan
- * [Feature #17039] Remove `Time#succ` (znz)
* `Time#succ` is obsolete since 1.9.2. -
05:55 AM Misc #17041 (Closed): DevelopersMeeting20200831Japan
- # The next dev meeting
**Date: 2020/08/26 13:00-17:00**
Place/Sign-up/Agenda/Log: https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20200826Japan.md
- Dev meeting *IS NOT* a decision-making place. All decisions ... -
04:35 PM Bug #16492: TestBugReporter#test_bug_reporter_add test failures
- On top of that, I also received following error:
~~~
+ make runruby 'TESTRUN_SCRIPT=-Itool/lib test/-ext-/bug_reporter/test_bug_reporter.rb -v'
./revision.h unchanged
./miniruby -I./lib -I. -I.ext/common ./tool/runruby.rb --extout... -
01:33 PM Bug #16492: TestBugReporter#test_bug_reporter_add test failures
- > waiting somewhere else:
Presumably waiting for `status ||= Process.wait2(pid)[1]` -
01:29 PM Bug #16492: TestBugReporter#test_bug_reporter_add test failures
- Just two examples from my testing:
~~~
+ make runruby 'TESTRUN_SCRIPT=-Itool/lib test/-ext-/bug_reporter/test_bug_reporter.rb -v'
./miniruby -I./lib -I. -I.ext/common ./tool/runruby.rb --extout=.ext -- --disable-gems -Itool/lib te... -
03:40 PM Bug #14804 (Closed): GzipReader cannot read Freebase dump (but gzcat/zless can)
- This can now be handled using `Zlib::GzipReader.zcat`, which was recently added to zlib.
-
03:39 PM Bug #9790 (Closed): Zlib::GzipReader only decompressed the first of concatenated files
- matz approved Zlib::GzipReader.zcat, so I merged the pull request into zlib.
-
03:39 PM Bug #11180 (Closed): Missing lines with Zlib::GzipReader
- matz approved Zlib::GzipReader.zcat, so I merged the pull request into zlib.
-
03:36 PM Feature #16923 (Closed): Switch reserved for numbered parameter warning to SyntaxError
- Implemented in commit:d47e124857ecdccfeb0766c04cf1ef2cdfdd08bc
- 03:35 PM Revision fdcbb288 (git): * 2020-07-23 [ci skip]
-
03:34 PM Revision d47e1248 (git): Switch reserved for numbered parameter warning to SyntaxError
-
02:58 PM Misc #17019 (Closed): DevelopersMeeting20200720Japan
-
12:28 PM Revision 50aac2ff (git): Share the size for sigaltstack between configure.ac and signal.c
-
11:46 AM Revision 8b0dc77a (git): configure.ac: Bump the size of sigaltstack
- The RubyVM uses C macro defines to feature detect whether
`backtrace(2)` support is available, and if so it includes C level backtraces
when the RubyVM itself crashes.
But on my machine, C level backtraces from `vm_dump.c` didn't work w... -
09:38 AM Revision 7befc0cd (git): Promote optparse to default gems
-
05:16 AM Feature #17040: cleanup include/ruby/backward*
- I'm pretty confident that nobody is against such change. But opening an issue anyways, because this is a breaking change.
-
05:14 AM Feature #17040 (Open): cleanup include/ruby/backward*
- I recently noticed [[ruby-dev:35813]](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-dev/35813):
> こんなところでどうでしょうか。include/ruby/backwardは2.0までには
> ...
It reads: "How about the following. Will delete include/ruby/backward by 2...
07/21/2020
-
10:07 PM Revision a50750c8 (git): Enhanced RDoc for Array
-
10:07 PM Revision d29de7b3 (git): Enhanced RDoc for Array
-
10:07 PM Revision 8a974e0f (git): Enhanced RDoc for Array
-
08:18 PM Bug #17023: How to prevent String memory to be relocated in ruby-ffi
- Sorry for not responding earlier! Unfortunately this issue still remains. So it is not closed and the backported commit doesn't fix it in any way.
I tried Aarons hint to change all passed strings to non-embedded content. The result is... -
07:11 PM Revision 20172672 (git): Add require 'irb/ruby-lex' to use RubyLex
-
07:04 PM Feature #10911 (Closed): IPAddr.new should ignore zone identifiers
-
06:49 PM Revision ee2529df (git): Sometimes result indicator (=>) isn't shown
-
06:13 PM Revision 0faf0271 (git): Use simple assersion
-
05:53 PM Feature #16786: Light-weight scheduler for improved concurrency.
- Replying to only one of your points for now:
> like a tailor-made solution for integrating nio4r into Ruby.
I see it as a way to cleanly integrate non-blocking concurrency with Fibers in Ruby, without forcing a single implementation li... -
06:49 AM Feature #16786: Light-weight scheduler for improved concurrency.
- I've been working a lot with fibers recently, and I would like to share my thoughts on this issue. Disclaimer: I'm currently working on a concurrency solution for Ruby using Fibers, but which takes a very different approach: https://gith...
- 05:42 PM Revision 1d0e8fd4 (git): * 2020-07-22 [ci skip]
- 05:35 PM Revision 02951a45 (git): [ruby/rdoc] Create link to unary operator methods correctly
- https://github.com/ruby/rdoc/commit/54500cf12a
- 05:34 PM Revision 7693aa70 (git): [ruby/rdoc] Remove empty lines from html file by using ERB trim_mode flag
- https://github.com/ruby/rdoc/commit/9e27299a46
-
05:34 PM Revision 38480ad5 (git): [ruby/rdoc] Fix parsing of rb_define_module_under
- Fixes Ruby Bug #15819
https://github.com/ruby/rdoc/commit/94a052d833 -
05:34 PM Revision f76d67f4 (git): [ruby/rdoc] Fix RDoc::Context#instance_method_list
- The warn method returns nil, it's a bug of #instance_method_list.
https://github.com/ruby/rdoc/commit/a20df89263 -
05:31 PM Revision f6e789e3 (git): [ruby/irb] handle rescue modifier properly
- https://github.com/ruby/irb/commit/6de1341f5e
-
05:31 PM Revision 22d38d54 (git): [ruby/irb] Add test_eval_object_without_inspect_method
- https://github.com/ruby/irb/commit/c0d9a26bce
-
05:31 PM Revision b40e925c (git): [ruby/irb] Fix error when `inspect` is called but not found in inspector
- https://github.com/ruby/irb/commit/ce6d53e6d9
-
05:31 PM Revision 4268084d (git): [ruby/irb] Add encoding magic comments of editors
- https://github.com/ruby/irb/commit/f8c10ea24b
-
05:31 PM Revision c72a2fad (git): [ruby/irb] Simplify RubyLex.compile_with_errors_suppressed
- nobu-san reviewed,
https://github.com/ruby/irb/pull/106#pullrequestreview-423400033
> How about lexer = Ripper::Lexer.new(";\n#{code}", nil, 0)?
> ...
I employ the way.
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
https://git... -
05:31 PM Revision 1dfd24a7 (git): [ruby/irb] Suppress incomplete encoding magic comment error
- https://github.com/ruby/irb/commit/443e90af80
-
05:31 PM Revision 78ccab25 (git): [ruby/irb] Suppress incomplete coding magic comment error
- https://github.com/ruby/irb/commit/6a457edbd1
-
02:56 PM Bug #17038 (Rejected): On master, ancestry edits can lead to duplicates in Module#ancestors
- Note that this change is listed in the `NEWS`
I'm thus closing this. -
03:23 AM Bug #17038: On master, ancestry edits can lead to duplicates in Module#ancestors
- > I believe it's always been possible to have duplicates in ancestors, even before this change
Thank you for the example; I stand corrected. I made the ticket because I thought we were introducing
brand new potential failure modes into ... -
02:25 AM Bug #17038: On master, ancestry edits can lead to duplicates in Module#ancestors
- I imagine that @alanwu feels the example code should behave the same way if the `include` were done sooner or later.
Jeremy Evans is right, the issue has existed for a long time.
I would prefer if we could always include a module m... -
12:50 AM Bug #17038: On master, ancestry edits can lead to duplicates in Module#ancestors
- I believe it's always been possible to have duplicates in ancestors, even before this change:
```ruby
class A
end
class B < A
end
module C
end
B.include C
A.include C
B.ancestors
# => [B, C, A, C, Object, Kernel, BasicObject... -
01:58 PM Feature #16345: Don't emit deprecation warnings by default.
- matz (Yukihiro Matsumoto) wrote in #note-46:
> So I changed my mind. Deprecation warnings should be turned on manually (probably with `-Wdeprecate` or `Waning[:deprecated]=true`).
I'm glad to hear that.
I still think deprecation... -
12:32 PM Bug #16492: TestBugReporter#test_bug_reporter_add test failures
- So I did quite a lot of testing focusing especially on internals of `EnvUtils.invoke_ruby` and I am not sure if there is a fix. It seems that especially the s390x build cluster is sometimes under heavy load. I extended the timeout and so...
-
11:43 AM Feature #17039 (Closed): Remove Time#succ
- `Time#succ` is obsolete since 1.9.2.
```
% docker run -it --rm rubylang/all-ruby env ALL_RUBY_SINCE=ruby-1.8 ./all-ruby -e 'Time.at(0).succ'
ruby-1.8.0 -e:1: undefined method `succ' for Thu Jan 01 00:00:00 UTC 1970:Time (... -
11:28 AM Revision 48eb1ad2 (git): [DOC] time.c document updated.
- * fraction -> subsecond
for consistency with method name
* The sentence,
"A non-portable feature allows the offset to be negative on some systems.",
is removed.
Time before 1970 should work portably now.
If localtime() doesn't... -
11:27 AM Bug #17030: Enumerable#grep{_v} should be optimized for Regexp
- I have an idea to solve it without any compatibility problem.
[1] Introduce such a Regexp object that `===` method is same as `match?`.
[2] Introduce regexp literal option that makes the Regexp object as [1].
If the option is `'f'... -
12:20 AM Revision 73ee1295 (git): Add memsize support for the call cache table
- Each class/module/iclass can potentially have their own cc table.
Count their malloc usage. - 12:18 AM Revision ac3dbbd4 (git): * 2020-07-21 [ci skip]
-
12:17 AM Revision a8eeccea (git): [ruby/csv] Bump minimum ruby version to 2.5.0 (#159)
- A dependency to stringio was added to csv, which requires Ruby version
>= 2.5. Bump the gemspec version accordingly.
https://github.com/ruby/csv/commit/bc5a26029f - 12:17 AM Revision c6f389d8 (git): [ruby/csv] Move doc/* to doc/csv/* to work in ruby/ruby too
- https://github.com/ruby/csv/commit/910f8e0c5d