Jacob Lifshay

I would say `try_deref` is a good name, except that implies that you'd return `None`/`Err` if `deref` would fail/panic instead of the actual operation of returning `None` if the initialization...

> #### `&Option` > Since returning `&None` isn't possible in a constant functions this is not the ideal return type. it is totally possible if you use an inline `const`...

> @programmerjake didn't know this worked! However when trying it for mutable references it gives the error: `mutable references are not allowed in the final value of constants` so I'm...

so maybe return `&Option` and `Option` and name the functions something like `flatten_ref_opt` and `flatten_mut`

or have all of: ```rust impl { pub fn flatten_ref(self) -> Option { pub fn flatten_mut(self) -> Option

> ```rust > /// [`io::ErrorKind::AlreadyExists`] should be returned if the `path` already has an object. > pub fn make(&self, f: F) -> Result > where > F: FnMut(&Path) -> Result,...

> Adding or removing a `use` statement cannot modify the bahavior of the program. (Or can it already, for different reasons? I'm not sure.) adding `use` statements can already change...

part of how a fast interpreter is likely implemented is to specifically use function pointers: ```rust #[derive(Copy, Clone)] #[repr(transparent)] struct ProgramPos, _phantom: PhantomData]>, } impl { fn get(self) -> Instruction...

working example of fn ptr based interpreter: https://play.rust-lang.org/?version=stable&mode=release&edition=2021&gist=fad6c3f2c35131012cc811ccdaab5228

other stuff that needs to be changed to TCE: PR title, RFC file's name, feature name