Activity
From 04/02/2019 to 04/08/2019
04/08/2019
-
11:26 PM Feature #15742: Add Date#jisx0301 support new Japanese era
- akr (Akira Tanaka) wrote:
> > Maybe, we should await next JIS X 0301?
> ...
As Japanese government has claimed that only one month is enough for the transition, the new standard will be issued in this month at latest :) -
05:34 AM Feature #15742: Add Date#jisx0301 support new Japanese era
- - Unicode CLDR 35.1 alpha uses "R".
https://www.unicode.org/repos/cldr/tags/release-35-1-alpha/common/main/ja.xml
- OpenJDK also uses "R".
https://bugs.openjdk.java.net/browse/JDK-8205432
http://hg.openjdk.java.net/jdk/jdk/rev/... -
10:08 PM Misc #15723: Reconsider numbered parameters
- sawa (Tsuyoshi Sawada) wrote:
> Marc, regarding `|x, |`, I see plenty of cases like `map(&:first)` (or `map(&:last)`). Probably taking care of these cases is more important than the explicit `|x, |` cases. If you are going to count, you... -
07:17 PM Misc #15723: Reconsider numbered parameters
- Eregon (Benoit Daloze) wrote:
> @sawa Thank you for think link, I missed that issue.
> ...
Even more confusion ahead.
I don't see that this feature adds any benefit besides saving some chars in an ideal case.
On the downside it wil... -
06:15 PM Misc #15723: Reconsider numbered parameters
- @sawa Thank you for think link, I missed that issue.
I stand by my opinion though, and expressed it there too. -
11:58 AM Misc #15723: Reconsider numbered parameters
- Eregon (Benoit Daloze) wrote:
> @sawa The `|x,|` behavior for `@1` can only be considered a bug. It prevents `array_of_arrays.each { p @1 }` to work correctly.
> ...
@Eregon I think you better check the relevant threads before dumping ... -
- FWIW, I would bet >99% of Rubyists would agree this is a bug: https://twitter.com/eregontp/status/1115318993299083265
-
- As I said in #15723,
I believe the `|x,|` behavior for `@1` can only be considered a bug.
It prevents `array_of_arrays.each { p @1 }` to work correctly.
Why would we want to prevent that and make this pattern not general, dangerou... -
06:11 PM Bug #15754: MinGW build/compile failure with Ruby 2.5.5, but 2.6.2 & trunk ok
- As to commits, see:
r64620 - Declare as gnu_printf on mingw
https://github.com/ruby/ruby/commit/c115b39e033979bac7cfd2db5735549430dc14f7
and
r64630 - use mingw ANSI stdio
https://github.com/ruby/ruby/commit/1cf2bb4b20857581125... -
- @nobu
Thanks for the reply. Stupid on my part, I overlooked the changes re `gnu_printf` in configure.ac, and it's compiling fine.
I found the patch for it looking in an old copy of ruby-loco (using 'makepkg'). Back when Appveyor ... -
- `PRI_LL_PREFIX` should be defined in config.h by configure.ac.
```sh
$ grep '#define PRI_LL_PREFIX' .ext/include/x64-mingw32/ruby/config.h
#define PRI_LL_PREFIX "I64"
``` -
- Applied in changeset trunk|r67472.
----------
object.c: fix searching nested const paths
* object.c (rb_mod_const_get, rb_mod_const_defined): nested const
paths should not search from toplevel constants.
[ruby-core:92202] [Bug #15758] -
11:30 AM Bug #15758 (Closed): Object.const_defined?(name) falsely returns true on classes that are not defined
- in short https://i.imgur.com/qvIIBuu.png
Object.const_defined?('Baz::Bar') -> true
yet Baz::Bar -> class not found!
test to run, all ok on ruby 2.6.0, bug in 2.6.2
~~~ruby
class Foo
end
class Bar
end
class Baz
cla... -
- * object.c (rb_mod_const_get, rb_mod_const_defined): nested const
paths should not search from toplevel constants.
[ruby-core:92202] [Bug #15758]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67472 b2dd03c8-39d4-4d8f-98ff-823fe6... -
- * test/ruby/test_module.rb (TestModule#test_nested_get): fix a
typo. nested module's name is a qualified path.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67471 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- shevegen (Robert A. Heiler) wrote:
> But having a situation where changes to MRI could possibly be delayed due to difficulties
> ...
I am not proposing anything like that.
Practically, whenever MRI decides to add an experimental featu... -
- naruse (Yui NARUSE) wrote:
> Web browsers showed us that it cannot achieve at once both experimental and portable.
I will dare to challenge that.
Why would `ExperimentalFeatures.resolve_feature_path` not be portable?
Portable here ... -
11:41 AM Feature #15752: A dedicated module for experimental features
- One worry that I have here is that this change may add bureaucratic overhead to MRI in
particular. I have nothing against alternative ruby implementations at all, quite the
opposite - the easier it is to implement ruby/rubies the bette... -
09:54 AM Feature #15752: A dedicated module for experimental features
- Web browsers showed us that it cannot achieve at once both experimental and portable.
-
- ioquatix (Samuel Williams) wrote:
> I think it's a good idea. Might I suggest two potential ideas?
Go ahead :)
> ...
This is equivalent to my proposition of `ExperimentalFeatures` with a different name, right?
I don't understan... -
01:26 AM Feature #15752: A dedicated module for experimental features
- I think it's a good idea. Might I suggest two potential ideas?
Firstly, maybe have a shared `Ruby` module for common but interpreter specific functionality.
Then, interpreter specific modules e.g. `CRuby`, `MRuby`, `JRuby`, `Truffl... -
- Run these tests under the build tree.
-
- As far as I remember, the name "RubyVM" is introduced because the name of the implementation which is called as CRuby or MRI cannot be decided, and also its VM's name is not actually YARV. To rename it to something, it needs to reopen th...
-
- * struct.c (rb_struct_hash): force hash values fixable on LLP64
environment.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67470 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I **STRONGLY** object removal of flip-flop, in "-e" option at least.
It is too tiresome to rewrite with a flag variable in one-liners. -
- Applied in changeset trunk|r67468.
----------
range.c: force hash values fixable
* range.c (range_hash): force hash values fixable on LLP64
environment. [ruby-core:92194] [Bug #15757] -
02:36 AM Bug #15757 (Closed): [BUG] Unnormalized Fixnum value on Range#hash.to_s on Windows
- To reproduce:
```
ruby -e "(0..1).hash.to_s"
```
Result:
```
-e:1: [BUG] Unnormalized Fixnum value 0x8fa800e97a8f86b7
ruby 2.6.1p33 (2019-01-30 revision 66950) [x64-mingw32]
-- Control frame information ------------------... -
- Applied in changeset trunk|r67467.
----------
range.c: force hash values fixable
* range.c (method_hash): force hash values fixable on LLP64
environment. [ruby-core:92191] [Bug #15756] -
- To reproduce:
```
ruby -e "method(:p).hash.to_s"
```
Result:
```
-e:1: [BUG] Unnormalized Fixnum value 0xd258e532a3942665
ruby 2.6.1p33 (2019-01-30 revision 66950) [x64-mingw32]
-- Control frame information --------------... -
- Applied in changeset trunk|r67466.
----------
enumerator.c: force hash values fixable
* enumerator.c (arith_seq_hash): force hash values fixable on
LLP64 environment. [ruby-core:92190] [Bug #15755] -
- To reproduce:
```
ruby -e "0.step.hash.to_s"
```
Result:
```
-e:1: [BUG] Unnormalized Fixnum value 0xb3735f03e7a21893
ruby 2.6.1p33 (2019-01-30 revision 66950) [x64-mingw32]
-- Control frame information ------------------... - 03:26 AM Revision b29f55c5 (git): * 2019-04-08
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67469 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * range.c (range_hash): force hash values fixable on LLP64
environment. [ruby-core:92194] [Bug #15757]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67468 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * range.c (method_hash): force hash values fixable on LLP64
environment. [ruby-core:92191] [Bug #15756]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67467 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * enumerator.c (arith_seq_hash): force hash values fixable on
LLP64 environment. [ruby-core:92190] [Bug #15755]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67466 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:35 AM Bug #15753: unknown keyword when passing an hash to a method that accepts a default argument and a named argument
- I believe this is the same issue as #12717. We are trying to address this issue in #14183.
-
- I have updated my GitHub branch (https://github.com/jeremyevans/ruby/commits/keyword-argument-separation) to fix the issues in mame's branch that I identified in my previous comment.
Now, my branch keeps compatibility with Ruby 2.6 in...
04/07/2019
-
- As many of you may recall, I'm not a c type, especially regarding build errors. Recently tried to build 2.5.5 locally, and I get errors similar to the below. I do not have any errors using the same build code (ruby-loco) when building ...
-
08:24 PM Bug #15753 (Closed): unknown keyword when passing an hash to a method that accepts a default argument and a named argument
- e.g.
```ruby
>> def a(b = {}, c: 1); p [b, c]; end; a(a: 1)
Traceback (most recent call last):
3: from (irb):3
2: from (irb):3:in `rescue in irb_binding'
1: from (irb):3:in `a'
ArgumentError (unknown keyw... -
- BTW, @bozhidar discussed relevant points about Ripper and `RubyVM::AbstractSyntaxTree` in
https://metaredux.com/posts/2019/03/30/the-missing-ruby-code-formatter.html#the-impact-of-the-parser
He makes good points there. -
- mame (Yusuke Endoh) wrote:
> As far as I understand, RubyVM module is completely different than other builtin modules.
> ...
@mame Could you summarize this in the documentation of `RubyVM::AbstractSyntaxTree`?
Currently, it doesn't ... -
- It's kind of interesting that in this issue, I can count only 4 people which seem happy with the current state, and all the 25 others think the syntax should be changed or be removed.
Maybe it's time to rethink this feature and acknow... -
- jeremyevans0 (Jeremy Evans) wrote:
> But of the other proposals considered, I think only `\1` wouldn't present backwards compatibility issues, and that is associated with string escaping, newline continuation, and regexp backreferences,... -
- I completely agree with @marcandre here.
The cases using `@2` and higher are extremely rare, all feel pretty hard to read to me and force the simple case of a single argument to be more complicated and look more weird (`@1` instead of... -
- * [Misc #15723] Reconsider numbered parameters (eregon)
* We should address this soon. I think it's good to collect opinions within MRI committers. -
- The patch looks good to me.
I will let @nobu commit it.
A nice extra would be specs in `spec/ruby/core/exception/frozen_error_spec.rb` (similar to `spec/ruby/core/exception/name_error_spec.rb`) but this is not a requirement. -
- nobu (Nobuyoshi Nakada) wrote:
> I haven't look C-API well, the additional argument would be ok.
> ...
OK, v3 of the patch is attached, based off the initial patch with the positional argument, with the function renamed to `rb_frozen_e... -
- I haven't look C-API well, the additional argument would be ok.
`rb_raise_frozen_error` should be `rb_frozen_error_raise` like `rb_name_err_raise`?
As for the test, `assert_same` would be better for the equality of the receiver.
-
- waheedi (Waheed Barghouthi) wrote:
> The pull request you just created does not really reflect what you are saying, `The RubyVM module only exists on MRI. +RubyVM+ is not defined in`
I'm just trying to clarify as much as possible the... -
02:56 PM Feature #15743: RubyVM should be renamed to CRuby
- Eregon (Benoit Daloze) wrote:
> waheedi (Waheed Barghouthi) wrote:
> ...
I totally agree on your point
> There is more than one VM that can execute Ruby code, so I think "the Ruby VM" is simply confusing.
The pull request you just ... -
- waheedi (Waheed Barghouthi) wrote:
> @Eregon, I do believe there is a sense in what you are trying to do, but what makes more sense to me is that Matz Ruby was named "Ruby".
I believe "Ruby" refers to the programming language and fro... -
- Eregon (Benoit Daloze) wrote:
> I made a PR on GitHub to discuss the proposed documentation changes, please take a look and review:
> ...
@Eregon, I do believe there is a sense in what you are trying to do, but what makes more sense to... -
- I made a PR on GitHub to discuss the proposed documentation changes, please take a look and review:
https://github.com/ruby/ruby/pull/2113 -
- I just noticed `RubyVM.resolve_feature_path`.
This is a portable API, and as such should not be mixed with MRI-specific APIs (by being under `RubyVM`).
This shows the need for a common namespace for experimenting with portable experi... -
- mame (Yusuke Endoh) wrote:
> If you think so, you have to implement the feature in any way, regardles of whether it is renamed to CRuby or not? I don't see at all what the renaming will solve.
I think the rename will solve the probl... -
- I believe we should introduce a module for experimental features portable across Ruby implementations.
An example of such a portable experimental feature is `RubyVM.resolve_feature_path`.
This feature has nothing MRI specific in it, ... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67465 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * gc.c (obj_memsize_of): T_RATIONAL and T_COMPLEX cannot be an
imemo.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67464 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:18 AM Revision 57573566 (git): Add debug message for test_rinda crash
- We often see test-all worker crash on test_rinda, but for now we even
can't know which test is unstable from this output:
http://ci.rvm.jp/results/trunk_gcc5@silicon-docker/1926481
Let me print `caller` on the timeout failure.
git-svn-...
04/06/2019
-
- Eregon (Benoit Daloze) wrote:
> In the patch in `rb_raise_frozen_error`, `exc` is used for both the message and the exception object, could you use different variables?
> ...
Sure, I can make that change. Can you and nobu come to an a... -
- `NameError#initialize` uses a keyword argument for `receiver`, so I it makes some sense to be consistent.
OTOH, keyword arguments often imply extra processing, especially if the caller is not Ruby code, so I actually find the position... -
- nobu (Nobuyoshi Nakada) wrote:
> Seems reasonable, but shouldn't `FrozenError#initialize` use a keyword argument as well as `NameError#initialize`?
`NameError#initialize` uses an additional positional argument for the `name` argument... -
- Seems reasonable, but shouldn't `FrozenError#initialize` use a keyword argument as well as `NameError#initialize`?
-
- Similar to `NameError#receiver`, this returns the object on which
the modification was attempted. This is useful as it can pinpoint
exactly what is frozen, as in many cases when a `FrozenError` is
raised, you cannot determine from th... - 04:03 PM Revision 93ecb9a1 (git): * 2019-04-07
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67462 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67461 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67460 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * internal.h (rb_imemo_tmpbuf_auto_free_pointer_new_from_an_RString):
create tmpbuf to keep the pointer before xmalloc which can raise
a NoMemoryError exception. extracted from
https://github.com/bear-metal/ruby/tree/transient-ime... -
- Marc, regarding `|x, |`, I see plenty of cases like `map(&:first)` (or `map(&:last)`). Probably taking care of these cases is more important than the explicit `|x, |` cases. If you are going to count, you better count these in. And if di...
-
- jeremyevans0 (Jeremy Evans) wrote:
> Marc,
> ...
I showed it is *much less* useful. The cases `|x, y|`, `|x, y, z|` and `|w, x, y, z|` are making only 3.26 % of the block signatures (14.8% of signatures with arguments).
That is not ... -
- Marc,
Thank you for your analysis, I think you have raised a number of good points.
marcandre (Marc-Andre Lafortune) wrote:
> Let's first agree that a shorthand notation would only simplify `{|x| foo(x) }` and no other block signa... -
- I would like a notation to replace `{|x| ...}`, and *only* to replace this.
I strongly disagree with current implementation:
1) that allows multiple unnamed parameters
2) where `{@1}` actually doesn't replace `{|x| ...}` but `{|x, |... -
04:37 AM Feature #15195 (Closed): Deal with new Japanese era
-
- The final version of Unicode 12.1.0 will be published on May 7 (May 8 Japanese timezone). We should make sure that we switch from `UNICODE_BETA = YES` back to `UNICODE_BETA = NO`.
However, this has to be done very carefully. We have t... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67458 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67457 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67456 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Trying to fix
https://ci.appveyor.com/project/ruby/ruby/builds/23639998/job/0hm9v79xlryod1ff
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67455 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67454 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
04/05/2019
-
- This completes issue #15195.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67453 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 11:16 PM Revision 4e788540 (git): * 2019-04-06
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67452 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Debugging output is no longer needed because the problem has been fixed with r67449.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67451 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67450 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67449 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:58 PM Misc #15723: Reconsider numbered parameters
- Thank you Martin for your feedback.
I agree there is a degree of similarity between the thought disambiguation. Actually to some extent it even makes me consider using `@` prefix as a more coherent option.
In the same time, this *f... -
- psychoslave (mathieu lovato stumpf guntz) wrote:
> An other proposal would be to use a single letter. For example using `a` as suffix, you end up with `1a`, `2a`, `3a` and so on. Fully regular, as short to type as the arobase prefixed... -
- Hello Tsuyoshi Sawada:
> I hope you are not trying to repeat the joke in #15741 posted four days before.
I wasn't aware of this thread (thank you for the hint), and didn't try to make a joke with my own totally independent proposal. -
- psychoslave (mathieu lovato stumpf guntz) wrote:
> Sticking to English custom and habit regarding ordinal number notation, the proposal could take the form of this arguments could become : `1st`, `2nd`, `3rd`, `4th`, `5th`, and so on.
... -
- Hello Matthew! You wrote:
> The argument against the feature is people who don't want to use it, who inherit code (one way or another) from people who did use it and are therefore forced to use it. If you don't see it, it doesn't hur... -
- dvogel (Drew Vogel) wrote:
> jeremyevans0 (Jeremy Evans) wrote:
> ...
Even if you don't consider someone defining `Integer#to_a` to use `*` as a unary operator, it would create issues when `*` is used as a binary operator:
```ruby
... -
01:01 AM Misc #15723: Reconsider numbered parameters
- jeremyevans0 (Jeremy Evans) wrote:
> dvogel (Drew Vogel) wrote:
> ...
I make this suggestion knowing that it would have to be delayed until ruby 3. I consider the improvement in terms of simplicity and approachability to be worth the c... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67448 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Unicode file download doesn't work with Visual Studio, we need more debug output.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67447 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:52 AM Bug #15749 (Third Party's Issue): Rails Sever Crashing
- Started GET "/" for ::1 at 2019-04-05 12:41:02 +0100
/Users/akanksha/.rvm/gems/ruby-2.5.1@alkimii/gems/pg-0.18.4/lib/pg.rb:45: [BUG] Segmentation fault at 0x000000010d9bda7c
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]
... - 10:39 AM Revision f6338966 (git): * remove trailing spaces.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67446 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Unicode file download doesn't work with Visual Studio, see e.g.
https://ci.appveyor.com/project/ruby/ruby/builds/23614399/job/f8vya2l7fjdfcye4
We temporarily produce more output for debugging.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby... -
08:41 AM Revision b2311c67 (git): `rb_add_method` is void function.
- * method.h (rb_add_method): make it void function because
nobody use a return value.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67444 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 08:15 AM Revision 4b53f843 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67443 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * insns.def: add definemethod and definesmethod (singleton method)
instructions. Old YARV contains these instructions, but it is moved
to methods of FrozenCore class because remove number of instructions
can improve performance for... -
- Unicode Version 12.1.0 adds one single character, U+32FF SQUARE ERA NAME REIWA,
for the new Japanese era starting on May 1st. 12.1.0 will be finalized only on
May 7th, so we go with the beta version because further changes in the data we... -
12:22 AM Misc #15744: Improvement needed to documentation of 'Literals'
- shevegen (Robert A. Heiler) wrote:
...I don't know myself either...
Robert,
I was only musing about a how a "literal" might be defined. My only point is that I think a definition is required, since the term is frequently used in d...
04/04/2019
- 11:40 PM Revision c8d60fdd (git): * 2019-04-05
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67440 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * template/unicode_norm_gen.tmpl: Change formatting of output to produce only a
single item (or range) for each line to make future diffs shorter and easier
to understand and check.
* lib/unicode_normalize/tables.rb: output of the a... -
02:03 PM Misc #15748: [Documentation] Suggestion to adjust Object.html#method-i-instance_variable_set
- Duplicates #15265?
-
01:27 PM Misc #15748: [Documentation] Suggestion to adjust Object.html#method-i-instance_variable_set
- 'Frustrating' here isn't expressing any opinion - to 'frustrate' something means to prevent it from being done. The effort is being frustrated, not the author of the class. It's the same as saying 'thereby preventing the efforts'. You ca...
-
- This is not hugely important but since it was mentioned on reddit for
whatever the intent (by surfordie), I'll add the issue here too.
The "issue" is a bit with the wording of:
https://ruby-doc.org/core-2.6.2/Object.html#method-i... -
- * common.mk, defs/gmake.mk: rid of unicode normalization tables
timestamp. update the target tables file only when only it
exists.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67438 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
10:07 AM Misc #15723: Reconsider numbered parameters
- psychoslave (mathieu lovato stumpf guntz) wrote:
> If there is one thought that I would think worth considering in my text above, it's to turn the feature off by default and let user enable it at their own discretion.
That's like a w... -
- Thank you Jeremy for your detailed feedback.
> Not backwards compatible as `by` could already be a local variable or method.
One could just assume precedence of locally defined identifiers over keywords, but that is a whole othe... -
- dvogel (Drew Vogel) wrote:
> matz (Yukihiro Matsumoto) wrote:
> ...
This would not be backwards compatible:
```ruby
class Integer
def to_a
[:a]
end
end
h = {:a=>1, :b=>2}
proc{h[*0]}.call(:b)
# => 1
```
psychos... -
- What about introducing a keyword that refer to an array rather than a direct access to each element? For example naming this hypothetical array accessor `by`:
``` ruby
h = Hash.new { by[0][by[1]] = "Go Fish: #{by[1]}" }
# Or to my m... -
- matz (Yukihiro Matsumoto) wrote:
> Yes, I admit `{ @1[@2] = "Go Fish: #{@2}" }` is cryptic. But `{@1 * @2}` is not. So use numbered parameters with care (just like other features in Ruby). The **possibility** to make code cryptic itself... -
- * iseq.h (struct iseq_compile_data): Remove the dead ensure_node
and for_iseq members.
[Fix GH-2108]
From: Lourens Naudé <lourens@bearmetal.eu>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67437 b2dd03c8-39d4-4d8f-98ff-823fe69b... -
- * defs/gmake.mk: try to update Unicode normalization tables file
if Unicode data files exist.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67436 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:43 AM Bug #11903: [BUG] vm_call_cfunc - cfp consistency error
- jfeltesse (Julien Feltesse) wrote:
> I can reproduce in ruby 2.3.1 by lazy loading a sequence in FactoryGirl which has the same name as the attribute it is meant for.
Similarly, I can reproduce consistently in `ruby 2.4.1p111 (2017-0... - 03:34 AM Revision f1fb989f (git): enumerator.c: make arith_seq_first support nil begin
- * enumerator.c: (arith_seq_first): support nil begin.
* test/ruby/test_arithmetic_sequence.rb (test_first): add assertions for
beginless and endless arithmetic sequences.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67435 b2dd03... - 03:34 AM Revision 53d3fe06 (git): ruby/test_arithmetic_sequence.rb: add assertions for beginless and endless ranges
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67434 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 03:34 AM Revision dcb37d06 (git): range.c: support to make beginless arithmetic sequences
- * range.c (range_step): fix the guard condition so that a beginless
range can be turned into a beginless arithmetic sequence.
* test/ruby/test_range.rb (test_step): add assertions for the above
change.
git-svn-id: svn+ssh://ci.ruby... -
- Eregon,
Thank you for your reply, but I'm not convinced yet.
> But we cannot, end users use whatever is available in MRI, including RubyVM. Some gems use RubyVM.
If you think so, you have to implement the feature in any way, reg... - 01:34 AM Revision e5901735 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67432 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This reverts commit d147ad6231aebb1d478162fb8e109e0c6a696169.
because failing on CI:
http://ci.rvm.jp/results/trunk-mjit@silicon-docker/1916925
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67431 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:02 AM Feature #15747: `(..1).last(2)` should return array but raise TypeError
- Thank you to response.
mame (Yusuke Endoh) wrote:
> In general, I think that an enumerating operation against a beginless range should raise an exception. It is also the case at `Range#last` with an argument. Note that the meanin... -
- Thank you for playing with a beginless range.
In general, I think that an enumerating operation against a beginless range should raise an exception. It is also the case at `Range#last` with an argument. Note that the meaning of `Ran... -
- `Range#last` with argument for beginless range shouldn't raise exception, should it?
```
$ ./miniruby -ve 'p (..1).last(2)'
ruby 2.7.0dev (2019-04-04 trunk 67430) [x86_64-linux]
Traceback (most recent call last):
4: from -e:1:in ...
04/03/2019
- 04:06 PM Revision e896292d (git): * 2019-04-04
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67430 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Looks good in micro benchmark:
```
$ benchmark-driver benchmark/vm2_super.yml -v --rbenv 'before;after'
before: ruby 2.7.0dev (2019-04-03 trunk 67428) [x86_64-linux]
after: ruby 2.7.0dev (2019-04-03 trunk 67428) [x86_64-linux]
last_commi... -
- Tests of minitest randomly fails with strange errors:
https://dev.azure.com/rubylang/ruby/_build/results?buildId=303
https://dev.azure.com/rubylang/ruby/_build/results?buildId=314
Instead of marking `continueOnError` for all, let me sel... -
12:35 PM Misc #15723: Reconsider numbered parameters
- > However, limiting the usefulness to a single argument isn't bad at at. In fact, a single argument seem to be the limit of what makes sense:
> ...
Very ugly and not readable. Plese dont go this way! -
11:05 AM Misc #15723: Reconsider numbered parameters
- >
> ...
There is nothing more permanent than temporary code. What I'm concerned about is open-source libraries and quickly-made scripts using this syntax and never cleaning it up. This also begs the question of "Why add a syntax change... -
- vo.x (Vit Ondruch) wrote:
> mame (Yusuke Endoh) wrote:
> ...
I also vote for #3. (and hashrockets as the default syntax).
I'm sorry, but `@1` syntax is grotesquely ugly for a language like Ruby. (If this feature absolutely is necess... -
06:48 AM Misc #15723: Reconsider numbered parameters
- Thanks everyone for the discussion. I think the feature looks nice, but the syntax does concern me, as I think it looks too much like instance variables.
If this is going to be in the language I think $1 and $2 etc. make a lot more se... -
- * [Feature #15752] A dedicated module for experimental features (eregon)
* We need to address this soon, it prevents clean separation and alternative implementations to implement experimental features.
* [Feature #15743] RubyVM shoul... -
12:21 PM Misc #15459: DevelopersMeeting before/after RubyKaigi2019
- (removed, patch accepted)
-
- hsbt (Hiroshi SHIBATA) wrote:
> I strongly against to rename to `CRuby` from `RubyVM`. Because the implementation language like C in the namespace is irrelevant for users of Ruby.
Would you prefer MRI or YARV then?
As I mentioned ab... -
- About the naming discussion, I picked CRuby because I think this is what @matz uses when referring to this implementation.
@matz Could you confirm?
MRI is the more well-known name, but it also has other meanings, and some consider it... -
12:16 PM Feature #15743: RubyVM should be renamed to CRuby
- I strongly against to rename to `CRuby` from `RubyVM`. Because the implementation language like C in the namespace is irrelevant for users of Ruby.
-
- k0kubun (Takashi Kokubun) wrote:
> Could you provide real-world use case in which `CRuby` looks more appropriate than `RubyVM`?
I think all constants under RubyVM are clear examples:
```
CRuby::InstructionSequence - it is the bytec... -
- mame (Yusuke Endoh) wrote:
> I'm negative against the rename for some reasons.
Thank you for your feedback. I will reply inline.
> ...
Yes, `ruby`, not `Ruby`. For me `Ruby` means the language, and `ruby` is CRuby/MRI's executable... -
- Could you provide real-world use case in which `CRuby` looks more appropriate than `RubyVM`?
Off topic: mruby is also "the Ruby VM implemented in C" and "Matz' Ruby implementation" -
- I'm negative against the rename for some reasons.
1) CRuby/MRI is a popular name, not an official name. In fact, `RUBY_ENGINE` is `"ruby"`.
```
$ ruby -e 'p RUBY_ENGINE'
"ruby"
```
2) A casual user is not recommended to use ... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67427 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 10:56 AM Revision a6146af5 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67426 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67425 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:40 AM Feature #15553: Addrinfo.getaddrinfo supports timeout
- This is also related to it: https://bugs.ruby-lang.org/issues/14997 - once the DNS timeout is in place (when available) I could give the #14997 a shot adding per ip timeout and including the resolving timeout in the overall timeout.
-
10:08 AM Bug #15746 (Rejected): 11 test cases run failed
- Below problem is find on 2.5.3 and also 2.6.2.
and ruby is compiled from source. and source get from:
http://cache.ruby-lang.org/pub/ruby
below test failed:
ruby test_delegate.rb
ruby test_forwardable.rb
ruby test_pstore.rb
r... -
09:37 AM Bug #15745 (Closed): There is no symmetry in the beginless range and the endless range using `Range#inspect`
- The following commit introduces beginless range.
https://github.com/ruby/ruby/commit/95f7992b89efd35de6b28ac095c4d3477019c583
```
% ruby -v
ruby 2.7.0dev (2019-04-03 trunk 67423) [x86_64-darwin17]
```
There is no symmetry with ... -
09:35 AM Revision f0204a25 (git): Revive accidentally removed assertion
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67424 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- `(..2).cover?(..1)` should return true.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67423 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Committed at r67422. Please give it a try and let me know if you find any issue.
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67422 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
05:50 AM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- @tenderlovemaking
I try your patch again and no error this time (without the middleware to call GC.compact)
Maybe I forgot to restart server after switching to branch without middleware on my last test
However with middleware (I h... -
01:17 AM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- Sorry, I meant @noahgibbs
-
- @noah I think I have these errors fixed on my branch (including the performance regression). I slowed down every call to free an object because they may need to be removed from the global object_id table. Should be fixed here though: h...
04/02/2019
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67421 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I will use this from another function in compaction
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67420 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Also fix tests
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67419 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I am not sure if your definition can be used. For example, you refer to "compile time", but what is meant with
compile time? As far as I know, ruby is not compiled in the sense of generating some binaries/binary executable,
such as whe... -
- Documentation of "Literals" for v2.6.0 is given here: https://docs.ruby-lang.org/en/2.6.0/syntax/literals_rdoc.html. (I don't think it has been changed for some time.) It gives examples of literals but does not provide a definition. It i...
- 07:13 PM Revision 714c2b0a (git): * 2019-04-03
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67418 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This code was trying to access memory before unpoisoning it.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67417 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- This commit just adds poisoning around the freelist to help debugging.
Also verify that the freelist only contains T_NONE objects when checking
the heap integrity
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67416 b2dd03c8-39d4-4d8... -
- > whereas CRuby refers to ... what name exactly?
CRuby is the name some people (including Matz I believe) used to refer to the standard implementation of Ruby. Other people use the name MRI. It literally means 'the Ruby VM implemented... -
05:37 PM Feature #15743: RubyVM should be renamed to CRuby
- I agree with making the "RubyVM" namespace a little less generic. In JRuby and TruffleRuby, we both have our own "JRuby" and "TruffleRuby" namespaces, which tuck away our implementation-specific stuff.
However I'm not sure CRuby is re... -
- I am not involved in any of this so this should be up to those who are
involved; but one comment that is somewhat unrelated is that, at the least
to me, the meaning of the words are different. RubyVM sort of indicates
some VM, wherea... -
- My understanding is that `RubyVM` is supposed to only exist on MRI/CRuby, and not on any other Ruby implementation.
In fact, almost all features under `RubyVM` are not realistically implementable on other major Ruby implementations (JRu... -
06:34 PM Misc #15459: DevelopersMeeting before/after RubyKaigi2019
- [Feature #13683] Add strict `Enumerable#single`
* Matz already showed his discontent with the name `single`, but `only` could be a good alternative as proposed by nobu and Lisa on that issue. -
- I was pointed here after sharing the following code with my team mates. I really like the idea, and find I often reach for it. I second the name `only`.
``` ruby
module Enumerable
def only
only!
rescue IndexError
nil
... -
- The current master branch is
https://github.com/rubygems/rubygems/commit/97b264f0fa248c864b6ee9a23d3ff1cdd217dddb
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67415 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:39 AM Misc #15723: Reconsider numbered parameters
- I fail to see how the downsides outweigh the problems. The @-syntax looks ugly, misleading and adds even more complexity to the language. The `\1`, `\2`, etc. syntax makes much more sense if you deal with regular expressions a lot, but o...
-
- shevegen (Robert A. Heiler) wrote:
> Why would it be completely impossible to, for example, add BOTH @1 @2 AND "it"
> ...
The `itself` keyword is already used under different scope (wider than a block). And `it` has already been exclud... -
- I was about to comment on what ted wrote, but it would have become too long,
so here is a significantly shorter variant to just focus on a few points:
- I think "itself" is very similar to "it". Kotlin makes use of "itself", so
it i... -
07:57 AM Misc #15723: Reconsider numbered parameters
- What strikes me is that this feature attempts to solve a problem that is very limited in scope:
- Blocks where the arguments can't be given a meaningful name arguably become more noisy than they may need to.
with a very big hammer:... -
- zverok (Victor Shepelev) wrote:
>
> ...
I hate this. Suddenly you have `&` and `.:` and `.()`, and where everything outside the parens has an obvious receiver-message relationship, nothing inside does.
At least this:
```ruby
HT... -
- test-bundler started to fail with r67383
https://dev.azure.com/rubylang/ruby/_build/results?buildId=278
which is very unlikely to be Ruby implementation's fault.
test-bundled_gems also started to fail with r67413
https://dev.azure.com/r... -
- I think it's early that only you maintain them. We welcome to your patch or direct commit.
-
- * tool/downloader.rb (Downloader.save_cache): keep linked file
newer than cached file, so that GNU make triggers when the
content is updated. it uses the timestamp of symlink itself
instead of the target.
git-svn-id: svn+ssh://ci... -
- nobu (Nobuyoshi Nakada) wrote:
> Maybe, we should await next JIS X 0301?
I think it is too late.
JIS X 0301 update schedule is not shown.
However, we can wait vendors such as Microsoft.
Microsoft also needs the single letter a... -
- akr (Akira Tanaka) wrote:
> I think no-era representation is similar to truncation of ISO 8601:2000.
> ...
It reminds me the second parameter to `Time.parse`:
> We can change the date used to infer our missing elements by passing a
>... -
02:52 AM Feature #15742: Add Date#jisx0301 support new Japanese era
- Can this be handled like thread exceptions?
```ruby
Thread.abort_on_exception=true
```
I like this approach because it's dynamic and changes the behavior for
the current runtime.
```ruby
Date.japanese_era_exception=true
```
Or... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67412 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67411 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 03:49 AM Revision 5f3e5e6f (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67410 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67409 b2dd03c8-39d4-4d8f-98ff-823fe69b080e