Brice

Nope, just noticed it while testing something out.

Are you planning to implement this with an AST traversal or a simulated execution?

No, I agree, AST traversal is the better option, as that will allow you to easily explore all paths through the code, and even estimate costs for code that doesn't...

It's because the runtime costs include more than just the basic execution -- things like type-checking, lookups, etc.

We could also add a check for a function that is defined as public but could be readonly. It should always be preferred to make the function read-only if it...

Good idea. The GitHub API could be useful for implementing that - https://docs.github.com/en/rest/reference/releases#get-the-latest-release

I noticed today that `gh` had a nice friendly way of doing this. I ran a command and after the output, it said: ``` A new release of gh is...

Here's another case, `(< u"\u{0380}" u"Z")`.

This fix is in release 0.6.2 but it doesn't seem to work in production the way it works when debugging. Reopening to look at it again later.

This SIP was also approved by the Economics CAB. See meeting minutes [here](https://github.com/stacksgov/sips/blob/main/considerations/minutes/economic-cab/2024-02-01-sip-021.md)