Borja o'Cook

I don't think this should be closed, it should at least be fixed by making the compiler print an error message.

@sgebbie Since this changes the standard library, I think this will be required to go through the [RFC](https://github.com/ponylang/rfcs#when-you-need-to-follow-this-process) process.

@sgebbie Cool. One point to consider is that since pony is pre-1.0, we can be more relaxed about breaking changes. In this case, I'd at least write down the option...

Previous notes that motivated this change on Zulip: https://ponylang.zulipchat.com/#narrow/stream/189985-beginner-help/topic/json.20iso

Maybe. I tried looking for errors related to uifset but couldn't find any open issues.

Sorry, yes, it's the same issue, I'll add a comment there, thanks!

@SeanTAllen How does this bug manifest itself? I wasn't able to see any problems with `arch=armv8` on the M1. The installed `ponyc` binary seems to work fine using `make install`...

One way I thought about is to use the `enter_command` (`C-e`), which currently [does nothing](https://github.com/void-rs/void/blob/f0a9f72ea438e593ddcaa4d5981a51941b5882a6/src/screen.rs#L401-L406) to add properties to entries. These properties could be checked by `C-k` (or any other...

For the "see themselves as `ref`", we could probably reuse the material for the ["Accessing an Actor with Arbitrary Transactions"](https://patterns.ponylang.io/async/access.html#solution), although that requires talking about capabilities, which are not introduced...

@cindRoberta BigInteger and BigDecimal are arbitrary precision integers, so they can be as big as you want as long as you have the memory to spare.