effectfully

A month later, there was a bit of progress on this particular issue, but not much. We're working towards a better builtins machinery in general and the scope of this...

Progress report: we've basically settled on separating the type-level universe from the term-level one and I've already started working on making it a reality, but I'm constantly getting distracted by...

Very little tangible progress has been made on this one in the past several months, unfortunately.

This was brought into the sprint, but hasn't been worked on yet. Chances are, it'll take a bit more time for us to get to this issue, I will keep...

More discussion in [this](https://github.com/input-output-hk/plutus/pull/5270) ADR. @zliu41 do you have an idea on what we should do with this issue?

@zliu41 should we keep this issue open or advertise using `Strict` and close the issue or something else? I'm just not sure how proceed with this specific GitHub issue.

> Let's keep it open until we merge https://github.com/input-output-hk/plutus/pull/5292 and start telling people to use Strict. @zliu41 we aren't telling people to use `Strict` quite yet, right?

> The internal ticket tracking this is PLT-5830. It's merged now (has been for a while) and hence we can close this issue with the following general advice: use `Strict`,...

Two years later (sorry, we are setting up proper GitHub monitoring only now)... In order to add a builtin you only need to edit one file, [`PlutusCore.Default.Builtins`](https://github.com/input-output-hk/plutus/blob/b0f5f28d8f0c3e25665feba96e044549318b91cc/plutus-core/plutus-core/src/PlutusCore/Default/Builtins.hs), following the pattern...

@michaelpj > But I'm not sure that's a good enough reason to change things around. We could try and preserve this in future, but it's too late for any more...