From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on starla X-Spam-Level: X-Spam-Status: No, score=0.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_BL_SPAMCOP_NET,SPF_HELO_PASS, SPF_PASS autolearn=no autolearn_force=no version=3.4.6 Received: from nue.mailmanlists.eu (nue.mailmanlists.eu [94.130.110.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id DC6B61F4EB for ; Tue, 18 Feb 2025 10:59:39 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=ml.ruby-lang.org header.i=@ml.ruby-lang.org header.a=rsa-sha256 header.s=mail header.b=GWMgqHmz; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=VwBYYO0G; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1739876347; bh=HeP6+lvCedtNxQrsAOMIbS7yPHWKYEt8zRr7alj9uKo=; h=Date:References:To:Reply-To:Subject:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From:Cc:From; b=GWMgqHmz1T/ujOIIK0BWhvg7fr7NgjLWeQbvZLQQN4iDZu/wdD+ECw50E6vRJy6I3 gKQq2gc0RB1Q0cSUEPgkOo/+3ECKWDhnv8QNnKzr8FSsClMmmAEvhQrm9XCW7yEemz tKRMGcQP9D2GAa+helgG4ZYEgAiCSdy5zhvxFgAI= Received: from nue.mailmanlists.eu (localhost [IPv6:::1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 4970147030 for ; Tue, 18 Feb 2025 10:59:07 +0000 (UTC) Authentication-Results: nue.mailmanlists.eu; dkim=pass (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=VwBYYO0G; dkim-atps=neutral Received: from s.wrqvwxzv.outbound-mail.sendgrid.net (s.wrqvwxzv.outbound-mail.sendgrid.net [149.72.154.232]) by nue.mailmanlists.eu (Postfix) with ESMTPS id BBA3B46A06 for ; Tue, 18 Feb 2025 10:59:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ruby-lang.org; h=from:references:subject:mime-version:content-type: content-transfer-encoding:list-id:to:cc:content-type:from:subject:to; s=s1; bh=NMsRGrGJl27BC9yR8TfyBwhiEZCFk5CQfNEgPhbsmqM=; b=VwBYYO0G46bxwyvwLuJSgtEklE6H4UpgjdqRjiuvbmz829fF3thCP/+IUeeZNrhzsjOl mnZXuKuC/o+GFmSeAQvgFjzQbUcMJXgp1FrfVGLag3rEsv3pViaVMeZephuzA/lw5G+mPl Y9CFBnhdU1+WYmLLHXfFsVkaZyKS+PVAspWjx+Yz5Rkbu9yuqMLTcKDB013GGaDaDicc6e YIR8EMFGYONoW7N2RgMshLAB656pxsAXotzj8uj9cFRZ9rlH/zuLumk/xf7bFdBX/gYOrY VQlIIhGxoxkIaIro7fnlICwyd6lr1+olbHbFR7LXBUmcGK17d6Clvozb63+4XR5g== Received: by recvd-84b546689d-7lhwp with SMTP id recvd-84b546689d-7lhwp-1-67B467F4-7 2025-02-18 10:59:00.076083249 +0000 UTC m=+8256972.483067644 Received: from herokuapp.com (unknown) by geopod-ismtpd-20 (SG) with ESMTP id vf65TjuJTySxeM_T_uzPew for ; Tue, 18 Feb 2025 10:59:00.001 +0000 (UTC) Date: Tue, 18 Feb 2025 10:59:00 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Bug X-Redmine-Issue-Id: 20968 X-Redmine-Issue-Author: koic X-Redmine-Issue-Priority: Normal X-Redmine-Sender: Eregon X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-Redmine-MailingListIntegration-Message-Ids: 97822 X-SG-EID: =?us-ascii?Q?u001=2EByjZWvxTCjdoV8K03xEuhE7KqN4thWULFLM7+oH78KY30oYB3qFthsDpL?= =?us-ascii?Q?4w4cbYa3ttBh8bAHPOnE=2FkzPba67JNu7Lnrked2?= =?us-ascii?Q?O7K9VQ=2FJax2VjBqF7DjuoDDCFTfbR1AIJDWL4vJ?= =?us-ascii?Q?TENe4s98xuzBLAexzx5uk6MD0Z3Pj8Xj3BegeIo?= =?us-ascii?Q?O7yNB3VU8wS=2F2gvl+D3XFLvByhtlChCpcSJESX0?= =?us-ascii?Q?xXR6QugtQVc9mZ1lLxGFdGxdbjZtYeUMiz2tXYV?= =?us-ascii?Q?0A79Z+janEVH3Ps5gEw1llUwIA=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: K3DGQAMAT5LJ4JTFLSWC3EQYZJ4KFJQO X-Message-ID-Hash: K3DGQAMAT5LJ4JTFLSWC3EQYZJ4KFJQO X-MailFrom: bounces+313651-b711-ruby-core=ml.ruby-lang.org@em5188.ruby-lang.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:121100] [Ruby master Bug#20968] `Array#fetch_values` unexpected method name in stack trace List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: "Eregon (Benoit Daloze) via ruby-core" Cc: "Eregon (Benoit Daloze)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #20968 has been updated by Eregon (Benoit Daloze). I agree with Jeremy and Jean, this is not a bug. There are more and more methods implemented in Ruby, and that's a good thing: https://gist.github.com/eregon/912e6359e83781c5fa1c638d3768c526 That means these methods can look slightly different in backtraces, but it doesn't matter, `from :211:in 'Array#fetch_values'` is still in the backtrace above. It's a bit like `Hash#[]`, if there is an error during calling `key.hash` you will see `#hash` in the backtrace, it's natural. ---------------------------------------- Bug #20968: `Array#fetch_values` unexpected method name in stack trace https://bugs.ruby-lang.org/issues/20968#change-112021 * Author: koic (Koichi ITO) * Status: Open * ruby -v: ruby 3.4.0dev (2024-12-19T04:44:56Z master 2783868de2) +PRISM [x86_64-darwin23] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- It seems that the current Ruby implementation is displaying unexpected method name in stack trace. ## Expected Similar to `Hash#fetch_values`, the method name `Array#fetch_values` is expected to be displayed in the stack trace. ```console $ ruby -e '{k: 42}.fetch_values(:unknown)' -e:1:in 'Hash#fetch_values': key not found: :unknown (KeyError) from -e:1:in '
' $ ruby -e '[1].fetch_values(42)' -e:1:in 'Array#fetch_values': index 42 outside of array bounds: -1...1 (IndexError) from -e:1:in '
' ``` ## Actual The stack trace displays the `Array#fetch` method, which user is not aware of, along with the `` stack trace. ```console $ ruby -e '[1].fetch_values(42)' :211:in 'Array#fetch': index 42 outside of array bounds: -1...1 (IndexError) from :211:in 'block in Array#fetch_values' from :211:in 'Array#map!' from :211:in 'Array#fetch_values' from -e:1:in '
' ``` It likely requires an approach such as implementing it in C, as suggested in https://github.com/ruby/ruby/pull/11555. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/