From: tenderlove@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:90955] [Ruby trunk Bug#13115][Closed] `YAML.dump` outputs deperecated message even with delegated object
Date: Wed, 09 Jan 2019 22:37:33 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-76161.20190109223731.f1923eb97fdda910@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-13115.20170108115036@ruby-lang.org
Issue #13115 has been updated by tenderlovemaking (Aaron Patterson).
Status changed from Assigned to Closed
This has been fixed since Psych 3.0.0 https://github.com/ruby/psych/commit/712a65a53f3c15105cd86e8ad3ee3c779050ada4
----------------------------------------
Bug #13115: `YAML.dump` outputs deperecated message even with delegated object
https://bugs.ruby-lang.org/issues/13115#change-76161
* Author: mtsmfm (Fumiaki Matsushima)
* Status: Closed
* Priority: Normal
* Assignee: tenderlovemaking (Aaron Patterson)
* Target version:
* ruby -v: ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
`YAML.dump` outputs deprecated message if it calls with delegated object
but doesn't with inherited object:
~~~ ruby
require 'yaml'
require 'delegate'
$VERBOSE = true
class Delegated < DelegateClass(Object)
def initialize
super(Object.new)
end
end
puts 'YAML.dump(Delegated.new)'
YAML.dump(Delegated.new)
class Inherited < Object
end
puts 'YAML.dump(Inherited.new)'
YAML.dump(Inherited.new)
# $ ruby test.rb
# YAML.dump(Delegated.new)
# implementing to_yaml is deprecated, please implement "encode_with"
# YAML.dump(Inherited.new)
~~~
Is this intentional?
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2019-01-09 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-13115.20170108115036@ruby-lang.org>
2017-01-08 11:50 ` [ruby-core:79013] [Ruby trunk Bug#13115] `YAML.dump` outputs deperecated message even with delegated object mtsmfm
2017-01-18 12:30 ` [ruby-core:79124] [Ruby trunk Bug#13115][Assigned] " nobu
2019-01-09 22:37 ` tenderlove [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-76161.20190109223731.f1923eb97fdda910@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).