Anton Trunov

That would be awesome!

Looks like you also need to commit the changes to the generated `stdlib.ts`

@Gusarich Looks like after #768 this can be implemented directly in Tact

@Gusarich Any progress on this?

> I think we can keep this PR as it's now and do that for future stdlib updates Let's do a bit of doogfooding here: the more we use our...

> then what about all other functions from stdlib? Many of them are used in writeStdlib.ts so we can't just rewrite them natively in Tact. It's fine. If it cannot...

> @anton-trunov so should I move the new functions from stdlib.fc to Tact stdlib for this PR? Yes, let's go for it

LGTM. Just the specllchecker complaints. Btw, we do have Knip now with `pre-push` lints running automatically and those include spellchecking

These are some really nice suggestions: https://github.com/tact-lang/tact/issues/136#issuecomment-2021459272. Moving `bin/tact` to a separate package sounds reasonable, since we'd like to adhere to building the Tact compiler as a library with more...

> It would be especially nice to have the AST or CST exposed right after the parsing phase, so that it can be re-used in tools We should definitely expose...