John-John Tedro

FWIW: I've now paused efforts to implement an `Entry` api. If anyone else wants to take a stab at it please give it a go! I do have to say...

Go for it! I'd also note that if `unsafe` use leads to a cleaner API which more closely matches std collections it is worth it.

Very neat @pitaj! If you change the feature flag to instead be `#[cfg(fixed_map_unfinished)]` (which prevents implicit use even if part of a release since you explicitly have to `RUSTFLAGS="--cfg fixed_map_unfinished"`...

Interesting. Thanks for the report! I'm not sure how to solve it, but at least I've proposed to expose `checkers::with_muted` in #6. It's not perfect since this is obviously not...

From #6 > I guess one way to do it is to "initialize" the program, clear the global allocator (or mark allocated regions as DONT_CARE or something along those lines),...

1. Yes, even if cranelift support is incorporated it would be done in a manner which allowed for normal Vm execution. 2. Strictly no; Since Rune lacks type annotations in...

I'm gonna have to think this over. It's not a style choice that I would choose, so if I include it I'd like to see the following changes done: *...

> The AnyObj runtime support (just nice to avoid the vtable increase if it's not used but not super important). Actually, no this can't be done. `AnyObjVtable` is public API!...

Don't sweat it! And don't feel like you have to make requested changes immediately. I don't have any plans to change things in Rune for at least a week or...

I'll be back after this weekend and then I'll take a look! Cheers!