Jacob Lifshay

> As I've written before, if cast to a data pointer truncates, cast to usize also does, so this doesn't seem to cause any new issues. if a function pointer...

I think we should add `core::ffi::uintfptr` and `core::ffi::intfptr` types (like C's `uintptr_t` and `intptr_t`, except for function pointers) and add a `addr` method to all function pointer types. Then I'd...

> I like this. I see one problem, however. Any crate which provides a container that can be sliced which is not updated will require `&container[(a..b).into()]`. > > This could...

> What is `Wrapper` in this context? Is that a reference to all containers, a specific internal type, or a public type I somehow don't know about? just some user-defined...

when combined with pattern types, what way does the precedence go? so, does `v as i32 is 5` parse as `(v as i32) is 5` or `v as (i32 is...

> If we add `is` as a keyword, we must also **reserve** `isnot` as a keyword for _future_ NOT-patterns I disagree, IMO not patterns can be written as `!Some(_)` (`!`-patterns...

I think we should add: ```rust unsafe impl DynSized for T { // : Sized just to be explicit fn size_of_val(&self) -> usize { core::mem::size_of::() } } ```

> This feature is pretty useless without alignment info. You can't generically box a value without knowing its runtime alignment, for one. actually, I have a proposal that would allow...

> @programmerjake Could you explain how specifically a type would ebd up having an unknown alignment in that? I can't figure out how one would construct such a _type_, even...

another good use case for arbitrary self types that may be worth mentioning in the rfc: ```rust #[derive(Default)] pub struct GCArena { objects: Vec, } impl GCArena { pub fn...