37 lines
1.6 KiB
Plaintext
37 lines
1.6 KiB
Plaintext
------------------------------------------------------------------------
|
|
|
|
- Handle tables with mixed key types, e.g. some strings, some numbers.
|
|
- Right now it crashes trying to sort keys when it can't compare them.
|
|
- Possible approaches:
|
|
- Group keys into sub-tables by type, sort each sub-table, then
|
|
sort the types and recombine sub-tables.
|
|
- Just use a custom comparison function. Performance risk?
|
|
|
|
- JIT Profiling
|
|
|
|
- Support entity definitions?
|
|
- Is this even feasible when we could only display initial_properties
|
|
and can't extract even the freeze/thaw logic that may be necessary
|
|
to handle basic display even?
|
|
- Supposedly these are one of the things we would need to handle "mixed
|
|
key type tables" for, even following MT strict rules.
|
|
|
|
- Try to build "documentation evidence" structure if possible
|
|
- Search all mods for files like LICENSE, README, COPYING, etc.
|
|
https://github.com/licensee/licensee/blob/master/lib/licensee/project_files/license_file.rb
|
|
- Copy those into the output dir if any defs are used
|
|
from the mod in question.
|
|
- Only ever add or update files, never purge old.
|
|
- Include warning in readme that this may not be exhaustive and
|
|
users may need to verify manually.
|
|
|
|
- Document test cases?
|
|
- A space-bending puzzle game
|
|
- Before: 12s load time, 28M media, 1.2G memory used
|
|
- After: 2s load time, 4M media, 611M memory used
|
|
- Can creative-centric games with a "bloaty" reputation like
|
|
dreambuilder be used to make schematics for an efficient game now?
|
|
|
|
------------------------------------------------------------------------
|
|
|