Tomasz Kurcz
Tomasz Kurcz
@taiki-e I don't think so. Marking the variable that holds the "wrapper" type with `mut` isn't needed to take advantage of interior mutability. Here's [proof](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=39ca0375a2a298d03ec45313b5cb53df). Note this in particular: ```...
> It's possible to create it like > > ```rust > const THE_ANSWER: U256 = U256([42, 0, 0, 0]); > ``` Ahh, I haven't noticed the field is public. Nice.
Hi! The "concretized generic function pointer as type ID" thing is brilliant. Stealing that for `jtd-derive`. Another approach I suspect you could try is to use those type IDs to...
I figured this would be a great way to dig into proc macros, so I played around with it a bit. Who'd guess I'd have a PoC so soon: https://github.com/uint/serbia...
So I've been looking at implementing this thing: ```rust pub const BUFSIZE: usize = 1024; pub type Buffer = [u8; BUFSIZE]; #[make_big_arrays_work] #[derive(Serialize, Deserialize)] struct S { #[big_array(BUFSIZE)] buffer: Buffer,...
@dtolnay I've been hacking at this. At this point, I think [Serbia](https://github.com/uint/serbia) is pretty usable, but would love feedback.