Activity
From 01/09/2019 to 01/15/2019
01/15/2019
-
11:15 PM Bug #15540 (Closed): 2.6.0 Dir#glob regression
- in an empty base folder create the following structure
```
.
└── c
├── d
│ └── a
│ ├── a.file
│ └── b
│ ├── b.file
│ └── c
│ └── c.file
└── e
... -
11:04 PM Bug #15539 (Rejected): Proc.new with no block shouldn't always warn
- Hi,
r66772 introduced a warning for the following code:
``` ruby
def foo bar = Proc.new
bar.call
end
foo { p "block" } # warn
foo ->() { p "block" } # no warn
```
I don't think this case of `Proc.new` should warn.... -
05:52 PM Feature #14915: Deprecate String#crypt
- If we want to remove a feature, we deprecate and warn first, that has always been the case in MRI.
@shyouhei Please add the warning. Otherwise, no users will consider it deprecated.
@normalperson If you disagree, please start a gen... -
03:34 PM Bug #15536: Crash on merging specific hashes using keyword splat
- That was fast, thank you.
-
02:19 PM Bug #15536 (Closed): Crash on merging specific hashes using keyword splat
- Applied in changeset trunk|r66832.
----------
st.c (rb_hash_bulk_insert_into_st_table): avoid out-of-bounds write
"hash_bulk_insert" first expands the table, but the target size was
wrong: it was calculated by "num_entries + (size to b... -
- Good catch. The following code still crashes on trunk.
```
{
**{
a0: nil,
a1: nil,
a2: nil,
a3: nil,
a4: nil,
a5: nil,
a6: nil,
a7: nil,
a8: nil,
},
a0: nil,
a1: nil,
a2: n... -
- Here's a snippet that leads to a crash on ruby 2.5.3. I tried to make it as small as possible.
```ruby
1000.times do
{
**{
a1: nil,
a2: nil,
a3: nil,
a4: nil,
a5: nil,
a6: nil,
a... -
03:21 PM Feature #15538: Erb indenting / unindenting
- kke (Kimmo Lehto) wrote:
> In `Erb`, would it be possible to add a new trim mode that would indent the following content to match the depth of the tag? The tag could for example be `<%|` and it would be enabled using `Erb.new(template, ... -
02:10 PM Feature #15538 (Feedback): Erb indenting / unindenting
- It's hard to understand your proposal for me. Could you fix the following two parts first?
1. Do not use "...." in the template. We are talking about a feature to change indentation and the indentation you imagine in "...." is not cle... -
01:35 PM Feature #15538 (Third Party's Issue): Erb indenting / unindenting
- In `Erb`, would it be possible to add a new tag that would indent the following content to match the depth of the tag? The tag could be `<%~` (to resemble the `<<~EOS` squiggy heredoc).
## Reason
Something like this would be easy t... -
- "hash_bulk_insert" first expands the table, but the target size was
wrong: it was calculated by "num_entries + (size to buld insert)", but
it was wrong when "num_entries < entries_bound", i.e., it has a deleted
entry. "hash_bulk_insert"... -
01:52 PM Revision 10d85b19 (git): Clarify Array#- and Array#difference documentation
- Currently we are not explicit enough regarding the potentially confusing
behavior of `Array#-` and `Array#difference` when it comes to duplicate items
within receiver arrays.
Although the original documentation for these methods does us... -
12:08 PM Feature #15438: Threads can't switch faster than TIME_QUANTUM_(NSEC|USEC|MSEC)
- Hi nobu. Thanks for looking into this !
Here's the patch for 2.6. I would be glad if you could consider also applying the other patch to 2.5. -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66830 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:17 AM Bug #15537 (Closed): Numeric#step doesn't iterate under some conditions
- Numeric#step doesn't iterate under the following conditions:
- receiver and/or `by` are `Float`
- `by` is negative
- `to` is default
- without block
### Example:
Good:
~~~ruby
p 1.step(by: 3).take(2) ... -
09:08 AM Bug #15399: [PATCH] insns.def (duparray, duphash): add dtrace hooks
- ruby_2_6 r66829 merged revision(s) 66767.
-
- insns.def (duparray, duphash): add dtrace hooks
They are considered Array and Hash creation events, so
allow dtrace (and systemtap) to track those creations.
Co-Authored-By: Eric Wong <e@80x24.org>
git-svn-id: ... -
- ruby_2_6 r66828 merged revision(s) 66788.
-
- Update refinements docs
Co-Authored-By: Vladimir Dementyev <dementiev.vm@gmail.com>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@66828 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ruby_2_6 r66827 merged revision(s) 66736.
-
- ast.c: argument must be a string
[ruby-core:90904] [Bug #15511]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@66827 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ruby_2_6 r66826 merged revision(s) 66745.
-
- Bump version to date-2.0.0.
I forgot to change it when Ruby 2.6.0 was released.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@66826 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ruby_2_6 r66825 merged revision(s) 66735.
-
- Fix mday overflow
[ruby-core:90897] [Bug #15506]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@66825 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
07:38 AM Feature #11741: Migrate Ruby to Git from Subversion
- Thumbs up for this incredible discussion of yours. I've truly appreciated perusing this discussion today and I figure this may be extraordinary compared to other discussions that I've perused yet. If it's not too much trouble prop this w...
-
06:42 AM Bug #15460 (Closed): Behaviour of String#setbyte changed
- Applied in changeset trunk|r66824.
----------
setbyte / ungetbyte allow out-of-range integers
* string.c: String#setbyte to accept arbitrary integers [Bug #15460]
* io.c: ditto for IO#ungetbyte
* ext/strringio/stringio.c: ditto for S... -
- * string.c: String#setbyte to accept arbitrary integers [Bug #15460]
* io.c: ditto for IO#ungetbyte
* ext/strringio/stringio.c: ditto for StringIO#ungetbyte
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66824 b2dd03c8-39d4-4d8f-... -
06:01 AM Bug #15513: MJIT compilation terminated due to -Wfatal-errors on GCC 7.3.0
- バージョンがかわってしまったので元にもどしました。
-
- 下記のとおりコンパイルされることが確認できました！ありがとうございます。
~~~
$ time ruby -v --jit-verbose=2 --jit-save-temps --disable-gems /tmp/t.rb
ruby 2.7.0dev (2019-01-15 trunk 66823) +JIT [x86_64-linux]
MJIT: CC defaults to /usr/bin/gcc
MJIT: tmp_dir is /tmp
... -
- This reverts commit b32fb23083912c37a2601c66531ed786a7c9f3e5.
This didn't work on AIX.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66823 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:53 AM Feature #15523: Let `Range#begin` and `Range#end` be aliases of Range#first and Range#last
- mame (Yusuke Endoh) wrote:
> I understand that "your problem" is confusion between a keyword "begin" and "Range#begin". First, I have never been confused by the fact. Then,
Actually, that was a minor point (I, myself, have not be... - 03:43 AM Revision a01f2f0a (git): * 2019-01-15
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66822 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66821 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:22 AM Feature #15301 (Closed): Symbol#call, returning method bound with arguments
-
- Eregon (Benoit Daloze) wrote:
> tenderlovemaking (Aaron Patterson) wrote:
> ...
Yes, I totally agree. I think `deep_freeze` is going to be necessary for adoption of Guilds, and the code I'm proposing in this patch would be an optimiza...
01/14/2019
-
- Required arguments cannot be placed between optional arguments **syntactically**, so it must be a `SyntaxError`.
`ArgumentError` is a runtime error.
-
07:52 PM Bug #15535 (Rejected): Optional arguments for definition - Syntax Error is not the correct Error type
- The below definition throws a Syntax Error, while there is no syntax error and I'm not sure what is the intention behind the Syntax Error
``` ruby
def hello(foo="bar", bar, yanko="me")
p "Hello"
end
```
The same definition be... -
- Your patch can't apply to the latest code.
Could you rebase it? -
- Anyone interested on the subject ?
-
- Thank you for the confirmation.
-
05:26 PM Bug #8059: Unrelated block value returned by String#match(regex) when regex is returned by a method that uses define_method and super
- The example appears to have been a little mangled on Redmine.
This code reproduces the issue on 1.9.3-p327 and 1.9.3-p551:
~~~
class Superclass
define_method :regex do
/^(\d)$/
end
end
class Subclass < Superclass
... -
06:40 PM Feature #15527: Redesign of timezone object requirements
- > Note that a timezone system requires two API.
Sorry for my arrogance, but can you please explain this a bit?..
From what I can understand from code, `local_to_utc` is used only from `Time.new`, but I am not quite sure why exactly.
... -
- This appears to still be an issue with Ruby 2.6.0 (ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-linux]):
Example:
~~~
module M
@@xyz = 123
end
puts "M.class_variables: #{M.class_variables.inspect}"
puts "M.class_variable... -
03:45 PM Feature #15526: New way to destruct an object hash
- Related/duplicate https://bugs.ruby-lang.org/issues/11758
-
02:34 PM Misc #15534 (Closed): Is there reliable way to check for new Ruby releases?
- In Fedora, we are using https://release-monitoring.org/ to check for packages updates. Unfortunately, the content of https://cache.ruby-lang.org/pub/ruby/ is a bit inconsistent which makes this service unuseful.
If I open the page, th... -
02:15 PM Feature #15523: Let `Range#begin` and `Range#end` be aliases of Range#first and Range#last
- @sawa Sorry, please don't mind my previous comment. I confused the behavior of Range and one of ArithmeticSequence.
-
- @sawa Please tell us how can we get both the end-value of the exclude-end range and the last element of the sequence generated by the range if your proposal were accepted?
-
- k0kubun (Takashi Kokubun) wrote:
> @vo.x Could you check if r66812 works?
Actually it is r66811 + r66812. Applying these two patches, the test suite passes on RHEL7 on all supported architectures and it keeps passing on Fedora Rawhid... -
- @vo.x Could you check if r66812 works?
-
- Applied in changeset trunk|r66812.
----------
mjit_worker.c: pass -lgcc to GCC platforms
using `-nodefaultlibs -nostdlib`.
I assume libgcc is needed when we use -nostdlib, and it's linked on some
platforms but not linked on some platf... -
- Memo: r61591, r61592, r66324 are related.
-
- > Maybe this patch too.
> ...
Hmm, these two pull requests are not merged yet in ruby/openssl and neither committed into ruby trunk.
We can backport them only after they are committed into trunk according to our stable branch managemen... -
11:17 AM Bug #15533 (Third Party's Issue): Segmentation fault: mysql2 client
- Started GET "/" for 127.0.0.1 at 2019-01-14 10:55:17 +0000
/../../.rvm/gems/ruby-2.6.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:90: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-darwin17] -
- This is a ticket for backport management.
r66819 contains bug fix for RubyVM::AbstractSyntax.parse/.parse_tree.
-
- tool/redmine-backporter.rb: change revision resource URL.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66820 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66819 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
09:48 AM Bug #15498 (Closed): Update Refinements documentation
- Fixed at r66788
-
- ruby_2_5 r66818 merged revision(s) 64589,64593.
-
- cont.c: set th->root_fiber to current fiber at fork
Otherwise, th->root_fiber can point to an invalid Fiber,
because Fibers do not live across fork. So consider
whatever Fiber is running the root fiber.
... -
- Target version is used by release engineering; don't use this as just a goal.
In this case set target version after drb removes `ObjectSpace._id2ref`. -
- Target version is used by release engineering; don't use this as just a goal.
-
- @kajisha 多分 r66817 で直ると思うのですが、最新のtrunkでMJITが動くかご確認いただけないでしょうか。
-
- Applied in changeset trunk|r66817.
----------
mjit_worker.c: pass -nostdlib when making pch as well
[Bug #15513] -
- [Bug #15513]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66817 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- r66812 might have allowed this. Testing.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66816 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ruby_2_6 r66815 merged revision(s) 66595.
-
- fix missed script_compiled events. [Bug #15471]
* ruby.c (process_options): script_compiled events are missed on
command line -e or specified file. this commit fix it.
[Bug #15471]
This patch shoul... -
- ruby_2_6 r66813 merged revision(s) 66670,66676.
- 06:34 AM Revision 8e2c6c16 (git): * 2019-01-14
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@66814 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- compile.c: support branch coverage for `a&.foo = 1`
[Bug #15476]
compile.c (iseq_set_sequence): fix branch coverage table
Not only TRACE_ELEMENT but also INSN_ELEMENT may have events.
The old pc2branchi... -
- using `-nodefaultlibs -nostdlib`.
I assume libgcc is needed when we use -nostdlib, and it's linked on some
platforms but not linked on some platforms (like aarch64, and possibly
AIX as well) as said in https://wiki.osdev.org/Libgcc :
>... -
- This should have no impact.
The CC_LIBS was too hard to read for human.
I don't remember whether the order of -lmsvcrt and -lgcc matters or not,
but I kept that for the best safety.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@668... - 04:49 AM Revision b4bc6ccb (git): * 2019-01-14
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66810 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- In r66597, both VM and JIT seem to be made slower:
```
$ benchmark-driver benchmark.yml --rbenv 'r66596::before --disable-gems;r66597::after --disable-gems;r66596+JIT::before --disable-gems --jit;r66597+JIT::after --disable-gems --jit' ...
01/13/2019
-
- Applied in changeset trunk|r66808.
----------
rdoc: ignore gemspec files
[ruby-core:91067] [Bug #15531] -
- Followed up https://bugs.ruby-lang.org/issues/14163#note-5.
The current documentation generated by rdoc shows gemspec files like:
https://docs.ruby-lang.org/en/2.6.0/lib/csv/csv_gemspec.html
It should be ignored. -
- [ruby-core:91067] [Bug #15531]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66808 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66807 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Objection.
I understand that "your problem" is confusion between a keyword "begin" and "Range#begin". First, I have never been confused by the fact. Then,
> * Let Range#begin and Range#end be aliases of Range#first and Range#last... -
- * lib/rdoc/options.rb (RDoc::Options#init_ivars): exclude backup
files by default.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66806 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66805 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Do not reuse the existence issue and modify status by yourself without maintainers. Because We use status is backport workflow for stable versions.
Please open another issue. -
- And here they are again: https://docs.ruby-lang.org/en/2.6.0/ (seems the problem is related to new default gems?)
-
- Sounds interesting, but `zone.utc_offset(time)` can only be a partial alternative of `utc_to_local` with using `gmtime(3).
Note that a timezone system requires two API.
One is an API which converts from [year, month, day, hour, minut... -
-
-
-
- Ruby 2.2.x is EOL status.
-
-
07:50 AM Bug #15390: Error installing nokogiri on ruby-2.6.0-rc1
- Possibly related: https://github.com/Homebrew/brew/issues/5068
Also this section from Nokogiri documentation: https://nokogiri.org/tutorials/installing_nokogiri.html#unable-to-find-libraries-on-macos-mojave -
- zverok (Victor Shepelev) wrote:
> Now, from what I can understand, you followed this rule of thumb:
> ...
Right.
> So, in fact, it is my "option 2": "codify that `#call` from now on has a special meaning in Ruby", and considering your a... -
- * time.c (vtm_add_offset): separate sign argument to get rid of
repeated negations.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66804 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I fixed the mail-bomb issue [ruby-core:91051](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/91051) - [ruby-core:91056](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/91056).
-
-
- Now, I did upgrade bugs.ruby-lang.org to Redmine 4.0 from 3.2.
See, notable changes via official announcement.
https://www.redmine.org/news/119
I migrated our custom plugins for Redmine 4.0 and Rails 5.2. When you encountered th... -
- * time.c (vtm_add_offset): just add offset to other components
only. removed subtraction of utc_offset as it is overwritten
always immediately in callers.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66803 b2dd03c8-39d4-4d8f-9... - 03:27 AM Revision 128b6577 (git): * 2019-01-13
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66802 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Apologies for catching those so late.
[Fix GH-2067] [ci skip]
From: Olivier Lacan <hi@olivierlacan.com>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66801 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
01/12/2019
-
- ruby_2_6 r66800 merged revision(s) 66768.
-
- Get rid of C99 feature for now [ruby-core:90949] [Bug #15519]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@66800 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ruby_2_6 r66799 merged revision(s) 66582.
-
- ruby_2_6 r66799 merged revision(s) 66582.
-
- Fix Net::Protocol::BufferedIO#write when sending large multi-byte string
This commit should fix Net::Protocol::BufferedIO#write when sending
large multi-byte string like following example.
```
$ ruby -rn... -
03:04 PM Feature #15526: New way to destruct an object hash
- zverok (Victor Shepelev) wrote:
> 1) Ruby has very consistent "argument **deconstruction**" rules. Basically, "it is deconstructed the same way it is constructed", e.g., if you can _call_ (construct) with arguments like `meth(a, *b, c: ... -
- In this patch:
* explanation of the class concept, with examples;
* docs for all class methods (most of them just say "Like `Enumerable#<methodname>`, but chains operation to be lazy-evaluated.", but I believe they are useful this way ... -
- In the light of discussions here: https://bugs.ruby-lang.org/issues/15428#change-76265 (TL;DR: `#call` is "implicit Proc conversion") I retract this proposal.
Please close. -
- > `#call` method is called by `Enumerable`, `Enumerator`, finalizer and `Signal`.
That's interesting. I just looked through the docs and understood I was not very aware of this fact:
* `Enumerable#find` (is the only method using `#ca... -
- nobu (Nobuyoshi Nakada) wrote:
> `#call` method is called by `Enumerable`, `Enumerator`, finalizer and `eval`.
Sorry, the last is `Signal`, not `eval`. -
- > > `#to_proc` is not an implicit conversion method, as it needs the specific syntax, `&`.
> ...
The point is that is done **explicitly**.
> > It is a usual case that a method may expect its argument to have particular method(s),
> ... -
- > `#to_proc` is not an implicit conversion method, as it needs the specific syntax, `&`.
But ideologically, it is the way to designate "this object quacks as a `Proc`", e.g. could be used instead of a `Proc` object.
> ...
Well, I b... -
- Sorry, I was going to reopen this after r66769, but have forgotten.
> Currently, it is the **only** place in Ruby where coercing argument to `Proc` is done with `#call` method.
These methods do not coerce argument, but just expect... -
- Sorry for my arrogance, but I am kinda surprised (to say the least) with how this ticket is treated.
* Ticket is closed silently (are you aware that it is an event when Redmine doesn't send the notification, so unless I'll check manua... -
12:39 PM Revision ad0ba0dc (git): trivial fix r66778 [ci skip]
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66798 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- @hsbt Thanks, I'll provide the patch.
Can we leave this ticket open? I believe it is an existing problem of the trunk, that should be tracked here, too. -
- I welcome the patch for documentation of bundler on the upstream that is https://github.com/bundler/bundler or ruby repo both.
I can handle it because I'm a member of Bundler team. -
- Since 2.6, Bundler is a part of the standard library. But the logic of standard library docs for "default gems" (only gem's `lib` is copied to Ruby source tree, and libraries main class/module is rendered as a docs entry point) lead to u...
-
- [ruby-core:91021] [Bug #15525]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66797 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- In #14850, there was timezone support introduced, there were pretty specific requirements for the Timezone object:
> A timezone argument must have `local_to_utc` and `utc_to_local` methods... The `local_to_utc` method should convert a... -
- Applied in changeset trunk|r66796.
----------
No TypeError at nil if exception: false
[ruby-core:91021] [Bug #15525] -
- [ruby-core:91021] [Bug #15525]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66796 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 04:53 AM Revision 52a97e36 (git): * 2019-01-12
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66795 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66794 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
01/11/2019
-
- > Admit it, you only wanted to use `.then`
That's absolutely not the point. The real point here is:
1) Ruby has very consistent "argument **deconstruction**" rules. Basically, "it is deconstructed the same way it is constructed", ... -
08:15 PM Feature #15526: New way to destruct an object hash
- > What do you guys think?
Ultimately you only have to convince matz, so the rest is just people giving opinions. :)
Victor wrote:
> ...
config.then { |host:, port:|
Admit it, you only wanted to use **.then**. ;)
To the o... -
- Not exactly what you are describing, but, funny enough, there is a way!
```ruby
config = { host: 'localhost', port: 3000 }
config.then { |host:, port:|
p "host=#{host}, port=#{port}"
}
``` -
07:45 PM Feature #15526 (Open): New way to destruct an object hash
- JavaScript has a nice a neat way to destruct objects.
~~~ javascript
const person = { name: "John Doe", age: 33 };
const { name, age } = person;
~~~
Erlang has a similar way to destruct a tuple:
~~~ erlang
Person = {"John Doe... -
07:52 PM Misc #15462: DevelopersMeeting20190110Japan
- On 2019/01/11 06:53, dementiev.vm@gmail.com wrote:
> Issue #15462 has been updated by palkan (Vladimir Dementyev).
>
>
> * [Feature #14344] refine at class level
> * there are some proposals for shorter refinements syntax; wan... -
- sharkcz (Dan Horák) wrote:
> I guess -nodefaultlibs should be omitted and/or -static-libgcc added. Skipping libgcc seems dangerous in general on any arch.
I removed `-nodefaultlibs` and it changed nothing. But reading GCC options [1]... -
- > Header and the content of /tmp directory (except the .gch, which was huge :/) are attached.
Thanks! Much appreciated.
> ...
Possibly. It's causing issues on #15513 as well... I'll try to fix it. -
10:42 AM Bug #15522: TestJIT#test_compile_insn_local fails on aarch64 RHEL7
- I suppose "-nostartfiles -nodefaultlibs -nostdlib" are the reason that libgcc isn't linked into the _ruby_mjit_p111u0.so
__multi3 is provided in /lib64/libgcc_s-4.8.5-20150702.so.1
I guess -nodefaultlibs should be omitted and/or -s... -
- So here is the output:
~~~
$ ruby --disable-gems --jit-verbose=2 --jit-min-calls=1 --jit-debug --jit-wait --jit-save-temps -e "
begin
def foo
a = 0
[1, 2].each do |i|
a += i
[3, 4].... -
04:04 PM Feature #14344: refine at class level
- shevegen (Robert A. Heiler) wrote:
> I think that:
> ...
On the other hand, it's closer to what we have to write now (`using(Module.new do`) and it doesn't have any additional constraints like being at the top level of class/module con... -
- I think that:
using do
refine Array do
Is not good. It looks very strange to me.
The other variants, such as the original one:
class Test
refine String do
or just toplevel:
refine String do
... -
- I had a chance this week to ask matz if he wants to allow bigger inputs or not for those methods. He answered yes. He prefers mod 256 behaviour for larger numbers. I will fix them again.
-
- Found by specs added in https://github.com/ruby/spec/pull/648
-
02:16 PM Bug #15525 (Closed): Complex(nil, exception: false) and Rational(nil, exception: false) raises an error
- Each line below raises an error
~~~
Complex(:sym, 0, exception: false) # TypeError (not a real)
Complex(nil, exception: false) # TypeError (can't convert nil into Complex)
Complex(0, nil, exception: false) # TypeError (can't convert ... -
- I have no particular pro or con opinion towards this proposal per se; however within
the two suggestions made, I think having these as aliases would be better than
obsolete them. People could then decide to use either variant if they w... -
04:51 AM Feature #15523: Let `Range#begin` and `Range#end` be aliases of Range#first and Range#last
- Done.
-
- Sorry, please change this to a feature request instead of a bug report.
-
- My understanding is that `Range#begin` and `Range#end`'s features are just subsets of `Range#first` and `Range#last`, respectively. And since they are slightly confusing with the keywords `begin` and `end`, I propose to either:
* Let ... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66793 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- It is supported since 2.6, [Feature #13770].
-
08:31 AM Bug #15524 (Rejected): Unicode not Supported in Class Names
- The details are at the attached file.
-
- You have not provided enough information about your environment. Could you please provide output of the following commands?
~~~
$ rpm -q ruby
$ rpm -q rubygem-nokogiri
~~~
Also, your backtrace has no debug information. You shoul... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66792 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66791 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66790 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
-
01:49 AM Feature #14145: Proposal: Better Method#inspect
- Eregon (Benoit Daloze) wrote:
> ko1 (Koichi Sasada) wrote:
> ...
+1. I'm using `#source_location` like `p method(:foo).source_location` sometimes to know the definition. If "Method#inspect" shows this information, it will help *me*.
... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66789 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
01/10/2019
-
11:40 PM Bug #15520: [patch] configure should refuse to build with jemalloc when headers are missing
- Thanks for the quick response! Could you backport this to the active backport branches, too?
-
- Applied in changeset trunk|r66779.
----------
configure: refuse to build with jemalloc when header is missing
[ruby-core:90964] [Bug #15520]
Freom: Misty De Meo <mistydemeo@github.com> -
- > The actual build is unlikely to succeed in this case since the functions won't be defined.
Agreed, makes sense to me. I remember that I may run into similar situations every now
and then when I e. g. wish to upgrade some program m... -
- When the `--with-jemalloc` option is passed, the configure script will correctly fail with an error if the library is missing. However, if the library is present and headers are missing, configure will succeed and allow the build to proc...
-
11:07 PM Feature #6240 (Closed): Enumerable#drop with negative argument
- knu (Akinori MUSHA) wrote:
> Using an existing feature, `[1,2,3,4,5].lazy.drop(-n)` could be written as `[1,2,3,4,5].each_cons(n+1).lazy.map(&:first)`.
> ...
That is clever.
I'll close this request, since it's not clear how frequent t... -
08:30 AM Feature #6240: Enumerable#drop with negative argument
- Using an existing feature, `[1,2,3,4,5].lazy.drop(-n)` could be written as `[1,2,3,4,5].each_cons(n+1).lazy.map(&:first)`.
Enumerable#each_cons does not use a circular buffer, though. (It currently uses push & shift) -
08:23 AM Feature #6240 (Feedback): Enumerable#drop with negative argument
-
- * [Feature #14344] refine at class level
* there are some proposals for shorter refinements syntax; want to hear commiters opinions (which one is better and good to be implemented) -
- * [Feature #15477] Proc#arity returns -1 for composed lambda Procs of known arguments
* May I commit? -
- * [Feature #11473] Immutable String literal in Ruby 3
* As I recall, matz said that this has been cancelled at the old developers' meeting. I'd like to confirm. -
- Co-Authored-By: Vladimir Dementyev <dementiev.vm@gmail.com>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66788 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
05:00 PM Bug #15468: Net::Protocol::BufferedIO#write raises NoMethodError when sending large multi-byte string
- Can we get this issue closed and the with right backport field values?
-
04:43 PM Misc #15514: Add documentation for implicit array decomposition
- If that's covered (and I agree it should be) it's also worth showing a case where they are not optional:
```
def baz
yield [1, 2], 3
end
baz { |a, b, c| p a: a, b: b, c: c }
#=> {:a=>[1, 2], :b=>3, :c=>nil}
baz { |(a, b), c|... -
- and ignore only -Wgnu-empty-initializer.
https://travis-ci.org/ruby/ruby/jobs/477867392
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66787 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- because it was for "-assi -Wpedantic" on Travis, but we changed the
Travis build to "-std=c99 -Wpedantic".
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66786 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ruby_2_5 r66784 merged revision(s) 66756.
- 03:02 PM Revision 06c98773 (git): * 2019-01-11
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_5@66785 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Mark array as "going to be modified" in `Array#reject!`
Before this patch, if `reject!` is called on a shared array it can
mutate the shared array rather than a copy. This patch marks the array
as "going to be m... - 03:00 PM Revision 1e19973d (git): * 2019-01-11
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66783 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- It's safer to backport r66768 to 2.6 branch, but for 2.7 it's not
needed anymore.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66782 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Thank you. I'll wait for that first.
Also having logs with --jit-verbose=2 version of https://bugs.ruby-lang.org/issues/15522#note-3 would be helpful.
P.S. The output format is changed in r66781. -
- k0kubun (Takashi Kokubun) wrote:
> > Also, it would be nice if the JIT output used different markup, which does not collide with Redmine markup :/
> ...
Thx
> > This should be the C code (although generated on my x86_64, because I d... -
- > Also, it would be nice if the JIT output used different markup, which does not collide with Redmine markup :/
Yeah. I'll change that later.
> ...
How did you get the output in the ticket description? If possible, I want you to up... -
- This should be the C code (although generated on my x86_64, because I don't have aarch64 readily available).
-
- The smaller reproducer probably is:
~~~
$ ruby --disable-gems --jit-verbose=10 --jit-min-calls=1 --jit-debug --jit-wait --jit-save-temps -e "
begin
def foo
a = 0
[1, 2].each do |i|
a += i
... -
- IMHO either something calls __multi3 and doesn't link to libgcc or gcc emits call to __multi3 and it's not implemented in libgcc.
Would be useful to see /tmp/_ruby_mjit_p20163u1.c source and the command line used to compile/link it. -
- Also, it would be nice if the JIT output used different markup, which does not collide with Redmine markup :/
-
- Trying to build Ruby 2.6 on RHEL7, I observe the following test failure on RHEL7, but just on aarch64. The other platforms pass just fine:
~~~
1) Failure:
TestJIT#test_compile_insn_local [/builddir/build/BUILD/ruby-2.6.0/test/ruby... -
- to avoid breaking redmine quote like
https://bugs.ruby-lang.org/issues/15522
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66781 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ruby_2_5 r66780 merged revision(s) 63823,63839.
-
- ruby_2_5 r66780 merged revision(s) 63823,63839.
-
- time.c: [DOC] Time#localtime
* time.c: state that Time#localtime does nothing when nothing
changes. [ruby-core:87675] [Bug #14880]
skip test_localtime_zone if force_tz_test is false
For example Solar... -
- [ruby-core:90964] [Bug #15520]
Freom: Misty De Meo <mistydemeo@github.com>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66779 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:40 PM Feature #6470: Make attr_accessor return the list of generated method
- > There's no use for private attr_reader, attr_writer, etc.
The intended usage is to ease future refactorings. If you always start with a method then later you can easily redefine just the method.
Initial code
~~~
class Somet... -
11:26 AM Feature #6470: Make attr_accessor return the list of generated method
- In general I support this request, but in this proposed use-case ...
> ```ruby
> ...
`foo=` without `@` or `self.` will assign a local variable. You'd have to change it to `foo=(...)` or `send :foo=, ...` anyway, no?
-
- @matz There are use cases, see https://bugs.ruby-lang.org/issues/11539 and https://bugs.ruby-lang.org/issues/11541.
Also, one case which has been IIRC frequently requested (mentioned just above in this issue, https://bugs.ruby-lang.or... -
08:28 AM Feature #6470 (Rejected): Make attr_accessor return the list of generated method
- There's no use for `private` attr_reader, attr_writer, etc.
And `protected` is not encouraged enough for new features. So I reject this.
Matz.
-
- and functions to clarify the intention and make sure it's not used in a
surprising way (like using 2, 3, ... other than 0, 1 even while it seems
to be a boolean).
This is a retry of r66775. It included some typos...
git-svn-id: svn+ssh... -
- ruby_2_5 r66777 merged revision(s) 66111.
-
- ruby_2_5 r66777 merged revision(s) 66111.
-
- Avoid GCing dead stack after switching away from a fiber
Fixes <https://bugs.ruby-lang.org/issues/14561> and discussed
<https://bugs.ruby-lang.org/issues/15362>.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby... -
- A volunteer is welcome: update the patch for trunk, test, perform re-experiment, etc.
-
- This reverts commit bb1a1aeab0f2a5fe437c89b841a887ba56653453.
We hit something on ci.rvm.jp, reverting until investigation is done.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66776 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- and functions to clarify the intention and make sure it's not used in a
surprising way (like using 2, 3, ... other than 0, 1 even while it seems
to be a boolean).
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66775 b2dd03c8-39d4-4d8... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66774 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:10 PM Bug #15499: Breaking behavior on ruby 2.6: rb_thread_call_without_gvl doesn't invoke unblock_function when used on the main thread
- > Patrik: can you try r66708? (git 9e66910b3bd85de32e95cf019ed285a36aecfd9e)
Eric: Sorry, I should have mentioned it in my comment. I also tried r66716 (`ruby 2.7.0dev (2019-01-05 trunk 66716) [x86_64-darwin18]`), [which can be seen a... -
- Ugh. I feel ashamed, honestly :)
Never thought about using `.slice` this way, somehow! It is definitely cleaner.
Can be closed. -
- Following is better
```ruby
next_page = response.dig('meta', 'pagination', 'next')&.slice(/&page=(\d+)/, 1)
``` -
-
- There's no use for `private` attr_reader, attr_writer, etc.
And `protected` is not encouraged enough for new features. So I reject this.
Matz.
-
- [Misc #15347]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66773 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * proc.c (proc_new): promoted lambda/proc/Proc.new with no block
in a method called with a block to a warning/error.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66772 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- For developer's reference, I created <s>https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/C99</s> https://github.com/ruby/ruby/wiki/C99-Usage-Guidelines and linked it from <s>https://bugs.ruby-lang.org/projects/ruby/wiki/DeveloperHowto...
-
- Applied in changeset trunk|r66771.
----------
configure.ac: Require C99
We already added AC_PROG_CC_C99 in r66605.
This commit stops warning C99 features.
[Misc #15347] [close https://github.com/ruby/ruby/pull/2064] -
- This is accepted for Ruby 2.7 at DevelopersMeeting20190110Japan [Misc #15462]. I'll take following actions:
* Disable change C90 checking on Travis to C99 https://github.com/ruby/ruby/pull/2064
* Fix configure as needed
* -std=c99... -
- I forgot use case.
use case is welcome -
- duerst (Martin Dürst) wrote:
> But I still have a very fundamental question: Why isn't this information available by introspection, without having to go over the net to a Web API? Ruby itself should not have any problem providing this... -
- Hello Jan,
> You are right, there is no guarantee and I agree with your thoughts. Nevertheless, I've also put the raw data on GitHub, so it does not depend on me solely: https://github.com/janlelis/stdgems. If there is an interest in ... -
- We already added AC_PROG_CC_C99 in r66605.
This commit stops warning C99 features.
[Misc #15347] [close https://github.com/ruby/ruby/pull/2064]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66771 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Yes, please.
Matz.
-
- duerst (Martin Dürst) wrote:
> I seem to remember from the book (http://exceptionalruby.com/) by Avdi Grimm that in general, methods that have the same name as classes are more tolerant than other constructors. If I remember correctly, ... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66770 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- ioquatix (Samuel Williams) wrote:
> > But dropping old rubies will happen every year and it can affect gems to remove legacy code. If it is considered as breaking changes as you said, it will cause major bump and it's false positive for... -
07:10 AM Feature #2250 (Rejected): IO::for_fd() objects' finalization dangerously closes underlying fds
- We discussed this issue today's Ruby developer meeting.
Our conclusion is that changing the default behavior of IO.for_fd is
too incompatible. It changes good working program to FD-leaking program.
It is another big issue, especial... -
- まつもと ゆきひろです。
一貫性という観点からは、両方共括弧なしでは呼べないという風にしたいのですが、どうやら互換性の問題が大きいので、とても直せそうにありません。ということで、苦肉の策ですが、現状維持とします。
調べると2006年まで両方とも「括弧を省略するな」という警告を出してました。が、リテラル内は2006年に文法エラーにできましたが、引数の方は、2007年にあきらめてしまって警告もなくしてしまってたようです。犯人は私ですがまったく覚えていなかった。禁... -
06:57 AM Bug #15521: encoding is missed when using `CSV.generate`
- Thank you.
I used `ruby/csv@master`, I confirmed this is fixed -
- Thanks for your report.
This has been fixed at master: https://github.com/ruby/csv/issues/62
I'll release a new version in a few weeks. Could you try the release (or master) again? -
- # Sample code
~~~ ruby
require "csv"
rows = [
["a", "b", "c", "d", "e"],
["あ", "い", "う", "え", "お"],
]
str = CSV.generate do |csv|
rows.each do |row|
csv << row
end
end
p str
p str.encoding
~~~
# Expec... -
- Applied in changeset trunk|r66769.
----------
proc.c: check if callable
* proc.c: check the argument at composition, expect a Proc,
Method, or callable object. [ruby-core:90591] [Bug #15428] -
- * proc.c: check the argument at composition, expect a Proc,
Method, or callable object. [ruby-core:90591] [Bug #15428]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66769 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I consider this for years. I REALLY like the idea but I am sure introducing this could cause HUGE compatibility issue, even bigger than Ruby 1.9. So I officially abandon making frozen-string-literals default (for Ruby3).
This does not... -
- I feel the expression `ary.map(&(:to_i << :chr))` is far less readable than `ary.map{|x|x.to_i.chr}`.
And the latter is faster and can take arguments NOW e.g. `ary.map{|x|x.to_i(16).chr}`.
Given these superiorities, this proposal doe... -
- I agree with the concept of showing more information by `Method#inspect`. Patch welcome.
Matz.
-
- If it doesn't work, please upload the full command logs of ./configure and make (on the slightly older trunk, r66767 as said above), or at least configure flags and CFLAGS if you don't want to show a full output.
-
- I agree r66768 should be backported to 2.6 to fix it safely. But at the same time,
> It should be fixed IMO, unless #15347 is accepted.
I think the build error should be fixed regardless of #15347 acceptance. Due to r66605, I belie... -
- Applied in changeset trunk|r66768.
----------
Get rid of C99 feature for now [ruby-core:90949] [Bug #15519] -
- I filled Backport field.
It's up to the 2.6 maintainer (not me now, I think) but this could be a bugfix rather than a feature change. -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66768 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- These tests were removed in r48217, so I'm closing this.
-
- Is this still failing? I don't see it on RubyCI.org
-
- Fixed here: https://github.com/ruby/fiddle/commit/0fc697bbc5c55c5f45ea4f67a6279fba38d2d514
01/09/2019
-
- Applied, thank you.
-
- They are considered Array and Hash creation events, so
allow dtrace (and systemtap) to track those creations.
Co-Authored-By: Eric Wong <e@80x24.org>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66767 b2dd03c8-39d4-4d8f-98ff-823fe... -
- Closing because there is no feedback
-
- This has been fixed since Psych 3.0.0 https://github.com/ruby/psych/commit/712a65a53f3c15105cd86e8ad3ee3c779050ada4
-
- Closing as I think this is a dup of Bug #9933 (and already fixed)
-
- I think all these warnings are fixed, so I'm closing this now
-
- This is fixed here: https://github.com/ruby/psych/pull/382
-
-
07:13 PM Misc #15462: DevelopersMeeting20190110Japan
- * [Feature #15456] Adopt some kind of consistent versioning mechanism
* More uniformity within the ecosystem would be nice. -
- * [Bug #15500] Behavior of require method in 2.5 is different from 2.4 and 2.6
* Is this bug or not? -
- * [Feature #15445] Reject '.123' in Float() method
* I want to know Matz's opinion. - 07:11 PM Revision 5f17fa6c (git): * 2019-01-10
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66766 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * hash.c: add special setter function (inc and dec).
* internal.h: constify RHash::iter_leve.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66765 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- @headius Would you like to start the deprecation of `ObjectSpace._id2ref` since you started this issue?
-
- I am observing following compilation:
~~~
gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -mtune=generic -fPIC -m64 -D_FORTIFY_SOURCE=2 -fstack-prot... -
02:38 PM Misc #15486: Default gems README.md
- Thank you for the feedback. In the GH issue the general opinion is to have a single README file with all the info.
duerst (Martin Dürst) wrote:
>
> ...
This is correct, although it might not be overly complex. If I understood hsbt c... -
- It was backported into 2.5 branch by r66689.
-
- Applied in changeset trunk|r66764.
----------
class.c: refactor class_instance_method_list
* class.c (class_instance_method_list): gather singleton and
extended methods first separately from ancestors.
[ruby-core:90872] [Bug #15501] -
- * class.c (class_instance_method_list): gather singleton and
extended methods first separately from ancestors.
[ruby-core:90872] [Bug #15501]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66764 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66763 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66762 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 12:55 PM Revision df0faba1 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66761 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- see r65802 and [Bug #14359]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66760 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
12:37 PM Feature #15483: Proc or Method combination with Symbol
- I think it will not work in the following cases.
```ruby
# NG: Error undefined method `call' for :chr:Symbol (NoMethodError)
p (30.method(:+) >> :chr).call 42
h = { Alice: 30, Bob: 60, Cris: 90 }
# OK
p (:to_sym >> h).call ... -
- I made [function-composite](https://rubygems.org/gems/function-composite) gem, as a PoC.
-
- ```ruby
# symbol/functionalized.rb
module Symbol::Functionalized
refine(Symbol) do
def call(*args, &block)
to_proc.call(*args, &block)
end
def <<(other = (b = true), &block)
to_proc << (b ? block : oth... -
- hi, nobu :)
> 引用
Why not using refinements?
It is example code.
Also, `Symbol#call` is not called in `Proc#<<`.
```ruby
# Error: undefined method `call' for :chr:Symbol (NoMethodError)
p %w{72 101 108 108 111}.map(&proc { |s... -
- Why not using refinements?
```ruby
# symbol/functionalized.rb
module Symbol::Functionalized
refine(Symbol) do
def call(*args, &block)
to_proc.call(*args, &block)
end
def <<(other = (b = true), &block)
... -
10:15 AM Feature #14594: Rethink yield_self's name
- I think the word should be `hit`.
Example:
~~~ ruby
construct_url.
hit(&Faraday.method(:get)).body.
hit(&JSON.method(:parse)).dig('object', 'id').
hit { |id| id || '<undefined>' }.
hit { |id| "server:#{id}" }
~~~ -
- At first, it isn't intentional behavior change. I should fix it, but I need to consider what is the correct behavior.
Ruby 2.5's behavior is given below:
```
$ RBENV_VERSION=2.5 irb --simple-prompt
>> (1 .. 10).first(5)
=> [1, 2... -
-
- With finite ranges, the class of the elements in the return value seems to reflect the class of the `step` parameter as shown below (although, I am not sure why the one with rational has `1` instead of `(1/1)`. A bug, perhaps?):
```ru... -
05:44 AM Bug #15518 (Closed): good old Infinite range notation behavior
- Ruby 2.5.3's behavior
~~~
# without step, it produces integer sequence
(1..Float::INFINITY).first(10) #=> [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
# with step, it produces floats instead of integers
(1..Float::INFINITY).step(1).first(10) #... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66759 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
07:55 AM Bug #15465: Tests failed on i386-cygwin
- In case of `make btest`, test_massign.rb and test_thread.rb succeeded.
The cause of failures is environment variable `RUBY_FIBER_MACHINE_STACK_SIZE=1` in tools/runruby.rb.
The workaround (not beautiful) is as follows:
```diff
... - 07:05 AM Revision fc9e0302 (git): complex.c: optimize zero check for Float
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66758 b2dd03c8-39d4-4d8f-98ff-823fe69b080e