From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Q: BLV for function slots + BL obarray/hmap for symbol lookup? Date: Sat, 22 May 2021 23:25:22 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32610"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Arthur Miller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 23 05:26:07 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lkekg-0008Gz-BU for ged-emacs-devel@m.gmane-mx.org; Sun, 23 May 2021 05:26:06 +0200 Original-Received: from localhost ([::1]:57282 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lkeke-0003SM-O5 for ged-emacs-devel@m.gmane-mx.org; Sat, 22 May 2021 23:26:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60722) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lkek9-0002lC-Ad for emacs-devel@gnu.org; Sat, 22 May 2021 23:25:33 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:49985) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lkek7-0002IW-8k for emacs-devel@gnu.org; Sat, 22 May 2021 23:25:32 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 97525441193; Sat, 22 May 2021 23:25:29 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 0D51844118D; Sat, 22 May 2021 23:25:24 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1621740324; bh=mB8igf875tgKEZm+pd08dR5oxCjXMRDiuTCv12oHk6I=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=GhqO0Wdx+BS42jGAmqCdK2TN1EjV8ELAak3tzNQ+0gDvvWaGxJ6dlA28+sPPT0IuW xvaS5Jjp+ri3av/Uu57rvlflfLD3QOqbsNONms2Qqr+F7TdmKRSIB+AMSRSYFRTji9 LNR5cuw+T+HSTxzlameLnbQ7X4xUUSO1DUBkXeK3iwN3Dn/x01M5ezLPz4bmv54feC uAqD8rbLR422DERj8mwKPqxV0GurHLh3C5IhNJ3KBf7JRQ90VWJH18wT2MA9VdLvtS yQYL/Fkns0VSk91t42Jp0n2ATq81rneqpLVuRoYX2YqMmUyu8LoUb72tHSqWS3Uk7y bP9Rtzn3/Ff/A== Original-Received: from alfajor (69-196-163-239.dsl.teksavvy.com [69.196.163.239]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id A2635120388; Sat, 22 May 2021 23:25:23 -0400 (EDT) In-Reply-To: (Arthur Miller's message of "Sun, 23 May 2021 01:31:16 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:269644 Archived-At: > Ok, there you have something interesting. In which way? If you have time > to expand on that one. It is already possible to use custo obarray, but > we have to tell Emacs which obarray to use. I would like it to sort of > happen automatically if there is a buffer local one. Sort of. No idea > what would happen if there were more than one local :-). I have the impression that your needs are a bit vague ;-) E.g. which buffer should be used to resolve the "buffer-localness"? The one when `intern` is called or the one when the already-interned symbol is used? Maybe you'd be interested in the effort to add some kind of namespace mechanism by adding some "prefix rewrite" rules used by the reader, so you could say that the "f:" prefix maps to "formi-" and then a symbol like "f:dable" is read as "formi-dable"? Stefan