Hi!

While reviewing PRs lately I have noticed quite a number of print
statements in the code. Imho that is ok while developing but should not
be there when merging it in. The internals of builtins don't need
documentary status output like "---=== Method X builtin function
starting now ===---". These wouldn't hurt as much as something that
prints out intermediates. A few more thoughts on it:

* For high frequency bulitins print() statements not only slow down
execution but also fill up logs unnecessarily.

* An "if verbose" toggle might be a half baked remedy as it increases
compile time if there's a lot of debugging code to remove.

* print() statements that are left in the code get in the way of
rewrites and operator fusion.

So I'm inclined to clean out all the print() statements (or at least
comment them out) while merging PRs.

Opinions?

Best regards,
Mark

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to