From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Tianxiang Xiong Newsgroups: gmane.emacs.devel Subject: Re: Print representation of records and hash tables Date: Wed, 13 Dec 2017 19:33:35 -0800 Message-ID: References: <87efnz7tw6.fsf@lifelogs.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c1cbf308e38a90560448c75" X-Trace: blaine.gmane.org 1513222428 9371 195.159.176.226 (14 Dec 2017 03:33:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 14 Dec 2017 03:33:48 +0000 (UTC) Cc: Emacs developers To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 14 04:33:44 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ePKHG-00021Z-VC for ged-emacs-devel@m.gmane.org; Thu, 14 Dec 2017 04:33:43 +0100 Original-Received: from localhost ([::1]:38977 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePKHM-0007gN-Hl for ged-emacs-devel@m.gmane.org; Wed, 13 Dec 2017 22:33:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50651) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePKHC-0007gF-MP for emacs-devel@gnu.org; Wed, 13 Dec 2017 22:33:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ePKHB-0007mz-Db for emacs-devel@gnu.org; Wed, 13 Dec 2017 22:33:38 -0500 Original-Received: from mail-wm0-x233.google.com ([2a00:1450:400c:c09::233]:45332) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ePKHB-0007lw-6x for emacs-devel@gnu.org; Wed, 13 Dec 2017 22:33:37 -0500 Original-Received: by mail-wm0-x233.google.com with SMTP id 9so8648089wme.4 for ; Wed, 13 Dec 2017 19:33:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=d6zzlVYtEPLcP/6plUvlwXf3oCics0LZ8YsofqxJ+3E=; b=a9m/rdey0KSwCiNhuSN76EDzEKlPf2LHIkor0peI6Ds5EoV6drvo6CrJWvwEe6GP2Y arxhposduTG/uj3oDWsSF6CoIP3XITRsJBJ/Oc8ZIXFvo58hJnyJTC2sxyTXPs71pcNa dege4Tb3c4tp0CjjygdoLFgcCJjBueU8Q7qjYnyCytfiah/n3M0Ts+amiSs70VfazOWu SYdh8otk/XIHF4LBGUwJ905TzeFDSRs79kKuobz5XRw4FrjktupldnABZhW4SqbOLvw+ scmd6Q2Ok1NEHl+Hus+l72mNTkrGl2kve/VAlnPXbROt3RXzaFPlP4x7RZLR1m3rRyVO M/UA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=d6zzlVYtEPLcP/6plUvlwXf3oCics0LZ8YsofqxJ+3E=; b=BE+TDsBBrGrAXD93qZug5ERDKRNNvNFOMp1S+5Ndd1knk6dsDzxoKjmzuy7B3dwyL9 tFghq1JlV7qsnsNogJNnXKSj1XJ59V3a9N/70pYF2KptDdbc+I91YMhupvWD2qWjvYW7 T/FxUQWiGRGXTeQO2lp/tCKMi+Ag9DDghpmCFjigv2RePS04/tKa6pSnA5MWgk3P8sco ekLrkYcXbinUEqatejnnFegg1kuWa6RkwrrP1eGMoEqU2CHHeIz05nh397Oh4BIM4i+v +HkyQEOZ0znGAb2W7xAYYIKo2jOkLy20sVcggfK4YKXJnMyh/jZmepYLbVJ4y5j4U/I6 zDWQ== X-Gm-Message-State: AKGB3mLGoZfN1iyndfWKUb5VMTBJHLlo06hkUVDie7w2qlbSNvKln3L1 F5fz/MAFISqWe271Mr+hGV0F6m168X/xnu7doH8= X-Google-Smtp-Source: ACJfBovKnYs7dpQespslrkmNogefR00O99Is0Zdq4yEUUoiceoMct+Dr1SD83YYvMIoPinfzTkcI3yCpOp08pAJz6Uc= X-Received: by 10.80.208.150 with SMTP id v22mr10140960edd.62.1513222415725; Wed, 13 Dec 2017 19:33:35 -0800 (PST) Original-Received: by 10.80.178.228 with HTTP; Wed, 13 Dec 2017 19:33:35 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:400c:c09::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221039 Archived-At: --94eb2c1cbf308e38a90560448c75 Content-Type: text/plain; charset="UTF-8" @Stefan, perhaps it'd be helpful to explain *why* `#s` was chosen. I'd guess it's to fit with the `#s` read macro for structures in CL? It's too bad hash tables already use `#s`--`#{` or `#h` would be more appropriate. On Tue, Dec 12, 2017 at 12:22 PM, Stefan Monnier wrote: > >>> Yes, it's confusing, and I'm very much against it. Interpretation of > ELisp > >>> code (even compiled code) now changes in a very subtle manner > depending on > >>> whether a record named `hash-table` happens to be defined or not. > SM> Similarly, interpretation of Elisp code can change in a very subtle > SM> manner if someone does (fset 'apply (lambda ...)). > > OK, but the read behavior is more broken. Right now records have > > basicall taken over all #s > > No, only those that are not taken by other uses. > > > Stefan > > > --94eb2c1cbf308e38a90560448c75 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
@Stefan, perhaps it'd be helpful to explain wh= y=C2=A0`#s` was chosen. I'd guess it's to fit with the `#s` read = macro for structures in CL?

It's too bad h= ash tables already use `#s`--`#{`=C2=A0or `#h`=C2=A0would be m= ore appropriate.


<= div class=3D"gmail_quote">On Tue, Dec 12, 2017 at 12:22 PM, Stefan Monnier = <monnier@iro.umontreal.ca> wrote:
>>> Yes, it's confusing, and I= 'm very much against it. Interpretation of ELisp
>>> code (even compiled code) now changes in a very subtle manner = depending on
>>> whether a record named `hash-table` happens to be defined or n= ot.
SM> Similarly, interpretation of Elisp code can change in a very subtle<= br> SM> manner if someone does (fset 'apply (lambda ...)).
> OK, but the read behavior is more broken. Right now records have
> basicall taken over all #s

No, only those that are not taken by other uses.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stefan



--94eb2c1cbf308e38a90560448c75--