Michael Lamparski

I should also note that the disassembler Binary Ninja also has SSA forms. So I guess they have use cases for decompilation as well? (anything useful for us?) Anyways, getting...

actually, `interupt[]`s could be a *really big problem* for any attempt to build a CFG.

### Option 1: Add Encoding as context to ToMeta/FromMeta **Advantages:** Changes are generally straightforward to make. **Problems with this solution:** * Big signature changes. ToMeta becomes fallible. ```diff pub trait...

### Option 2: `AnmFile` and similar **Summary** * `compile/decompile` will use `AnmFile` * `write_to_stream/read_from_stream` will use `AnmFile` **Advantages:** * Changes are made almost exclusively to `anm.rs`, `std.rs`, `msg.rs`, and `cli_defs.rs`....

## The solution I tried Personally speaking, I am *also* bothered by the fact that ANM sprite IDs currently get special treatment; they are type-checked and evaluated in a completely...

> The thing is, we can't really do this the same way we've been doing sprite IDs; they can't just be treated as consts because they are offsets that we...

It does the same as `PathInfo::join`. (well, `PathInfo::join` doesn't exist, but I know what you mean) It has been around in my crate since before I started using `path_abs`. It's...

Option 2. The trouble with finding existing examples is that if a library does it right, you don't notice. I opened this thread: https://users.rust-lang.org/t/crates-that-use-the-inherent-trait-method-pattern/30381 > Personally I don't think it...

Yes, granted, the RHS of `join` (and other functions that take relative paths in the crate) could be changed to `AsRef`, and the `str` impl could be removed. It's just...

**Update:** The `Vec` docs now specify a number of tools that let you precisely control the capacity. > `vec![x; n]`, `vec![a, b, c, d]`, and `Vec::with_capacity(n)`, will all produce a...