QUERY · ISSUE

Copy code-emitter documentation from Kickstarter to docs.micropython.org

openby adritiumopened 2018-08-20updated 2024-07-27

docs

There is documentation of the different emitters at micropython.org but I still find myself going back to the Kickstarter page because there is a nice comparison between the 3 different emitters.

Someone should copy-paste from Kickstarter to docs.micropython.org

CANDIDATE · ISSUE

Clarification of benchmark figures

closedby errordeveloperopened 2014-05-07updated 2014-05-11

The wiki page about performance should have a note on what percentage of MCU time was spent parsing the code etc, i.e. before it got to the steady state... (at least a rough indication).

The wiki page also links to the kickstarter post, where it's shown that one can use decorators to set a specific emitter for a function. That's something not mentioned on the wiki at all and seems important to clarify which one of the emitters was used to obtain those figures.

Assessment

Q Qwen · high

Both items concern code emitters and documentation, but they address different specific needs. Issue #4066 requests copying a comparison of the three emitters from Kickstarter to the official docs. Issue #579 requests clarification of benchmark figures on the wiki, specifically asking for details on parsing overhead and which emitter was used for benchmarks. While both reference the Kickstarter page and discuss emitters, #579 is about clarifying existing benchmark methodology, not about creating a general comparison document. The candidate does not resolve the query's request for a comprehensive emitter comparison.

Suggested action

Keep both issues open as they address distinct documentation needs. #4066 should be resolved by creating a dedicated comparison section in the official docs, while #579 requires adding specific details to the performance wiki page about benchmark methodology.

Copy code-emitter documentation from Kickstarter to docs.micropython.org

Clarification of benchmark figures

Keyboard