WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
Breaking changes
Fix variable initialization checks / revise flow logic (#2578) (6717de0)
Initialization of global variables sometimes wasn't guaranteed before, allowing unsafe behavior if initialization indeed wasn't performed before access. To mitigate, variables from now on require either an initializer, a primitive type with a trivial default value (typically 0), a nullable type (if a reference, defaulting to null) or otherwise annotation with definitive assignment (i.e. let someObject!: ..., then inserting a runtime check upon access).
Other
Speed-up signature lookups, make signatures immutable (#2582) (378659a)