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=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham 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 18ED11F44D for ; Wed, 20 Mar 2024 20:27:58 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; secure) header.d=ml.ruby-lang.org header.i=@ml.ruby-lang.org header.a=rsa-sha256 header.s=mail header.b=0Bxw7swO; 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=HMe2B0Gz; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id C6399835CD; Wed, 20 Mar 2024 20:27:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1710966469; bh=N1LhWbwH4ZNUbYwdGfLLLy9d9v6N265kQXPc6pzpPQs=; 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=0Bxw7swOXdsykpa72Y1hW+fC5VwGoCKAZkzFQ3/nt+vSpP5GjL14bAbTCnNQ27uvf FVGXz96AViYW77BDP3FnMYzXeI+BPf1v5Pe1si9IJVaz+7O3Aa8u/aly50A+OPlmVo sCvTyessy02H6DP3kdk9vwwOwgtgAsaWy6sd4SlI= Received: from s.wfbtzhsv.outbound-mail.sendgrid.net (s.wfbtzhsv.outbound-mail.sendgrid.net [159.183.224.104]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 632A0834F0 for ; Wed, 20 Mar 2024 20:27:44 +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=HMe2B0Gz; dkim-atps=neutral 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=BAh/UCYVBU2MJiTPXjFUuBfyLeXiU9mrg66r7dZC3SA=; b=HMe2B0GzhqDUDF1TXMuuwBSFbBsbp+6NDMxncyI/KMJNhGQpdfOJmGvh+CtIhpfzISfS wxM9HKZIhgWkhrHlQx9jqi8pdVUryKm3iTCPXoU6VkmWS+YGaWj7CyXiWnKyS+i0EdXldT BYCMsa1+704ywHYGpHw02pX0dwCBWj1R63Gn6a9rNC/2vqGfBy3EzpJe2M457RkSxRPFqN jt6bSRLDpBmU3gyVy8Ye21QenplaWQ9vmdoHKiuJ+m20OrzgI6b6fsqrSgMLWGTXMipgOK fU2+iRCX11X83Ze84WJamd8nPWjh6FT5bBBVl8kDGKTaTU+md/IHzUVNz9hlVZDg== Received: by recvd-7555548f4d-dp9sk with SMTP id recvd-7555548f4d-dp9sk-1-65FB46BF-A 2024-03-20 20:27:43.421744548 +0000 UTC m=+170900.330261685 Received: from herokuapp.com (unknown) by geopod-ismtpd-canary-0 (SG) with ESMTP id zDavhDmtRNSZvo8qDNSsbw for ; Wed, 20 Mar 2024 20:27:43.382 +0000 (UTC) Date: Wed, 20 Mar 2024 20:27:43 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Feature X-Redmine-Issue-Id: 20384 X-Redmine-Issue-Author: kddnewton X-Redmine-Issue-Priority: Normal X-Redmine-Sender: kddnewton 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: 93866 X-SG-EID: =?us-ascii?Q?u001=2E41nWPij=2FD1kdGmpgWeHScbb9X8tZePZrQQx3bl8Vy2odBuMhLMhId2kIq?= =?us-ascii?Q?I4MmMJ43lNHfKPNNds=2Fb3JsTYpYoWyQb3+sPV4d?= =?us-ascii?Q?vscaSKwkBzW7zUwt7z3M=2FIGVsYZCgeGrvAJDJye?= =?us-ascii?Q?ozFjMMH0bPwulZmQWJX0o0eke31hbT9AxJ84TGx?= =?us-ascii?Q?3sbFxxMJ8EWVr4B0CPETXt61lxvoiN4hS6hjIO+?= =?us-ascii?Q?1wlzMsxtK0cXRFLNziIuinRDhV4+jO0JbGj+8Ob?= =?us-ascii?Q?IOh+gal47sYPCmxE9KYE=2FI7NVw=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: 7KNVA6RSY2YELX42OIALS557QEOKEJUH X-Message-ID-Hash: 7KNVA6RSY2YELX42OIALS557QEOKEJUH 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.3 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:117268] [Ruby master Feature#20384] RubyVM::InstructionSequence.{new,compile} use --parser option List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: "kddnewton (Kevin Newton) via ruby-core" Cc: "kddnewton (Kevin Newton)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #20384 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Feature #20384: RubyVM::InstructionSequence.{new,compile} use --parser option https://bugs.ruby-lang.org/issues/20384 * Author: kddnewton (Kevin Newton) * Status: Open ---------------------------------------- Right now we have `RubyVM::InstructionSequence.compile` and `RubyVM::InstructionSequence.compile_prism`. We introduced this API in order to properly test the integration, even when running with `--parser=parse.y`. I'm running into issues, however, when tests are comparing between `eval` and `RubyVM::InstructionSequence.new`. The latter always uses `parse.y`, even if `--parser=prism` is passed on the command line. I would like to change that so that `RubyVM::InstructionSequence.{new,compile}` respects the `--parser` option so that it's consistent. Would this change be okay? It would only impact processes with `--parser=prism`, so I don't imagine there's any kind of risk here. -- 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/postorius/lists/ruby-core.ml.ruby-lang.org/