Activity
From 12/18/2019 to 12/24/2019
12/24/2019
-
11:41 PM Revision 8e6d51e0 (git): Sync did_you_mean
-
-
10:28 PM Bug #16449 (Assigned): Bundler is 2.1.1 in master, not 2.1.2 ?
-
05:04 PM Bug #16449 (Closed): Bundler is 2.1.1 in master, not 2.1.2 ?
- NEWS mentions that Bundler has been updated to 2.1.2, but lib/bundler/version.rb
https://github.com/ruby/ruby/blob/5220145ea289d9eb955b373f31773fab2d4f0271/lib/bundler/version.rb
is showing 2.1.1. Normally I think I've seen NEWS d... -
- [Misc #16449][ruby-core:96458]
-
09:13 PM Revision da0a0bae (git): NEWS: add meaning of "CoW" ("copy-on-write")
-
-
07:54 PM Revision f3067deb (git): Revert "Add NEWS entry about Module#name performance (#2779)" (#2781)
- This reverts commit 3e9221d94a12b54c1285923b642364acdbc31c7e.
-
-
05:37 PM Feature #15973: Let Kernel#lambda always return a lambda
- more aggressive proposal is obsolete `lambda` call, and use `->` (maybe it is too aggressive).
-
- This is one idea: how about to prohibit `lambda(&...)` method call? (block literal is always prohibited)
3.0: deprecation warning and show 3.1 will raise exception for `lambda(&...)`
3.1: raise exception for `lambda(&...)`
same as... -
04:51 PM Feature #14912: Introduce pattern matching syntax
- Thanks @mame for explanation and response.
That kinda make sense with the `Point[]`. Is this universal for any class?
I was playing with it and could not make it, for example when I have implemented my own class with `deconstruct_... -
- These functions are enabled only on USE_DEBUG_COUNTER=1.
- 04:00 PM Revision 9b617ffa (git): * 2019-12-25 [ci skip]
-
-
-
-
- https://github.com/ruby/irb/commit/4bb1340687
-
-
-
09:53 AM Revision 4ba93475 (git): `Object#=~` warning also obeys `Warning[:deprecated]`
-
-
09:39 AM Revision 7758849c (git): Remove unused variable
-
- It doesn't behave the same as the delete-char.
-
-
-
-
07:34 AM Feature #16289: Reduce duplicated warnings for the change of Ruby 3 keyword arguments
- I've updated my pull request to update [the article of Ruby 3's keyword argument separation](https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/).
https://github.com/ruby/www.ruby-l... -
- @naruse also approved. Thank you for quick replies.
-
07:10 AM Feature #16289: Reduce duplicated warnings for the change of Ruby 3 keyword arguments
- Approved.
Matz.
-
- @marcandre
You have to wait for matz and naruse's approvals! I'll ask them. -
- > I think no user expects that the "subclass relation" is different than the order of ancestors, isn't it?
Regardless whether users know or not, they are actually different. Consider:
```ruby
module M; end
class C; prepend M; en... -
- >s it that releases of the json gem will be done from the ruby/ruby repository?
No. We can merge commits from ruby/ruby to flori/json and release it. -
-
- This reverts commit e57d6194218efc73c30f3fed9dd321d2e357030b.
Test fails:
http://ci.rvm.jp/results/trunk-gc-asserts@ruby-sky1/2518563
http://ci.rvm.jp/results/trunk-gc_compact@silicon-docker/2518533 -
-
-
05:04 AM Bug #16437: Codespell report for Ruby 2.6.5 (and 2.7.0-rc1)
- nobu (Nobuyoshi Nakada) wrote:
> * I see the word "unuseful" in some online dictionaries.
Yes, but that doesn't mean it's best. As an example, "unuseful" shows up on Google about 363,000 times, but "useless" shows up on Google abou... -
- And as I added fixing typos in ChangeLog file taking from git-notes, the file in the next package will be fixed.
-
- Thank you, yes, "exapmle" in test/openssl/test_x509name.rb is intentional to test malformed RDN by a typo.
And for others:
* Fixed the typos in debug_counter.h and error.c.
* I see the word "unuseful" in some online dictionaries.
* `... -
-
-
-
02:54 AM Bug #16398: Active Support unit test error since caac5f777ae288b5982708b8690e712e1cae0cf6
- This issue has been addressed by https://github.com/rails/rails/pull/38069 .
-
- Sorry, I've forgotten completely.
Updated the [patch](https://github.com/ruby/ruby/pull/2778), but it is sorry to be too late for 2.7. -
-
-
02:00 AM Revision f2e1e6cb (git): Enhance explanations for beginless range and #clamp, and add missing feature
-
- https://docs.google.com/document/u/1/d/1W_wrFsFxxU1MepA6HBpfl-9h-nLD8EBsgMsS7yTDvHE/pub
-
- [Bug #16437]
-
- English version pages seem no longer provided.
-
01:30 AM Revision f09a4ff2 (git): Added NEWS for Feature 15373
-
- Numbered parameter is not an experimental feature,
confirmed by Matz.
https://twitter.com/yukihiro_matz/status/1209271452798607361 -
- The IRB maintainer @aycabta has determined to remove the message. https://github.com/ruby/ruby/commit/0e528ae9cb5c1078e4d07287e403cb548e97f0a3
-
- https://github.com/ruby/reline/commit/55d4dfec1e
-
- https://github.com/ruby/irb/commit/8da0c74640
-
- https://github.com/ruby/irb/commit/d9a7844f50
12/23/2019
-
-
- https://github.com/ruby/rdoc/commit/c65e14d112
-
-
- https://github.com/ruby/rdoc/commit/74d3984324
-
- https://github.com/ruby/rdoc/commit/957d041ae0
-
10:12 PM Feature #16446: Enumerable#take_*, Enumerable#drop_* counterparts with positive conditions
- sawa (Tsuyoshi Sawada) wrote:
> wishdev (John Higgins) wrote:
> ...
Nothing wrong with that at all - but I think adding a :reverse options to the methods would accomplish a right to left search feature.
As I said - declaring what y... -
09:52 PM Feature #16446: Enumerable#take_*, Enumerable#drop_* counterparts with positive conditions
- wishdev (John Higgins) wrote:
>I prefer simpler examples
> ...
My intention of including two `0`s in the example was to show that there remains an asymmmetry; the search is done from the left, not from the right. In principle, we can s... -
- The answer here is simplicity (declarative) as opposed to wordsmithing.
We need to add an drop_until and take_until to handle 5-8 and drop_while and take_while handle 1-4
All 4 methods get a new parameter "bucket" which determines wher... -
03:14 PM Feature #16446: Enumerable#take_*, Enumerable#drop_* counterparts with positive conditions
- I have not thought about the proposal here quite much so far, sorry (and admittedly I may need
to do so on a fresh morning as I am a bit tired).
Just two brief comments:
- Some of the examples remind me a bit of .select/.reject/.... -
- #16441 led me to think about the issue more generally. When we want to split a series of iterations by the first element that satisfies (or dissatisfies) a condition, we have three factors to consider.
(1) Whether we want the conditio... -
09:49 PM Feature #16289 (Closed): Reduce duplicated warnings for the change of Ruby 3 keyword arguments
- Great, thanks.
Pushed. -
05:47 PM Feature #16289: Reduce duplicated warnings for the change of Ruby 3 keyword arguments
- I'm fine with @marcandre's changes.
-
12:51 PM Feature #16289: Reduce duplicated warnings for the change of Ruby 3 keyword arguments
- Sounds clearer to me with @marcandre's changes.
-
- @marcandre , thank you for creating a pull request.
Your proposal:
old: The last argument is used as keyword parameters; maybe ** should be added to the call
new Using the last argument as keyword parameters is deprecated; maybe *... -
- I'm glad this was merged in, but disappointed the error message still doesn't mention that this is a deprecation warning.
Wouldn't it be cleared with https://github.com/ruby/ruby/pull/2776 ? - 09:47 PM Revision 819b6040 (git): Reword keyword arguments warning messages to convey these are deprecation warnings
-
-
-
- 07:17 PM Revision aa01441f (git): * 2019-12-24 [ci skip]
-
-
- Re `obj.is_a?(mod)` we can consider it as `obj.singleton_class.ancestors.include?(mod)` or even `obj.class.ancestors.include?(mod)` in this case.
That's consistent with `ancestors`. -
- At the very least it's inconsistent with the order of Module#ancestors:
```ruby
module M; end
class C; prepend M; end
> C.ancestors
=> [M, C, Object, JSON::Ext::Generator::GeneratorMethods::Object, PP::ObjectMixin, Kernel, BasicOb... -
- The current behavior is consistent. The rdoc of `Module#<` says:
```
call-seq:
mod < other -> true, false, or nil
Returns true if <i>mod</i> is a subclass of <i>other</i>.
```
Note that subclass is not directly related ... -
02:29 PM Feature #12655: Accessing the method visibility
- mri/2.x.0/internal.h:1363:11: error: conflicting types for โrb_st_copyโ
1363 | st_table *rb_st_copy(VALUE obj, struct st_table *orig_tbl);
looks like this has changed in ruby 2.7
we would have appreciated the public methods from ... -
-
02:01 PM Bug #16448: regex global variables are working differently depending on scope
- It is very unexpected.(
Thank you. -
- `$~` is not a global variable, but a kind of local variable. `String#gsub` assigns the match data to `$~` of its caller. `data.gsub(/test/, &f1)` assigns `$~` of the scope of `check`. The lambda `f1` reads `$~` of the toplevel scope, ...
-
- Hi, everyone.
I am trying to write a code similar to this
``` ruby
#!/usr/bin/env ruby
def check(f1)
f2 = ->(match) { p match; p $~ }
data = "hello test test test"
data.gsub(/test/, &f1)
data.gsub(/test/, &f... -
-
01:46 PM Bug #16437: Codespell report for Ruby 2.6.5 (and 2.7.0-rc1)
- Yes, your mentioned types of false positives are often found and I had tried to eliminate them before. Some nevertheless overseen ones are now also excluded. Additionally the mentioned sub-directories of external gems are now also exclud...
-
-
- hsbt (Hiroshi SHIBATA) wrote:
> We will handle the new feature of JSON with ruby/ruby repo in the future.
I'm not sure what you mean, could you clarify?
Is it that releases of the json gem will be done from the ruby/ruby repository? -
- naruse did release json-2.3.0 from the current master branch of ruby/ruby.
We will handle the new feature of JSON with ruby/ruby repo in the future. -
- @marcandre
You can pick the commits from ruby/* repository like this.
```
# git clone from the upstream repository and copy from the upstream repository with cp -rf. It's lost the git commits.
ruby tool/sync_default_gems.rb rubyg... -
- @hsbt is your tool to do this published somewhere?
In particular I noticed that some `gemspec` files are not in the same spot (e.g. `lib/matrix/matrix.gemspec` vs `lib/ostruct.gemspec`).
I'm moving one in the main repo, but it's no... -
- Thank you for contributing.
I and naruse got the approval for releasing the new version of JSON from flori.
So, I can merge and release them. But It's too late for releasing Ruby 2.7. I'm going to handle it in 2020. -
- Sorry for bothering the core tracker.
I understand (though, only partially) that JSON standard library is in a weird state "it is kinda maintained but we can't contact maintaner" (is there no way to just move the project's main repo und... -
- knu (Akinori MUSHA) wrote:
> Which does `hash1.transform_keys(hash2)` iterate over, hash1's keys or hash2's keys?
My intention of including the key `:author` in `hash` was to show that the iteration is done over the receiver (your `... -
- As for the behavior when both a hash argument and a block are given, I suggested in the issue to have the block applied after the hash has applied:
**Original proposal**
```ruby
hash.transform_keys({created: :created_at, updated: :u... -
- matz (Yukihiro Matsumoto) wrote:
> FYI, we do not accept a similar change to `transform_values`.
Matz - Do you mean "we reject a similar change to `transform_values`", or do you mean "we have not yet accepted a similar change to `t... -
-
- wmap_finalize expects id2ref() returns a corresponding object
even if the object is dead. Make id2ref_obj_tbl() for this
purpose. -
-
- This is intentional. There was no way to distinguish Time objects that differ in a fraction of a second.
The behavior of Time#to_s kept unchanged for compatibility.
Matz.
-
02:18 AM Bug #16445 (Closed): Time#inspect shows a fractional number
- `Time#inspect` shows a fractional number.
```
irb(main):001:0> Time.at(0.5)
=> 1970-01-01 09:00:00.5 +0900
irb(main):002:0> Time.at(0.1)
=> 1970-01-01 09:00:00 3602879701896397/36028797018963968 +0900
```
Is this intentional? - 06:59 AM Revision 7779ade4 (git): NEWS: Fix issue reference [#15807] [DOC]
- 06:55 AM Revision dadf1255 (git): README: Add Range#minmax to the list of potential incompatibilities [#15929] [DOC]
- 06:48 AM Revision 3e1adf57 (git): README: Improve wording [DOC]
- 06:40 AM Revision 7df2503b (git): NEWS: Hint at potential incompatibility with Range#minmax [#15807]
-
- objspace->id_to_obj_tbl can contain died objects because of lazy
sweep, so that it should check liveness. -
-
- [ruby-core:96227] [Feature #16419]
-
- This reverts commit 1bf8d5e9797f6304b2e27cb7f42d467f84de0ff4.
Because 204dc3f39f12b4e2640555306bd1dd4530344277 reverts 61aff0cd189e67fa6f2565639ad0128fa33b88fc - 02:54 AM Revision 204dc3f3 (git): Revert "Should return "." for File.extname("file.") also on Windows"
- We want to introduce consistency and better compatibility with unixen,
but the Windows APIs doues not have consistency fundamentally and
we can not found any logical way...
This reverts commit 61aff0cd189e67fa6f2565639ad0128fa33b88fc. - 02:48 AM Revision 048f797b (git): [ruby/prime] Bump version
- 02:48 AM Revision 446c243d (git): [ruby/ostruct] Bump version
- 02:48 AM Revision 9be3295d (git): [ruby/ostruct] Create OpenStruct::VERSION
- 02:48 AM Revision 49d94248 (git): [ruby/ostruct] Move gemspec
- 02:48 AM Revision 48d1acdf (git): [ruby/matrix] Bump version
-
-
-
- "X" must be used in conjunction with "+".
-
12:52 AM Misc #15843: Make "trunk" a symbolic-ref of "master" on git.ruby-lang.org
- Reminder to everyone:
> 2020 1/1: trunk branch cannot be git fetched and git pushed anymore.
The ruby.git's "trunk" branch will be deleted within 10 days. -
-
- docx (Lukas Dolezal) wrote:
> I wonder what do you think about only allowing curly brackets for hash pattern, and only square brackets for array pattern?
The rationale of the current design I've heard from @ktsj is to fit the pattern... -
-
- This reverts commit f85e8d2a8b2a37740334db4fd92ef820f05ddbc5.
It violated the limit of width (> 80) and caused the test failure
12/22/2019
-
- Fixed misspellings reported at [Bug #16437]
-
- In #2612 I made two typos (extra ,, and copy-pasted
same line of code instead of showing two different
ones), fixing them. -
-
-
- Hi, I was playing with the type/hash patterns (2.7.0-preview3), and I find this confusing and non-intuitive:
while generic hash pattern uses curly brackets e.g.
```in {id: id, name: "Bob"}```
when added type to it, it has to b... -
-
- * fix list in #flat_map
* fix wrong indentation in #filter_map and #with_index
* other small fixes -
- https://github.com/ruby/reline/commit/be17740e82
-
- A patch to suppress the warning when started as `console`.
```diff
diff --git a/lib/irb/init.rb b/lib/irb/init.rb
index 2af872fd03..464b33ae03 100644
--- a/lib/irb/init.rb
+++ b/lib/irb/init.rb
@@ -31,6 +31,8 @@
@TRACER_INI... -
- I guess we may provide an API to hide or alter the message for rails console and other tools. Pull request is welcome to ruby/irb.
-
11:02 AM Misc #16444: What is the reason for the warning of IRB?
- Thanks for your feedback. OK. I understood that too late to discuss and a message is as expected.
I think it would be good if the message could be configurable, but I will also consider expanding the options on the library side. Th... -
- I believe that it is too late to discuss "opt-in or opt-out?".
IMO, the quality of the new IRB is not so low. But it highly depends upon environments (OS, terminal, how to use, etc.), so we want people to use the new version, give fe... -
- Agreed for compatibility - may be better to retain the old behaviour as-is.
I believe it was not a deliberate change but an oversight since the author
of reline here on the issue tracker also mentioned compatibility being
an importa... -
- Ruby 2.7 always shows a warning when starting IRB. Why is this necessary?
Of course, ways to suppress the warning have been suggested.
However, libraries that extend IRB, such as `rails console` and `aruba`, may not receive argumen... - 03:17 PM Revision 3a18e43c (git): * 2019-12-23 [ci skip]
-
- at 61aff0cd189e67fa6f2565639ad0128fa33b88fc [Bug #15267]
-
-
- * Change === docs to mention it uses cover?
* Add different example to === docs to showcase
behavior better
* Change include? docs to mention cover?
and clarify the difference -
-
-
-
-
-
02:12 PM Revision 890c834e (git): Enhancements for ENV doc
- 02:01 PM Revision 54be15f3 (git): [Doc] Fix sample in Encoding#names
- 02:01 PM Revision 9654241d (git): [Doc] Fix wrong example in Encoding.aliases
-
- jschleus (Jens Schleusener) wrote:
> There was now also a check done for Ruby master but since the according tarball isn't embedded into the Fossies standard services a test folder was used:
> ...
Some are not misspells (a part of path... -
- There was now also a check done for Ruby master but since the according tarball isn't embedded into the Fossies standard services a test folder was used:
https://fossies.org/linux/test/ruby-master.tar.gz/codespell.html
(https://foss... -
- Fixed misspellings reported at [Bug #16437], missed and a new
typo. -
- Does this log mean the following libraries are stopped by `make` due to the first failure in `cxxanyargs` or in yet another branch?
> ```
> ...
> ``` -
10:02 AM Bug #16331: fails to build with BSD make when any -j option is given (including -j 1)
- I executed following shell script on my FreeBSD test environment and got attached log file.
``` shell
#!/bin/sh
LANG=C
(
echo System Information:
echo --------------------------------------------------------------------... -
-
-
-
- At least as of Ruby 2.6.5, I get a different output from above for at least one of the examples:
```ruby
N = 0
module A
module B
def self.f; N; end
end
N = 1
end
N = 0
A::B.f # => 1
``` -
-
02:55 AM Revision ced4c5da (git): add NEWS about cache improvement [ci skip]
-
12/21/2019
-
- * Use Queue for synchronization.
* Don't use `sleep 0.2` and use `th.join` because created thread
can raise an exception after 0.2 seconds. -
- @matz Is it OK to warn for this in the next Ruby version?
I think it's going to highlight wrong usages (good) and I would expect there are very few usages of `lambda(&existing_proc)`.
The warnings were implemented in https://github... -
- https://github.com/ruby/reline/commit/e98ad3b486
-
-
- Applied in changeset commit:git|75acbd5f0076970d48bc423c2b058adbdb5da9e8.
----------
compile.c: avoid newarraykwsplat for arguments
`foo(*rest, post, **empty_kw)` is compiled like
`foo(*rest + [post, **empty_kw])`, and `**empty_kw` is ... -
- same as: `p(*nil, nil, **{})`
```
(gdb) bt
#0 0x00005555557d6de0 in CALLER_REMOVE_EMPTY_KW_SPLAT (cfp=0x7ffff6bc4fa0, calling=<optimized out>, calling=<optimized out>, ci=0x555555c4e6e0)
at /home/ko1/src/ruby/trunk/vm_insnhelp... -
04:38 PM Bug #16442 (Closed): Segmentation fault when calling a method with array splat and empty kwargs splat
- `a=[1];b(*a, 2, **{})`
~~~
$ ruby -e "a=[1];b(*a, 2, **{})"
-e:1: [BUG] Segmentation fault at 0x0000000000000005
ruby 2.7.0preview3 (2019-11-23 master b563439274) [x86_64-darwin19]
~~~
~~~
$ ./miniruby -e "a=[1];b(*a, 2, **{}... -
- `foo(*rest, post, **empty_kw)` is compiled like
`foo(*rest + [post, **empty_kw])`, and `**empty_kw` is removed by
"newarraykwsplat" instruction.
However, the method call still has a flag of KW_SPLAT, so "post" is
considered as a keyword ... -
- See https://docs.ruby-lang.org/en/master/GC.html#method-c-compact
Typically, I'd just submit a documentation PR, but I am not sure I can properly explain what it does and when it should be used. -
05:51 PM Revision 3a29f05b (git): Move stats under a dict
- 05:42 PM Revision 61aff0cd (git): Should return "." for File.extname("file.") also on Windows
- But not changes another cases, such as "file.rb."
[Bug #15267] - 04:58 PM Revision 29ea228e (git): * 2019-12-22 [ci skip]
-
-
- Follow up of the previous commit
https://github.com/ruby/irb/commit/ab207353d3 -
- Fixes #47
https://github.com/ruby/irb/commit/6b8eca4635 -
- The old version of cursor_pos discards the input buffer, which made IRB
ignore the input immediately after IRB is invoked.
This change keeps the input before cursor_pos by using ungetc.
https://github.com/ruby/reline/commit/4a8cca331f -
- https://github.com/ruby/reline/commit/b111cde3c3
-
04:52 PM Feature #6810: `module A::B; end` is not equivalent to `module A; module B; end; end` with respect to constant lookup (scope)
- I just inadvertently made a dup of this issue (#16430) and would like to throw my hat in the ring as supporting this change.
Honestly, this literally the first time since I started ruby that I encountered something in the language th... -
- This is of course only my personal opinion, but I believe that long
names can be somewhat problematic. Now I myself use really very
long method names, but for ruby as a "basic building block" (that
is the core parts), I think the shor... -
- Flip-flop is the winner!!!
-
- The method is just like `#take_while`, but also includes the item where condition became true.
Examples of usefulness:
```ruby
str = <<DOC
prologue
<<
1
2
3
>>
epilogue
DOC
```
Imagine we want to take everything starti... -
- > Does a Date range represent a series of individual days between May 1st and May 31th, like `[2019-05-01 00:00:00, 2019-05-02 00:00:00..... 2019-05-31 00:00:00]` ? Or it represents a continuous time range that starts from May 1st's 00:0...
-
03:05 PM Bug #16440: Date range inclusion behaviors are inconsistent
- To: wishdev (John Higgins)
> (and in fact on my system - the to_time option returns false instead of true).
Sorry that I accidentally tested my code in a Rails console instead of pure irb. The result for that case should be `false`... -
- I have no strong opinion either way but I can understand the
assumption by st0012 to some extent. For example, I personally
always seem to think more about .include? than .cover?, largely
because I simply use .include? a lot more. I ... -
- Changing the flag at runtime causes problems, mainly editors' syntax highlighting, `ruby -c` etc.
How about a new "magic comment" pragma?
```ruby
# -*- experimental-syntax: true -*-
```
or, more strictly
```ruby
# -*- experiment... -
- Applied in changeset commit:git|85a337f986fe6da99c7f8358f790f17b122b3903.
----------
Kernel#lambda: return forwarded block as non-lambda proc
Before this commit, Kernel#lambda can't tell the difference between a
directly passed literal... -
- Before this commit, Kernel#lambda can't tell the difference between a
directly passed literal block and one passed with an ampersand.
A block passed with an ampersand is semantically speaking already a
non-lambda proc. When Kernel#lambd... -
-
-
- mame (Yusuke Endoh) wrote:
> If you want to request a feature, please research the old tickets. I've found #6810.
Ok, thanks. I tried searching before submitting this, but I apparently didn't use the right terms. -
- If you want to request a feature, please research the old tickets. I've found #6810.
-
- Fixed small bug in initial description.
-
- sawa (Tsuyoshi Sawada) wrote:
> What is the purpose of writing the code in three different files? It only looks to me that it is making things more complicated.
I was trying to offer a minimal (non)-working example. The benefit arise... -
- mame (Yusuke Endoh) wrote:
> It is by design. See "Scope" section of https://github.com/ruby/ruby/blob/master/doc/syntax/modules_and_classes.rdoc
Ok, I see that, but is this a good design? I would argue not and am therefore changing... -
12/20/2019
-
06:47 PM Revision 9eded024 (git): Add Array#minmax, Range#minmax, and Proc#ruby2_keywords to NEWS
-
- `Range#include?` works as `#to_a.include?`. E.g. this:
```ruby
(may1..may31).include? noon_of_may3
# => false
```
Is equivalent to this:
```ruby
dates = (may1..may31).to_a # => each Date between May 1 and 31
dates.include? noon_... -
- Nothing strange with your example - but that doesn't mean it totally works right.
First your example is a DATE range - so adding this line
`(may1..may31).each { |x| puts x }`
That shows that your set is each day within the range... -
- It's weird that a Date range can include Time and DateTime objects that were converted from a Date object. But it can't include a newly generated DateTime object. For example:
```
may1 = Date.parse("2019-05-01")
may3 = Date.parse("2... -
- Applied in changeset commit:git|07e595fdbd75ed44473073cdf8cd758572d11709.
----------
Added `experimental` warning category
[Feature #16420] - 03:07 PM Revision 63ce7792 (git): * 2019-12-21 [ci skip]
-
- [Feature #16420]
-
- [Feature #16420]
-
-
02:33 PM Bug #8841: Module#included_modules and prepended modules
- > Module#included is not called when the module is prepended
I think that's fine, because it calls `Module#prepended`.
> ...
That yes:
```ruby
class Base
end
module A
end
module B
end
Base.prepend(A)
Base.include(B... -
- Summary:
* `Module#include?` and `Module#included_modules` regard prepended modules as `included` (not well documented)
* `Module#included` is not called when the module is prepended
Is this right? -
- Applied in changeset commit:git|a84ad24386d27269b90794146c2a351c1d79471b.
----------
Added -W: command line option
To manage `Warning[category]` flags. Only `-W:deprecated` and
`-W:no-deprecated` are available now. [Feature #16345] -
- I think this issue resolved by changing from `@1` to `_1`.
-
- To manage `Warning[category]` flags. Only `-W:deprecated` and
`-W:no-deprecated` are available now. [Feature #16345] -
-
01:02 PM Bug #16439 (Closed): Resolv::DNS: timeouts if multiple IPv6 name servers are given and address contains leading zero
- Hi,
Resolv::DNS does not return any results under those conditions:
- there are at least two name servers (in /etc/resolv.conf).
- The name servers have IPv6 addresses containing leading zeros.
Example resolv.conf:
nameserver 20... -
- Add an example of "<expr> in <pattern>", an example of
NoMatchingPatternError, and mention that the slides are slightly
obsolete. -
- (old)
test.rb:4: warning: The last argument is used as the keyword parameter
test.rb:1: warning: for `foo' defined here; maybe ** should be added to the call?
(new)
test.rb:4: warning: The last argument is used as keyword parameters; ma... -
- It was discussed and Matz approved to fix it after Ruby 2.7 release.
-
- I don't see the practical benefit of this proposal. Besides that incompatibility is a clear drawback.
Matz.
-
- @jeremyevans0 It's OK to merge the patch to the master after the 2.7 release, to see how big the influence is.
Matz.
-
- I understand. Accepted.
FYI, we do not accept a similar change to `transform_values`.
Matz.
-
07:28 AM Feature #16274: Transform hash keys by a hash
- Which does `hash1.transform_keys(hash2)` iterate over, hash1's keys or hash2's keys?
-
- We have suspended the idea of `.:` operator, so this proposal is no longer meaningful. We may revisit the method reference operator in the future. We have to remember this PR as well. FYI, we have numbered parameters now, so the proposed...
-
- [Bug #16438]
-
- At developer's meeting, the followings are proposed. They will be merged into Ruby 2.7 RC2.
```ruby
def foo(**kw)
end
foo({})
# current:
#=> test.rb:4: warning: The last argument is used as the keyword parameter
# test.rb:... -
- Applied in changeset commit:git|a8bddb3a189545a2bef8ee7cffdb328d8de7974c.
----------
Refined the warning message for numbered-parameter like variables
[Bug #16438] -
- > pls check current master.
Sorry, became warning. -
- ```ruby
$SAFE = 1
#=> t.rb:1: warning: $SAFE will become a normal global variable in Ruby 3.0
```
> # no warning
pls check current master. -
- >
```ruby
def _1; end
#=> test.rb:1: warning: `_1' is used as numbered parameter
```
~~Warn by parameter name instead of method name.~~
Became warning.
```ruby
# warning: `_1' is used as numbered parameter
def _1; end
#... -
- Please check Ruby 2.7 new introduced warning messages.
* deprecation warning
```ruby
def foo(**kw)
end
foo({}) #=> test.rb:4: warning: The last argument is used as the keyword parameter
# test.rb:1: warning: for `fo... -
- [Bug #16438]
-
- [Bug #16438]
-
- Applied in changeset commit:git|435a4ca2a38f3be1f5d2db0f71487a52c8285e9c.
----------
Makes the receiver to FrozenError.new a keyword parameter
[Feature #16419] -
- [Feature #16419]
-
-
- You can see a list of the upstream with https://github.com/ruby/ruby/blob/master/doc/maintainers.rdoc#default-gems-maintainers
-
- Fixed for ruby core, standard libraries, default gems and rubyspec.
Could you report other upstreams (rubygems, bundler, minitest, rake, test-unit, and unicode.org)?
BTW, I'm unsure what word is appropriate to the variable for the โr... -
- Applied in changeset commit:git|db166290088fb7d39d01f68b9860253893d4f1a7.
----------
Fixed misspellings
Fixed misspellings reported at [Bug #16437], only in ruby and rubyspec. -
- Fixed misspellings reported at [Bug #16437], for default gems.
-
03:18 AM Misc #16436: hash missing #last method, make it not so consistent (it has #first)
sawa (Tsuyoshi Sawada) wrote:
> What is this issue? Is it just a note to everyone, or are you claiming this to be a bug, or is it a feature request?
Sorry, this issue not a bug, i knew Hash#first come from Enumerable, the reason i ...-
- sawa wrote:
> What is this issue? Is it just a note to everyone, or are you
> ...
I think it could only possibly be a feature request since it
is not a bug. But you are uite right that it is difficult to
infer from the issue descri... -
-
- * [Feature #16432] Using `_1` inside `binding.irb` will cause unintended behavior(osyo)
* Calling `binding.irb` in a block that uses `_1` and using `_1` in `irb` will cause unintended behavior.
* Should it be a runtime error?
-
02:15 AM Misc #16393: DevelopersMeeting20191220Japan
- I'd like to discuss about type signature integration for Ruby3. I plan to discuss in this meeting but not trying to make some decisions today. Asking for feedbacks to make a concrete proposal for the next meeting or else.
A doc is av... -
- * [Bug #11014] String#partition doesn't return correct result on zero-width match (mame)
* I'd like to confirm if the current behavior is inteneded. -
- [Bug #10929] NilClass#to_proc and & don't mix? (mame)
* I think it is not worth adding. -
- * [Bug #10388] Operator precedence problem in multiple assignment (massign) (mame)
* "`a, b = c = 1, 2` is currently taken as `a, b = (c = 1), 2`; I'd expect it to be taken as `a, b = (c = 1, 2)`." Jeremy gave a try to implement but ... -
- * [Bug #9815] attr_reader doesn't warn on a uninitialized instance variable (mame)
* A reader method defined by `attr_reader :foo` is not warned as "instance variable @foo not initialized". Is it intentional? -
- * [Bug #8841] Module#included_modules and prepended modules (mame)
* `Module#include?` and `Module#included_modules` regard prepended modules as included (not well documented); `Module#included` is not called when the module is prepen... -
- Thanks!
-
- Thanks comments :)
> This is because the eval code is executed at the current context exactly.
> ...
Yes, and if `_1` is nested, a syntax error will occur.
```ruby
proc {
_1
# error: numbered parameter is already used in
... -
- Now I'm unsure if the feature is worth adding. It was accepted six years ago, but not implemented yet. I've never heard any actual trouble due to the lack.
-
- matz (Yukihiro Matsumoto) wrote:
> But according to the slide, the optional `include_ancestors` is true, but it does mean cherry-picking prepended modules from ancestor list. I cannot think of any use case of this behavior.
I guess ... -
-
- Fixed misspellings reported at [Bug #16437], only in ruby and rubyspec.
12/19/2019
-
- As far as I understand, no one showed any actual use case that justifies adding `nil.to_h #=> {}`.
I agree with matz, it would be better to remove `nil.to_a #=> []` instead of adding `nil.to_h #=> {}` for this issue. I don't think it... -
-
- Is there anyone who is interested in this? I'd be happy if anyone could look through the result and create a patch. Contribution is welcome.
@jschleus Thanks. If possible, could you apply the checker to master? In the tarballs, th... -
- The FOSS server fossies.org offers a new feature "Source code misspelling reports":
https://fossies.org/features.html#codespell
Although such reports are normally only generated on request, as Fossies administrator I have just cre... -
07:46 PM Bug #16288: Segmentation fault with finalizers, threads
```
--- a/thread.c
+++ b/thread.c
@@ -682,7 +682,7 @@ thread_do_start(rb_thread_t *th)
else {
args_ptr = RARRAY_CONST_PTR(args);
}
-
+ rb_funcallv(NULL, idInspect, 0, 0);
th->valu...-
-
- Applied in changeset commit:git|27ddb6e99848c397a415b785315896ab50308076.
----------
Warn also numbered parameter like parameters
[Feature #16433] -
- Currently, output warning if local variable name is `_1`.
```ruby
# warning: `_1' is used as numbered parameter
_1 = 42
```
However, if parameter name is `_1`, no output warning is issued.
```ruby
# Actual behavior
# no war... - 04:37 PM Revision 844f1fad (git): * 2019-12-20 [ci skip]
-
- What is this issue? Is it just a note to everyone, or are you claiming this to be a bug, or is it a feature request?
-
- `Hash` doesn't have `#first` either :)
```ruby
Hash.instance_method(:first)
# => #<UnboundMethod: Hash(Enumerable)#first(*)>
# ^^^^^^^^^^
```
The `first` method existence is just because of hash being a... -
- ``` ruby
(pry):main(0)> h = {x:1, y:2, z:3}
{
:x => 1,
:y => 2,
:z => 3
}
(pry):main(0)> h.first
[
:x,
1
]
(pry):main(0)> h.first.first
:x
(pry):main(0)> h.first.last
1
```
last method not exist.
... -
- [Feature #16433]
-
- The idea is obvious, but I couldn't find it discussed anywhere on tracker before. Please point me at the previous discussions if any.
```ruby
class Array
def to_proc
proc { |v| v.dig(*self) }
end
end
# Or, alternatively,... -
- Thank you for the report.
Maybe https://github.com/brianmario/mysql2/issues/1075 seems related. Anyway, the issue seems to occur in mysql2 library. Cloud you ask them first? -
- Although it is unclear without the backtrace by ruby itself, it seems caused by a wrong argument to `Mysql2::Client#connect`.
https://github.com/brianmario/mysql2/blob/785969fbceadd96d495ec9fecc67efee03d0056c/ext/mysql2/client.c#L438
T... -
02:19 PM Bug #16434 (Third Party's Issue): rails c crashed
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: https://www.ruby-lang.org/bugreport.html
[IMPORTANT]
Don't forget to include the Crash Report log file u...-
- It is same as the following code without irb.
```ruby
proc {
p eval("(1..10).map{_1+_1}") #=> [84, 84, 84, 84, 84, 84, 84, 84, 84, 84]
_1
}.call(42)
```
This is because the `eval` code is executed at the current context ex... -
- ## Summary
Calling `binding.irb` in a block that uses `_1` and using `_1` in `irb` will cause unintended behavior.
## Steps to reproduce
1. Use `_1` in block
2. Use `binding.irb` in block
3. Use block with `_1` in `binding.i... -
12:13 PM Feature #15306 (Closed): Generate prelude.c using miniruby
-
- prelude.c is not anymore [1], so I'm closing this specific ticket.
However, I'll be happy if the discussion is remembered for future.
[1]: https://github.com/ruby/ruby/commit/9c2807b2df14984e3c81d72a381d9a4d288b3fbe -
- vo.x (Vit Ondruch) wrote:
> Nevertheless it does not address the "disk consumption" concern. I also previously forgot to mention possible increased network bandwidth required to build and distribute the cloud image.
By how much does ... -
- I agree with @zverok here, a method behaves as a lambda, and doesn't unpack arguments (except a few special methods that specifically do that).
@nobu I think we should merge your PR. Could you show an example of a Symbol#to_proc Proc ... -
- > As a symbol proc cannot know the method to be invoked, so now I think it cannot be lambda.
> ...
@nobu, I am not sure I get it right. Can you please show when it is not true?..
For as far as I can understand, there are two distinctio... -
- Just curious: How do you want to use the result of `lambda?`? Even if it returns true, we may pass an arbitrary number of arguments: `lambda {|*a| ... }`. I think that `lambda?` is useless except debugging.
-
- As a symbol proc cannot know the method to be invoked, so now I think it cannot be lambda.
In the case `:+`, it looks like a lambda, but it is not always true. -
- I will try to remove it at racc-1.5 in the next year.
-
- JustJosh (Joshua Stowers) wrote:
> @sawa - I 100% agree with what you are saying. I did a poor job expressing my concerns.
> ...
I understand your point. If that is a concern, then we can simply not allow the abbreviated form for `Arra... -
04:52 AM Feature #16039: Array#contains? to check if one array contains another array
- @sawa - I 100% agree with what you are saying. I did a poor job expressing my concerns.
I am nervous that singling out array arguments in the abbreviated form could result in confusion and misuse. This is not a problem for `Range#cove... -
- JustJosh (Joshua Stowers) wrote:
> I do not think we should use the name `cover?` because the types of arguments accepted by `Range#cover?` would be incompatible with this use case.
> ...
When the argument is an array, it should be und... -
- @alanwu
Please add `(alanwu)` in the next time. My agenda generator overlooks your post. -
-
-
-
12/18/2019
-
- I think the issue is that the filing is about reverting the promotion to
default gems, which is different to the use case of making it (or what a
ruby user wants to use) more flexible.
The ideal scenario would be to have a fully cus... -
- rbjl (Jan Lelis) wrote:
> Then, a good configuration for the cloud could be this?
> ...
It should probably be `$ RUBYOPT=--disable-did_you_mean ruby -e "p defined? DidYouMean" # => nil` because env variables are typically easier to con... -
12:36 PM Bug #16427: Revert did_you_mean promotion to default gem.
- > But all these applications have to pay for longer startup time, higher memory and disk consumption. All these are not negligible in the age of cloud. I am pretty sure there is also performance hit during exception handling.
Then, a ... -
- mame (Yusuke Endoh) wrote:
> But it's just like saying that "ruby cannot start when I remove lib/rubygems.rb".
Speaking of which is problematic by itself. But the difference is that 99% of Ruby applications needs RubyGems for their r... -
- It does not make sense at all.
In Ruby 2.6, did_you_mean was a bundled gem, which may be uninstalled by a user. As it is not always able to require, gem_prelude.rb did `require "did_you_mean" rescue LoadError`.
In Ruby 2.7, did_you_... -
- While I agree on the situation at hand (being able to use did you mean
or disable it at the discretion of the user), I think there was a wrong
filing in the linked issue in that the suggestion of the linked in
thread was "Revert did_y... -
- I just have opened PR [1], which allows Ruby to run when did_you_mean is not available. As I previously discussed in #16427, there are cases when speed, memory, disk or network bandwidth is a concern and did_you_mean is not useful for ru...
-
- # *#cover?*
I do not think we should use the name `cover?` because the types of arguments accepted by `Range#cover?` would be incompatible with this use case.
For example:
```ruby
(1..3).cover?(2) # true
```
But if Array's implem... - 05:08 PM Revision e732e007 (git): * 2019-12-19 [ci skip]
-
05:08 PM Revision 1e88f6eb (git): Refactor free page insertion
- I am trying to fix this error:
http://ci.rvm.jp/results/trunk-gc_compact@silicon-docker/2491596
Somehow we have a page in the `free_pages` list that is full. This
commit refactors the code so that any time we add a page to the
`free... -
- Sorry, I don't think we can do anything for this report.
Did you manually build ruby and install it to /usr/local? If so, I'm unsure why chromebrew invokes it.
I presume you are using a ruby package from Linux distribution or chrome... -
- It is by design. doc/extension.rdoc says:
```
T_FIXNUM can be converted to a C integer by using the
FIX2INT() macro or FIX2LONG(). Though you have to check that the
data is really FIXNUM before using them, they are faster.
```
... -
- Closing as it is not a bug.
Now you can see unified coverage reports for Ruby's C and Ruby code in https://rubyci.org/coverage. It is measured under GitHub Actions: https://github.com/ruby/actions/blob/master/.github/workflows/covera... -
- Could you check the path of `@file1` in that file, and the filesystem of that volume?
-
- BTW preciously, I was testing against 053f78e139 where the bug had not been present yet.
-
- ~~~
$ cat /etc/os-release
NAME=Fedora
VERSION="32 (Rawhide)"
ID=fedora
VERSION_ID=32
VERSION_CODENAME=""
PLATFORM_ID="platform:f32"
PRETTY_NAME="Fedora 32 (Rawhide)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fe... -
- Note that `make runnable` makes links in `bin/`, which might be able to run if configured with `--enable-load-relative` option.
-
- Closing as it is not a bug.
A ruby binary that is built but not installed is half-baked. It is very hacky to run it without installation; it requires setting library paths, GEM_HOME, etc and etc. In the build process, the half-baked... -
- `"\x{00000020}"` ใๆธใใชใใใใชใฎใงใใจใใใใ็พ่กใฎๆๅใฏๆๅณ็ใงใใใจ่ใใพใใ้ใซใ`/\x{00000020}/` ใ่จฑใใชใ `"\x{00000020}"` ใ่จฑใใญใฐใใฃใฆใใจใซใชใใฎใงใฏใชใใงใใใใใใใใใไปๆงๅคๆดใซๆ่ฆใฏใชใใงใใใBug ใงใฏใชใใใใจใใใใจใง้ใใพใใ
`ONIG_SYN_OP_ESC_X_BRACE_HEX8` ใฏๅฎ่ฃ ่ฉณ็ดฐใชใใงใ็ดใใใใฃใใๆ็ฌใใใฎ่จใใจใใใซใใใใใใใใฏupstreamใ็ด... -
- minirubyใ ใจไธ่ดใใใฎใฏใrubygemsใใญใผใใใฆใใชใใใใฎใใใงใใ
```
$ TZ=Asia/Tokyo ./bin/ruby --disable=gems -ve "ENV['TZ']='right/Asia/Tokyo';t=Time.at(2<<30);p t;p t.utc"
ruby 2.7.0dev (2019-12-18T05:53:19Z master efbc0d499c) [x86_64-linux]
2038-01-... -
- @naruse ใใไฝใใฉใFeedbackใชใใงใใ๏ผใใใพใงใฎใใใจใใ ใจ @znz ใฏ่ฆๆฑใใใฆใใๆ ๅ ฑใๆขใซใใใชใ็ญใใฆใใใจใใ่ชญใใพใใใใ
-
01:41 PM Bug #16159: rubyspec about time fails in Asia/Kuala_Lumpur timezone
- ruby_2_6 r67836 merged revision(s) d6a2bce64a7fa1099e507e1d36b5f1533f42f60f,c687be4bc01c9ce52ea990945d9304d6fe59fe9b.
-
- time.c (find_time_t): fix round-to-zero bug
`find_time_t` did not work correctly for year older than the Epoch
because it used C's integer division (which rounds negative to zero).
For example, `TIme.new(1933)` ... -
- Closing as it is by design. If you want the change, please open a feature request ticket with a use case.
-
- Following log indicates that the SEGV happens inside of ffi.
> -- Control frame information -----------------------------------------------
> ...
and
> 759d3cd000-759d3fa000 r-xp 00000000 00:26 266588 /home... -
06:50 AM Feature #16428: Add Array#uniq?, Enumerable#uniq?
- Following a suggestion of `Enumerable#uniq?`, I also added `Enumerable#uniq?` to my patch.
`Array#uniq?` is left because it is faster than `Enumerable#uniq?`. -
- I seem to member that many years ago, I made the same proposal, and Nobu created a patch, but unfortunately, I didn't find any traces anymore on this tracker or in my mail.
Anyway, I support this proposal. It's definitely an useful fu... -
-
05:38 AM Bug #16384: Cannot cross-compile 2.7: undefined method `each_builtin' for RubyVM:Class (NoMethodError)
- I confirmed that the problem was fixed in cf948a3d3f and 2.7.0-rc1. Thank you for the fix!
-
- could you try on current master? It was fixed.
40026a408d -
- Nobody uses it any longer.
-
-
- Errno::EROFS may occur when the source tree is placed in a
read-only filesystem. -
- Hangs up only in ruby/ruby on Travis-CI.
https://github.com/ruby/io-console/commit/de39aa6dd6 -
- Methods and their definitions can be allocated/deallocated on-the-fly.
One pathological situation is when a method is deallocated then another
one is allocated immediately after that. Address of those old/new method
entries/definitions ... -
03:07 AM Feature #14912: Introduce pattern matching syntax
- How long is the current pattern matching expected to stay experimental before becoming stabilized? (And thanks for the work so far on it!)
-
- * Default VMIN and VTIME to minimum input.
* Disable parity check bits explicitly.
* Disable all bits for flow control on input.
Co-Authored-By: NARUSE, Yui <naruse@airemix.jp>
https://github.com/ruby/io-console/commit/5ce201a686 -
- It is by design. See "Scope" section of https://github.com/ruby/ruby/blob/master/doc/syntax/modules_and_classes.rdoc
-
- What is the purpose of writing the code in three different files? It only looks to me that it is making things more complicated.
A::B.foo and A::C.foo are undefined, and return a NoMethodError, as expected. If you meant A::B#foo and A... -
- I added this to https://bugs.ruby-lang.org/issues/16393
-
- * [Feature #16419] FrozenError.new ignores receiver: (znz)
* It seems that no one have strong opinion. So I want matz to decide.
* [Feature #16420] Warning[:experimental]=false (znz)
* I heard many warnings may make users trying p...