diff options
| author | Jean Boussier <[email protected]> | 2024-04-19 14:51:51 +0200 |
|---|---|---|
| committer | Jean Boussier <[email protected]> | 2024-04-23 08:59:23 +0200 |
| commit | fff228487158cbc3c1cb0b4e09d2d727038ae0b7 () | |
| tree | bf2b2d86896c3b701c7158979c0331068aa5f032 /vm_method.c | |
| parent | a53435868e09fd1b149def652f356840f58f4d32 (diff) | |
Consolitate redefined the method warning
Currently redefining a method doesn't emit one but two warnings. One at the location of the new method, and one at the location of the old method. I believe this is not ideal because when collecting warnings via a custom `Warning.warn`, it has to be pieced together. It's even more tricky because the second part may or may not be emitted depending on whether the original method has an associated ISeq. I think it's much better to emit a single warning with all the information in one go.
| -rw-r--r-- | vm_method.c | 15 |
1 files changed, 10 insertions, 5 deletions
@@ -1015,7 +1015,6 @@ rb_method_entry_make(VALUE klass, ID mid, VALUE defined_class, rb_method_visibil old_def->type != VM_METHOD_TYPE_ALIAS) { const rb_iseq_t *iseq = 0; - rb_warning("method redefined; discarding old %"PRIsVALUE, rb_id2str(mid)); switch (old_def->type) { case VM_METHOD_TYPE_ISEQ: iseq = def_iseq_ptr(old_def); @@ -1027,10 +1026,16 @@ rb_method_entry_make(VALUE klass, ID mid, VALUE defined_class, rb_method_visibil break; } if (iseq) { - rb_compile_warning(RSTRING_PTR(rb_iseq_path(iseq)), - ISEQ_BODY(iseq)->location.first_lineno, - "previous definition of %"PRIsVALUE" was here", - rb_id2str(old_def->original_id)); } } } |