Morgan Smith <[email protected]> writes: > I often diff the elc files before and after making a change to see the > effect. I do this with rx forms to make sure they still compile to > constants. I forget my findings but I believe this helped me decide how > to include other regex variables in a regex using the rx constructs > literal, regexp, and eval.
byte-compiler warnings are IMHO sufficient in such cases. > It'd be pretty easy to do that to double check the sharp quote function > stuff if you wanted. I'm not going to bother checking though. I do not think we really need such fine-granular checks. The only real reason to look into byte-compiled vs not byte-compiled is performance bottlenecks. Doing it everywhere is simply wasting time that could otherwise be spend to improve other, more critical, areas in the code. > Is there a better workflow for comparing the byte-code (and maybe the > native code) before and after a change? I never had a need to do it, except some testing of native compiler, where I used M-x disassemble. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
