[#98621] Re: Function getlogin_r()'s protoype] — Bertram Scharpf <lists@...>
FYI,
3 messages
2020/06/02
[#98947] [Ruby master Feature#16986] Anonymous Struct literal — ko1@...
Issue #16986 has been reported by ko1 (Koichi Sasada).
66 messages
2020/06/26
[#98962] [Ruby master Bug#16988] Kernel.load loads file from current directory without '.' in path — misharinn@...
Issue #16988 has been reported by TheSmartnik (Nikita Misharin).
5 messages
2020/06/26
[#98969] [Ruby master Feature#16994] Sets: shorthand for frozen sets of symbols / strings — marcandre-ruby-core@...
Issue #16994 has been reported by marcandre (Marc-Andre Lafortune).
7 messages
2020/06/26
[#100117] [Ruby master Feature#16994] Sets: shorthand for frozen sets of symbols / strings
— matz@...
2020/09/25
Issue #16994 has been updated by matz (Yukihiro Matsumoto).
[ruby-core:98732] [Ruby master Bug#16950] Stop nonsense keyword argument warnings in 2.6
From:
mame@...
Date:
2020-06-11 07:14:09 UTC
List:
ruby-core #98732
Issue #16950 has been reported by mame (Yusuke Endoh).
----------------------------------------
Bug #16950: Stop nonsense keyword argument warnings in 2.6
https://bugs.ruby-lang.org/issues/16950
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
* Assignee: usa (Usaku NAKAMURA)
* ruby -v: ruby 2.6.7p147 (2020-03-31 revision 67883) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
Ruby 2.6 warns the following code with `-w` option:
```
def foo(x) # warning: in `foo': the last argument was passed as a single Hash
end
h = { k: 42 }
foo(**h) # warning: although a splat keyword arguments here
```
This warning had been introduced by @nobu based on the original proposal of [#14183 "Real" keyword argument](https://bugs.ruby-lang.org/issues/14183). However, the design was changed so that automatic conversion from keywords to positional arguments will be kept in 3.0. In other words, the code above will work even in 3.0, so the warning no longer makes sense.
Rather, according to @matsuda and @kamipo, this warning sometimes hindered the fix work for the keyword argument change in Rails. This issue is possible to work around by using always non-keyword argument (and [they actually did so](https://github.com/rails/rails/commit/c0fd8f4bb2d4dd9abfbef9cc658ca0c88b8b0842)), but they say it is very annoying.
So, I propose stopping the warning in 2.6. This is a change for 2.6, but matz already accepted this. @usa, do you accept this?
A patch is quite simple:
```patch
diff --git a/vm_args.c b/vm_args.c
index 299ed16aa8..2e70ed3fcf 100644
--- a/vm_args.c
+++ b/vm_args.c
@@ -685,17 +685,6 @@ setup_parameters_complex(rb_execution_context_t * const ec, const rb_iseq_t * co
else if (!NIL_P(keyword_hash) && RHASH_SIZE(keyword_hash) > 0) {
argument_kw_error(ec, iseq, "unknown", rb_hash_keys(keyword_hash));
}
- else if (kw_splat && NIL_P(keyword_hash)) {
- if (RTEST(ruby_verbose)) {
- VALUE path = rb_iseq_path(iseq);
- VALUE line = rb_iseq_first_lineno(iseq);
- VALUE label = rb_iseq_label(iseq);
- rb_compile_warning(NIL_P(path) ? NULL : RSTRING_PTR(path), FIX2INT(line),
- "in `%s': the last argument was passed as a single Hash",
- NIL_P(label) ? NULL : RSTRING_PTR(label));
- rb_warning("although a splat keyword arguments here");
- }
- }
if (iseq->body->param.flags.has_block) {
if (iseq->body->local_iseq == iseq) {
```
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>