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,T_SCC_BODY_TEXT_LINE 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)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 5A37D1F451 for ; Thu, 11 Jan 2024 10:30:59 +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=i7e1SuPj; 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=CECbNSMY; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id BA3DD81D52; Thu, 11 Jan 2024 10:30:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1704969052; bh=dgdOHxlZAIDAI4QrB1RSkKQaa5akhFscAK7OlRli26I=; 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=i7e1SuPj3Su9Abk6zTDbtXrm9wvmJ7Je1bXaRkVF5txpaNtTVUWXhg++K+CPA+9UO 5CUHPBw+/pgxt+plcno3Dh/MjHT4AhDpxxRT/oNJQE/EzeBo39WAIzQv4v4EdXtMsW MXLJ4sDAkt9/yFl46t/XiDygU2rWGFJ1pbGa9QmA= Received: from wrqvtvtt.outbound-mail.sendgrid.net (wrqvtvtt.outbound-mail.sendgrid.net [149.72.120.119]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 7244381D50 for ; Thu, 11 Jan 2024 10:30:49 +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=CECbNSMY; 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=PKKnWokotdjfVXBA3oLa8sqaeJK3p30K4m/mISR8vxU=; b=CECbNSMYdq7xmdciE3MPFqGPLnfiwO3IjwlaO6hYsrIrIuTix2iB/mVbOeJK/C0xP7lu OlVH1oWcw54t2pdwskQoCjNdlj9KAlA7B/odgGP9AkzaLebbKQUlcmO7Fnv5EWzOHNZHnW Odfhcb/238J6ba63ivJkzQEaGdx5bqOOk0GCMKQIOO8+4WHDW3G4A/+dZQT/76ayFiwRby 4ILtOzfqHYWgbctLD6tEXlCwmG5ojod80MFqdOoyQBaxKPD3cq5nsdimtuwZQDdUVCIrBA +cEMzn9BRsribQ9fJjZ5kKfZ2gcPlqS6M0fDMqYbXEPjEvOz5naXvrwQlUicWQxQ== Received: by filterdrecv-655bd866f5-w9hhg with SMTP id filterdrecv-655bd866f5-w9hhg-1-659FC358-8 2024-01-11 10:30:48.106135773 +0000 UTC m=+2658454.160774022 Received: from herokuapp.com (unknown) by geopod-ismtpd-37 (SG) with ESMTP id i3fGqzWaSmO5kxIkKfXFPA for ; Thu, 11 Jan 2024 10:30:47.980 +0000 (UTC) Date: Thu, 11 Jan 2024 10:30:48 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Feature X-Redmine-Issue-Id: 18576 X-Redmine-Issue-Author: byroot 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: 92735 X-SG-EID: =?us-ascii?Q?DvL3W2Xo+Vk=2FeUn3F50L=2FNc8u9NqZCnbE0mXZHiyye4R1YZg=2FtAFc0SAFzpcS=2F?= =?us-ascii?Q?Zcr7BqPN=2FYCcMZBMITNeIci9STxYay0JAJWPbek?= =?us-ascii?Q?rFR+qXKqRwVtzoDtzbnvrBA1oJGn114IWR2QZFY?= =?us-ascii?Q?QjLEEvI9LKW4aMeXAmmGbtKfgbJbKd7N7qbCgYj?= =?us-ascii?Q?J=2FJNhcH+xrmJ1wFUOxoAd0EIbDX7VsaoHLXb3QT?= =?us-ascii?Q?UqvUZf66rvF4FeTJENfpDgu3BKYtAdwap32JHL8?= =?us-ascii?Q?AzpiPBXF8FcIwIDsAsNcw=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: b/2+PoftWZ6GuOu3b0IycA== Message-ID-Hash: 67BMJDPAHF2TXCSSURAKYYGXYSYEZBEL X-Message-ID-Hash: 67BMJDPAHF2TXCSSURAKYYGXYSYEZBEL 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:116172] [Ruby master Feature#18576] Rename `ASCII-8BIT` encoding to `BINARY` 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Issue #18576 has been updated by Eregon (Benoit Daloze). Also given the efforts of @byroot in https://bugs.ruby-lang.org/issues/1857= 6#note-21 and the offer from @matz in https://bugs.ruby-lang.org/issues/185= 76#note-19, I'd like to do exactly what matz said: > If you (or someone) estimate the compatibility issue is minimal, and want= to experiment to see if it's true during pre-release, I'd say go. I estimate it to be minimal. We can know from the experiment if it's true or not, there are more than 11= months before 3.4, so plenty of time to discover any potential issue with = it. ---------------------------------------- Feature #18576: Rename `ASCII-8BIT` encoding to `BINARY` https://bugs.ruby-lang.org/issues/18576#change-106185 * Author: byroot (Jean Boussier) * Status: Open * Priority: Normal * Target version: 3.4 ---------------------------------------- ### Context I'm now used to it, but something that confused me for years was errors suc= h as: ```ruby >> "f=E9e" + "\xFF".b (irb):3:in `+': incompatible character encodings: UTF-8 and ASCII-8BIT (Enc= oding::CompatibilityError) ``` When you aren't that familiar with Ruby, it's really not evident that `ASCI= I-8BIT` basically means "no encoding" or "binary". And even when you know it, if you don't read carefully it's very easily con= fused with `US-ASCII`. The `Encoding::BINARY` alias is much more telling IMHO. ### Proposal Since `Encoding::ASCII_8BIT` has been aliased as `Encoding::BINARY` for yea= rs, I think renaming it to `BINARY` and then making asking `ASCII_8BIT` the= alias would significantly improve usability without backward compatibility= concerns. The only concern I could see would be the consistency with a handful of C A= PI functions: - `rb_encoding *rb_ascii8bit_encoding(void)` - `int rb_ascii8bit_encindex(void)` - `VALUE rb_io_ascii8bit_binmode(VALUE io)` But that's for much more advanced users, so I don't think it's much of a co= ncern. --=20 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-c= ore.ml.ruby-lang.org/