Re: Changing a cl-defstruct definition in a published package

["Clément Pit-Claudel" <cpitclaudel@gmail.com>]

On 2018-07-15 09:11, Stefan Monnier wrote:
> Hmm... then it's going to be difficult: old UI plugins will see objects
> created by the new core, and there's no much we can do at that point,
> I think.

:'( good point

>> Is there a setting to tell cl-defstruct to not generate macros for
>> constructors and accessors?
> 
> Not currently, no.  But João would also like to have such a thing.

I see. That would be very neat.

> Note that the recompilation issue can be solved outside of package.el:
> - "recompile package" doesn't have to be in package.el (tho it is its
>   most natural place).
> - you could have code in flycheck.el that does:
> 
>     (eval-when-compile
>       (dolist (pkg (find-pkgs-using-the-old-flycheck-object-layout))
>         (recompile-package pkg)))
>   
>   so it will be executed when flycheck is compiled.

That's a interesting idea, and a good point.
But wouldn't it have to run *after* Flycheck is compiled? (Can you call the byte-compiler from code that's currently being run by the byte-compiler?)

Thanks again for your help,
Clément.