From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Slot accessing issues in EIEIO Date: Thu, 07 May 2020 08:15:51 -0400 Message-ID: References: <87a72lhf3b.wl-all_but_last@163.com> <878si5gmt7.wl-all_but_last@163.com> <877dxoh1m6.wl-all_but_last@163.com> <874kssgzrf.wl-all_but_last@163.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="28844"; 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: Zhu Zihao Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 07 14:17:00 2020 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 1jWfSW-0007PN-Bc for ged-emacs-devel@m.gmane-mx.org; Thu, 07 May 2020 14:17:00 +0200 Original-Received: from localhost ([::1]:44638 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jWfSV-00077c-DC for ged-emacs-devel@m.gmane-mx.org; Thu, 07 May 2020 08:16:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41784) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWfRX-00064u-DN for emacs-devel@gnu.org; Thu, 07 May 2020 08:15:59 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:6737) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWfRU-0008VR-BH for emacs-devel@gnu.org; Thu, 07 May 2020 08:15:58 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 8B492100FAD; Thu, 7 May 2020 08:15:54 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id EC697100F54; Thu, 7 May 2020 08:15:52 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1588853752; bh=00++HzhOtLNuD0v49hnnMy5cv2uqckbWHTLUts5nBEw=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=KrrHFwvmbwX1scv6J3V3C4OrdNhcHKVlqwirkYHdFDgwMNgpp0hxHlXBvDQPcVwc6 B+lEXfOz8JeW09jyk2RKSTBxvvIfvrrasm/FBoHdsc3ZepM1adSfafGtWCbDxeycqN /joNOK8SyP/stzJti1bCyCtl1BCgUwklLbUZHVpv1/24RjG2Fm/aqMkn09MZbifG2A 0WNRcZvp4hqvqOoRoccBCkypxC5nMeew2REv1SqHEUg/6rK2/7J6Szur1VDtWePMBD uoDxVCtNjS8o1jaM+3DNwDK8p0NP3tBJm/TR/lBu64DBdUucosS+pNPI7MfVpEyo2P gWAlDCLBoq+7A== Original-Received: from alfajor (unknown [216.154.3.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 9FD7F1202FA; Thu, 7 May 2020 08:15:52 -0400 (EDT) In-Reply-To: <874kssgzrf.wl-all_but_last@163.com> (Zhu Zihao's message of "Thu, 07 May 2020 12:00:52 +0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/07 08:11:37 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] 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_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN 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:249165 Archived-At: > When we put the sync logic in slot-missing. How to distinguish really missing slots > and "simulated slots" is a problem. Maybe another approach is to rely on the `slot-unbound` notion: when a slot is not in-sync, mark it unbound so any access to it will call the generic function `slot-unbound`. I don't think this would support write-access via closql (or at least I can't see how that could be used to catch modification of the object slot to propagate them to the DB). Stefan