From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: Inferred function types in the *Help* buffer Date: Wed, 31 May 2023 08:19:31 -0400 Message-ID: References: <83o7manh0e.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37933"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Andrea Corallo , Eli Zaretskii , emacs-devel To: Mattias =?utf-8?Q?Engdeg=C3=A5rd?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 31 14:20:27 2023 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 1q4KoV-0009b3-AL for ged-emacs-devel@m.gmane-mx.org; Wed, 31 May 2023 14:20:27 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q4Kne-0005Wn-Cy; Wed, 31 May 2023 08:19:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q4Knc-0005WZ-HO for emacs-devel@gnu.org; Wed, 31 May 2023 08:19:32 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q4Knb-0000DG-Q9; Wed, 31 May 2023 08:19:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=tvgBsKGrpvADtLjz/UGNnN1uT4Hm/w5Z61wwYqlUSro=; b=N6Wf8n+2P9OWDuQybXrK ymMyN5hnXFzfomihxAnyTMnfxKF6YhGQjHdbNqAhT/j1C+3xj+0uZBJO3b0JJKw0HPT9PaCC5+/v8 5zL5fxlL4D2nVMUcY7y/92IzNkx7sfOGmvK0byxjLtu1p1cStIRVANs71C8xvwXqXtv+xhPBOsCR5 EQI7VZyV00/F++ACILHSFWgecmMevqRgIRQIFktkxY76Kf8uExNBao84II0XlQXo5mOf5Vdn4VB+0 Yjz0lp452qev9/AJMtHdPxBqO+JNWnIeaUlEszjSHhfzTV45VwZgAmnXadLydN8pRbwQyc25Grft4 d8aNijYz9CYRnA==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1q4Knb-0008JO-AK; Wed, 31 May 2023 08:19:31 -0400 In-Reply-To: (Andrea Corallo's message of "Tue, 30 May 2023 14:48:52 -0400") X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306439 Archived-At: Andrea Corallo writes: > Mattias Engdeg=C3=A5rd writes: > >> 30 maj 2023 kl. 18.46 skrev Andrea Corallo : >> >>> Ideally I think we should have a declare syntax and maybe an extention >>> to the DEFUN macro to cover for primitives as well, in order to have >>> these declaration where each function is defined. >> >> That would probably be a good thing in the long run, yes. There are othe= r declarations we would like to be able to attach to DEFUN as well. > > Hi Mattias, > > thanks for your feedback. > > yep agree, I think we should convey on a syntax for everything we want > to express (type and other properties), so we have something to > implement on the long run both for the Lisp both for the C side. > >>> But probably for now >>> something like the attached patch is sufficient and considerably less >>> invasive? >> >> Actually it sort of increases coupling; I'd rather it stayed in >> comp.el for the time being. You could write a function (in comp.el) >> for access. > > The main reason why I'd like to move them out is not to require the load > of comp.el for a simple C-h f. Secondary yeah I think that if it's in > use outside the compilation functionality should just not live there. Thinking about more I can't see why we should force people to load comp.el for a simple C-h f. If this data is consumed by both comp.el and help-fns.el it should stay in a commonly available place. Moreover this functionality would be available to non native compiled Emacsen as well, so forcing the load of comp.el feels to me even more odd. Andrea