Hey folks, thanks for a pretty bad ass library! I'm seeing a 3-3.3x gain when decoding fairly large JSON payloads (40-50MB) as compared stdlib/json-iterator.

Few things in the generated code that struck me as odd are the allocation sizes for slices/maps:

• Slice is set to size 1 initially, values are appended using append
• Map does not have a default size specified

Instead of this, I

text in the search input in the entity field is unreadable due to lack of contrast, letters are not bright enough to seen

Expected behavior
just a bug fix to make the letters white

Screenshots

**Desktop (please c

Is your feature request related to a problem? Please describe.

No MappedTypeNode definition in ts-morph.
No TypeQueryNode definition in ts-morph.
No TypeOperatorNode definition in ts-morph.

We are reliant primarily on the examples for testing at this point. It would be good to "stress" the allocator because I would be (pleasantly) surprised if it's bug-free.

• More extensive unit testing
• Integration test under tests/ that (for example) uses the max number of registers of a given kind and confirms the register allocator doesn't fall over
• More specifically, handling of "cast

As we're unlikely to ever return to Travis CI, references to Travis are confusing, e.g. the directory containing the CI scripts being called chore/travis and the .travis.yml config file being present. We should remove anything that is no longer necessary, and rename everything else appropriately.

In the process of removing the Travis CI traces, we should also ensure that we've migrated all

Unused imports are included in the headers of generated files causing 2.12 builds with the default -Yfatal-warnings` setting to fail (unless the correct linting options are unset)

Expected behavior

Scrooge generates files with headers including only the imports the current file needs.

Actual behavior

Scrooge generates import statements for classes that are never used.

St