code-generation

What happened?

The close button should be on top of the text.

What you expected to happen

1. Title should be - 14px bold
2. Commit message box should

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

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

problem: the shadow classes (CtClass reflecting a binary class) built by JavaReflectionTreeBuilder can be modified. This is confusing for users, see INRIA/spoon#4664.

solution: the JavaReflectionTreeBuilder should construct immutable objects, closed to modification, where all setters throw an UnsupportedOperationException

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