i509VCB

Sure I could send a PR, probably won't be till Friday though.

Doing some work on this, some things that should unlock more parts of the library that can be made const for the future. 1. Lookup tables are `static`, not sure...

> Other `Instruction` methods that could be made `const`: > > * `new` ctor > * setters, so far only the getters have been made `const` (EDIT: apparently not possible...

I've learned of the `clippy::missing_const_for_fn` lint. This could be useful for determining what could be made const.

Not planning on branching out too far, mainly a clarification of certain categories of entities like mobs, animals, hostile mobs, etc.

So I've been thinking up a concept for new package standard: `entity.mob` for all Mobs. These are entities which can control their own movement. `entity.mob.passive` for all passive mobs. Such...

Nothing so far has changed in my idea, we have gotten some new mobs but some are yet to be added yet.

I pretty much have just proposed the idea here, someone else can take on the contributions if they wish.

Save game makes more sense to me than `level` does. I would like to see people look into that further.

Taking a look at vulkano_win, that seems to require SafeBorrow on its input. Seeing from what you said, I probably shouldn't be making the surface own the window. Based on...