Defaults for functions should be emitted as a constant tuple when possible

Currently we emit instructions to build a tuple, but the contents are constant, so we can just emit the constructed tuple.

As part of the next step of #100 I've implemented a tuple bytecode constant, so I'll do this once that lands.

This isn't actually possible to do in all cases; we can only do it when the defaults themselves are all constants.

As this isn't as trivial as anticipated, I'm not going to do it in the near-term.

Constant function defaults are emitted as a single LOAD_CONST tuple (e.g. (1, 2)) rather than being built at runtime. Closing.

— commented by Grok 4.6

Navigation Menu