oskgo

> `'unsafe` is shorter than any lifetime The RFC says that `'unsafe` is shorter than any _other_ lifetime. Is `'unsafe` shorter than `'unsafe` or not? This shouldn't have an effect...

I think "trait added method" might be a bit more complicated. The way I see it adding default methods is fine, and even adding non-default methods is fine, so long...

It is possibly to use freeze to build a sound and safe API that can expose secrets. I think this may be an issue because programmers writing safe Rust today...

@digama0 Not just any secrets, but secrets you don't know about and can't currently access with safe code. Rust user should know that UB, or more generally unsoundness, is a...

It's already been mentioned that a non-malicious compiler should do one of four things when freezing unit data, and two of those include getting stale data. I don't expect a...

Just mentioning that I'm running into this when using rust-analyzer even with the toolchain configured in `rust-toolchain`.

The following variant segfaults in the beta: ``` fn f(func: fn()-> None) -> fn() capturing -> None: fn wrapper(): func() return wrapper fn g(): pass def main(): f(g)() ```

@emillma Reproducing this behavior in the playground requires using `print(number)` rather than `print("outer=", number)`

In the beta you can use python imports to use `input` in `*.mojo` files as follows: ``` from python import Python as py def main(): input = py.import_module("builtins").input print(input()) ```...

@lattner Can I help move this issue forward by making a PR with an arbitrary precision integer type, or are you looking for a different path forward?