all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Madhu <enometh@meer.net>
Cc: emacs-devel@gnu.org
Subject: Re: question regarding my emacs package
Date: Tue, 13 Jun 2023 04:55:33 -0400	[thread overview]
Message-ID: <yp1ilbr91x6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20230613.093116.2248504087148072667.enometh@meer.net> (Madhu's message of "Tue, 13 Jun 2023 09:31:16 +0530 (IST)")

Madhu <enometh@meer.net> writes:

> *  Andrea Corallo <yp1mt148wh4.fsf @fencepost.gnu.org>
> Wrote on Mon, 12 Jun 2023 12:40:55 -0400
>> Madhu <enometh@meer.net> writes:
>>>
>>> So with my emacs-30 nativecomp this just doesnt work. the
>>> buffer-file-name slot of the cl-defstruct has to be changed to
>>> buffer-file-name-1 (and the corresponding accessors to
>>> breadcrumbs--breadcrumb-buffer-file-name-1) throughout the file.
>>
>> Does it works on the same Emacs codebase without native compilation?
>
> Yes, it looks like native-comp wont let you use buffer-file-name as a
> cl-defstruct slot name if you also have an initializer (SDEFAULT)
> form.  it gets confused and tries to use the elisp function
> definition.

Okay

> The following works on non-native comp but fails on native-comp.
>
> ```
> (require 'cl-lib)
> (defun xyz ())
> (cl-defstruct barf
>   (buffer-file-name (xyz)))
>
> (defun barf-foo ()
>   (let ((barf (make-barf)))))
> ```

What's the definition of fail here?

Thanks

  Andrea



  reply	other threads:[~2023-06-13  8:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  3:18 question regarding my emacs package ram
2023-06-07 15:53 ` Philip Kaludercic
2023-06-07 18:04   ` Philip Kaludercic
2023-06-07 19:45     ` ram
2023-06-07 19:48       ` Philip Kaludercic
2023-06-07 19:50         ` ram
2023-06-07 22:34           ` ram
2023-06-08  7:13             ` ram
2023-06-08  7:26               ` Philip Kaludercic
2023-06-08 18:50                 ` ram
2023-09-08  7:40                   ` Philip Kaludercic
2023-06-11 11:41                 ` Madhu
2023-06-12 12:52                   ` Madhu
2023-06-12 16:40                     ` Andrea Corallo
2023-06-13  4:01                       ` Madhu
2023-06-13  8:55                         ` Andrea Corallo [this message]
2023-06-13  9:19                           ` Madhu
2023-06-13 23:55                             ` Michael Heerdegen
2023-06-14 16:10                               ` Mattias Engdegård
2023-06-16  3:53                                 ` Michael Heerdegen
2023-06-16  4:46                                   ` Madhu
2023-06-16 15:28                   ` Michael Heerdegen
2023-06-17  3:01                     ` ram via Emacs development discussions.
2023-06-18  0:40                       ` Michael Heerdegen
2023-06-29 19:28                       ` ram
2023-06-11 18:49 ` João Távora
2023-06-11 19:08   ` ram via Emacs development discussions.
2023-06-12  8:45     ` Philip Kaludercic
2023-06-12 10:23       ` João Távora
2023-06-12 10:54         ` Philip Kaludercic
2023-06-12 20:43           ` João Távora
2023-06-13  0:36             ` ram via Emacs development discussions.
2023-06-13 18:13               ` João Távora
2023-06-13 21:46                 ` ram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yp1ilbr91x6.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=enometh@meer.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.