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: Thu, 01 Jun 2023 04:42:03 -0400 Message-ID: References: <83o7manh0e.fsf@gnu.org> <83y1l4ehpy.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2812"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: akrl@sdf.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 01 10:43:02 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 1q4dtd-0000Tv-Qh for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Jun 2023 10:43:01 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q4dsn-0007gF-EW; Thu, 01 Jun 2023 04:42:09 -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 1q4dsl-0007fT-Eu for emacs-devel@gnu.org; Thu, 01 Jun 2023 04:42:07 -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 1q4dsi-0004mB-9F; Thu, 01 Jun 2023 04:42:06 -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=zdxYrEcnGqkqZZ50CD1ffdU/QjMPyO3ZnxoOLT20L6g=; b=nYOWQ/ghVgSAnsl4HVbC 0xFh9OYxoq97s2IdgdjbWVE1lndhp+1h5xZNOvqMRWVVrLV3nC7nwY9Wqb+ZrRA+ADbXvvR6xxm85 5IZ6aM7I74W8W/zH894UhFwiMeUjeuidK9rjiR0Dg01j5eALWT3XeOL5ekSsBgAq4BmjGtnuusBH4 5S18BfSxTzBalFuf+tzkVAP6M2LiFjM3kj6jOM01pTCjAk5emvabQ73PJiNrEiWAwmvarAtw2GpUC VQ/lVlv2O/3wOjTV1GatLRQGWYi0UTaKrnPrVxqVuToc1ARRnq2BXJT0PTUFGmCc55vnaaXKymH6e FylvM0AhPF4oow==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1q4dsi-0007sZ-1c; Thu, 01 Jun 2023 04:42:04 -0400 In-Reply-To: <83y1l4ehpy.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 31 May 2023 16:46:49 +0300") 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:306495 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: Eli Zaretskii , emacs-devel@gnu.org >> Date: Tue, 30 May 2023 12:46:04 -0400 >> >> Okay I installed ecc1d990d9e into master to implement this, please let >> me know if the entry in NEWS can be improved or feel free to just do it >> (I'm terrible at writing). > > The NEWS entry, viz.: > > ** Help > ** 'describe-function' shows function inferred type when available. > For native compiled Lisp functions 'describe-function' prints (after > the signature) the automatically inferred function type as well. > > Is IMO too terse. "Inferred type" is terminology we didn't use and > don't explain the manual, so the above doesn't really tell what kind > of information is displayed. We should give a hint, and perhaps have > more details in the ELisp manual, probably as part of documenting > subr-type. Okay, I think I need some advise on where to get started on this so this weekend I can try to put some effort on. Where should we add the documentation for subr-type in the manual? >> Also I'd like to improve this feature to list also the function types >> that are known to the compiler (Read `comp-known-type-specifiers'). ATM >> they lives in comp.el but would be better to move them out. > > I don't necessarily see the reason. We will probably move to having > native-compilation be the default, in which case comp.el will be > loaded in the majority of sessions quite soon after startup. So it > doesn't make a lot of sense to try to move these out of comp.el. Right, from this POV I get it. Breaking comp.el in two I'm not sure it's worth, as of now the only part that would be used outside is actually comp-known-type-specifiers. Thanks Andrea