612cd4a4c8d0b1ca68926c0eece1fc35386e5622
It's most (probably all) cases where a static 'default' SecurityImmutable is
used, a Nullable<SecurityImmutable> would more accurately represent the state,
which could likely (probably always) be described as "waiting for my real
security from an asynchronous source."
Bugs (fixed):
* [Race] When Fills window opens, an exception is thrown if the sec-filter's
items are sorted with a 'default' SecurityImmutable.
Cause: The static default SecurityImmutable doesn't have an underlying sec
type (i.e., ContractOneofCase == None). The compare fn doesn't support
this.
TODO (maybe): It might be a good idea to 'fix' the compare fn as well
(i.e., make it support 'None' sec types)
TODO (probably): Remove remaining references to the static default
SecurityImmutable
Languages
C++
54.9%
C#
39.2%
CSS
2.7%
F#
1.3%
Python
0.8%
Other
0.9%